[
https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=331877#comment-331877
]
Robert Scholte commented on MNG-5366:
-------------------------------------
{code:title=org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(RepositorySystemSession,
UpdateCheck<Artifact, 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
