1. #Design#Setup
2. #Development
   1. #Environment
   2. #Dependencies
   3. #Test inside Eclipse
3. #Release with Eclipse

Design

...

Setup

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

...

• To test your changes, you can run the MPS GUI
  • Check out the MPSGui project
  • Add the MPSConfig project to MPSGui's build path
  • Remove the library mpsconfig.jar from MPSGui's build path
  • Run MPS GUI inside Eclipse

Release with Eclipse

• Add a note in $MPSGUI_ROOT/RELEASE_NOTES
  • Increment the tag version accordingly
• Commit to CVS
• Tag with mpsconfig-R#-#-#
• Check out the tagged version into production

  Code Block
  cd $PHYSICS_TOP/release cvs co -r mpsconfig-R#-#-# -d mpsconfig-R#-#-# physics/mps/mpsconfig

• Select File => New Java project => Create project from existing source
• Select $PHYSICS_TOP/release/mpsconfig-R#-#-#
• Name the project mpsconfig-R#-#-#
• Press "Finish"
• Right-click on the new project mpsconfig-R#-#-# => Export...
• Select Java => JAR file
• Check mpsconfig-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/mpsconfig-R#-#-#/jar/mpsconfig.jar

• Press "Finish"
• Move the symbolic link

  Code Block
  cd $PHYSICS_TOP/ rm -rf mpsconfig; ln -s release/mpsconfig-R#-#-# mpsconfig

• Launch MPS GUI from lclshome
  • MPS Global => MPS GUI...
  • MPS Global => MPS CUD...