Carsten Ziegeler wrote:
Reinhard Pötz wrote:
yes, I was too lazy to touch nearly every POM file in our repository
just to increase the version number of our parent POMs. I haven't done
this for the last release either and AFAICT, no problem occurred.
Does anybody know if it can cause problems if the development version
number isn't increased after a release?
I think we shouldn't change the version number just for the sake of
changing it.
I was releasing cocoon-parent because I wanted to use the latest
versions of some plugins and some dependencies (e.g. Spring).
If the pom doesn't change why should we increase the version number?
sure, in that case there is no need
I think we should simply drop the parent relationship from all modules
and use the current parent poms just as reactor poms. Every real module
pom directly has our root pom as the parent. This makes releasing imho
much easier as there is no release of any intermediate pom required
anymore. We're using this approach for a very long time now and it has
made things much easier.
+1, exept for cocoon-core-modules because this allows a release of all
of our core modules in one go (multi-module release).
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member [EMAIL PROTECTED]
________________________________________________________________________
