-
Notifications
You must be signed in to change notification settings - Fork 420
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.
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
picocli-4.6.0.jar requires groovy for OSGi but not for Maven #1329
Labels
Milestone
Comments
remkop
added
type: bug 🐛
theme: build
An issue or change related to the build system
labels
Feb 20, 2021
remkop
added a commit
that referenced
this issue
Feb 20, 2021
@Fiouz Thank you for raising this! I pushed a fix that I believe fixes the issue. Can you verify? |
The change on the current |
Thank you for the confirmation! |
MarkoMackic
pushed a commit
to MarkoMackic/picocli
that referenced
this issue
Oct 17, 2021
…not require groovy
MarkoMackic
added a commit
to MarkoMackic/picocli
that referenced
this issue
Oct 17, 2021
… should not require groovy" This reverts commit ab03e80.
MarkoMackic
added a commit
to MarkoMackic/picocli
that referenced
this issue
Oct 17, 2021
… should not require groovy" This reverts commit ab03e80.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since 4.6.0, the
META-INF/MANIFEST.MF
file of the main artifact contains the following line:This does not seem correct as there is a dedicated artifact for Groovy support, and, since it does not match the
pom.xml
definition, it confuses consumers that rely on the POM definition to construct their OSGi repository:https://docs.osgi.org/specification/osgi.core/7.0.0/framework.module.html#framework.module.importpackage
The text was updated successfully, but these errors were encountered: