The local repository plays no part in plugin installation. The only
directories that count for actual installation are ${maven.home}/plugins
(installed) and ${maven.home.local}/plugins (extracted). Note that these can
be overriden with other properites, but that's beside the point here.
The new structure just gives a location in the repository for maven
plugin:download and plugin dependency elements to find the plugins, and
install them to ${maven.home}/plugins.
Does this clear it up?
> -----Original Message-----
> From: Nathan Coast [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 1 October 2003 2:01 PM
> To: Maven Dev
> Subject: I'm confused - plugin installation dirs
>
>
> AFAICT there are 3 directories that plugins can end up in
>
> <maven_local_home>\repository\groupId\plugins
>
> <maven_local_home>\repository\maven\plugins
>
> <maven_home>\plugins
>
> they are then extracted to
>
> <maven_local_home>\plugins
>
> executing plugin:install results in this output:
>
> jar:jar:
> [copy] Copying 1 file to
> D:\apache\maven\local\repository\maven\plugins
> plugin:install:
> [copy] Copying 1 file to D:\apache\maven\plugins
>
> so the plugin gets copied to two dirs!
>
> can someone explain which plugins should go where with the new
> plugins-as-artifacts model? I'm having difficulty understanding what
> happens when a plugin is defined as a dependency. If the
> plugin exists
> in multiple places which one takes precedence and why?
>
> just spent a couple of hours trying to work out why old versions of
> plugins were being executed after I'd run plugin:install with newer
> versions.
>
> thanks
> Nathan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
