Users List
Cc: Maven Users List
Subject: Re: Sharing a version among different modules
Thanks, Nicola. Interesting alternative!
So if I understand you correctly, you have version numbers on
the aggregator and on modules below that, but you just keep
those to a fixed vale (say "0") and use the
Ernst de Haan wrote:
Thanks, Nicola. Interesting alternative!
So if I understand you correctly, you have version numbers on the
aggregator and on modules below that, but you just keep those to a
fixed vale (say "0") and use the root parent version to the outside
world?
No, once version number
y, May 25, 2010 8:58 AM
> To: Maven Users List
> Cc: Maven Users List
> Subject: Re: Sharing a version among different modules
>
> Thanks, Nicola. Interesting alternative!
>
> So if I understand you correctly, you have version numbers on
> the aggregator and on modu
Thanks, Nicola. Interesting alternative!
So if I understand you correctly, you have version numbers on the
aggregator and on modules below that, but you just keep those to a
fixed vale (say "0") and use the root parent version to the outside
world?
Cheers,
Ernst de Haan
Op 25 mei 2010
I keep all version numbers in the dependencyManagement section of my
parent POM, which is different from my aggregator POM and is parent to
the aggregator and all its modules. In this way I specify each version
exactly once. Something like:
bouncycastle
bcprov-jdk13
140
dependencyManagem
>> How do I share one version number across multiple module (subprojects)?
>>
>> Any suggestions for reducing the number of locations (preferably to 1) ?
>
> There's also the versions-maven-plugin...
Cheers, Wayne, the more options the better. I'll look at that as well.
Regards,
Ernst
-- tryi
> How do I share one version number across multiple module (subprojects)?
>
> Any suggestions for reducing the number of locations (preferably to 1) ?
There's also the versions-maven-plugin...
Wayne
-
To unsubscribe, e-mail: use
> But if you are using release plugin
> http://maven.apache.org/plugins/maven-release-plugin/ for releasing versions,
> same version numbers in poms are updating automatically. There is no need to
> have only one.
>
> See
> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html
>> - in the parent pom.xml, to denote the project version
> you need this
>
>> - in each module, to denote the module version
> just leave out the version and it will inherit it from the parent pom
>
>> - in each module's reference to the parent
> you need this
>
>> - in each module's reference
You can use {$parent.version} variable in modules poms.
But if you are using release plugin
http://maven.apache.org/plugins/maven-release-plugin/ for releasing
versions, same version numbers in poms are updating automatically. There
is no need to have only one.
See
http://maven.apache.org/p
that is how do it (http://github.com/mkristian/jruby-maven-plugins/)
On Mon, May 24, 2010 at 10:48 PM, Ernst de Haan wrote:
> How do I share one version number across multiple module (subprojects)?
>
> I have one parent pom.xml referencing 3 modules and -believe it or not- I've
> got the version
11 matches
Mail list logo
