I see. But apart from that, shouldn't at least the version number be updated? It looks very strange to have a jar with version 4.3.2 on the classpath, but a version number in the configuration of 4.3.2-SNAPSHOT.
Bye, Bert ________________________________ Van: [email protected] [[email protected]] namens Jan Haderka [[email protected]] Verzonden: maandag 19 juli 2010 12:35 Aan: Magnolia User-List Onderwerp: Re: [magnolia-user] upgrade modules from snapshot-version: module version handler doesn't recognize upgrade? On Jul 19, 2010, at 10:26 AM, Bert Leunis wrote: Hi all, For a short time we worked with snapshot-versions of magnolia modules. For example: magnolia-core version 4.3.2-SNAPSHOT and standard-templating-kit 1.3.1-SNAPSHOT. These modules have now reached their definitive versions: 4.3.2 and 1.3.1. We use those in our project now. The versionhandlers of these modules have NOT changed the version numbers in the configuration (/modules/standard-templating-kit/version still shows 1.3.1-snapshot). Does that mean that de versionhandlers have not run, and so have not installed the new bootstrap files etc? This behaviour seems not correct. The versionhandlers should recognize the move from 1.3.1-SNAPSHOT to 1.3.1 as an upgrade. Is that correct? The answer is "it depends". When you work with the snapshots you are using a module that is in an undeterminate state. It might be in early phase of the version development and there are not update tasks yet or it might be in the very late stage and all the update tasks are already in place. In the first case you want to run the update tasks when moving to final version, in the second you don't. There is no signature for each task so it is not possible to determine whether given task was executed or not. Decision is in this case up to you as a maintainer of the system. If you don't want to have any tasks executed, leave everything as is and just replace snapshot jar with the final one. If on the other hand you want to execute the update tasks, change the version number of given module to the previous version and after the restart update tasks will be executed. HTH, Jan Best regards, Bert ________________________________ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]<mailto:[email protected]>> ---------------------------------------------------------------- - Best regards, Jan Haderka, PhD. Magnolia International Ltd. http://www.magnolia-cms.com You should join us at Magnolia Conference 2010: http://www.magnolia-cms.com/conference http://twitter.com/magnolia_cms http://facebook.com/Magnolia -------------------------------------- Magnolia® - Simple Open-Source Content Management ________________________________ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
