Thanks for your reply. Are you suggestting something below.
Parent POM.
<groupId>com.tdsecurities</groupId>
<artifactId>test-parent</artifactId>
<version>1.0-SNAPSHOT</version>
In all child projects
<parent>
<artifactId>test-parent</artifactId>
<groupId>com.tdsecurities</groupId>
<version>1.0-SNAPSHOT</version>
</parent>
<groupId>com.tdsecurities</groupId>
<artifactId>test-child</artifactId>
<version>${parent.version}</version>
On 12/13/11, Guillaume Polet <[email protected]> wrote:
> Sure, writing it in the parent definition is the best way to go since
> you avoid to write it twice. This is the way I work at least.
> Sorry if I made that unclear with my previous e-mail.
>
> Guillaume
> Le 13/12/2011 01:07, Barrie Treloar a écrit :
>> On Tue, Dec 13, 2011 at 9:24 AM, Guillaume Polet
>> <[email protected]> wrote:
>>> I think that what he was trying to achieve is to not repeat the same
>>> version
>>> in all the pom's but this is totally impossible because of the way Maven
>>> works.
>> Yes, but at least you only need to define it once for each module (in
>> the parent/version section).
>> Only the parent pom needs to define the versions in the
>> dependencyManagement section.
>>
>> And as Benson points out, doing it this way release (or vesrions
>> plugin) will manage it for you.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
