RE: M2 release plugin snapshot version does not handle new development d
As kenney said "not unless perhaps you explicitly tell the release plugin to do
so".
I have asked this in my proposal patch [1].
parameter called rewriteReactorsWithNextDev (true/false) in prepare mojo (true
by default ?).
But no response.
Or an other parameter name instead of this huge one ;-).
--
Olivier
[1]http://jira.codehaus.org/browse/MRELEASE-91
-Message d'origine-
De : Jörg Schaible [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 4 octobre 2006 12:09
À : Maven Users List
Objet : RE: M2 release plugin snapshot version does not handle new development d
Hi Kennay,
Kenney Westerhof wrote on Saturday, September 30, 2006 8:29 PM:
> 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.
If all modules and submodules share the same release cycle and the version, it
does not make sense to keep such interproject dependencies at final releases:
http://jira.codehaus.org/browse/MRELEASE-160
It is quite cumbersome to restore all of them after a release - and higly
error-prone.
- Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: M2 release plugin snapshot version does not handle new development d
Hi Kennay, Kenney Westerhof wrote on Saturday, September 30, 2006 8:29 PM: > 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. If all modules and submodules share the same release cycle and the version, it does not make sense to keep such interproject dependencies at final releases: http://jira.codehaus.org/browse/MRELEASE-160 It is quite cumbersome to restore all of them after a release - and higly error-prone. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 release plugin snapshot version does not handle new development d
I don't understand the logic here. I'm not releasing independent projects.
I'm releasing a multi-module project. All the modules are renamed from
snapshot to release and then back to snapshot again. But suddenly the
multi-module project, after the release is completed, is no longer building
cohesive artifacts.
I just don't see a useful use-case where someone would actually want their
multi-module project (which almost certainly will have modules that are
depending on each other) to require a manual and potentially error prone
conversion. The only valid scenario I see for a multi-module project is for
the submodule interdependencies to be kept in step with each other, and that
not doing so in fact does break things, as opposed to the reverse.
Am I missing a useful use-case scenario here? It sounds like the
${pom.version} might be a solution. When I ran the archetype creation for
subprojects, I actually wondered why it didn't make it possible to set the
version only in the parent pom, so all sub-projects inherit the parent
version number.
- Harold
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 in your
dependencies.
-- Kenney
--
View this message in context:
http://www.nabble.com/M2-release-plugin-snapshot-version-does-not-handle-new-development-depency-version-correctly-in-multimodule-project-tf2152810.html#a6607157
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 release plugin snapshot version does not handle new development d
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: M2 release plugin snapshot version does not handle new development d
"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:[EMAIL PROTECTED]
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 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: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 release plugin snapshot version does not handle new development d
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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/M2-release-plugin-snapshot-version-does-not-handle-new-development-depency-version-correctly-in-multimodule-project-tf2152810.html#a6575828 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
