slachiewicz opened a new pull request, #1035:
URL: https://github.com/apache/maven-enforcer/pull/1035
Groovy-backed counterpart of `evaluateBeanshell`, which is deprecated ahead
of the BeanShell retirement (apache/maven#13207). Same shape: `condition`
(Maven `${…}` interpolated first, then evaluated by `GroovyShell`, must yield a
boolean) and `message`.
Groovy is an `optional` dependency of enforcer-rules rather than a hard one:
it is about 7 MB and the enforcer runs in nearly every build. Users add
`org.apache.groovy:groovy` to the plugin declaration (shown on the rule page);
without it the rule fails with a one-line message saying exactly that. The
Groovy call sits in a nested class so the rule itself loads and can report the
absence.
The rule page notes the one porting gotcha: BeanShell compared bare words
(`${project.artifactId} == foo`), Groovy needs both sides quoted. The
deprecation notices on `evaluateBeanshell` now point here.
Verified: `TestEvaluateGroovy` 8/8; ITs `evaluate-groovy` (two rules pass),
`evaluate-groovy-missing` (expected failure with the classpath message) and
`evaluate-beanshell` → Passed: 3; `mvn site -pl enforcer-rules` renders the new
page.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
