whats this directory for? <maven_local_home>\repository\maven\plugins
what seemed to be happening is that I had a plugin defined as a dependency for a project, this dependency existed in the repo under <artifactId>/plugins/asdfasdf.jar
I'd run plugin:install on the updated plugin which would copy the new plugin to both
<maven_local_home>\repository\maven\plugins and <maven_home>\plugins
when I'd execute a goal on the target, the old plugin would somehow get executed.
I've sorted the problem for now by deleting every old copy of the plugin I can find and all dependencies to the plugin. Relying on the plugins executing as installed plugins rather than dependency plugins.
I thought the preferred mechanism now is to declare dependencies to plugins, this is a bit clunky if you're developing plugins as there's no easy method to get the plugin to the repository and simultaneously delete installed copies of the plugin.
I think in short, don't use plugin dependencies if you're developing a plugin and want to test it. Use plugin:install to see your changes. Once the plugin is ready for prime time release the plugin to a remote repo and allow people to use plugin dependencies.
still cofused, but it seems to work now :)
thanks
Brett Porter wrote:
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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
