This does not happen in RC3-dev. It only uses plugins that have a plugin JAR in either the installation or cache directory and ignores old expanded directories.
It detects changes in these directories and updates the cache accordingly. - Brett > -----Original Message----- > From: Gilles Dodinet [mailto:[EMAIL PROTECTED] > Sent: Monday, 3 May 2004 3:41 PM > To: Maven Users List > Subject: Re: pom.getPluginContext deprecated > > > Brett Porter wrote: > > >>Besides, I would like to learn more about how maven plugins get > >>resolved (as how maven matches a plugin when 2 versions of the same > >>plugin are installed). > >> > >> > > > >Versionining is not well defined in Maven 1.x. All of the plugin > >installation goals actually remove all previous versions. > > > > real problem is when you manually put (most prolly by > mistake, without > using plugin:install) a new version of a plugin in the > plugins dir : maven will still use the old version unless you > delete the cache files > (deleting the old plugin dir isnot enough). > > -- gd > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
