On 10/16/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
Hi Dennis,
Dennis Lundberg wrote:
[snip]
==============================================================================
>> --- maven/plugins/trunk/maven-clean-plugin/pom.xml (original) +++
>> maven/plugins/trunk/maven-clean-plugin/pom.xml Mon Oct 16 10:55:07 2006
>> @@ -9,7 +9,7 @@
>> <artifactId>maven-clean-plugin</artifactId>
>> <packaging>maven-plugin</packaging>
>> <name>Maven Clean Plugin</name>
>> - <version>2.1.1</version>
>> + <version>2.1-SNAPSHOT</version>
>
> This doesn't seem right.
> After version 2.1.1 comes version 2.1???
>
> <snip>
What's wrong with this in general? We do this all the time! 2.1-SNAPSHOT
means for us always the latest version from the 2.1-trunk and from time to
time, we have a release, i.e. 2.1.0, 2.1.1, 2.1.2, ...
- Jörg
That's not consistent with Maven's processing of the versions. Say you
have version 2.1, 2.1.1, 2.1.2 and 2.1-SNAPSHOT, the order from first
to last is 2.1-SNAPSHOT, 2.1, 2.1.1 and 2.1.2.
Another way to look at it is that there are always 3 numeric version
values, even if one is absent. For example, 2.1 and 2.1.0 are the same
version. As such 2.1-SNAPSHOT is equivalent to 2.1.0-SNAPSHOT.
Instead of using 2.1-SNAPSHOT for those fix versions, you should
include the fix value. For example, when you release 2.1.2, the trunk
version would be 2.1.3-SNAPSHOT.
-Nathan
