davsclaus opened a new pull request, #26827: URL: https://github.com/apache/camel/pull/26827
When Groovy cannot resolve a class, the message offered three ways to add the library, one of them `//DEPS`, which is not the recommended way. Before: ``` Groovy cannot resolve the class org.apache.commons.validator.routines.EmailValidator: it is not on the classpath. Add the library that provides it as a dependency of the application (a Maven dependency; with the Camel CLI camel.jbang.dependencies=groupId:artifactId:version in application.properties, or a //DEPS line); a class of your own goes in a .groovy or .java file next to the route. ``` After — the same message with the `//DEPS` route dropped: ``` ... Add the library that provides it as a dependency of the application: a Maven dependency, or with the Camel CLI camel.jbang.dependencies=groupId:artifactId:version in application.properties. A class of your own goes in a .groovy or .java file next to the route. ``` Found while reading an overnight local-model benchmark run, where this message fires for real — a model reached for `commons-validator` in a Groovy expression. The message is otherwise doing its job, so only the recommendation changed. The `//DEPS` mentions that remain in the code base are javadoc on the configuration option that enables the feature, which is documentation rather than advice. 105 `Groovy*` tests in camel-groovy pass. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj -- 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]
