Re: [papyrus-rt-dev] Problems with Oomph developer setup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [papyrus-rt-dev] Problems with Oomph developer setup

From: Peter Cigéhn <peter.cigehn@xxxxxxxxx>
Date: Tue, 28 Mar 2017 15:35:51 +0200
Delivered-to: papyrus-rt-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/papyrus-rt-dev>
List-help: <mailto:papyrus-rt-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev>, <mailto:papyrus-rt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/papyrus-rt-dev>, <mailto:papyrus-rt-dev-request@eclipse.org?subject=unsubscribe>

Hi,

Okay, so the developer setup is in a "catch 22" right now, since the installer is already on Oxygen (with version 1.8), but we still use the Neon version of the JUnit utility. I guess that this will then resolve itself as soon as we get everything up on Oxygen then... :)

/Peter Cigéhn

On 28 March 2017 at 15:32, Remi Schnekenburger <rschnekenburger@xxxxxxxxxxxxxxxxx> wrote:

I thought there was an issue in the Papyrus-Neon nightly, according to OP. And the Oxygen stream is already updated to 3.0.0 as upper bound?

2017-03-28 15:25 GMT+02:00 Christian Damus <give.a.damus@xxxxxxxxx>:

Hi, Rémi,

Sure, I can take care of the developer setup.

But why a patch for the JUnit utilities in Neon? This version problem in e4 is only in the Oxygen stream.

Cheers,

Christian

On Mar 28, 2017, 09:23 -0400, Remi Schnekenburger <rschnekenburger@eclipsesource.com>, wrote:

Hi Christian,

Thanks for your reply. So I will propose a patch for version number of o.e.p.junit.utils for Neon. Master (oxygen) has already a fix for this upper bound [1]

For the installer, I would vote for a move as a peer to the releng project.

Cheers,

Rémi

[1] Commit 814e53cdc604131f93925eef8d7f4bd31edd5061

2017-03-28 13:47 GMT+02:00 Christian Damus <give.a.damus@xxxxxxxxx>:

Hi,

Indeed, it should be safe to update this upper bound because the particular API-incompatible change in this e4 bundle was discussed on the cross-project-devs list and was in an interface that is not used by these JUnit utilities. But, once the major version is updated, breaking changes can continue to happen that then break clients that thought they were okay, so constant vigilance would be required.

Anyways, it used to be that selecting a project for import in Oomph did not implicitly select all sub-projects. If that has changed, then probably the Installer should not have been a new sub-project, but a peer to the Releng project, sorry. Should I change that?

Cheers,

Christian

On Mar 28, 2017, 05:01 -0400, Remi Schnekenburger <rschnekenburger@eclipsesource.com>, wrote:

Hi,

I can only reply from dev point of view on that one. The implicit rule on dependencies is to reject the next major version, until we are sure API evolution on the next version is still compatible with our component. That is the reason why there is initially this upper bound of 2.0.0.

The plugin o.e.p.junit.utils has a dependency to e4.ui.model.workbench as it has some convenient rules for JUnit tests to show/hide some views, and manage the layout of these views and the Papyrus editor itself, which is done in Eclipse by the e4.model.workbench plugin.

The issue there is that the oomph installer proposed a new version out of the release train, which is quite invisible to the Papyrus project. It is however probably possible to update the dependency upper bound of the junit.utils plugin. I do not know exactly what were the API evolutions on e4.model.workbench plugin. Maybe Christian who worked more on the installer has a better understanding of the evolutions.

Cheers,

Rémi

2017-03-28 9:39 GMT+02:00 Peter Cigéhn <peter.cigehn@xxxxxxxxx>:

Hi,

