Does Oomph's target platform task honor p2.httpRule=allow?

[phermsdorf]

Hi,

happy New Year! :)

Now the Question: we have a target platform definition which consumer multiple p2 update sites from an internal nexus instance which for various reasons still only uses http (not https).
When adding this target definition to an Oomph setup definition the target cannot be set when starting the newly provisioned eclipse (without a real concrete error).

When then pressing Cancel and opening the target file it can be successfully resoved and set.

We provision that Eclipse installation with -Dp2.httpRule=allow in the Eclipse.ini file to prevent the "automtic" upgrade from http to https which came with some Eclipse version.

Could it be that the import task does not care about that and tries to make the connection via https instead?

Any other ideas or suggestions what the problem could be?

Thank you.

Bye Peter

[merks]

Have you actually imported the project containing the *.target definition before trying to set/use it? E.g., for the Platform SDK setup we also use the *.target file and must import that project before using the *.target in the modular target task:

Everything to do with this is delegated to PDE and anything to do with network connections on a normal target location is delegated to p2...

[phermsdorf]

I think the project is imported beforehand.

This is the kind of error message i see (and from the not found artifacts i would suspect it actually "see's" the target platform definition)

Performing Target Platform My Target
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.setup.pde.impl.TargetPlatformTaskImpl.perform(TargetPlatformTaskImpl.java:298)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:3869)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil$1.run(SetupTaskPerformer.java:5210)
  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2457)
  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2482)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.performNeededSetupTasks(SetupTaskPerformer.java:5203)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:3803)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performTriggeredSetupTasks(SetupTaskPerformer.java:3778)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.perform(SetupTaskPerformer.java:3656)
  at org.eclipse.oomph.setup.ui.wizards.ProgressPage$9.run(ProgressPage.java:592)
  at org.eclipse.oomph.setup.ui.wizards.ProgressPage$11$1.run(ProgressPage.java:721)
  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
  ERROR: org.eclipse.pde.core code=0 Problems loading repositories
    ERROR: org.eclipse.pde.core code=0 Unable to locate installable unit com.company.babel.feature.feature.group/4.20.1
  ERROR: org.eclipse.pde.core code=0 Problems loading repositories
    ERROR: org.eclipse.pde.core code=0 Unable to locate installable unit org.eclipse.justj.openjdk.hotspot.jre.full.feature.group/[11.0.25,11.0.26)
  ERROR: org.eclipse.pde.core code=0 Problems loading repositories
    ERROR: org.eclipse.pde.core code=0 Unable to locate installable unit com.company.other.feature.feature.group/2.4.0
  ERROR: org.eclipse.pde.core code=0 Problems loading repositories
    ERROR: org.eclipse.pde.core code=0 Unable to locate installable unit org.eclipse.nebula.visualization.feature.feature.group/2.1.0.202106201019
    ERROR: org.eclipse.pde.core code=0 Unable to locate installable unit org.eclipse.nebula.paperclips.core/2.1.0.202106201019
    ERROR: org.eclipse.pde.core code=0 Unable to locate installable unit org.eclipse.nebula.paperclips.widgets/2.1.0.202106201019
    ERROR: org.eclipse.pde.core code=0 Unable to locate installable unit org.eclipse.nebula.widgets.opal.multichoice.feature.feature.group/1.0.0.202106201019
    ERROR: org.eclipse.pde.core code=0 Unable to locate installable unit 
org.eclipse.nebula.widgets.opal.commons.feature.feature.group/1.0.0.202106201019
  ERROR: org.eclipse.pde.core code=0 Problems loading repositories
    ERROR: org.eclipse.pde.core code=0 Unable to locate installable unit org.eclipse.gef.nl_de/3.7.0.v20111128043401
    ERROR: org.eclipse.pde.core code=0 Unable to locate installable unit org.eclipse.draw2d.nl_de/3.7.0.v20111128043401

When pressing Cancel after that error and then opening the .target file in that workspace let's resolve the target successfully.

In the target we use repository references like this
<repository id="myrepoid" location="http://build2.intern.company.de/p2/mirror/rcp_composite/"/>
which map the myrepoid to a definition in the settings.xml for authentication reasons ... but if it works in PDE i guess it should work here as well ...

How to further debug here?

[merks]

You could create a development environment with all the source for Oomph, PDE, and p2:

I think Oomph version tool will complain about some errors that you can ignore/delete.

From that you can debug launch a self-hosted IDE with the appropriate system properties set.

In that debug IDE you could import the project with the *.target, or copy it into a project in that workspace.

Then you can use Navigate -> Open Setup -> Workspace and create/copy your Oomph target task there. Then the Perform Setup Tasks will run in that debug IDE and you can debug anything there.

I'm not sure what else to suggest. There are no other clues in the error log view?

[phermsdorf]

Thanks @merks , the look at the error log view revealed something interesting: while browsing the error messages i realized that there are always coming new warning messages in regarding the use of the unsafe http protocol.

I then saw then the Loading Target Platform Action was running even though there was the error about setting the target platform.

I disabled the Target Platform step in my setup and now the setup runs and the target platform get's loaded - magically. I gues it could have to do with the Maven Import step which then maybe discovers a tycho target platform definition in that Project ?

Thanks again.
Bye Peter