| Problem setting up Papyrus-RT Dev Environment [message #1771452] |
Fri, 25 August 2017 03:29  |
Eclipse User |
|
|
|
Hi,
When trying to set up the Papyrus-RT Dev environment with the Papyrus-RT setup in the eclipse installer i get this. I am setting product, platform and stream to oxygen.
Calculating requirements and dependencies.
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.util.OomphPlugin.coreException(OomphPlugin.java:280)
at org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl.resolve(ProfileTransactionImpl.java:425)
at org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl.commit(ProfileTransactionImpl.java:337)
at org.eclipse.oomph.setup.p2.impl.P2TaskImpl.perform(P2TaskImpl.java:729)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:3324)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:3252)
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:56)
ERROR: org.eclipse.equinox.p2.director code=0 Software being installed: artificial_root 1.0.0.v1503645577180
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 Common Plugin for Papyrus Table 3.0.0.201706140736 (org.eclipse.papyrus.infra.nattable 3.0.0.201706140736)
ERROR: org.eclipse.equinox.p2.director code=0 Common Plugin for Papyrus Table 4.0.0.201708250157 (org.eclipse.papyrus.infra.nattable 4.0.0.201708250157)
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.v1503645577180
ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.toolsmiths.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.v1503645577180
ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrusrt.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: Customization of Nattable Configuration 2.0.0.201708250157 (org.eclipse.papyrus.customization.nattableconfiguration 2.0.0.201708250157)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle org.eclipse.papyrus.infra.nattable
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Papyrus-RT Base Feature 1.0.0.201708250447 (org.eclipse.papyrusrt.base.feature.feature.group 1.0.0.201708250447)
ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrusrt.umlrt.tooling.feature.feature.group
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Papyrus-RT Modelling Feature 1.0.0.201708250447 (org.eclipse.papyrusrt.feature.feature.group 1.0.0.201708250447)
ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrusrt.base.feature.feature.group
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Papyrus-RT Tooling Feature 1.0.0.201707181457 (org.eclipse.papyrusrt.umlrt.tooling.feature.feature.group 1.0.0.201707181457)
ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrusrt.umlrt.tooling.properties [1.0.0.201707181457]
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Papyrus-RT Property View Configuration 1.0.0.201707181457 (org.eclipse.papyrusrt.umlrt.tooling.properties 1.0.0.201707181457)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle org.eclipse.papyrus.infra.nattable [3.0.0,4.0.0)
|
|
|
| Re: Problem setting up Papyrus-RT Dev Environment [message #1771489 is a reply to message #1771452] |
Fri, 25 August 2017 10:32  |
| Eclipse User |
|
|
|
I tried this quickly myself, and I get the same issue if I select "nightly" as the "Papyrus Build Type". If I instead select "releases" as the "Papyrus Build Type" the install proceeds without this issue.
Checking a bit closer, it looks like a major version bump have been made for the org.eclipse.papyrus.infra.nattable bundle in the nightly build of the Oxygen track, i.e. a bump to version 4.0.0, whereas in the latest release, i.e. the Oxygen.0 release, the version is 3.0.0.
This causes issues for Papyrus-RT which have a upper limit version range on one of its dependencies on org.eclipse.papyrus.infra.nattable that excludes any changes in the major version.
I suggest that you set "Papyrus Build Type" as "releases" to resolve this in the short term. But I guess this will break anyway as soon as Oxygen.1 is released when this version bump from 3.0.0 to 4.0.0 makes its way into the releases repo.
Not sure what the principles are for breaking API changes between Oxygen.0 and Oxygen.1, but it does not feel right. Such breaking API change I guess should wait until the Photon.0 release. When checking the Git repo I can see that the version was bumped both on the master branch and the streams/3.0-maintenance branches 3 weeks ago as part of solving bug 515806.
I suggest that you bring this up on the Papyrus-RT developer, or possibly the Papyrus developer, mailing list and not only here on the forum.
|
|
|
|
| Re: Problem setting up Papyrus-RT Dev Environment [message #1771617 is a reply to message #1771452] |
Mon, 28 August 2017 12:21 |
| Eclipse User |
|
|
|
Hi. Indeed, the problem seems to be that the Papyrus nightly repos are already on Photon (4.0.0) and our nightlies still depend on Oxygen (3.0.0).
Since there are currently no concrete plans for RT to move to Photon, I suggest using the "release" stream as Peter suggests.
Perhaps we should update our developer Oomph setup to use the p2 repo for the Papyrus streams/3.0-maintenance?
|
|
|
Powered by
FUDForum. Page generated in 0.23566 seconds
Home