[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [papyrus-rt-dev] Problems with Oomph developer setup
|
The developer setup model is updated. If anybody had previously imported the Releng/Installer project, I’d recommend first removing it from your workspace setup model before doing your next update. It will appear in the setup as an unresolved proxy labelled simply “Stream”. It should be quite harmless to leave it, but why leave clutter?
On Mar 28, 2017, 09:32 -0400, Christian Damus <give.a.damus@xxxxxxxxx>, wrote:
Hi, Peter,
Yes, the 1.8 development stream of the Oomph Installer has recently migrated to Oxygen. The 1.7 release (on which our latest Papyrus-RT Installer release is based) is on Neon.
On Mar 28, 2017, 09:31 -0400, Peter Cigéhn <peter.cigehn@xxxxxxxxx>, wrote:
Hi,
Do the Oomph installer use the Oxygen stream? Otherwise there seem to be some additional confusion here. Since the conflict appears between the Oomph installer (Papyrus-RT Installer) and the JUnit utility, I guess we need to understand why/if the Oomph installer (and thus the Papyrus-RT Installer) has a dependency on Oxygen. Is that the case?
/Peter Cigéhn
_______________________________________________
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