NSAmelchev opened a new pull request, #13665:
URL: https://github.com/apache/ignite/pull/13665

   IGNITE-28984 dropped the org.apache:apache parent because a newer version 
sets maven.compiler.release, and javac does not accept --add-exports (which 
Ignite needs for jdk.internal.* and sun.* packages) together with --release. 
The parent is restored at the current version, and the conflict is resolved the 
way Apache Flink does: the compiler and javadoc plugins get an explicit empty 
release override, so javac keeps using source/target, while the 
maven.compiler.release property stays defined for IDEs and the jar manifest.
   
   What comes back with the parent:
   
   LICENSE, NOTICE and DEPENDENCIES in every module jar and the 
Specification/Implementation manifest entries, as in 2.18.0 (currently only the 
shaded ignite-core jar has the license files).
   The apache-release profile (signing, source release, checksums) referenced 
by the release instructions.
   Managed plugin versions, so maven-install-plugin and others no longer fall 
back to Maven defaults. The distributionManagement duplicated by IGNITE-28995 
is removed again.
   
   Related build hygiene in the same POMs: maven-jar-plugin version is now 
managed for all modules (previously 3.4.1 in most modules and 3.5.0 in a few), 
the unused maven.surefire.plugin.version/maven.failsafe.plugin.version 
properties are dropped and benchmarks use the common surefire.version, the 
verbose javadoc flag is removed (it produced most of the build log), and 
ignite-checkstyle is compiled with --release 17.
   
   Visible changes in artifacts: license files and manifest entries listed 
above, Java-Version: 17 in manifests, fixed entry timestamps in jars 
(reproducible builds, as in releases up to 2.18.0). No Java sources are changed.


-- 
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]

Reply via email to