[
https://issues.apache.org/jira/browse/FELIX-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931972#comment-15931972
]
Ralph Goers commented on FELIX-5592:
------------------------------------
Interestingly, we want to use a multi-release jar for exactly the same reason
as LWJGL. Log4j 2 has to walk the stack to get location information into the
logs.
A major problem with your proposal is we don't want more jars. We have an API
jar and an impl jar and then jars for a whole bunch of optional things. We
don't want users on Java 9 to have to include an extra jar to get better
performance, nor do we want user's to have to pick and choose between jars that
are compiled for their environment. Log4j 2 as a whole compiles with Java 7. To
get the build to work I did have to create a maven module that compiles with
Java 9, but the classes generated there are copied into either the API or impl
jar as appropriate.
This all works fine except for the Maven bundle plugin.
> Maven bundle plugin does not support Java 9 Multi-Release jars
> --------------------------------------------------------------
>
> Key: FELIX-5592
> URL: https://issues.apache.org/jira/browse/FELIX-5592
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-3.2.0
> Reporter: Ralph Goers
>
> Log4j 2 currently packages its jars with the maven-bundle-plugin. To support
> Java 9 we are moving towards using Multi-Release jars to pick up the Java 9
> features. However, when the Maven bundle plugin encouters classes in
> META-INF/versions/9 it emits an error message saying "Classes found in the
> wrong directory:", which is incorrect for a Multi-Release jar in Java 9.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
