Closed jesse-gallagher closed 2 months ago
I ran into a case where an OSGi bundle has a Bundle-ClassPath reference to a JAR that isn't actually in the bundle. In situations like this, there should not be a dependency entry in the generated POM.
dependency
Heh, turns out I forgot this was already fixed via https://github.com/OpenNTF/p2-layout-provider/pull/44
I ran into a case where an OSGi bundle has a Bundle-ClassPath reference to a JAR that isn't actually in the bundle. In situations like this, there should not be a
dependency
entry in the generated POM.