Design
Development
Environment
- Effectively, you can only develop MPSConfig inside Eclipse on lcls-builder.
- Check out the CVS module physics/mps/mpsconfig into your workspace
- From now on, the root of project is referred to as $MPSCONFIG_ROOT
Dependencies
- ezJCA (version R0-0-10)
- javainterfaces (current version)
- Oracle JDBC driver (under $MPSCONFIG_ROOT/lib/)
- Sqlite JDBC driver (under $MPSCONFIG_ROOT/lib/)
- xal4lcls
- ext.jar (current version)
- xal.jar (current version)
Test
- To test your changes, you can run the MPSGUI
- Check out the MPSGui project
- Add the MPSConfig project from your workspace to its build path and remove the library mpsconfig.jar
- Run MPSGui from Eclipse
Release with Eclipse
- 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
Code Block cd $PHYSICS_TOP/release cvs co -r mpsgui-R#-#-# -d mpsgui-R#-#-# physics/mps/mpsgui
- 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)
Code Block $PHYSICS_TOP/release/mpsgui-R#-#-#/jar/mpsgui.jar
- 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...
...