[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [papyrus-rt-dev] Developer Setup for Oxygen
|
I forgot to mention that, although the “master” stream in the Oomph setup now is configured for Oxygen, if you are updating an existing workspace then it will have been set up for the Neon target platform. So, when you run the setup in the “Perform Setup…” dialog, you must first press the Back button to change the “Target Platform” variable to Oxygen. You probably will have to check the “Show all variables” option to access the setting.
On May 2, 2017, 09:13 -0400, Christian Damus <give.a.damus@xxxxxxxxx>, wrote:
Hi, Team,
Now that the migration to Oxygen is underway on the master branch (Core and Tooling components successfully building so far), I have updated the Oomph setup for developers to
- provision a PDE Target using the latest Eclipse Oxygen milestone and Papyrus nightly build
- (temporarily) pull the Papyrus-RT Core and Tooling components directly from their Hudson build jobs. We won’t have an Oxygen Product build at least until the Codegen build is fixed on Oxygen
- update the “master” streams of all Papyrus-RT setup-projects to Oxygen. This means that the “master” streams that you have already imported for Neon simply become the Oxygen stream when next you run the setup. Be sure to pull git too, of course, otherwise your workspace source and target will be out of sync
For more information, see
bug 514322 and its various attendant Gerrit patches.
