You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2008/10/03 21:11:08 UTC
[jira] Commented: (MINVOKER-70) invoker:install does not properly
handle versioned dependencies
[ http://jira.codehaus.org/browse/MINVOKER-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149825#action_149825 ]
Benjamin Bentmann commented on MINVOKER-70:
-------------------------------------------
Could you give some more details, e.g. the listing of JAR files resolved for your problematic dependency in the staging repo when using plugin version 1.2.1 and 1.3? I currently just don't get enough understanding of the problem from your description to come up with a test or fix.
> 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
>
> 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