[
http://jira.codehaus.org/browse/MINVOKER-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MINVOKER-37:
--------------------------------------
Attachment: MINVOKER-37.zip
Here's a mini multi-module project that suffers from this. Real-life examples
are JXR, Enforcer and Plugin Plugin.
> Stage Reactor Contents to IT Repo
> ---------------------------------
>
> Key: MINVOKER-37
> URL: http://jira.codehaus.org/browse/MINVOKER-37
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
> Affects Versions: 1.2
> Reporter: Benjamin Bentmann
> Attachments: MINVOKER-37.zip
>
>
> The new install feature added by MINVOKER-22 is a good start but not enough:
> Testing a multi module project that has never been built before will fail
> because of:
> # missing parent POMs
> # missing module JARs
> As for 1.), {{RepositoryTool.installLocallyReachableAncestorPoms()}} from the
> maven-plugin-testing-tools seems just like what we need (anything that is not
> locally reachable must already reside in some repo and is as such available
> to the forked build, too).
> As for 2.), simplying installing all transitive dependencies of the project
> under test should do.
--
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
