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:17:58 UTC
[jira] Created: (MECLIPSE-430) Non-project EJB dependencies should
not be placed in the .modulemaps file
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
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
[jira] Updated: (MECLIPSE-430) Non-project EJB dependencies should
not be placed in the .modulemaps file
Posted by "Michael Johns (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Johns updated MECLIPSE-430:
-----------------------------------
Attachment: MECLIPSE-430.2.patch
A byproduct of solving the problem presented in this issue is that we can no longer look in the .modulemaps file to find the ID for artifacts in the application.xml file. This causes the findModuleInApplicationXml() to not find elements that it should find.
The attached path (MECLIPSE-430.2.patch) solves the problem, but it very well may not be the correct solution. I'm just posting it for reference. It works fine for our environment, but it probably needs to take into account differences in artifact naming, versioning, etc when parsing the strings. I am just attaching it to get the discussion started and to make sure that this particular byproduct is not overlooked.
> 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.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 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-430) Non-project EJB dependencies should
not be placed in the .modulemaps file
Posted by "Michael Johns (JIRA)" <ji...@codehaus.org>.
[ 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