Hi All, When I was trying to do a workaround with http://jira.jboss.org/jira/browse/JBIDE-1862 (actually seems to be WTP 2.0.2bug) it appears that maven-eclipse-plugin ignores application.xml that is generated by maven ear plugin. While this might be ok with WTP 2.0.2 you will have a problem if you use a ejb module as a jar (not in a project in the workspace) it adds the module anyway and ignores the JEE5 spec _and_ the EAR plugin settings which allow to specify modules and eventually exclude them.
While it is possible to specify in maven-eclipse-plugin config a setting to use a hardcoded application.xml there are still 2 problems: 1. maven-ear-plugin already has the same setting, isn't it better to read it's settings? 2. If you choose to generate application.xml the plugin will put all modules in the application.xml (it does not check the JEE version) thus ignoring the JEE5 spec _and_ ear-plugin settings anyway. As soon as more users will upgrade their eclipse version lots of projects wont hot-deploy via WTP anymore... Your thoughts? Regards, Siarhei
