I had to change the version numbers of magnolia, magnolia-ui and the magnolia data module.
The solution which worked best for us is to have maven build you a WAR file (automated by Jenkins - hey we are developers and inherently lazy ;-) ). You just shutdown your app server, copy the WAR file to its location and start up again. We also had this JAR replacement thing in our early days but with added complexity it becomes very tedious to figure out what changed and what to copy and by the time you possibly forget one JAR it can get really messy. Rolling back to some version isn't possible either... For your situation I'd say make a directory diff and replace the jars and you'll be fine (but double check on this one ;-) ) -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=65729ef9-1dd7-4f98-8587-8fc901fb68d0 You are invited to Magnolia Conference. Less than a month to go! Register now: http://www.magnolia-cms.com/conference/register.html ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
