Problem setting up Eclipse Platform/UI workspace with Oomph (2025-12 and 2025-09)

[lathapatil]

Hello,

I am trying to set up the Eclipse Platform and UI workspace using the Oomph installer (Tried both 2025-12 and 2025-09 )
My Environment:
Windows 11
Java 21
Network is via corporate proxy

During setup I encounter errors while resolving the target contents. The log shows:

ERROR: org.eclipse.pde.core code=0 Problems occurred while resolving the target contents
at org.eclipse.oomph.util.OomphPlugin.coreException(OomphPlugin.java:296)
at org.eclipse.oomph.util.pde.TargetPlatformUtil.activateTargetDefinition(TargetPlatformUtil.java:151)
at org.eclipse.oomph.targlets.internal.core.TargletContainer.forceUpdate(TargletContainer.java:943)
at org.eclipse.oomph.setup.targlets.impl.TargletTaskImpl$4.run(TargletTaskImpl.java:1244)
at org.eclipse.oomph.util.pde.TargetPlatformUtil.runWithTargetPlatformService(TargetPlatformUtil.java:120)
at org.eclipse.oomph.setup.targlets.impl.TargletTaskImpl.perform(TargletTaskImpl.java:1091)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:3876)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil$1.run(SetupTaskPerformer.java:5217)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2505)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2533)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.performNeededSetupTasks(SetupTaskPerformer.java:5210)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:3810)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performTriggeredSetupTasks(SetupTaskPerformer.java:3785)
at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.perform(SetupTaskPerformer.java:3663)
at org.eclipse.oomph.setup.ui.wizards.ProgressPage$10.run(ProgressPage.java:612)
at org.eclipse.oomph.setup.ui.wizards.ProgressPage$12$1.run(ProgressPage.java:741)
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.v1758520882475
ERROR: org.eclipse.equinox.p2.director code=0 Missing requirement: XPathTest Model 0.4.0.v20250922-113120 (org.eclipse.e4.emf.xpath.test 0.4.0.v20250922-113120) requires 'osgi.bundle; org.apache.commons.jxpath 0.0.0' but it could not be found
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.v1758520882475
ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.equinox.p2.iu; org.eclipse.e4.emf.xpath.test 0.0.0
Took 6 seconds.
There are failed tasks.
Press Back to choose different settings or Cancel to abort.

Any guidance on resolving this would be very helpful.

[merks]

There is no longer that requirement in master for really quite long now:

Of course it's also been removed from the *.target too.

The default variables always create new clones, so I suspect you you have an old clone so I suspect you've configure things so that there is a single clone location shared across IDEs/workspace which I personally don't think is so ideal but some people want it that way.

Orbit does still have that bundle but with a new BSN, org.apache.commons.commons-jxpath, and with the CVE fixed (apparently).

[lathapatil]

@merks Thanks for the quick reply.

It turns out the issue was on my side - the Oomph variables were still pointing to my old fork, which hadn’t been synced for quite some time. I had assumed it would default to the official Eclipse Platform and UI repositories
Appreciate the help and clarifications!

[merks]

I prefer never to clone a fork URI, but rather to add a remote for the fork:

That way I never have to sync my fork and I always can pull the latest from the actual clone...

[lathapatil]

That’s a good point. I normally use the same setup for my Eclipse repositories (cloning the official repo and adding my fork as a remote). Somehow for this one I must have missed it, or I don’t remember when I switched it to clone from my fork. Thanks for pointing it out.