RE: M2 release plugin snapshot version does not handle new development d

[LAMY Olivier <Ol...@accor.com>]

"This is not a bug" in case of reactor projects : sure ?

Have a look : http://jira.codehaus.org/browse/MRELEASE-91

Personnaly, I have trouble using ${pom.version} due to http://jira.codehaus.org/browse/MNG-2339.

-- 
Olivier

-----Message d'origine-----
De : Kenney Westerhof [mailto:kenney@apache.org] 
Envoyé : samedi 30 septembre 2006 20:29
À : Maven Users List
Objet : Re: M2 release plugin snapshot version does not handle new development d


Hi,

This is not a bug - the release plugin just updates the module you're releasing.

Dependencies should be updated manually, since changing versions might break things.

What you could do though is specify ${pom.version} for the <version> in your dependencies.

-- Kenney


shinsato wrote:
> Did you find a solution?  I'm noticing the same problem.
> 
> The POM version is changed from 1.0.0.1-SNAPSHOT to 1.0.0.1 for the 
> release, and then up to 1.0.0.2-SNAPSHOT for the next development.
> 
> But the internal project dependencies are not changed from 1.0.0.1 to 
> 1.0.0.2-SNAPSHOT.  It seems like a definite bug, unless I'm missing 
> something in the way that the POM was supposed to be written.
> 
>         Harold
> 
> 
> 
> Markku Saarela wrote:
>> Hi,
>>
>> After release:perform snapshot version project pom.xml include 
>> dependency versions for dependent projects remains to new release 
>> version ex. 1.0a not new development version ex 1.0-SNAPSHOT. I 
>> couldn't find anything from google concerning  this issue. Is there 
>> any way to avoid this. It's annoying because there are over 40 modules in project.
>>
>> Regards, Markku Saarela
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org



This e-mail, any attachments and the information contained therein ("this message") are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited.
--------------------------------------------------------------------------------------------------------------
Ce message électronique et tous les fichiers joints ainsi que  les informations contenues dans ce message ( ci après "le message" ), sont confidentiels et destinés exclusivement à l'usage de la  personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci  de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites.
-------------------------------------------------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: M2 release plugin snapshot version does not handle new development d

[Kenney Westerhof <ke...@apache.org>]

LAMY Olivier wrote:
> "This is not a bug" in case of reactor projects : sure ?
> 
> Have a look : http://jira.codehaus.org/browse/MRELEASE-91

I have to agree with Mike Perham there. But the fact that dependencies 
and dependencyManagement are treated differently is a bug, though.
I don't think dependencies or dependencyManagement should update
dependency versions from stable to snapshots at all, not unless
perhaps you explicitly tell the release plugin to do so. Especially
when working on a maintenance branch, you only provide bugfix releases,
so you want to keep the changes small and not update dependencies except
if you really have to.

> Personnaly, I have trouble using ${pom.version} due to http://jira.codehaus.org/browse/MNG-2339.

Ah. Initially I'd say it's not a bug either, but the description is not that clear. I assume
it's about using ${project.version} in the plugin POM. 

I don't see why you using ${pom.version} in your own pom files is affected by that issue..

-- Kenney
 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org