application.xml generated incorrectly for 3rd party ejb modules
---------------------------------------------------------------
Key: MECLIPSE-466
URL: http://jira.codehaus.org/browse/MECLIPSE-466
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Affects Versions: 2.5.1
Reporter: Siarhei Dudzin
Attachments: test-project.tar.gz
As you may know by default the project version is not added to the project
name. In case I have 3rd party ejb modules from a maven repository (jboss seam
for example) the version number for those modules is removed from the generated
application.xml as well which breaks the WTP deployment: the server can't find
the 3rd party ejb jar because it expects the jar also be without the version
number.
Looks like during generation of application.xml there is no distinction made
between dependencies from projects and libraries.
I included a test case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
