[ http://jira.codehaus.org/browse/MNG-379?page=comments#action_41311 ]
John Casey commented on MNG-379: -------------------------------- I've got the settings model modified to support this, I think. It builds, and I've checked it in. I'm working on modification of the plugin version resolution stuff in the plugin manager - it'll call out to a PluginVersionManager eventually, which will incorporate the algorithm for searching for a plugin's version in the pom, then settings, then resolving RELEASE and rewriting the user settings with the resolved version. Separating this into a different manager will make it easy to incorporate update policies and auto-update vs. prompt policies. I'll probably have this finished tomorrow. > more control over plugin updates > -------------------------------- > > Key: MNG-379 > URL: http://jira.codehaus.org/browse/MNG-379 > Project: Maven 2 > Type: Improvement > Reporter: Brett Porter > Assignee: John Casey > Fix For: 2.0-alpha-3 > > > currently, plugin updates are checked daily (or whatever the plugin > repository's snapshot policy is), and new versions downloaded automatically. > The user needs more control: > - prompting for updates > - ability to stick to a particular version > - ability to check on different intervals than snapshots (probably default to > never, and use a --update-plugins clie or something) -- 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, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
