You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Maarten Billemont (JIRA)" <ji...@codehaus.org> on 2009/11/19 11:39:55 UTC
[jira] Commented: (MECLIPSE-619) Bundle artifact .classpath
generation skipped when jboss-sar-type artifacts in reactor
[ http://jira.codehaus.org/browse/MECLIPSE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198701#action_198701 ]
Maarten Billemont commented on MECLIPSE-619:
--------------------------------------------
FWIW, I just verified this issue also exists in 2.7
> Bundle artifact .classpath generation skipped when jboss-sar-type artifacts in reactor
> --------------------------------------------------------------------------------------
>
> Key: MECLIPSE-619
> URL: http://jira.codehaus.org/browse/MECLIPSE-619
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path (.classpath)
> Affects Versions: 2.5.1
> Reporter: Maarten Billemont
>
> Whenever I combine an artifact to the reactor of type bundle and jboss-sar, the bundle artifact does not have its .classpath file generated. I expect the jboss-packaging-maven-plugin breaks something that maven-eclipse-plugin relies on.
> The two artifacts have no dependency on each other. I can reproduce this with:
> {{{
> rm -rf my-bundle-artifact/.{classpath,project,settings}; mvn -pl my-sar-artifact,my-bundle-artifact eclipse:eclipse; ls my-bundle-artifact/.classpath
> }}}
--
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