[
https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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, List<ArtifactRepository>
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
