Matteo Pelucco wrote: > Nils: I like to use groovy as well; the only thing I have to argue here, is > that an app is more comfortable for "young" developers. But the app could be > a simple "push-button-and-launch-groovy" wrapper for your scripts. I'm in > target with your approach :-)
That won't be as easy though, because then you'd have to connect to Magnolia somehow. Running a command or Groovy script within Magnolia gets you direct access to all Magnolia API's. > And more: moving (or better: merging) content from environment A (stage) to > environment B (prod) and viceversa is a feature I expect, in 2014, from an > Enterprise CMS. Magnolia has lots of options for this. Magnolia modules, XML export/import, the packager module, backup/restore. Nils. ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
