[Sandeep]

Am using 2015 Stable 3.0.. Build Id 13.0.0-21060113
OS=MacOSX, OS version=10.10.2, OS arch=x86_64

I have a main RESTAPI (war) project, which depends on multiple projects(Jars) in the workspace.
If I do an exploded deployment of the war in tomcat and the Maven Deployment Assembly, it deploys all transitive dependencies also as exploded artifacts.
In the 2014 version it used to deploy ONLY the projects explicitly specified as dependencies.

Some of the transitive dependencies have duplicate resource names(e.g. persistence.xml used in JPA) and they all go to the same location … e.g. classes/META-INF/

So Project A gets deployed first
And then when project B gets deployed, its persistence.xml

overwrites

the Project A’s file.
Problem: Exploded Deployment of transitive dependencies causes artifacts to overwrite each other.

I cannot find any option to turn off this exploded deployment 🙁

In 2014, if I really wanted to debug, I could add the Project A as a dependency or add the source files to the JAR as a source. Now, with all this automatic explosion, it is just not working.
And I have to deploy the war as assembled. And i cannot do hot deploys anymore.

[support-swapna]

Sandeep,

You can turn off merged(exploded) deployment for individual modules from the war project’s Deployment Assembly page (right click on the main project > Properties > MyEclipse > Deployment Assembly)

For more information about module level merged deployment settings, please refer to section 7. Hot-Sync for Web Projects in the tutorial here : https://www.genuitec.com/products/myeclipse/learning-center/basics/myeclipse-deployment-assembly/

If you do not want any of the modules to be merged during deployment, you can disable the ‘Enable merged deployment of Utility and EJB modules’ setting in the Merged deployment of modules section.

Hope this helps. Let us know how it works for you.

–Swapna
MyEclipse Support

[Author]

Posts