[Tom McCobb]

This is a maven project, and the pom.xml specifies all the appropriate dependencies and locates certain third party jars in a /lib directory. It ran fine in ME10.7.

In MEPro2014, the Deployment assembly is adding a lot of unwanted jars into the root of the EAR. If i go to the Deployment Assembly definition screen and remove the unwanted jars, my changes are not saved and the deployment of the EAR still has all the junk I don’t want. The Deployment Assembly screen still has all the jars I removed when I go back to it.

Also, I notice that doing an exploded deployement of the EAR no longer explodes the ejb and war modules; they are packaged as archives. Did this change also in 2014?

[Tom McCobb]

Looks like it was a permissions problem on the file system and changes were not getting saved. Once that was resolved this went away.

Would still like to know about exploded deployment though.

[support-swapna]

tmccobb,

The deployment engine was modified from MyEclipse 10 to MyEclipse 2014 but the behavior in terms of deployment remains almost the same as we now have the Deployment Assembly.

Since it is a Maven project, please make sure that in Deployment Assembly of the EAR, project dependencies are added as projects and not as jars from local Maven Repository.

If the modules are still being packaged as archives, please send us all the .* files (.classpath,.settings,.project etc) and the POM.xmls to help us investigate the issue at our end.

Let us know how it works for you.

[Tom McCobb]

That did it; changing the Deployment Assembly to include the projects instead of the archives.

[support-tony]

tmccobb,

Thanks for letting us know. I’m glad that’s working for you now.

[Author]

Posts