Open PavelTurk opened 17 hours ago
Hi @PavelTurk,
While ideally we could have a text representation of module-info.class
in our *-source.jar
artifacts, the BND Maven plugin that generates them, only provides the compiled version.
I don't believe this is a big problem, since the information in module-info.class
can be extracted quite easily by any decompiler or jar -d
.
Description
As I found out
module-info
is generated automatically in 3.0.0-beta3. At the same time its source (module-info.java
) must be present in*-3.0.0-beta3-sources.jar
files. For example, there is nomodule-info.java
inlog4j-core-3.0.0-beta3-sources.jar
see [1], but there is amodule-info.class
inlog4j-core-3.0.0-beta3.jar
see [2].The absence of module-info.java makes it difficult for library user to get important information about module, for example, its dependencies, provided and used services etc.
[1] https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-core/3.0.0-beta3/log4j-core-3.0.0-beta3-sources.jar [2] https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-core/3.0.0-beta3/log4j-core-3.0.0-beta3.jar