[ 
https://jira.codehaus.org/browse/MECLIPSE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MECLIPSE-430.
-----------------------------------

    Resolution: Won't Fix

Please refer to 
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
 if you're wondering why this issue was closed out.

> Non-project EJB dependencies should not be placed in the .modulemaps file
> -------------------------------------------------------------------------
>
>                 Key: MECLIPSE-430
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-430
>             Project: Maven Eclipse Plugin
>          Issue Type: Bug
>          Components: RAD support
>    Affects Versions: 2.5.1
>            Reporter: Michael Johns
>         Attachments: MECLIPSE-430.2.patch, MECLIPSE-430.patch
>
>
> If I have an ear project that depends on an ejb artifact that was previously 
> built (ie, it's not another project in my multi-module pom), the plugin 
> should _not_ put an entry for that artifact in the .modulemaps file.  It 
> _should_ (and currently does) put an entry in application.xml.
> If there is an entry in .modulemaps, RAD gets confused and displays the 
> following error:
>  IWAE0027W The project OPFCommonServices for module or utility JAR 
> OPFCommonServices.jar in enterprise application project BP does not exist in 
> the workspace.
> In this case, OPFCommonServices.jar is an artifact that was built previously 
> but is an EJB library in my enterprise application.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to