Lukas,
I had read that issue, but didn't "get it" until now. I think you're
correct, declaring the plugin as a dependency causes it to be installed
into the local repo, and expanded into the cache, but not installed into
the maven plugins directory.
Arnauds statement that "It forces the developers to use THIS release of
the plugin for the project" is of course still correct.
Quite a nice feature really.
Doug
Lukas Theussl wrote:
Are you sure on this? I thought declaring a plugin dependency lets your
project depend on a particular version of a plugin without actually
installing it - so you can use that plugin on the fly without messing up
your (and every developer's) Maven installation.
There is actually a documentation issue open for this [1], would be nice
if we could clarify this before ;)
-Lukas
[1] http://jira.codehaus.org/browse/MAVEN-1478
Arnaud HERITIER wrote:
The plugin is automatically downloaded and installed instead of to ask
to the other developpers to manually install it.
It forces the developpers to use THIS release of the plugin for the
project.
Arnaud
On 2/9/06, Matteo Melani <[EMAIL PROTECTED]> wrote:
Hello,
what is the benefit of including in the project.xml file a dependency
to a plugin? (Besides telling other developers that the build depends on
the plugin)
For example let say that I include in my project.xml:
<dependency>
<groupId>codeczar-tomcat</group>
<artifactId>maven-tomcat-plugin</artifactId>
<type>plugin</type>
<version>1.1</version>
</dependency>
When I run Maven it downloads the .jar file for the plugin in the
repository plugin directory. And then?
I guess I do not understand the purpose if it.
Anybody can explain this feature?
Thanks,
-Matteo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
