Move Sakai trunk to monolithic build, remove assemblies, simplify POMs
Description
is depended on by
is related to
relates to
Activity
Aaron Zeckoski October 8, 2013 at 7:35 AM
Should be completed now. No merges back to 2.9
Anthony Whyte September 24, 2013 at 12:24 PM
Trunk r129935: Lessonbuilder assembly deleted, base pom tweeked eliminating assembly <module> reference, sonatype repo entry deleted (it's inherited) and version updated to 2.10-SNAPSHOT.
Hudson CI Server September 12, 2013 at 7:13 PM
Integrated in kernel-trunk #705 (See http://builds.sakaiproject.org:8080/job/kernel-trunk/705/)
https://sakaiproject.atlassian.net/browse/SAK-23907#icft=SAK-23907 - Adding warSourceDirectory back to maven plugin for kernel to deploy correct kernel artifacts (Revision 129688)
https://sakaiproject.atlassian.net/browse/SAK-23907#icft=SAK-23907 fixed up shared and common deploys to place kernel artifacts correctly (Revision 129686)
Result = SUCCESS
Hudson CI Server September 12, 2013 at 5:03 PM
Integrated in site-manage trunk #885 (See http://builds.sakaiproject.org:8080/job/site-manage%20trunk/885/)
Result = SUCCESS
Aaron Zeckoski September 12, 2013 at 2:19 PM
Removing all sakai.{project}.version properties (except for kernel). All code that used the properties will fail to work from now on. This required massive core code changes.
This is a large parent ticket with a primary aim of simplifying our processes. The aim is to simply releasing, building, and JIRA management.
Current state:
kernel <> master < base <- project <- sub
New state:
master <- kernel
<- base
<- project <- subproject (e.g. tool)
The roles of each part will be:
master - the institutional POM (defines versions and DM)
base - distribution POM (defines what modules are part of a release and profiles needed for building the entire project)
kernel/project - typical project base POM - defines what makes up a tool or service in Sakai and ties the api/impl/util parts together (also means the kernel POM is not anything special anymore)
For version processing (from within the project directory):
1) perl -pi -e 's/<version>0\.7-SNAPSHOT<\/version>/<version>2\.10-SNAPSHOT<\/version>/g' `find ./ -name pom.xml`
– swap 0.7-SNAPSHOT for the version you want to swap to 2.10-SNAPSHOT
2) svn diff (check for replacements of things which are NOT the versions of the current project)
Heads up that this is going to involve some trunk breakage for at least a little while.... so I think this quote sums it up:
"Now I am become Death, the destroyer of worlds." - J. Robert Oppenheimer quoting from Bhagavad Gita
https://www.youtube.com/watch?v=26YLehuMydo