Eclipse Community Forums: Oomph » Setup gets broken for unsupported target platforms

Help

Home

Home » Eclipse Projects » Oomph » Setup gets broken for unsupported target platforms

Show: Today's Messages :: Show Polls :: Message Navigator

Setup gets broken for unsupported target platforms [message #1806275]

Tue, 07 May 2019 10:53

Aparna Argade

Messages: 53
Registered: October 2010

Member

Hi,
Oomph setup by default shows all the eclipse releases (e.g. 2018-12, 2019-03, etc.) as 'Target Platform' on Variables page.
But our project does not do quarterly release and we do not create a .target file for each such release.
We provide defaultValue as per our last release in setup:VariableTask section.

But still if some user explicitly changes the target platform(e.g. default 'Photon' but changes to 2019-03), then the setup gives error-
ERROR: org.eclipse.equinox.p2.director code=0 Missing requirement: artificial_root requires SOME_FEATURE_NAME but it could not be found.

This SOME_FEATURE_NAME is not listed in baseline.target.

Is there any option so that only supported targets are shown in the combo box of targets on Variables page?
Or- Should we include that SOME_FEATURE_NAME to baseline target and maybe includeAllRequirements=false in oomph setup to make setup work for all releases?
Please suggest.
Regards,
Aparna

Additional details are as follows-
Offline = false
Mirrors = true
Include All Platforms = false
Include All Requirements = true
Include Binary Equivalents = true
Include Sources = false
Adding repository http://download.eclipse.org/eclipse/updates/4.11/R-4.11-201903070500
Calculating requirements and dependencies.
Cannot complete the request. Generating details.
ERROR: org.eclipse.pde.core code=0 Problems occurred while resolving the target contents
at org.eclipse.oomph.util.OomphPlugin.coreException(OomphPlugin.java:280)
at org.eclipse.oomph.util.pde.TargetPlatformUtil.activateTargetDefinition(TargetPlatformUtil.java:151)
at org.eclipse.oomph.targlets.internal.core.TargletContainer.forceUpdate(TargletContainer.java:792)
at org.eclipse.oomph.setup.targlets.impl.TargletTaskImpl$4.run(TargletTaskImpl.java:1167)
at org.eclipse.oomph.util.pde.TargetPlatformUtil.runWithTargetPlatformService(TargetPlatformUtil.java:120)
at org.eclipse.oomph.setup.targlets.impl.TargletTaskImpl.perform(TargletTaskImpl.java:1033)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:3335)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.access$1(SetupTaskPerformer.java:3278)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil$1.run(SetupTaskPerformer.java:4514)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.performNeededSetupTasks(SetupTaskPerformer.java:4508)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.access$0(SetupTaskPerformer.java:4506)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:3269)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performTriggeredSetupTasks(SetupTaskPerformer.java:3244)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.perform(SetupTaskPerformer.java:3144)
at org.eclipse.oomph.setup.ui.wizards.ProgressPage$9.run(ProgressPage.java:575)
at org.eclipse.oomph.setup.ui.wizards.ProgressPage$11$1.run(ProgressPage.java:701)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
ERROR: org.eclipse.equinox.p2.director code=10053 Cannot complete the install because one or more required items could not be found.
ERROR: org.eclipse.equinox.p2.director code=0 Software being installed: artificial_root 1.0.0.v1557224990421
ERROR: org.eclipse.equinox.p2.director code=0 Missing requirement: artificial_root 1.0.0.v1557224990421 requires 'org.eclipse.equinox.p2.iu; org.eclipse.nebula.widgets.nattable.core.feature.feature.group 0.0.0' but it could not be found

Report message to a moderator

Re: Setup gets broken for unsupported target platforms [message #1806298 is a reply to message #1806275]

Tue, 07 May 2019 13:22

Ed Merks

Messages: 30882
Registered: July 2009

Senior Member

You can use a different variable to choose your own repository list and set the other existing variable to None explicitly so that you don't inherit any update sites from the Eclipse.org Project Catalog's targlet task. That way you control the choices and can add new choices only when you create a new repository lists in your targlet task.

Report message to a moderator

Re: Setup gets broken for unsupported target platforms [message #1806313 is a reply to message #1806298]

Tue, 07 May 2019 16:09

Aparna Argade

Messages: 53
Registered: October 2010

Member

Thanks Ed! This will be the right way. Is there any example for this?

Report message to a moderator

Re: Setup gets broken for unsupported target platforms [message #1806324 is a reply to message #1806313]

Tue, 07 May 2019 17:57

Ed Merks

Messages: 30882
Registered: July 2009

Senior Member

You can look in the existing project catalog (visible in any setup editor when you tell it to show all resources via the toolbar, or using Navigate -> Open Setup's submenus) to see how the existing variable is defined (i.e., with nested choices), and you can copy that pattern to define your own variable (different name) with a list a of choices (arbitrary names) and you can change your targlet to use that variable instead of the existing variable.

Report message to a moderator

Previous Topic:	Eclipse installer error
Next Topic:	What's wrong with my setup file ?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Feb 17 19:18:48 GMT 2020

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter