Classes found in the wrong directory: {META-INF/versions/9/module-info.class=module-info} #3514
Comments
|
See #2227. We still do not have any support for multi-release jars. |
|
Closing as duplicate. |
|
maven-bundle-plugin:4.2.1 still having issues Classes found in the wrong directory: {META-INF/versions/9/module-info.class=module-info}. Working with a felix OSGi container, JDK8 only. Is there Maven support to suppress the problem? |
|
The issue can be ignored with: |
sfeilmeier
added a commit
to OpenEMS/openems
that referenced
this issue
May 19, 2023
Apply workaround from bndtools/bnd#3514
chrisrueger
added a commit
to chrisrueger/jspecify
that referenced
this issue
May 24, 2024
dilemma: unfortunatelly bnd in 6.4.0 does not support multi-release jars. It starts being support in 7.0.0 but this requires min.JDK 17. So the only way is to suppress the warning via -fixupmessage (see bndtools/bnd#3514 and https://bnd.bndtools.org/instructions/fixupmessages.html)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As it turns out, even with
Multi-Release: true, bnd doesn't like finding classes in the multi version directories. We should try to handle this a little better.You can elide the error with
-fixupmessagesbut you'd think the multi-release flag would capture that aspect and know what's going on.The text was updated successfully, but these errors were encountered: