[
https://issues.apache.org/jira/browse/FELIX-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931918#comment-15931918
]
Ralph Goers commented on FELIX-5592:
------------------------------------
If I get what you are suggesting, the Java 9 replacement classes would need to
have unique names or be in different packages. and then the code that wants to
use these would have to use the ServiceLoader to locate the implementations and
somehow pick the one for the current jdk. This seems like a lot more work than
what is required of the application for multi-release support. On the upside, I
suppose it would make debugging easier. But as far as I can tell, the only
reason for doing it with the service loader is to make OSGi "happy".
> 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)
