[jira] (MNG-5366) [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
[ https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351953#comment-351953 ] Igor Fedorenko commented on MNG-5366: - This maybe fixed by the new aether I just integrated in maven, but hard to tell for sure without example project or unit test to demonstrate the original problem. [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4 -- Key: MNG-5366 URL: https://jira.codehaus.org/browse/MNG-5366 Project: Maven Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0.4, 3.0.5, 3.1.0, 3.1.1, 3.2.1, 3.2.2 Reporter: Paul Gier Fix For: Issues to be reviewed for 4.x Using Maven 3.0.4, artifacts can only be resolved a single time during the build lifecycle using the Maven 2.x dependency resolution API. Using resolver.resolveAlways() should force re-resolution of the artifact, however if the artifact was already resolved once during the build, then it will not be re-resolved even when calling resolveAlways(). This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5366) [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
[
https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351954#comment-351954
]
Robert Scholte commented on MNG-5366:
-
{{maven-dependency-plugin\src\it\projects\purge-local-repository-reresolve}}
should verify this.
[Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
--
Key: MNG-5366
URL: https://jira.codehaus.org/browse/MNG-5366
Project: Maven
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 3.0.4, 3.0.5, 3.1.0, 3.1.1, 3.2.1, 3.2.2
Reporter: Paul Gier
Fix For: Issues to be reviewed for 4.x
Using Maven 3.0.4, artifacts can only be resolved a single time during the
build lifecycle using the Maven 2.x dependency resolution API. Using
resolver.resolveAlways() should force re-resolution of the artifact, however
if the artifact was already resolved once during the build, then it will not
be re-resolved even when calling resolveAlways().
This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5366) [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
[ https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Friedenhagen updated MNG-5366: Affects Version/s: 3.2.2 3.1.0 3.1.1 3.2.1 [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4 -- Key: MNG-5366 URL: https://jira.codehaus.org/browse/MNG-5366 Project: Maven Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0.4, 3.0.5, 3.1.0, 3.1.1, 3.2.1, 3.2.2 Reporter: Paul Gier Fix For: Issues to be reviewed for 4.x Using Maven 3.0.4, artifacts can only be resolved a single time during the build lifecycle using the Maven 2.x dependency resolution API. Using resolver.resolveAlways() should force re-resolution of the artifact, however if the artifact was already resolved once during the build, then it will not be re-resolved even when calling resolveAlways(). This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5366) [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
[ https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5366: --- Fix Version/s: (was: 3.2) Issues to be reviewed for 4.x [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4 -- Key: MNG-5366 URL: https://jira.codehaus.org/browse/MNG-5366 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0.4, 3.0.5 Reporter: Paul Gier Fix For: Issues to be reviewed for 4.x Using Maven 3.0.4, artifacts can only be resolved a single time during the build lifecycle using the Maven 2.x dependency resolution API. Using resolver.resolveAlways() should force re-resolution of the artifact, however if the artifact was already resolved once during the build, then it will not be re-resolved even when calling resolveAlways(). This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5366) [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
[ https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340242#comment-340242 ] Jason van Zyl commented on MNG-5366: This has been fixed in Aether and when the Aether 1.0 is released we'll absorb the fix. [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4 -- Key: MNG-5366 URL: https://jira.codehaus.org/browse/MNG-5366 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0.4, 3.0.5 Reporter: Paul Gier Fix For: Issues to be reviewed for 4.x Using Maven 3.0.4, artifacts can only be resolved a single time during the build lifecycle using the Maven 2.x dependency resolution API. Using resolver.resolveAlways() should force re-resolution of the artifact, however if the artifact was already resolved once during the build, then it will not be re-resolved even when calling resolveAlways(). This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5366) [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
[ https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338720#comment-338720 ] Robert Scholte commented on MNG-5366: - I've created https://bugs.eclipse.org/bugs/show_bug.cgi?id=425825 [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4 -- Key: MNG-5366 URL: https://jira.codehaus.org/browse/MNG-5366 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0.4, 3.0.5 Reporter: Paul Gier Fix For: 3.2 Using Maven 3.0.4, artifacts can only be resolved a single time during the build lifecycle using the Maven 2.x dependency resolution API. Using resolver.resolveAlways() should force re-resolution of the artifact, however if the artifact was already resolved once during the build, then it will not be re-resolved even when calling resolveAlways(). This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5366) [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
[ https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5366: --- Fix Version/s: (was: 3.1.x) 3.2 [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4 -- Key: MNG-5366 URL: https://jira.codehaus.org/browse/MNG-5366 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0.4, 3.0.5 Reporter: Paul Gier Fix For: 3.2 Using Maven 3.0.4, artifacts can only be resolved a single time during the build lifecycle using the Maven 2.x dependency resolution API. Using resolver.resolveAlways() should force re-resolution of the artifact, however if the artifact was already resolved once during the build, then it will not be re-resolved even when calling resolveAlways(). This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5366) [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
[
https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331875#comment-331875
]
Robert Scholte commented on MNG-5366:
-
I've searched for the code which is responsible for the {{Skipped remote
update check ...}}-message, and it is
{{org.eclipse.aether.internal.impl.DefaultUpdateCheckManager}}
Based on its checks I think we can fix it like this:
{code:title=org.apache.maven.artifact.resolver.DefaultArtifactResolver}
public void resolveAlways( Artifact artifact, ListArtifactRepository
remoteRepositories,
ArtifactRepository localRepository )
throws ArtifactResolutionException, ArtifactNotFoundException
{
DefaultRepositorySystemSession session = new
DefaultRepositorySystemSession( getSession( localRepository ) );
session.setUpdatePolicy( RepositoryPolicy.UPDATE_POLICY_ALWAYS );
resolve( artifact, remoteRepositories, session );
}
{code}
Still need to write a test for it, though.
[Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
--
Key: MNG-5366
URL: https://jira.codehaus.org/browse/MNG-5366
Project: Maven 2 3
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 3.0.4, 3.0.5
Reporter: Paul Gier
Fix For: 3.1.x
Using Maven 3.0.4, artifacts can only be resolved a single time during the
build lifecycle using the Maven 2.x dependency resolution API. Using
resolver.resolveAlways() should force re-resolution of the artifact, however
if the artifact was already resolved once during the build, then it will not
be re-resolved even when calling resolveAlways().
This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5366) [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
[
https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331877#comment-331877
]
Robert Scholte commented on MNG-5366:
-
{code:title=org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(RepositorySystemSession,
UpdateCheckArtifact, ArtifactTransferException)}
if ( isAlreadyUpdated( session.getData(), updateKey ) )
{
if ( logger.isDebugEnabled() )
{
logger.debug( Skipped remote update check for +
check.getItem()
+ , already updated during this session. );
}
check.setRequired( false );
if ( error != null )
{
check.setException( newException( error, artifact, repository )
);
}
}
{code}
The code above is part of Aether. As you can see it doesn't respect the policy.
It simply checks if the {{session.getData()}} contains the {{updateKey}}. This
can't be fixed from the Maven code, so this needs to be fixes at Aether.
[Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
--
Key: MNG-5366
URL: https://jira.codehaus.org/browse/MNG-5366
Project: Maven 2 3
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 3.0.4, 3.0.5
Reporter: Paul Gier
Fix For: 3.1.x
Using Maven 3.0.4, artifacts can only be resolved a single time during the
build lifecycle using the Maven 2.x dependency resolution API. Using
resolver.resolveAlways() should force re-resolution of the artifact, however
if the artifact was already resolved once during the build, then it will not
be re-resolved even when calling resolveAlways().
This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5366) [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
[ https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-5366: --- Affects Version/s: 3.0.5 [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4 -- Key: MNG-5366 URL: https://jira.codehaus.org/browse/MNG-5366 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0.4, 3.0.5 Reporter: Paul Gier Fix For: 3.1.x Using Maven 3.0.4, artifacts can only be resolved a single time during the build lifecycle using the Maven 2.x dependency resolution API. Using resolver.resolveAlways() should force re-resolution of the artifact, however if the artifact was already resolved once during the build, then it will not be re-resolved even when calling resolveAlways(). This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5366) [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
Paul Gier created MNG-5366: -- Summary: [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4 Key: MNG-5366 URL: https://jira.codehaus.org/browse/MNG-5366 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0.4 Reporter: Paul Gier Using Maven 3.0.4, artifacts can only be resolved a single time during the build lifecycle using the Maven 2.x dependency resolution API. Using resolver.resolveAlways() should force re-resolution of the artifact, however if the artifact was already resolved once during the build, then it will not be re-resolved even when calling resolveAlways(). This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5366) [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
[ https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier updated MNG-5366: --- Fix Version/s: 3.1 [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4 -- Key: MNG-5366 URL: https://jira.codehaus.org/browse/MNG-5366 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0.4 Reporter: Paul Gier Fix For: 3.1 Using Maven 3.0.4, artifacts can only be resolved a single time during the build lifecycle using the Maven 2.x dependency resolution API. Using resolver.resolveAlways() should force re-resolution of the artifact, however if the artifact was already resolved once during the build, then it will not be re-resolved even when calling resolveAlways(). This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
