Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Classes found in the wrong directory: {META-INF/versions/9/module-info.class=module-info} #3514

Closed
rotty3000 opened this issue Nov 2, 2019 · 4 comments
Closed

Classes found in the wrong directory: {META-INF/versions/9/module-info.class=module-info} #3514

rotty3000 opened this issue Nov 2, 2019 · 4 comments

Comments

@rotty3000
Copy link
Contributor

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 -fixupmessages but you'd think the multi-release flag would capture that aspect and know what's going on.
@bjhargrave
Copy link
Member

See #2227. We still do not have any support for multi-release jars.

@rotty3000
Copy link
Contributor Author

Closing as duplicate.

@aalmiray aalmiray mentioned this issue Apr 19, 2021
Closed
@wa6smn
Copy link

wa6smn commented Jul 21, 2021

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?

@schulm
Copy link

schulm commented Nov 19, 2022

The issue can be ignored with:
-fixupmessages "Classes found in the wrong directory"; restrict:=error; is:=warning

sfeilmeier added a commit to OpenEMS/openems that referenced this issue May 19, 2023
@sfeilmeier
Update wrapper
ef8e0fe 
Apply workaround from bndtools/bnd#3514
chrisrueger added a commit to chrisrueger/jspecify that referenced this issue May 24, 2024
@chrisrueger
fix "Classes found in the wrong directory"
64520dd 
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)
@chrisrueger chrisrueger mentioned this issue May 24, 2024
Merged
chrisrueger added a commit to chrisrueger/jspecify that referenced this issue Jul 14, 2024
@chrisrueger
fix "Classes found in the wrong directory"
1b84ca4 
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)
cpovirk pushed a commit to chrisrueger/jspecify that referenced this issue Jul 15, 2024
@chrisrueger @cpovirk
fix "Classes found in the wrong directory"
fad4315 
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
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rotty3000 @bjhargrave @wa6smn @schulm