You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2011/08/07 13:46:42 UTC

[jira] Commented: (MECLIPSE-431) Non-project EJB dependencies need a version number in application.xml

    [ 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