You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elmar Bomberg (JIRA)" <ji...@codehaus.org> on 2009/03/03 22:17:12 UTC
[jira] Updated: (MECLIPSE-431) Non-project EJB dependencies need a
version number in application.xml
[ http://jira.codehaus.org/browse/MECLIPSE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elmar Bomberg updated MECLIPSE-431:
-----------------------------------
Attachment: MECLIPSE_431.3.patch
The patch MECLIPSE_431.2 does not work in all cases. In our application.xml the version-number was resolved as timestamp-version. But the name of the referenced jar was xxx-SNAPSHOT. I would suggest the patch MECLIPSE_431.3.
This patch uses (dependency.getFile().getName()) instead of ("dependency.getArtifactId() + "-" + dependency.getVersion() + ".jar")
> Non-project EJB dependencies need a version number in application.xml
> ---------------------------------------------------------------------
>
> Key: MECLIPSE-431
> URL: http://jira.codehaus.org/browse/MECLIPSE-431
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: WTP support
> Affects Versions: 2.5.1
> Reporter: Michael Johns
> Attachments: MECLIPSE-431.2.patch, MECLIPSE-431.patch, MECLIPSE_431.3.patch
>
>
> This relates to issue MECLIPSE-430. When including EJBs that were built previously (ie, not part of the same multi-module project as the ear), the application.xml needs to include their version number.
--
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