You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oltu.apache.org by Simone Tripodi <si...@apache.org> on 2014/02/03 16:45:59 UTC
wrong versioning number when releasing commons
Hi all mates,
I am having a hard time on releasing the commons modules and at the moment
I am missing something because I don't understand the root of all evil:
when installing all modules from /trunk, versions respect what it is
specified in project.version field in the POM, but when releasing them, all
modules inherit the version from the parent: can I kindly ask you an extra
pair of eyes that would help me detecting why this is happening?
TIA, all the best!
-Simo
http://people.apache.org/~simonetripodi/
http://twitter.com/simonetripodi
Re: wrong versioning number when releasing commons
Posted by Simone Tripodi <si...@apache.org>.
Good catch Jasha, thanks a lot for your priceless help!
autoVersionSubmodules is indeed set in the parent :/ I am going to fix it
right now!
All the best!
-Simo
http://people.apache.org/~simonetripodi/
http://twitter.com/simonetripodi
On Mon, Feb 3, 2014 at 7:16 PM, Jasha Joachimsthal <ja...@apache.org> wrote:
> Are you using -DautoVersionSubmodules=true [1]? If so all submodules
> inherit the version from the root pom. Otherwise you must define the
> individual module versions.
>
> Jasha
>
> [1]
>
> http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#autoVersionSubmodules
>
> On 3 February 2014 16:45, Simone Tripodi <si...@apache.org> wrote:
>
> > Hi all mates,
> >
> > I am having a hard time on releasing the commons modules and at the
> moment
> > I am missing something because I don't understand the root of all evil:
> >
> > when installing all modules from /trunk, versions respect what it is
> > specified in project.version field in the POM, but when releasing them,
> all
> > modules inherit the version from the parent: can I kindly ask you an
> extra
> > pair of eyes that would help me detecting why this is happening?
> >
> > TIA, all the best!
> > -Simo
> >
> > http://people.apache.org/~simonetripodi/
> > http://twitter.com/simonetripodi
> >
>
Re: wrong versioning number when releasing commons
Posted by Jasha Joachimsthal <ja...@apache.org>.
Are you using -DautoVersionSubmodules=true [1]? If so all submodules
inherit the version from the root pom. Otherwise you must define the
individual module versions.
Jasha
[1]
http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#autoVersionSubmodules
On 3 February 2014 16:45, Simone Tripodi <si...@apache.org> wrote:
> Hi all mates,
>
> I am having a hard time on releasing the commons modules and at the moment
> I am missing something because I don't understand the root of all evil:
>
> when installing all modules from /trunk, versions respect what it is
> specified in project.version field in the POM, but when releasing them, all
> modules inherit the version from the parent: can I kindly ask you an extra
> pair of eyes that would help me detecting why this is happening?
>
> TIA, all the best!
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://twitter.com/simonetripodi
>