Yes. - I am in particularly interested in "content" only module (like samples) and how to code it so that when new version is installed proper bootstrap files get also updated/installed. Right now, with every new module version I have to manually update bootstrap files..
I will take a look at DMS...Thanks again Thanks Amir > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > Sent: Friday, August 03, 2007 3:56 PM > To: [email protected] > Subject: Re: [magnolia-dev] Update mechanism > > > On Aug 3, 2007, at 21:30 , Amir Mistric wrote: > > > Hi > > > > Is there a simple example on how to create a module using > "new way"? > > Maven archeotype? > > Also, an example that shows simple delta tasks in action (like what > > would code look like to upgrade between 2 versions)? > > Good point, we'll have to update the archetype. As far as an > example, you could have a look at DMS, although we surely > need to brush it up. > The samples module will also be an example of a "content > only" module (it's likely that it won't have a "class" nor a > version handler). You should also have a look at the > CoreModuleVersionHandler, which has probably the largest > amount and most varied tasks. However, keep in mind that it > is "special", since core was not a module before: when > upgrading from 3.0, it will be "installed", although it > really does an update. (in short, look at DMS for what you > should do, look at core for what can be done ;)) > > hth > > g > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/docs/en/editor/stayupdated.html > ---------------------------------------------------------------- > ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
