You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mirko Friedenhagen <mf...@gmail.com> on 2013/07/04 00:06:52 UTC
Problems setting up a custom package type II - plugin/mojo versions
in components.xml
Hello everyone,
now I am getting greedy :-). I see that you may specify versions for
the goals being executed during phases in components.xml for custom
package types.
Is there a way to convince the versions-maven-plugin etc. to update
these versions as well?
Or. where are the versions for the plugins in components taken from?
Regards Mirko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Problems setting up a custom package type II - plugin/mojo
versions in components.xml
Posted by Vincent Latombe <vi...@gmail.com>.
I'm not sure I got everything that you've said, but that looks right.
Vincent
2013/7/4 Mirko Friedenhagen <mf...@gmail.com>:
> Hello Vincent,
>
> thanks for your answer. Just so I get this right: I am looking at my
> IT-pom [1] and it has no parent defined. I am running Apache Maven
> 3.0.5. In my output I *do not* see the plugin-versions defined in the
> super POM from Maven-core (this are the ones defined in
> default-bindings.xml[2], right?) but newer ones as they are defined in
> the parent-pom of the plugin/extension project.
>
> * Say I have an extension (should be almost the same with a plugin)
> with version 2.13 of surefire in the pluginManagement of it's POM.
> * I include this extension in a parent pom PP and define 2.14.1 in the
> pluginManagement section.
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.14.1</version>
> </plugin>
> </plugins>
> </pluginManagement>
> <extensions>
> <extension>
> <groupId>g</groupId>
> <artifact>a</artifactId>
> <version>1.0</version>
> </extension>
> </extensions>
> </build>
> * In project A inheriting this parent pom I define 2.15 as version.
> * Now should I expect the run of 2.15 for A, 2.14.1 for projects just
> having PP as parent and all projects not using the PP but the
> extension to use 2.13, right?
>
>
>
>
> [1] https://github.com/mfriedenhagen/foss-jar-maven-plugin/blob/master/src/it/test-foss-jar/pom.xml
> [2] https://github.com/apache/maven/blob/master/maven-core/src/main/resources/META-INF/plexus/default-bindings.xml
> Regards Mirko
> --
> http://illegalstateexception.blogspot.com/
> https://github.com/mfriedenhagen/
> https://bitbucket.org/mfriedenhagen/
>
>
> On Thu, Jul 4, 2013 at 8:33 AM, Vincent Latombe
> <vi...@gmail.com> wrote:
>> These are taken from the parent pom (super POM coming from maven core,
>> any parent pom that you define)
>>
>> Regards,
>> Vincent
>>
>>
>> 2013/7/4 Mirko Friedenhagen <mf...@gmail.com>:
>>> Hello everyone,
>>>
>>> now I am getting greedy :-). I see that you may specify versions for
>>> the goals being executed during phases in components.xml for custom
>>> package types.
>>>
>>> Is there a way to convince the versions-maven-plugin etc. to update
>>> these versions as well?
>>> Or. where are the versions for the plugins in components taken from?
>>>
>>> Regards Mirko
>>>
>>> ---------------------------------------------------------------------
>>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Problems setting up a custom package type II - plugin/mojo
versions in components.xml
Posted by Mirko Friedenhagen <mf...@gmail.com>.
Hello Vincent,
thanks for your answer. Just so I get this right: I am looking at my
IT-pom [1] and it has no parent defined. I am running Apache Maven
3.0.5. In my output I *do not* see the plugin-versions defined in the
super POM from Maven-core (this are the ones defined in
default-bindings.xml[2], right?) but newer ones as they are defined in
the parent-pom of the plugin/extension project.
* Say I have an extension (should be almost the same with a plugin)
with version 2.13 of surefire in the pluginManagement of it's POM.
* I include this extension in a parent pom PP and define 2.14.1 in the
pluginManagement section.
<build>
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.14.1</version>
</plugin>
</plugins>
</pluginManagement>
<extensions>
<extension>
<groupId>g</groupId>
<artifact>a</artifactId>
<version>1.0</version>
</extension>
</extensions>
</build>
* In project A inheriting this parent pom I define 2.15 as version.
* Now should I expect the run of 2.15 for A, 2.14.1 for projects just
having PP as parent and all projects not using the PP but the
extension to use 2.13, right?
[1] https://github.com/mfriedenhagen/foss-jar-maven-plugin/blob/master/src/it/test-foss-jar/pom.xml
[2] https://github.com/apache/maven/blob/master/maven-core/src/main/resources/META-INF/plexus/default-bindings.xml
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/
On Thu, Jul 4, 2013 at 8:33 AM, Vincent Latombe
<vi...@gmail.com> wrote:
> These are taken from the parent pom (super POM coming from maven core,
> any parent pom that you define)
>
> Regards,
> Vincent
>
>
> 2013/7/4 Mirko Friedenhagen <mf...@gmail.com>:
>> Hello everyone,
>>
>> now I am getting greedy :-). I see that you may specify versions for
>> the goals being executed during phases in components.xml for custom
>> package types.
>>
>> Is there a way to convince the versions-maven-plugin etc. to update
>> these versions as well?
>> Or. where are the versions for the plugins in components taken from?
>>
>> Regards Mirko
>>
>> ---------------------------------------------------------------------
>> 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: Problems setting up a custom package type II - plugin/mojo
versions in components.xml
Posted by Vincent Latombe <vi...@gmail.com>.
These are taken from the parent pom (super POM coming from maven core,
any parent pom that you define)
Regards,
Vincent
2013/7/4 Mirko Friedenhagen <mf...@gmail.com>:
> Hello everyone,
>
> now I am getting greedy :-). I see that you may specify versions for
> the goals being executed during phases in components.xml for custom
> package types.
>
> Is there a way to convince the versions-maven-plugin etc. to update
> these versions as well?
> Or. where are the versions for the plugins in components taken from?
>
> Regards Mirko
>
> ---------------------------------------------------------------------
> 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