[
http://jira.codehaus.org/browse/MVERSIONS-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Folga updated MVERSIONS-45:
-------------------------------
Attachment: use-latest-versions-patch2.txt
Hi,
I came across the same issue but I think that you need to change two likes to
fix it properly.
The patch above fixes a call to versions.getNewerVersions where instead of
allowSnapshots false was passed.
I found that there is another issue here.
The line:
ArtifactVersions versions = getHelper().lookupArtifactVersions( artifact,
Boolean.TRUE.equals( allowSnapshots ) );
is wrong as lookupArtifactVersions expects usePluginRepositories not
allowSnapshots
public ArtifactVersions lookupArtifactVersions( Artifact artifact, boolean
usePluginRepositories )
Please find my patch attached that also includes previous patch.
> use-latest-versio ignores the allowSnapshots bug
> ------------------------------------------------
>
> Key: MVERSIONS-45
> URL: http://jira.codehaus.org/browse/MVERSIONS-45
> Project: Maven 2.x Versions Plugin
> Issue Type: Bug
> Affects Versions: 1.0-alpha-3
> Reporter: Martin Franklin
> Fix For: 1.0-beta-1
>
> Attachments: use-latest-bug-no-snapshots.patch,
> use-latest-versions-patch2.txt
>
>
> using the command -DallowSnapshots with display-dependency-updates with a
> dependency for which there is a newer snapshot dependency will display the
> snapshot - however using the command use-lastest-versions will not cause the
> pom file to be updated. Incorrect parameter sent to versions.getNewerVersiosn
> in useLatestversionsMojo
> Patch is supplied
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
