You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Juan Ignacio Garzón (JIRA)" <ji...@codehaus.org> on 2008/10/19 05:52:19 UTC
[jira] Commented: (MECLIPSE-466) application.xml generated
incorrectly for 3rd party ejb modules
[ http://jira.codehaus.org/browse/MECLIPSE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151263#action_151263 ]
Juan Ignacio Garzón commented on MECLIPSE-466:
----------------------------------------------
Im having the same problem here.
It looks like that maven-eclipse-plugin generated application.xml uses the "projectNameTemplate" configuration value to generate the 3rd party libraries filename.
For example, I have this value configurated:
<projectNameTemplate>myProjectName-[artifactId]-[version]</projectNameTemplate>
and the eclipse generated application.xml has a module named:
<module id="EjbModule_9114403">
<ejb>myProjectName-jboss-seam-2.0.2.GA.jar</ejb>
</module>
of course, when I deploy the ear through WTP if fails because the file is named jboss-seam-2.0.2.GA.jar
Even if i set the "bundleFileName" for that module in the maven-ear-plugin configuration, the generated name is the same.
Hope this helps!
> 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
> Fix For: 2.6
>
> 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