On 9/29/06, Vadim Gritsenko <[EMAIL PROTECTED]> wrote:
Reinhard Poetz wrote:
> Vadim Gritsenko wrote:
>> To maven gurus here:
>>
>> I see many a poms have a version inside, like "1.0.0-SNAPSHOT", or
>> "1.0.0-M2-SNAPSHOT".
>>
>> Am I right in understanding that this is either an error or omission,
>> and versions everywhere should read "2.2.0-SNAPSHOT" or
>> "2.2.0-M2-SNAPSHOT"?
>
> no, we decided (at least by not questioning it so far) that only the
> Cocoon core module will get the version 2.2.0. As we have never released
> any block as a seperate artifact yet, it makes sense to use 1.0.0 as
> version. It also indicates that we can finally(!) have separate release
> cycles for our various artifacts.
It is confusing, though. It would be better to start separate release cycles
with version 2.2.
That would likely get out of sync pretty quickly so at best it's a
short term solution. Would it make any sense to try and match up the
POM version with the version of the major JAR that the POM depends on?
I suspect not, so 1.0.0 seems as good of place to start as any...
--
Peter Hunsberger
