...
- If Sakai is already built and deployed, remove the following directory from the tomcat deploy
tomcat/components/sakai-content-pack - Then checkout and build the content branch
No Format svn co https://source.sakaiproject.org/svn/content/branches/SAK-12105 mvn clean install sakai:deploy -f SAK-12105/pom.xml -PJCR
- At the moment there is an issue with the content provider component. After installing remove components/sakai-content-providers-pack.
Sakai 2.5.x
TODO This is probably the same as the Sakai Trunk instructions, it just hasn't been tried out yet.
...
- Checkout and install DB from trunk
No Format svn co https://source.sakaiproject.org/svn/db/trunk db mvn clean install sakai:deploy -f db/pom.xml
- If you can, run maven und from 2.4.x db, otherwise removing the following from your tomcat:
- tomcat/components/sakai-db-pack
- tomcat/shared/lib/sakai-db-api
- If you can, run maven und from 2.4.x db, otherwise removing the following from your tomcat:
- Checkout and install entity from trunk
No Format svn co https://source.sakaiproject.org/svn/entity/trunk entity mvn clean install sakai:deploy -f entity/pom.xml
- Again if you can't use maven und, manually remove the following:
- tomcat/components/sakai-entity-pack
- tomcat/shared/lib/sakai-entity-api
- Again if you can't use maven und, manually remove the following:
- At this point there might be two versions of hibernate in tomcat/shared/lib
Remove hibernate 3.1.3 and leave 3.2.5ga - Checkout and install the new content code
No Format svn co https://source.sakaiproject.org/svn/content/branches/SAK-12105 mvn clean install sakai:deploy -f SAK-12105/pom.xml -PJCR
- If you can, run maven und from 2.4.x content, otherwise removing the following from your tomcat:
- tomcat/components/sakai-content-pack
- If you can, run maven und from 2.4.x content, otherwise removing the following from your tomcat:
- At the moment there is an issue with the content provider component. After installing remove components/sakai-content-providers-pack.
Content Migration
Unlike some of the other data upgrades that have been performed on Content Hosting, the conversion to a JCR implementation requires copying all of the data over to another repository. Below is a description of the first algorithm are working on to perform the migration.
...