Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: C:\java\apache-maven-3.9.0
Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse Adoptium\jdk-8.0.362.9-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584) Maven home: C:\java\apache-maven-3.9.0 Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse Adoptium\jdk-8.0.362.9-hotspot\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Description
How do I prevent the maven-bundle-plugin 5.1.8 to generate MANIFEST.MF/Require-Capability?
It seems that the instruction Require-Capability is not used precisely, it adds to the entry rather than set it.
In my example, for legacy requirements, Require-Capability must be absent, and I find no way to implement this. Using:
<Require-Capability></Require-Capability>
or
<Require-Capability>$${def;empty}</Require-Capability>
Cause the following to be generated for my Maven module:
Require-Capability: osgi.extender;filter:="(&(osgi.extender=osgi.compo
nent)(version>=1.3.0)(!(version>=2.0.0)))",osgi.ee;filter:="(&(osgi.e
e=JavaSE)(version=1.8))"
Any ideas?