I did bump into this issue as well, and concluded that this only happens if you include the Installer subproject, which is now nested under the Releng subproject (so if you don't pay attention, you get the Installer subproject "for free" when selecting the Releng subproject).

The conflict that then appears is due to that the Oomph installer requires version 2.0.0 of org.eclupse.e4.ui.model.workbench, whereas (for some reason), the JUnit utility from Papyrus has an upper limit for the same bundle that does not allow 2.0.0 to be used.

I avoided this by *not* including the Installer subproject in my workspace. But I guess it really should be looked into why the JUnit utility (org.eclipse.papyrus.junit.utils) really have put an upper bound of 2.0.0 on the org.eclipse.e4.ui.model.workbench. Why do the JUnit utility even have this dependency in the first place?

/Peter Cigéhn

On 27 March 2017 at 22:30, Ernesto Posse <eposse@xxxxxxxxxxxxx> wrote:

Hello. There seems to be a newly introduced issue, probably in Papyrus because performing setup tasks results in the exception below. Both Young-Soo and I see the same problem and both with and without a shared p2 pool. The exception occurs right after fetching the Papyrus Neon nightly. The only thing that we can think of is that we both installed SysML 1.4, but that should not affect an installation that doesn't share a p2 pool, right? Any ideas about what could be the problem? Can anyone else reproduce it?

Fetching content.xml.xz from https://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Developer/lastSuccessfulBuild/artifact/repository/ (9.91kB)

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.targlets.int ernal.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.v1490646303230

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 Eclipse Workbench Model 1.2.0.v20160229-1459 (org.eclipse.e4.ui.model.workbench 1.2.0.v20160229-1459)

ERROR: org.eclipse.equinox.p2.director code=0 Eclipse Workbench Model 2.0.0.v20170228-1842 (org.eclipse.e4.ui.model.workbench 2.0.0.v20170228-1842)

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.v1490646303230

ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.oomph.setup.installer.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.v1490646303230

ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.junit.utils 0.0.0

ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:

ERROR: org.eclipse.equinox.p2.director code=0 From: Eclipse 4 Rich Client Platform 1.6.0.v20170326-1903 (org.eclipse.e4.rcp.feature.group 1.6.0.v20170326-1903)

ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.e4.ui.model.workbench [2.0.0.v20170228-1842]

ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:

ERROR: org.eclipse.equinox.p2.director code=0 From: Oomph Setup Installer 1.8.0.v20170326-2000 (org.eclipse.oomph.setup.installer.feature.group 1.8.0.v20170326-2000)

ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.rcp.feature.group [4.7.0.v20170326-2000]

ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:

ERROR: org.eclipse.equinox.p2.director code=0 From: Utils classes for JUnit tests 2.0.1.201703260230 (org.eclipse.papyrus.junit.utils 2.0.1.201703260230)

ERROR: org.eclipse.equinox.p2.director code=0 To: bundle org.eclipse.e4.ui.model.workbench [1.2.0,2.0.0)

ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:

ERROR: org.eclipse.equinox.p2.director code=0 From: Eclipse RCP 4.7.0.v20170326-2000 (org.eclipse.rcp.feature.group 4.7.0.v20170326-2000)

ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.e4.rcp.feature.group [1.6.0.v20170326-1903]

--

Ernesto Posse

Zeligsoft

_______________________________________________
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

--

Remi Schnekenburger

Senior Software Architect / General Manager
EclipseSource Paris

Email: rschnekenburger@eclipsesource.com
Web: http://eclipsesource.com/paris
Phone: +33 1 85 41 08 65

German Phone: +49 89 21 555 30 - 25

Fax: +49 89 21 555 30 - 19

Hangouts: rschnekenburger@eclipsesource.com

EclipseSource France SAS
7 rue de la Croix Martre
91120 Palaiseau

General Manager: Remi Schnekenburger

Registered Office: 7 rue de la Croix Martre, 91120 Palaiseau, France

Commercial Register 824 977 516  R.C.S. EVRY

_______________________________________________
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

--

Remi Schnekenburger

Senior Software Architect / General Manager
EclipseSource Paris

Email: rschnekenburger@eclipsesource.com
Web: http://eclipsesource.com/paris
Phone: +33 1 85 41 08 65

German Phone: +49 89 21 555 30 - 25

Fax: +49 89 21 555 30 - 19

Hangouts: rschnekenburger@eclipsesource.com

EclipseSource France SAS
7 rue de la Croix Martre
91120 Palaiseau

General Manager: Remi Schnekenburger

Registered Office: 7 rue de la Croix Martre, 91120 Palaiseau, France

Commercial Register 824 977 516  R.C.S. EVRY

_______________________________________________
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

--
Remi Schnekenburger

Senior Software Architect / General Manager
EclipseSource Paris

Email: rschnekenburger@eclipsesource.com
Web: http://eclipsesource.com/paris
Phone: +33 1 85 41 08 65
German Phone: +49 89 21 555 30 - 25
Fax: +49 89 21 555 30 - 19
Hangouts: rschnekenburger@eclipsesource.com

EclipseSource France SAS
7 rue de la Croix Martre
91120 Palaiseau

General Manager: Remi Schnekenburger
Registered Office: 7 rue de la Croix Martre, 91120 Palaiseau, France
Commercial Register 824 977 516  R.C.S. EVRY

_______________________________________________
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

References:
- [papyrus-rt-dev] Problems with Oomph developer setup
  - From: Ernesto Posse
- Re: [papyrus-rt-dev] Problems with Oomph developer setup
  - From: Peter Cigéhn
- Re: [papyrus-rt-dev] Problems with Oomph developer setup
  - From: Remi Schnekenburger
- Re: [papyrus-rt-dev] Problems with Oomph developer setup
  - From: Christian Damus
- Re: [papyrus-rt-dev] Problems with Oomph developer setup
  - From: Remi Schnekenburger
- Re: [papyrus-rt-dev] Problems with Oomph developer setup
  - From: Christian Damus
- Re: [papyrus-rt-dev] Problems with Oomph developer setup
  - From: Remi Schnekenburger

Prev by Date: Re: [papyrus-rt-dev] Problems with Oomph developer setup
Next by Date: Re: [papyrus-rt-dev] Problems with Oomph developer setup
Previous by thread: Re: [papyrus-rt-dev] Problems with Oomph developer setup
Next by thread: [papyrus-rt-dev] Protocol state machines (Was Re: First 0.9.0 bug (maybe))
Index(es):
- Date
- Thread

Breadcrumbs