Setup
Environment
- Effectively, you can only develop MPSGui inside Eclipse on lcls-builder.
- Check out the CVS module physics/mps/mpsgui into your workspace
- From now on, the root of project is referred to as $MPSGUI_ROOT
...
- Client for the MPS History data (currently in Oracle, used to be in sqlite)
- SQL queries are located in the file oracle.properties in the package edu.stanford.slac.mpsgui.jdbc.hist
- Has an auxilliary API to insert/delete test messages
Release
...
to production
- Update the application version in $MPSGUI_ROOT/src/edu.stanford.slac.mpsgui.MpsGuiProperties
- Add a note in $MPSGUI_ROOT/RELEASE_NOTES
- Increment the tag version accordingly
- Commit to CVS
- Tag with mpsgui-R###
- Check out the tagged version into production, and build with ant:
Code Block |
---|
cd $PHYSICS_TOP/release cvs co -r mpsgui-R#-#-# -d mpsgui-R#-#-# physics/mps/mpsgui cd $PHYSICS_TOP/release/mpsgui-R#-#-# ant |
Move the symbolic link to point to the new version:
Code Block |
---|
cd $PHYSICS_TOP/
rm -rf mpsgui; ln -s release/mpsgui-R#-#-# mpsgui
|
- Launch from lclshome
- MPS Global => MPS GUI...
- MPS Global => MPS CUD...
========================================================
NO LONGER APPLICABLE: The following is preserved as the old eclipse-based release method. Pre-Partha's-ant-script!
- Select File => New Java project => Create project from existing source
- Select $PHYSICS_TOP/release/mpsgui-R###
- Name the project mpsgui-R###
- Press "Finish"
- Right-click on the new project mpsgui-R### => Export...
- Select Java => JAR file
- Check mpsgui-R### in "Resources to export"
- Check "Export generated class files and resources"
- As the export destination, type (and/or select)
$PHYSICS_TOP/release/mpsgui-R#-#-#/jar/mpsgui.jarCode Block - Press "Finish"
- Move the symbolic link
Code Block cd $PHYSICS_TOP/ rm -rf mpsgui; ln -s release/mpsgui-R#-#-# mpsgui
Launch from lclshome - MPS Global => MPS GUI... MPS Global => MPS CUD...
========================================================