Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] Developer Setup for Oxygen
Ah, yes.

It seems that it is not possible to install a sane Oxygen workbench from the latest Simultaneous Release milestone, owing to the ongoing difficulties with wiring issues and a broken version of some 3rd-party bundle from Orbit.  Long discussion on cross-project-dev.  Amongst other fall-out is that the Oomph setup bundles required to maintain your development environment don’t resolve in the Oxygen stream.  Also I found that with an installation based on the minimal “Eclipse Platform” to try to work around that, then the Project Explorer was completely broken by linkage errors in some JDT label decorator and the workbench is rendered unusable because of constant error dialogs.

What I resorted to was continuing with the Neon version of the Eclipse for Committers package, targeting the Oxygen platform.  So, the first step where you select the package to create your new installation from, be sure to pick the latest Neon, not Oxygen as shown in your screenshot.  But then do be careful to select Oxygen for the “Target Platform” variable in the importing projects step.

Cheers,

Christian

On May 2, 2017, 11:22 -0400, Young-Soo Roh <ysroh@xxxxxxxxxxxxx>, wrote:
Thanks Christian,
 
I installed the fresh workspace without Model Migration feature.
After eclipse is restarted it did not perform setup task to import git repository and setup workspace.
Also I could not find Perform Setup Task menu to run manually.
Do I select Master(Oxygen) ?? or Neon? for the streams?
 
 
 
 
 
 
 

Regards,
Young-Soo Roh
Zeligsoft(2009) Ltd

 

From: papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Damus
Sent: Tuesday, May 2, 2017 10:55 AM
To: papyrus-rt developer discussions
Subject: Re: [papyrus-rt-dev] Developer Setup for Oxygen

You don’t need to lose your workspace.



HTH,

Christian

On May 2, 2017, 10:48 -0400, Young-Soo Roh <ysroh@xxxxxxxxxxxxx>, wrote:
Ok. I wasn't sure how to access stream property so installing a fresh workspace.
I am not that attached to my current workspace.
 
Thanks.

Regards,
Young-Soo Roh
Zeligsoft(2009) Ltd

 

From: papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Damus
Sent: Tuesday, May 2, 2017 10:19 AM
To: papyrus-rt developer discussions
Subject: Re: [papyrus-rt-dev] Developer Setup for Oxygen

There is some kind of a problem still with the Papyrus Interoperability component on the Oxygen stream, which has been refactored and is now being unrefactored.  Itís in flux and Rémi had to exclude the RSA-RTE import bundles from the Papyrus-RT Tooling build to unblock it.

So, if you had imported the Papyrus-RT Migration project from the Oomph setup, then you will have to un-import it before you can run the update.  Just remove it from the ëstreamsí property of your workspace model.

Cheers,

Christian

On May 2, 2017, 10:02 -0400, Young-Soo Roh <ysroh@xxxxxxxxxxxxx>, wrote:
Hi Christian,,
 
Thanks for the update.
I am trying to update the existing workspace and I got the following error.
Do you have any idea??? Do I have to install fresh?
 
Thanks.
 
 
 
 
Cannot complete the request.  Generating details.
ERROR: org.eclipse.equinox.p2.director code=10054 Cannot complete the install because of a conflicting dependency.
  at org.eclipse.oomph.targlets.internal.core.TargletContainer.forceUpdate(TargletContainer.java:820)
  at org.eclipse.oomph.setup.targlets.impl.TargletTaskImpl$4.run(TargletTaskImpl.java:1128)
  at org.eclipse.oomph.util.pde.TargetPlatformUtil.runWithTargetPlatformService(TargetPlatformUtil.java:120)
  at org.eclipse.oomph.setup.targlets.impl.TargletTaskImpl.perform(TargletTaskImpl.java:1036)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:3324)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.access$1(SetupTaskPerformer.java:3267)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil$1.run(SetupTaskPerformer.java:4488)
  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.performNeededSetupTasks(SetupTaskPerformer.java:4482)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.access$0(SetupTaskPerformer.java:4480)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:3258)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performTriggeredSetupTasks(SetupTaskPerformer.java:3233)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.perform(SetupTaskPerformer.java:3133)
  at org.eclipse.oomph.setup.ui.wizards.ProgressPage$9.run(ProgressPage.java:567)
  at org.eclipse.oomph.setup.ui.wizards.ProgressPage$11$1.run(ProgressPage.java:693)
  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
  ERROR: org.eclipse.equinox.p2.director code=0 Software being installed: artificial_root 1.0.0.v1493733341146
  ERROR: org.eclipse.equinox.p2.director code=1 Only one of the following can be installed at once:
    ERROR: org.eclipse.equinox.p2.director code=0 Papyrus Tools 3.0.0.201705021217 (org.eclipse.papyrus.infra.tools 3.0.0.201705021217)
    ERROR: org.eclipse.equinox.p2.director code=0 Papyrus Tools 2.0.100.201703151744 (org.eclipse.papyrus.infra.tools 2.0.100.201703151744)
  ERROR: org.eclipse.equinox.p2.director code=1 Only one of the following can be installed at once:
    ERROR: org.eclipse.equinox.p2.director code=0 Papyrus M2M QvTo Common Plugin 1.0.0.201705020145 (org.eclipse.papyrus.uml.m2m.qvto.common 1.0.0.201705020145)
    ERROR: org.eclipse.equinox.p2.director code=0 Papyrus M2M QvTo Common Plugin 1.0.0.201705021217 (org.eclipse.papyrus.uml.m2m.qvto.common 1.0.0.201705021217)
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root 1.0.0.v1493733341146
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.interoperability.rsa.feature.feature.group 0.0.0
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root 1.0.0.v1493733341146
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.junit.framework 0.0.0
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root 1.0.0.v1493733341146
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.sdk.feature.feature.group 0.0.0
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: Papyrus core 2.0.0.201703151744 (org.eclipse.papyrus.infra.core.feature.feature.group 2.0.0.201703151744)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.infra.tools [2.0.100.201703151744]
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: Papyrus RSA Import Feature 1.2.0.201705020922 (org.eclipse.papyrus.interoperability.rsa.feature.feature.group 1.2.0.201705020922)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.uml.m2m.qvto.common [1.0.0.201705020145]
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: Conditional Junit Annotations 1.2.0.201705020146 (org.eclipse.papyrus.junit.framework 1.2.0.201705020146)
    ERROR: org.eclipse.equinox.p2.director code=0 To: bundle org.eclipse.papyrus.infra.tools [3.0.0,4.0.0)
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: Papyrus UML 3.0.0.201703151744 (org.eclipse.papyrus.sdk.feature.feature.group 3.0.0.201703151744)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.infra.core.feature.feature.group [2.0.0.201703151744]
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: Papyrus UML 3.0.0.201705021217 (org.eclipse.papyrus.sdk.feature.feature.group 3.0.0.201705021217)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.uml.m2m.qvto.feature.feature.group [1.0.0.201705021217]
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: Papyrus UML M2M QvTo common plugins 1.0.0.201705021217 (org.eclipse.papyrus.uml.m2m.qvto.feature.feature.group 1.0.0.201705021217)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.uml.m2m.qvto.common [1.0.0.201705021217]
 

Regards,
Young-Soo Roh
Zeligsoft(2009) Ltd

 

From: papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Damus
Sent: Tuesday, May 2, 2017 9:24 AM
To: papyrus-rt developer discussions
Subject: 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.

Cheers,

Christian

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.

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
_______________________________________________
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