[opencms-dev] Versioning Modules

Jason Trump jason.trump at brulant.com
Thu Dec 1 17:47:07 CET 2005


i think part of the rationale for using numbers, is that there is an ordering on numbers for dependencies.  for example "module A needs at LEAST version 1.0.2 of module B"; in other words, version 1.0.3 is OK but version 1.0.0 is not.  converting to arbitrary strings makes these sort of rules more difficult to implement.

-----Original Message-----
From: opencms-dev-bounces at opencms.org on behalf of Nick Panienski
Sent: Thu 12/1/2005 10:56 AM
To: 'The OpenCms mailing list'
Subject: [opencms-dev] Versioning Modules
 
Hi,

I'd like to version my modules in a more complex way than just using
numbers.

I tried to edit the manifest.xml but as soon as I use somthing like rc08 for
a release candidate the SAX parser complains: The version you provided is no
valid number. Right... but how come 1.0.0 is a "number" then?

I also tried to tell OpenCms to use 08 as the version. Now i've got version
8 of my module installed - which is logically the same as 08 :) - but
doesnt't fit our versioning scheme.

Would it be possible to use Strings instead of numbers for versioning?

Regards
Nick

-- 
codecentric
Grünewalder Str. 29-31
42657 Solingen

Office 0212  24 94 318
Mobile 0151 167 06 496
panienski at codecentric.de



_______________________________________________
This mail is send to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://mail.opencms.org/mailman/listinfo/opencms-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 3285 bytes
Desc: not available
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20051201/d12284fa/attachment.bin>


More information about the opencms-dev mailing list