Just so it's propagated when do bumps and reduce amount of revbumps
needed later (given qtwebengine is a huge package), it will be needed
whenever libxml2-2.14 is added & keyworded/unmasked with a new soname.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
- switches to default slot (SLOT=0)
- consumers should be switched on version bumps
Signed-off-by: Volkmar W. Pogatzki <gentoo@pogatzki.net>
Signed-off-by: Florian Schmaus <flow@gentoo.org>
See https://openjdk.org/jeps/238
This commit adds basic support for building multi-release jar files.
A multi-release jar file has release-specific classes in directories
under META-INF/versions/ and its MANIFEST.MF contains a line with
'Multi-Release: true'.
The probably most common case of a multi-release jar file has only one
single such class which is 'META-INF/versions/9/module-info.class'.
To do so, we add JAVA_RELEASE_SRC_DIRS as a new eclass variable which
is also used as the condition to trigger the new functionality. A new
local variable 'multi_release' is added to the packaging section (the
part using the 'jar -create' command). Only when JAVA_RELEASE_SRC_DIRS
is set, additional actions take place:
- Compilation (those are the parts with 'ejavac') will additionally loop
over the release-specific directories listed in JAVA_RELEASE_SRC_DIRS
and compile the release-specific classes into corresponding directories
under target/versions/.
- Packaging (the part using the 'jar -create' command) will add the
details to the 'multi_release' variable so that the release-specific
directories under target/versions/ can be packaged into the jar file.
This commit also adds funtionality to generate 'module-info.java' files.
It is useful for packages where module-info.java is not provided in the
sources but needs to be generated by the build system. We use the built-in
jdeps function with the --generate-module-info option which became available
with Java 11.
It generates the module-info.java file based on an intermediate jar file
and places it in the "${JAVA_MODULE_INFO_OUT}/${JAVA_INTERMEDIATE_JAR_NAME}/"
directory.
For this purpose we add three new eclass variables:
- JAVA_INTERMEDIATE_JAR_NAME
- JAVA_MODULE_INFO_OUT
- JAVA_MODULE_INFO_RELEASE
When both JAVA_MODULE_INFO_OUT and JAVA_INTERMEDIATE_JAR_NAME are defined in the
ebuild we
- compile the sources still without module-info
- package them as an intermediate {JAVA_INTERMEDIATE_JAR_NAME}.jar
- let java-pkg-simple_generate-module-info generate the module-info
- compile module-info.java with the --patch-module option
- package the final jar file including the module-info.class
When the JAVA_MODULE_INFO_RELEASE variable is set, module-info.java is
generated into a release specific directory
"${JAVA_MODULE_INFO_OUT}/${JAVA_INTERMEDIATE_JAR_NAME}/versions/{JAVA_MODULE_INFO_RELEASE}".
Bug: https://bugs.gentoo.org/900433
Signed-off-by: Volkmar W. Pogatzki <gentoo@pogatzki.net>
Signed-off-by: Florian Schmaus <flow@gentoo.org>
Maciej Barć
William Hubbs
Ionen Wolkens
Matt Turner
Hans de Graaff
Volkmar W. Pogatzki
Arsen Arsenović
Anna (cybertailor) Vyalkova
Joonas Niilola
Yixun Lan
Florian Schmaus
Mario Haustein
Alexander Kurakin