[MAGNOLIA-888] release: automate the tomcat bundle Created: 18/May/06  Updated: 23/Jan/13  Resolved: 10/Oct/06

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.0 Beta 1
Fix Version/s: 3.0 RC3

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

Currently I have to proceed multiple steps before releasing manually. Even if the maven release plugin helps a lot.

Following the log:

  • update the license.xml in the core jar (could be done by a filter)
  • update the license.txt file and the release.txt
  • date
  • version number
  • magnolia.properties --> set magnolia.develop=false
  • bind name in repositories.xml must differ for the plublic war
  • bootstrap the war (magnoliaAuthor, magnoliaPublic)
  • default changes (not yet bootstapped)
  • activation port is 8081
  • secure /.magnolia/*
  • default /features.html
  • cache (switch on)
  • set admin flag false
  • delete the war files


 Comments   
Comment by Philipp Bracher [ 10/Oct/06 ]

done

Generated at Mon Feb 12 03:21:36 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.