- This topic has 4 replies, 3 voices, and was last updated 11 years, 7 months ago by
.
-
Posts
-
Deployment descriptor management policy not working in myeclipse spring.
I have chosen – do not modify application.xml and yet the application.xml is modified on exploded deploy.
MyEclipse for Spring
Version: 10.6.0
Build ID: 10.6.0-20120831cgopalkrish,
Sorry that you are seeing this issue. I could not replicate the issue at my end.
Can you please give us steps in detail that you are following to help us replicate the issue at our end?
Also share the details of the server and version which the project is being deployed to.The server I am deploying to is Weblogic 11g (10.3.5)
I created a web project and then created a seprate enterprise project. Then used the “deployment assembly” dialog to add the war project into ear project. After this I chosed “don’t modify the application.xml” which is not effective. Myeclipse is modifing the application.xml at the time of deployment
cgopalkrish,
Thank you for the steps. I could replicate the issue at my end. I have filed a PR for the dev team to look into it.
Sorry for inconvenience caused.
cgopalkrish,
Deployment Assembly was not fully supported in MyEclipse 10.x and it had it’s limitations. With MyEclipse 2013 we have introduced full support for Deployment Assembly and better handling of applicaiton.xml, which is never rewritten, but updated only if needed (e.g. module addition through DA).
We are currently working on MyEclipse for Spring 2013, so your issue will be fixed with the next release. For now, I would recommend you to not use Deployment Assembly and manage modules through “MyEclipse” -> “Add/Remove modules” context menu of EAR project.
