You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jared Roberts (JIRA)" <ji...@codehaus.org> on 2008/10/03 17:46:08 UTC
[jira] Created: (MINVOKER-70) invoker:install does not properly
handle versioned dependencies
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
[jira] Commented: (MINVOKER-70) invoker:install does not properly
handle versioned dependencies
Posted by "Jared Roberts (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MINVOKER-70) invoker:install does not properly
handle versioned dependencies
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MINVOKER-70) invoker:install does not properly
handle versioned dependencies
Posted by "Jared Roberts (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MINVOKER-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jared Roberts updated MINVOKER-70:
----------------------------------
Attachment: MINVOKER-70-Example.zip
The problem is that no "maven-metadata-local.xml" exists when a dependency of the main project is downloaded from the remote repository. This file is inserted into the local repo when the project is deployed. I'm attaching a couple of test projects to illustrate what I'm seeing.
These are the steps to recreate the problem:
1) Deploy project "bar"
2) Clear your local repository
3) Verify project "foo"
> 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
[jira] Closed: (MINVOKER-70) invoker:install does not properly
handle versioned dependencies
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MINVOKER-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MINVOKER-70.
-------------------------------------
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 1.4
Fixed in [r706426|http://svn.apache.org/viewvc?view=rev&revision=706426], snapshot deployed.
Jared, thanks for the test! The problem was that the plugin installed snapshot artifacts with the timestamped version instead of just "*-SNAPSHOT" as required for local repos.
> 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
> Assignee: Benjamin Bentmann
> Priority: Critical
> Fix For: 1.4
>
> 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