[
http://jira.codehaus.org/browse/MECLIPSE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Johns updated MECLIPSE-430:
-----------------------------------
Attachment: MECLIPSE-430.patch
You can of course ignore the C2PA comments. Those are there so I know where
I've altered the core release of the plugin.
> Non-project EJB dependencies should not be placed in the .modulemaps file
> -------------------------------------------------------------------------
>
> Key: MECLIPSE-430
> URL: http://jira.codehaus.org/browse/MECLIPSE-430
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: RAD support
> Affects Versions: 2.5.1
> Reporter: Michael Johns
> Attachments: 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 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
