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
;-).
--
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
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
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
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
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
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
