Re: [papyrus-rt-dev] Developer Setup Updates for Oxygen

[Christian Damus <give.a.damus@xxxxxxxxx>]

Hi, Young-Soo,

You don’t actually have to re-install until it’s convenient to do so.  In the mean-time, whenever you run an update, you can just uncheck the p2 task.

But, yes, a Neon workbench cannot be updated to Oxygen because you will end up with a constant barrage of error dialogs caused by classpath errors (wiring problems) in JDT UI.  It would have to be installed from scratch.  But, at least, an existing workspace seems to be safely upgradeable.

Cheers,

Christian

On May 26, 2017, 11:26 -0400, Young-Soo Roh <ysroh@xxxxxxxxxxxxx>, wrote:

Thanks Christian,

 

I will have to re-install my dev env then.

 

Regards,

 

Young-Soo Roh

Sr. Software Developer

Zeligsoft (2009) Ltd.

 

From: papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Damus
Sent: Friday, May 26, 2017 11:07 AM
To: papyrus-rt developer discussions
Subject: [papyrus-rt-dev] Developer Setup Updates for Oxygen

 

Hi, Team,

 

Since Oxygen M7 seems to resolve the Apache bundle wiring problems in the Eclipse/Oomph/MPC/etc. substrate, the developer setup model now is updated to install Papyrus and Papyrus-RT Oxygen in the development environment instead of Neon.  This should help at least with editing models and avoid PDE’s complaints about forward targeting.

Cheers,

 

Christian

Virus-free. www.avg.com

_______________________________________________
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