It's for when you release them together, it will match up the versions and 
replace them. Either approach works.

I think your change is good, ${project.version} is preferable. It both 
indicates to the reader that "it's the same as the current project and that's 
important", as well as causing fewer changes during the release process.

- Brett

On 17/03/2010, at 9:28 AM, Hervé BOUTEMY wrote:

> I didn't know this one: how can release plugin know that another artifact 
> version should be kept in sync with current one?
> I took this pattern in Maven 3 trunk and found it quite good.
> 
> I'm interested in any feeed back
> 
> Le mardi 16 mars 2010, Stephen Connolly a écrit :
>> I thought best practice was to leave the version as is and let maven
>> release plugin update it for you?
>> 
>> On 15 March 2010 17:26, <[email protected]> wrote:
>>> Author: hboutemy
>>> Date: Mon Mar 15 17:26:16 2010
>>> New Revision: 923347
>>> 
>>> URL: http://svn.apache.org/viewvc?rev=923347&view=rev
>>> Log:
>>> use ${project.version} for internal artifacts to avoid copy/paste
>>> 
>>> Modified:
>>>   maven/archetype/trunk/pom.xml
>>> 
>>> Modified: maven/archetype/trunk/pom.xml
>>> URL:
>>> http://svn.apache.org/viewvc/maven/archetype/trunk/pom.xml?rev=923347&r1=
>>> 923346&r2=923347&view=diff
>>> 
>>> =========================================================================
>>> ===== --- maven/archetype/trunk/pom.xml (original)
>>> +++ maven/archetype/trunk/pom.xml Mon Mar 15 17:26:16 2010
>>> @@ -64,7 +64,7 @@ under the License.
>>>      <dependency>
>>>        <groupId>org.apache.maven.archetype</groupId>
>>>        <artifactId>archetype-common</artifactId>
>>> -        <version>2.0-alpha-5-SNAPSHOT</version>
>>> +        <version>${project.version}</version>
>>>      </dependency>
>>>      <dependency>
>>>        <groupId>org.apache.maven</groupId>
>> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

--
Brett Porter
[email protected]
http://brettporter.wordpress.com/





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to