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

Support for Multi-release JAR #242

Closed
sparsick opened this issue Mar 10, 2021 · 0 comments · Fixed by #251
Closed

Support for Multi-release JAR #242

sparsick opened this issue Mar 10, 2021 · 0 comments · Fixed by #251
Assignees
@sparsick
Milestone
1.6.0

Comments

@sparsick
Copy link
Collaborator

Currently, the p2 maven plugin can't manage multi-release JARS because of a bug in the embedded BND tool.

A possible workaround is to add BND instruction -fixupmessages "Classes found in the wrong directory";restrict:=error;is:=warning as default instruction into the plugin till BND tool has a fix for its issue.
@sparsick sparsick mentioned this issue Mar 26, 2021
Closed
@sparsick sparsick added this to the 1.6.0 milestone Mar 26, 2021
@sparsick sparsick self-assigned this Mar 28, 2021
@sparsick sparsick linked a pull request Apr 3, 2021 that will close this issue
FIxed #242: Support for Multi-release JAR #251
Merged
sparsick added a commit that referenced this issue Apr 6, 2021
@sparsick
Merge pull request #251 from sparsick/242-multi-release
891adfe 
FIxed #242:  Support for Multi-release JAR
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sparsick sparsick

Labels
None yet
Projects
None yet
Milestone
1.6.0
Development

Successfully merging a pull request may close this issue.

FIxed #242: Support for Multi-release JAR sparsick/p2-maven-plugin
1 participant
@sparsick