[ http://jira.codehaus.org/browse/MNG-379?page=comments#action_41295 ]
John Casey commented on MNG-379: -------------------------------- What is the required logic for merging global and user plugin update policies? I've rethought about this, and I'm going to do a shallow merge for now - that is, add from the global if the user-level update isn't present...otherwise, ignore the global version. I'm not sure this is good for situations where you're trying to maintain a homogenous maven build across multiple developers on a single server/network sharing the same globals. In this case, it makes more sense to make the globals authoritative (though maybe not for the entirety of the global settings.xml), since one developer who uses a different plugin version than the rest could lead to a broken build. Perhaps we need to add some sort of mergeAdvice to the pluginUpdate, to give a hint on how to merge the globals and the user-level?? > 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]
