[DOCU-38] Section on best practice for updating Magnolia 3 or 3.01 to 3.02 Created: 12/Mar/07  Updated: 17/Mar/09  Resolved: 15/Dec/08

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Giancarlo Berner Assignee: Philipp Bärfuss
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Please define the best practice on how to update Magnolia 3 or 3.01 to Magnolia 3.02.

I would like to add a step-by-step section, so that no one has problems with the update. What is the best way to do that?

Thanks!



 Comments   
Comment by Philipp Bracher [ 13/Mar/07 ]
  • shutdown
  • backup (optional)
  • install latest jars into WEB-INF/lib
  • startup
Comment by Giancarlo Berner [ 06/Jun/07 ]

What SVN source can the devs check-out? Do they have to use a branch or the trunk?
Will Maven do the compilation?

I am thinking of adding the steps to check-out the source, build the jars with Maven and then copy them to WEB-INF/lib. Is there any recommendation?
Thanks!

Generated at Mon Feb 12 01:05:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.