You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/08/25 01:30:33 UTC
[jira] Closed: (MNG-4745) [regression] Maven does not check for
plugin updates, even if forced via -U
[ http://jira.codehaus.org/browse/MNG-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4745.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-beta-3
Assignee: Benjamin Bentmann
Fixed by [r988749|http://svn.apache.org/viewvc?view=revision&revision=988749].
> [regression] Maven does not check for plugin updates, even if forced via -U
> ---------------------------------------------------------------------------
>
> Key: MNG-4745
> URL: http://jira.codehaus.org/browse/MNG-4745
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 3.0-beta-1
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Priority: Minor
> Fix For: 3.0-beta-3
>
>
> Trying to bring the (currently disabled) IT MavenIT0109ReleaseUpdateTest back into shape revealed an actual issue with the plugin version resolution. Once Maven 3.0-beta-1 resolved a plugin version, it will never ever refetch the corresponding g:a-level metadata (unless completely removed from the local repo).
--
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