The picocli-groovy
module should declare groovy-all
as dependency
#1613
Labels
lang: groovy
Groovy-related
theme: build
An issue or change related to the build system
theme: module
An issue or change related to JPMS modules
type: dependency 📚
Milestone
History: the
picocli.groovy
package used to be bundled inside thepicocli.jar
, until it was split off into a separate artifactpicocli-groovy
in version 4.0.It was not desirable (#232) for the
picocli.jar
to depend ongroovy-all
(there was a version 2.0.2 published that had this dependency), and this dependency was removed in picocli 2.0.3.In picocli 2.0.3, the
groovy-all
dependency was changed to acompileOnly
dependency.This
compileOnly
build configuration was retained even when thepicocli.groovy
packages were moved into the separatepicocli-groovy
module.The POM for
picocli-groovy
now looks like this:This is incorrect, since various classes in the
picocli.groovy
packages expose Groovy APIs.From 4.7.0, the picocli-groovy POM will reflect this:
This also aligns the Maven dependency in line with the
module-info
declaration:The text was updated successfully, but these errors were encountered: