Aleksey,
I thought it would update the sibling modules based on the modules included in
the parent pom. It updates the sibling dependencies when it changes the tagged
version just not the next version.
So you're saying move the sibling dependencies to the dependencyManagement and
use ${project.version}, or just use ${project.version} in the sibling poms
instead of using the X.X-SNAPSHOT version ??
Thanks for your response
Rick
-----Original Message-----
From: Aleksey Didik [mailto:[email protected]]
Sent: Thursday, July 08, 2010 8:12 AM
To: Maven Users List
Subject: Re: maven release plugin not updating sub-module dependencies
Hello Rick.
In this case release will not change dependencies versions, because
maven have no difference between external artifact and module artifact.
My suggestion is to use ${project.version} and <dependencyManagement>
for cross module dependencies.
hth,
Aleksey Didik.
08.07.2010 17:59, DeGrande, Rick пишет:
> No, I was thinking about doing that, but I have the dependencies in the
> sibling poms. I'm not using the ${project.version} in these poms. I just
> have the SNAPSHOT version specified on the sibling dependencies.
>
>
> Thanks
> Rick
>
> -----Original Message-----
> From: Aleksey Didik [mailto:[email protected]]
> Sent: Thursday, July 08, 2010 1:14 AM
> To: Maven Users List
> Subject: Re: maven release plugin not updating sub-module dependencies
>
>
> Hello, Rick.
> Please, clarify, how do you define submodule dependency?
> Do you use<dependecyManagement> section in parent pom with
> ${project.version} property?
>
> Best regards,
> Aleksey Didik.
>
>
> 08.07.2010 2:34, DeGrande, Rick пишет:
>> I have a multi--module configuration. the directory structure is:
>>
>> aggregate
>> ejb
>> war
>>
>> The war file includes the ejb as a dependency. When I do a
>> release:prepare -DdryRun maven generates the pom.xml.tag correctly but
>> it doesn't update the sub module dependencies in the pom.xml.next. How
>> do I get it to update the sub-module dependencies ?
>>
>>
>>
>> thanks
>>
>>
>>
>>
>> -----------------------------------------
>> The information in this message may be proprietary and/or
>> confidential, and protected from disclosure. If the reader of this
>> message is not the intended recipient, or an employee or agent
>> responsible for delivering this message to the intended recipient,
>> you are hereby notified that any dissemination, distribution or
>> copying of this communication is strictly prohibited. If you have
>> received this communication in error, please notify First Data
>> immediately by replying to this message and deleting it from your
>> computer.
>
> ---------------------------------------------------------------------
> 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]
