Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
servicemix-bean-2008.01, servicemix-camel-2008.01, servicemix-cxf-bc-2008.01, servicemix-cxf-se-2008.01, servicemix-drools-2008.01, servicemix-eip-2008.01, servicemix-file-2008.01, servicemix-ftp-2008.01, servicemix-http-2008.01, servicemix-jms-2008.01, servicemix-jsr181-2008.01, servicemix-mail-2008.01, servicemix-osworkflow-2008.01, servicemix-quartz-2008.01, servicemix-saxon-2008.01, servicemix-script-2008.01, servicemix-scripting-2008.01, servicemix-shared-2008.01, servicemix-truezip-2008.01, servicemix-validation-2008.01, servicemix-wsn2005-2008.01, servicemix-xmpp-2008.01
-
servicemix-bean, servicemix-camel, servicemix-common, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jms, servicemix-jsr181, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-script, servicemix-scripting, servicemix-truezip, servicemix-validation, servicemix-wsn2005, servicemix-xmpp
-
None
Description
Because the current versioning scheme for the components resembles the versioning we use for the containers, users think that there is a link between both of them. E.g. they wonder if the 4.0-SNAPSHOT version of the components only works in the 4.0-SNAPSHOT of the container.
By changing the versioning for the components into something completely different (2008.01 where 2008 is the current year and 01, 02, ... is used to designate subsequent releases within the same year).
Have a look at http://cwiki.apache.org/SM/discussion-forums.html#nabble-td18563641|a18563641 for some background on this issue