[cle-release-team] Please avoid updating tomcat version in master unless updating repo

Matthew Jones matthew at longsight.com
Fri Aug 23 10:37:08 PDT 2013


This is just a reminder that anyone who updates the tomcat version in the
master pom in trunk needs to also deploy new tomcat artifacts to the
repository as this breaks the pack profiles without it.

https://confluence.sakaiproject.org/display/REL/Releasing+an+updated+tomcat+to+Sakai+repo+for+pack-demo

Upgrade of tomcat version (even to a new minor) should be a separate jira,
since version changes have also caused regressions (usually on webdav) in
the past and it makes it a little easier to track.

It's a pretty easy job to update, but can cost a lot of time trying to
figure out why it isn't working.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20130823/42daf9c6/attachment-0001.html 


More information about the cle-release-team mailing list