stechio commented on issue #539:
URL:
https://github.com/apache/maven-jar-plugin/issues/539#issuecomment-5230186996
@elharo:
> No. it is fixed. Issue trackers are tracking code. not the release.
As @pzygielo noted, the fix seems to have been applied only to `master`
branch (version 4 beta); **the brand-new stable version (3.5.1) still behaves
the wrong way**: it adds `Build-Jdk-Spec` and `Build-Tool-Jdk-Spec` entries to
the MANIFEST despite `addBuildEnvironmentEntries` is set to `false`:
```xml
<plugin>
<artifactId>maven-jar-plugin</artifactId>
<version>3.5.1</version>
<configuration>
<archive>
<manifest>
<addBuildEnvironmentEntries>false</addBuildEnvironmentEntries>
<addDefaultEntries>false</addDefaultEntries>
<addDefaultImplementationEntries>true</addDefaultImplementationEntries>
<addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
</manifest>
<manifestEntries>
<Java-Version>17</Java-Version>
</manifestEntries>
</archive>
</configuration>
</plugin>
```
Result:
```
Manifest-Version: 1.0
Specification-Title: xxxx-xxx
Specification-Version: 2.0
Specification-Vendor: xxxx.xxx
Implementation-Title: xxxx-xxx
Implementation-Version: 2.0-SNAPSHOT
Implementation-Vendor: xxxx.xxx
Java-Version: 17
Build-Jdk-Spec: 21
Build-Tool-Jdk-Spec: 25
````
**Since the current production-grade release is 3.5.x, its fix should be
prioritized over the dev branch**, thanks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
