Reinhard Pötz wrote:
Grzegorz Kossakowski wrote:
[EMAIL PROTECTED] pisze:
Author: reinhard
Date: Tue Aug 5 12:42:45 2008
New Revision: 682901
URL: http://svn.apache.org/viewvc?rev=682901&view=rev
Log:
back in snapshot mode
Modified:
cocoon/trunk/tools/pom.xml
Modified: cocoon/trunk/tools/pom.xml
URL:
http://svn.apache.org/viewvc/cocoon/trunk/tools/pom.xml?rev=682901&r1=682900&r2=682901&view=diff
==============================================================================
--- cocoon/trunk/tools/pom.xml (original)
+++ cocoon/trunk/tools/pom.xml Tue Aug 5 12:42:45 2008
@@ -26,7 +26,7 @@
<parent>
<groupId>org.apache.cocoon</groupId>
<artifactId>cocoon</artifactId>
- <version>7</version>
+ <version>5-SNAPSHOT</version>
<relativePath>../parent</relativePath>
Development version is lower than released one. Is it intended?
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'm actually working on a fix to maven for this at the moment. It would
allow you to put <version>MAVEN_PARENT_VERSION</version> in the pom
instead of an actual version number. Don't get your hopes up though.
I've been working on this for the last few weeks in the precious little
available time I have right now. The thing that makes it difficult is
that when your pom gets installed or deployed it has to have a real
version number in it.
Ralph
