You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Robrecht Anrijs (JIRA)" <ji...@codehaus.org> on 2011/07/12 08:41: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=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