You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Arnaud Heritier (JIRA)" <ji...@codehaus.org> on 2007/11/30 05:00:57 UTC
[jira] Updated: (MECLIPSE-322) Depdendency with scope
'integration-test' is NOT resolved via reactor
[ http://jira.codehaus.org/browse/MECLIPSE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MECLIPSE-322:
-------------------------------------
Component/s: Dependencies resolution and build path
> Depdendency with scope 'integration-test' is NOT resolved via reactor
> ---------------------------------------------------------------------
>
> Key: MECLIPSE-322
> URL: http://jira.codehaus.org/browse/MECLIPSE-322
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Dependencies resolution and build path
> Reporter: Jörg Hohwiller
>
> When I define a dependency on one of my own modules with scope integration-test then the eclipse plugin fails if that artifact is not already installed to the local repository even though that module was in the reactor of the build when eclipse:eclipse was called.
> Why does the scope matter for eclipse:eclipse at all?
--
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