...
| Code Block |
|---|
ant crn-export -Dtype=layout -Ddir=<export_directory> -Dsysid=<username> |
uPortal < 3.0
Exporting from an earlier version of uPortal is a bit of an adventure. Some of the branches have had the export system backported. However, Eric Dalquist made a major commit to uPortal/trunk with r44591 on 1/13/2009. Any improvements with this commit probably have yet to be backported. For example, 2.5-patches had the export system committed with r42716 on 12/12/2007 and is way out of date. The backports have an import-export.xml file that you call ant on. For example:
| Code Block |
|---|
ant -f import-export.xml export -Ddir=<export_dir> -Dtype=all
|
You could use this file, or else just add a crn-export task to your build.xml file.
When CalPoly performed it's migration the cernunnos scripts were under heavy development, I first applied the 2.5-patches branch export commit to our portal, then merged in some of the newer scripts from uPortal/trunk. Presently, it may be cleaner to simply work off uPortal/trunk.
Recommended Procedure
Here is what I would recommend doing:
- Branch your portal project in your repository. You may have an undeployable portal after all of this due to upgraded jars and changes to build.properties. Better to keep this work cleanly separated.
- Copy the files from https://www.ja-sig.org/svn/uPortal/trunk_ under _uportal-impl/src/main/resources/org/jasig/portal/io into your portal project.
- Hook into the scripts by copying import-export.xml from a backported branch or by just adding a crn-export task to your build.xml similar to the uPortal/trunk build.xml file.
- Get the latest cernunnons jar from uPortal/trunk and put it in your classpath
- You may need to upgrade other jar files, I copied used all of the new jars from Eric's export.zip patch found in this JIRA issue. I had to upgrade to Spring as well. In the end, instead of setting every jar in build.properties, I just added lib/*.jar to the ant classpath.