You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Johns (JIRA)" <ji...@codehaus.org> on 2008/04/11 19:29:58 UTC
[jira] Created: (MECLIPSE-431) Non-project EJB dependencies need a
version number in application.xml
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
Affects Versions: 2.5.1
Reporter: Michael Johns
Attachments: MECLIPSE-431.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
[jira] Updated: (MECLIPSE-431) Non-project EJB dependencies need a
version number in application.xml
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MECLIPSE-431:
-------------------------------------
Component/s: RAD support
> 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: RAD support, WTP support
> Affects Versions: 2.5.1
> Reporter: Michael Johns
> Attachments: MECLIPSE-431.2.patch, MECLIPSE-431.patch, MECLIPSE_431.3.patch, MECLIPSE_431.4.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
[jira] Commented: (MECLIPSE-431) Non-project EJB dependencies need
a version number in application.xml
Posted by "Robrecht Anrijs (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MECLIPSE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272992#comment-272992 ]
Robrecht Anrijs commented on MECLIPSE-431:
------------------------------------------
patch MECLIPSE_431.4 and MECLIPSE_431.3 are working. I was wondering when these bugs are being fixed in the plugin. Is this plugin end of life?
> Non-project EJB dependencies need a version number in application.xml
> ---------------------------------------------------------------------
>
> Key: MECLIPSE-431
> URL: https://jira.codehaus.org/browse/MECLIPSE-431
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: RAD support, WTP support
> Affects Versions: 2.5.1
> Reporter: Michael Johns
> Attachments: MECLIPSE-431.2.patch, MECLIPSE_431.3.patch, MECLIPSE_431.4.patch, MECLIPSE-431.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-431) Non-project EJB dependencies need
a version number in application.xml
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MECLIPSE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275192#comment-275192 ]
Robert Scholte commented on MECLIPSE-431:
-----------------------------------------
I'm willing to apply these patches, but I'm missing an integration test to verify it (for now and for ever to prevent regression). Would be great if someone could provide one.
See https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/it/ for some examples. These are just mini maven projects hitting the problem.
> Non-project EJB dependencies need a version number in application.xml
> ---------------------------------------------------------------------
>
> Key: MECLIPSE-431
> URL: https://jira.codehaus.org/browse/MECLIPSE-431
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: RAD support, WTP support
> Affects Versions: 2.5.1
> Reporter: Michael Johns
> Attachments: MECLIPSE-431.2.patch, MECLIPSE_431.3.patch, MECLIPSE_431.4.patch, MECLIPSE-431.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-431) Non-project EJB dependencies need a
version number in application.xml
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MECLIPSE-431:
-------------------------------------
Component/s: WTP support
> 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.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
[jira] Updated: (MECLIPSE-431) Non-project EJB dependencies need a
version number in application.xml
Posted by "Dan Sullivan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Sullivan updated MECLIPSE-431:
----------------------------------
Attachment: MECLIPSE-431.2.patch
The same problem exists for the EclipseWtpApplicationXMLWriter as for the RadApplicationXMLWriter.
> 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
>
>
> 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
[jira] Updated: (MECLIPSE-431) Non-project EJB dependencies need a
version number in application.xml
Posted by "Elmar Bomberg (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MECLIPSE-431) Non-project EJB dependencies need a
version number in application.xml
Posted by "Elmar Bomberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elmar Bomberg updated MECLIPSE-431:
-----------------------------------
Attachment: MECLIPSE_431.4.patch
I also corrected the RadApplicationXMLWriter with Patch MECLIPSE_431.4.
> 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, MECLIPSE_431.4.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