Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] Codegen+RTS version 0.7.2
Hi,

I checked the updated .setup-files. I am not sure if it is possible to "include" or "inherit" Oomph .setup-files, otherwise I see a risk of these files getting out of sync, since they currently share a big chunk of common settings that now needs to be kept in sync manually. But I guess it is doable to manually maintain the consistency...

But I still do no understand the purpose and expected stakeholder for the two different configuration in the developer .setup-file.

Now the "Nigtly build for testers" configuration installs the latest *release* of the core, profile and tooling parts, i.e. a "fixed" release and not any "nightly" builds of the tooling part. You actually *only* get the 24-hour nightly builds of the code-generator and run-time. Who is the intended user of this configuration? I guess it will be very misleading for anyone that actually expects to get the latest nightly (24 houirs) builds of the tooling as well (but the problem is that no such build configuration exist today).

The "Latest Successful builds for testers", uses the "24 hour" repo for the code-generator and run-time and the "20 minutes" repo for the tooling part. To be consistent I would have expected this configuration to pick up the "20 minutes" builds for the code-generator and run-time as well, i.e. instead of the http://download.eclipse.org/papyrus-rt/builds/nightly/ repo it should use the http://download.eclipse.org/papyrus-rt/builds/repo/ repo.

It looks like we continue to have a rather confusing situation with different repos and different build frequencies of the core/profile/tooling parts vs. the code-generator/run-time parts. To reduce this confusion I have a strong feeling that we need to combine both the builds and the output repos from the different builds. Or if they should continue to be kept separate, then at least make it consistent and have a "24 hour" time-triggered build and a "20 minutes" git-poll-triggered build for *both* the core/profile/tooling part *and* the code-generator/run-time part.

/Peter Cigéhn

PS. Then I saw also that the version range that you had specified was written incorrectly using a "strict" version rage, i.e. [ ]. In this case you should use a "open" version range, i.e. [ ). In the main .setup-file the version range for base Papyrus should be [1.1.3, 1.1.4) with a ) and not ]. The same goes for the version ranges of base Papyrus in the developer .setup-file as well. Another minor thing was that you gave the 0.7.2 configuration the name "0.7.2" whereas the previous ones was named "070" and "071". The label can still be "0.7.2", but the name should not contain dots (.) otherwise they will be exchanged with _ anyway to avoid having dots (.) in directory names in the file system. DS.

On 15 December 2015 at 19:53, charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote:
I have implemented the separation I discussed in my last email. There are now two setup files:

  • Papyrus-RT.setup : for end users
  • Papyrus-RT_Dev.setup : for testers and experienced users who are not afraid of development builds

I have also added a “Tester Guide” page on the Papyrus-RT wiki, with information on how to use the Papyrus-RT_Dev.setup file. Note that both setup file can co-exist in the Eclipse Installer.


Sincerely,

Charles Rivet
Senior Product Manager
charles@xxxxxxxxxxxxx


On 2015.12.15, at 09:40 , charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote:

All fixed. Thanks for the feedback. Most of the issues were version numbering.

I would actually prefer not to have any of the nightly/last successful builds in the default setup file - just the release (and a “current” entry once we create a composite update site to support it). I don’t think that “normal” users would need this level of timeliness with regards to Papyrus-RT releases - and it may not be “safe” to provide it to them without guidance (e.g., likeliness of support burden).

I could then create a “Papyrus-RT Tester/Developer” setup file that would provide the other options. This could then be added to the documentation on the Papyrus-RT Developer Guide - DevEnv Mars wiki page. Or even just add the repository information on that page.

/Charles

On 2015.12.15, at 07:40 , Peter Cigéhn <peter.cigehn@xxxxxxxxx> wrote:

Hi,

I tested the updated setup file a little bit. I got a bit confused though regarding the change related to the installation of the nightly build. There are now two options to install something called "Nightly" versus "Latest Development Build." I am not sure I understand the difference between them.

The problem though, is that neither of them are possible to install. When checking the .setup-file a bit more in detail it looks like the "Nightly" choice only has the p2 repo http://download.eclipse.org/papyrus-rt/builds/nightly/. Since this repo *only* have the code-generator and run-time features (and not code, profile and tooling), it is not possible to install Papyrus-RT as a whole from this repop only.

And when checking the "Latest Development Build" configuration, then there is *only* the the p2 repo https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Master-All/lastSuccessfulBuild/artifact/repository/. But since this repo only contains the core, profile and tooling features, and not any of the code-generator and run-time features, you are not able to install Papyrus-RT as whole using this configuration either.

To be able to install a complete Papyrus-RT "nightly/deveopment build" (whatever we call that), you need to have *both* http://download.eclipse.org/papyrus-rt/builds/nightly/ (or possibly http://download.eclipse.org/papyrus-rt/builds/repo/ which is built more frequent than the former which is only built every 24 hours) *and* https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Master-All/lastSuccessfulBuild/artifact/repository/. Otherwise, you will not be able to make a complete installation.

I suggest that we combine these two configurations back into one single option to install a "Nightly" as we had before.

One option though is still to have two different options depending on if you want to have the builds every 24 hours of the code-generator and the run-time in the http://download.eclipse.org/papyrus-rt/builds/nightly/ repo and one other option if you want to have builds with more frequent polling frequency, i.e. every 20 minutes, by using the http://download.eclipse.org/papyrus-rt/builds/repo/ repo. The https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Master-All/lastSuccessfulBuild/artifact/repository/ for the code, profile and tooling is always polled every 20 minutes to get a frequent build. So you will always have that build frequency anyway for the core, profile and tooling parts.

/Peter Cigéhn

PS. I also saw that the version range for the base Papyrus feature is [1.1.2,1.1.4) when installing the new 0.7.2 of Papyrus-RT. I guess that should be [1.1.3,1.1.4) to be correct. DS.

On 11 December 2015 at 19:35, charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote:
I updated the Papyrus-RT setup file (org.eclipse.papyrus-rt/releng/org.eclipse.papyrus-rt.oomph/setups/Papyrus-RT.setup) to have a 0.7.2 option.

I will only merge it once everything is in place, so that users do not see the new configuration until everything else is in place.


Sincerely,

Charles Rivet
Senior Product Manager
charles@xxxxxxxxxxxxx

On 2015.12.11, at 13:20 , Ernesto Posse <eposse@xxxxxxxxxxxxx> wrote:

I've updated MANIFEST and POM files for codegen and rts to 0.7.2. 


--
Ernesto Posse

_______________________________________________
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


_______________________________________________
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


_______________________________________________
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

_______________________________________________
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


_______________________________________________
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


Back to the top