You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Matteo Melani <ma...@slac.stanford.edu> on 2006/02/09 00:27:11 UTC
Plugin dependency in project.xml file
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Plugin dependency in project.xml file
Posted by Lukas Theussl <lt...@apache.org>.
Matteo Melani wrote:
> Let's see if I get it:
>
> I use plugin X and Y for building my project therefore I put 2
> dependencies in the project.xml.
>
> Now when other developers check out the code and run Maven the *.jar
> file of the plugins get downloaded in the repository.
Right.
> Now the developers have to install the plugin manually right?
> (how do they do that?)
No, that's exactly the point: the developers do NOT have to install the
plugins manually. Maven will use the downloaded jars to build the
project, independently of which plugin version each developer has installed.
> What if the developers have a different version of a plugin installed?
They will not be touched.
-Lukas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Plugin dependency in project.xml file
Posted by Matteo Melani <ma...@slac.stanford.edu>.
Let's see if I get it:
I use plugin X and Y for building my project therefore I put 2
dependencies in the project.xml.
Now when other developers check out the code and run Maven the *.jar
file of the plugins get downloaded in the repository.
Now the developers have to install the plugin manually right?
(how do they do that?)
What if the developers have a different version of a plugin installed?
-Matteo
Doug Douglass wrote:
> 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 <ma...@slac.stanford.edu> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Plugin dependency in project.xml file
Posted by Doug Douglass <dd...@denverdata.com>.
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 <ma...@slac.stanford.edu> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Plugin dependency in project.xml file
Posted by Lukas Theussl <lt...@apache.org>.
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 <ma...@slac.stanford.edu> 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: users-unsubscribe@maven.apache.org
>>For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Plugin dependency in project.xml file
Posted by Arnaud HERITIER <ah...@gmail.com>.
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 <ma...@slac.stanford.edu> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org