Hi, Team,
I have completed the changes to the build system and Oomph setup models [1] for pinning the Papyrus-RT dependency on Papyrus to the Papyrus Neon.1 release.
For the setup models, both the developer and tester setups have a new variable:
- papyrus.buildtype: selection of whether to include the latest nightly, milestone, or release build of Papyrus (from the appropriate stream, currently Neon). For the developer setup this applies also to the PDE Target
The default value of the this new setup variable is ‘nightly’ to ensure continuity with the previous behaviour. So, you will have to change this variable to ‘release’ if you want to test properly on the Papyrus Neon.1 release platform.
The Hudson build jobs are all configured with a new property that similarly determines the kind of Papyrus build to use:
- papyrus.kind: currently, all builds have "papyrus.kind=papyrusrelease”. After the 0.8 release, when to return to picking up the latest Papyrus Neon.2 nightly builds, we need to update the build jobs to “papyrus.kind=papyrusnightly”. No changes should be needed in the POMs or the TPDs to make this happen (fingers crossed)
Please let me know if you have any questions or concerns.
Christian
|
