Re: [papyrus-rt-dev] Builds and Setup Models Updated for 0.8 Release

[Peter Cigéhn <peter.cigehn@xxxxxxxxx>]

Hi,

I tested the updated developer setup with the new variable. One implication of this was that I had to switch to advanced mode when installing. Previously I always made the installation of the tester setup, using the simple mode. 

Apart from this I also realized that I now will have a bit hard time knowing/remembering which choice I have made for this single tester setup. And what about if I want to have both a nightly setup and a release setup installed at the same time? Sure I can manually ensure installations into separate folders, instead of just picking the default location. But it requires some more work, and you manually have to create icons on your desktop so you loose some of the convenience that you get from using the Eclipse Installer.

Maybe it would be better to actually have different "product versions" defined (compare with the end-user setup where you can select 0.7.0, 0.7.1, 0.7.2 and current). Then you solve both the issue of making the selection available in simple mode, as well as making it possible to have both a nightly and a release tester version installed at the same time (and automatically getting icons on the desktop named according to the different product versions).

Any opinions?

/Peter Cigéhn

On 30 September 2016 at 17:32, Christian Damus <give.a.damus@xxxxxxxxx> wrote:

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

[1]  http://eclip.se/502480

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev