Nathan Coast <[EMAIL PROTECTED]> wrote on 01/10/2003 02:25:10 PM: > whats this directory for? > <maven_local_home>\repository\maven\plugins
Extracted installed 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 'Dependent' plugins will be installed each time the project runs. The version in the dependencies will be used regardless of other installed plugins. > 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. See above. > 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. This is the preferred method. [snip] > 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. Definitely. Plugin dependencies are only where a project may ship and need plugins it wont distribute with it, and can guarantee it requires that exact version. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
