The most important build activities are automated, but some require manual intervention and should be executed just before a release to ensure that procedures still work.
Models, Grammars and other auto-generated code
The Classic OCL GenModels should be reloaded and regenerated and the changes checked to ensure that the code is compatible with the latest MF even though 2.7 compatibility is selected.
The LPG grammars are regenerated by the "LPG Parser" and "LPG Backtracking Parser" External Tools launches. Some manual restoration of Hava annotations is needed to make errors go away.
The "Generate OCL All" should regenerate all the pivot models. After cleaning up import and overrides, no significant changes should remain.
The documentation is generated by the "OCL Documentation" External Tools launch.
The Javadoc is generated by the Hudson build when the Javadoc parameter is selected.
The code nominally works with any version of Guava, but is only compiled/tested against the latest provided by diverse sources.
Other versions of Guava may be tested by editing the ocl.eclipse.ocl.pivot MANIFEST.MF to explicitly import and re-export a specific com.google.guava version, which may be made available be dropping the relevant jar into the plugins directory.
Suggested versions to check for compilation/JUnit test errors are Guava 12, 15, 21. Using the 'wrong' version for JUnit plugin tests doesn't seem to work.
Check that installation on the one/two year old Eclipse releases works.
The org.eclipse.ocl.examples.consumers.tests plugin has additional tests for use within Papyrus. It would be good to get these working again.
The org.eclipse.ocl.examples.xtext.tests (Standalone Classpath) launch should be updated to the prevailing plugin versions and used to demonstrate that genuinely standalone operation still works.
The org.eclipse.ocl.examples.xtext.tests (CG) launch should be run to provide more intensive CG testing.
Check that the OOMPH setup works.