[
http://jira.codehaus.org/browse/MNG-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115130
]
Samuel Le Berrigaud commented on MNG-3023:
------------------------------------------
This sounds like a critical issue to me. It is _impossible_ to work with
multi-module projects if dependencies resolution goes to the repositories
instead of the reactor. An good example of this is working with the release
plugin (version 2.0-beta-7 IIRC):
1. I do a clean checkout on a build server,
2. I run mvn release:prepare
And as release:prepare relies on the @requiresDependencyResolution, it fails
because the SNAPSHOT is not installed locally.
> Reactor projects should be included in dependency resolution
> ------------------------------------------------------------
>
> Key: MNG-3023
> URL: http://jira.codehaus.org/browse/MNG-3023
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.7
> Reporter: Mark Hobson
> Fix For: Reviewed Pending Version Assignment
>
> Attachments: patch.txt
>
>
> Dependency resolution for mojos with @requiresDependencyResolution should
> include the projects within the reactor. See attached it0122 for an example
> (numbered as such due to MNG-2994's it0121).
--
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
