plugin:download and plugin:install are completely unnecessary.
Say your project "foo" requires this plugin, so you add it to
project.xml for foo as a dependency.
When you run that, it downloads the plugin (if needed), and runs with
it for that project only. It doesn't get permanently installed, but is
always available to that project.
If you later need a newer version, you just change te dependency.
This is only appropriate if it is a plugin only dep.
Cheers,
Brett
On Fri, 10 Dec 2004 09:15:06 -0500, Eric Black <[EMAIL PROTECTED]> wrote:
> If I run 'maven plugin:download' in a project that has the plugin
> dependency but not the plugin source itself, maven asks what plugin I want
> with a prompt for the groupId, artifactId, and version. Maybe I'm missing
> a step that would make the dependency updating easier. This is what I
> understand:
>
> 1. I put a dependency in my project.xml file with a specific version so it
> doesn't get downloaded everytime I build the project like it would with a
> SNAPSHOT version.
> 2. The first time I build, the dependency is downloaded and installed in
> my user's .maven directory
> 3. If there is an updated version in the repository, I need to manually
> run plugin:uninstall in my project directory(not the plugin source
> directory) to invalidate the cache info, then manually delete the plugin
> jars from my user's maven/repository/${groupId}/plugins directory to have
> the dependency plugins downloaded and installed again.
>
> Is this correct or is there an easier way?
>
> Eric
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
