functionality we want would be best provided as modules: for example we
intend to replace the current mail module with an implementation that
can use Amazon's Simple Email Service instead.
Seems a nice thing to put in the forge, if you want...
* What is the best way to tell Magnolia to "redeploy" a module?
For all the other topic you already have one answer. About this point, I
usually use this little utility:
http://www.openmindlab.com/lab/products/mgnltasks.html
Combined with maven releases, it will simply redeploy all the xmls in
your module each time the release version changes. It's not completely
documented, but you simply start extending the
SimpleModuleVersionHandler class as you version handler, and add just a
few tasks to do the missing points.
Regards, Danilo.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
