[
http://jira.codehaus.org/browse/MINVOKER-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150235#action_150235
]
Jared Roberts commented on MINVOKER-70:
---------------------------------------
A work around that I've found is to use the instructions [1] for improving
build speed by including a custom settings.xml file. The local repository is
then set up as a remote repository for the forked build and the required
artifacts are resolved.
[1] http://maven.apache.org/plugins/maven-invoker-plugin/examples/fast-use.html
> invoker:install does not properly handle versioned dependencies
> ---------------------------------------------------------------
>
> Key: MINVOKER-70
> URL: http://jira.codehaus.org/browse/MINVOKER-70
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Jared Roberts
> Priority: Critical
> Attachments: MINVOKER-70-Example.zip
>
>
> The fix for MINVOKER-64 introduced a regression. Previously, only the
> artifact under test was installed to the IT local repository. The other
> dependencies were then resolved from remote repositories. In 1.3, the other
> dependencies are pulled from the actual local repository. It appears that the
> resolution of uniquely versioned dependencies is different in the two flows
> because the 1.2.1 flow downloaded both the uniquely versioned jar and the
> non-unique jar but the 1.3 flow only installs the uniquely versioned jar. My
> build now fails because it cannot find the non-uniquely versioned jar to run
> my integration tests.
--
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
