Californium removed?

Nadahar · April 24, 2025, 6:56pm

I think that will most likely fix it. There’s a problem with 7.1 that has been fixed, but the fix won’t be released until 7.2 is released:

github.com/bndtools/bnd

Bnd Run File Editor: “Resolve” button stopped working in Maven workspaces since Bndtools 7.1.0

opened 10:38PM - 30 Nov 24 UTC

closed 01:55PM - 02 Dec 24 UTC

sad-poet

Starting with Bndtools 7.1.0, opening a *.bndrun file in a Maven-only workspace …and clicking the *Resolve* button results in a NullPointerException (see below). The problem is not reproduced when using Bndtools 7.0.0. # Environment * Bndtools 7.1.0.202411251545 (installed from https://bndtools.org/bndtools.p2.repo/7.1.0/) * `Git-Descriptor: 7.0.0.DEV-1660-g47e504d78` * `Git-SHA: 47e504d7881ba466703c55a8dca7b0578561582d` * Eclipse Temurin JDK 21.0.5 * Eclipse IDE for Java Developers 2024-09 * Eclipse Java Development Tools 3.19.600.v20240903-0240 * Eclipse PDE is not installed * Apache Maven 3.9.9 * bnd-maven-plugin 7.1.0 * Devuan GNU+Linux codename Ceres (corresponding to Debian sid/unstable) It was also possible to reproduce the error using Eclipse 2024-12 preview version, and on Windows 11. # Steps to reproduce 1. Install Eclipse IDE (from Eclipse Installer) and latest Bndtools (from Eclipse Marketplace Client), including Bndtools m2e integration feature. 2. Clone the example project and open it in Eclipse IDE: https://github.com/sad-poet/bndtools-resolve-npe-reproducer 4. Open app/app.bndrun file in Bnd Run File Editor. 5. Click Resolve button. # Expected result There should be no error. A *Resolution Results* window should open, displaying the required resources used to create the Run Bundles list. # Actual result The following error message is displayed in the *Resolution Results* window: ``` Exception during resolution. java.lang.NullPointerException: Cannot invoke "aQute.bnd.build.Project.get(String)" because "project" is null at biz.aQute.resolve.RunResolution.resolve(RunResolution.java:101) at org.bndtools.core.resolve.ResolveOperation.lambda$run$0(ResolveOperation.java:62) at org.bndtools.core.resolve.ResolveOperation.coordinate(ResolveOperation.java:102) at org.bndtools.core.resolve.ResolveOperation.run(ResolveOperation.java:52) at org.bndtools.core.resolve.ResolveJob.run(ResolveJob.java:89) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) ``` ![screenshot](https://github.com/user-attachments/assets/f9db767a-2a59-43c6-bc43-860129645da9) No new errors appear in the Eclipse’s *Error Log* view. The problem persists in all Maven projects that use bnd-maven-plugin. I was also able to reproduce the error when trying to resolve the app/app.bndrun file in a different example project found at https://github.com/fipro78/osgi-jakartars/tree/main/jakartars. # Workaround If bnd-resolver-maven-plugin is set up, the command line `mvn bnd-resolver:resolve` can be used and works as expected.

As I understand it, 7.1 is “broken”. This issue has also been discussed on this forum earlier: