Open laeubi opened 9 months ago
Do we have a fix for this? or any workaround to apply? We are also having the same constraint and the maven builds are failing. Please advise.
I fear now one has worked on this until now, so the only option is to provide that dependency.
Same issue s [ERROR] Missing requirement: org.bndtools.headless.build.manager 7.0.0.202310060912 requires 'osgi.service; (objectClass=org.bndtools.headless.build.manager.api.HeadlessBuildPlugin)' but it could not be found [ERROR] Cannot satisfy dependency: com.st.stellar.ui.templates 1.1.0.qualifier depends on: osgi.bundle; org.eclipse.pde.ui 0.0.0 [ERROR] Cannot satisfy dependency: org.eclipse.pde.bnd.ui 1.1.100.v20240806-2133 depends on: java.package; org.bndtools.headless.build.manager.api [1.1.0,2.0.0) [ERROR] Cannot satisfy dependency: org.eclipse.pde.ui 3.15.300.v20240815-2201 depends on: osgi.bundle; org.eclipse.pde.bnd.ui 1.0.0: See log for details
It's really hard to find the providers of these service registrations, but the do exist. These are all in the platform's target platform:
We don't know how you've defined your target platform. Try adding this:
You can also get them from here:
You are right i am on the target platform 2024-09 (eclipse official update site)
Build is OK in updating pom as below
`
<dependency>
<groupId>org.bndtools</groupId>
<artifactId>org.bndtools.headless.build.plugin.gradle</artifactId>
<version>7.0.0</version>
<scope>compile</scope>
<optional>false</optional>
</dependency>
</dependencies>`
I am trying to update with your update site Thank you for your support
See this comment here:
https://github.com/eclipse-equinox/p2/blob/57ecc5a05ba4420f4983be2c27832fe139ab5d09/bundles/org.eclipse.equinox.p2.publisher.eclipse/src/org/eclipse/equinox/p2/publisher/eclipse/BundlesAction.java#L392
Currently P2 generates for example when using this manifest headers:
the following requirement:
<requiredProperties namespace='osgi.service' match='(objectClass=org.bndtools.headless.build.manager.api.HeadlessBuildPlugin)' min='0'/>
this has some drawbacks so one can't choose for the effectiveness in a P2 resolve operation should apply or not.
I therefore would suggest that we transform this into something like
filter="(osgi.effective.active=true)"
so one can choose in the resolve context if such a requirement is to be considered or not.