You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Siarhei Dudzin (JIRA)" <ji...@codehaus.org> on 2008/07/16 22:45:26 UTC
[jira] Created: (MECLIPSE-466) application.xml generated
incorrectly for 3rd party ejb modules
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
[jira] Updated: (MECLIPSE-466) application.xml generated
incorrectly for 3rd party ejb modules
Posted by "Barrie Treloar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barrie Treloar updated MECLIPSE-466:
------------------------------------
Fix Version/s: (was: 2.6)
2.7
> 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
> Components: WTP support
> Affects Versions: 2.5.1
> Reporter: Siarhei Dudzin
> Fix For: 2.7
>
> 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
[jira] Closed: (MECLIPSE-466) application.xml generated incorrectly
for 3rd party ejb modules
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MECLIPSE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MECLIPSE-466.
-----------------------------------
Resolution: Duplicate
Fix Version/s: (was: 2.9)
> application.xml generated incorrectly for 3rd party ejb modules
> ---------------------------------------------------------------
>
> Key: MECLIPSE-466
> URL: https://jira.codehaus.org/browse/MECLIPSE-466
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: WTP support
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-466) application.xml generated
incorrectly for 3rd party ejb modules
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MECLIPSE-466:
-------------------------------------
Fix Version/s: 2.5.2
> 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.5.2
>
> 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
[jira] Updated: (MECLIPSE-466) application.xml generated
incorrectly for 3rd party ejb modules
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MECLIPSE-466:
-------------------------------------
Component/s: WTP support
> 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
> Components: WTP support
> 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
[jira] Commented: (MECLIPSE-466) application.xml generated
incorrectly for 3rd party ejb modules
Posted by "Juan Ignacio Garzón (JIRA)" <ji...@codehaus.org>.
[ 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