Back before script-security started to actively prevent directories on
script classpaths[1] (such as for groovy-postbuild plugin), it was a
common practice to add a directory with bunch of .groovy files and use
the classes from the script. However, since script-security disallowed
this it does no longer work. I was thinking about migrating out users to
secure variant by consolidating the directory into a single file (or
using one CP entry par file in that directory) that will be properly
approved by script-security but it seems the groovy will not load the
classes if the files are on the classpath (it work with directories only).
```
$ groovy -cp libdir/Lib.groovy -e 'Lib.method()'
Caught: groovy.lang.MissingPropertyException: No such property: Lib for
class: script_from_command_line
groovy.lang.MissingPropertyException: No such property: Lib for class:
script_from_command_line
at script_from_command_line.run(script_from_command_line:1)
$ groovy -cp libdir/ -e 'Lib.method()'
Hello World!
```
I experience the same from Jenkins. Also, this change seems to make this
KB entry[2] obsolete.
Do I miss something? Is there any way to get this to work with
script-security? I would really like to avoid building .jars out of it...
[1] https://issues.jenkins-ci.org/browse/JENKINS-24399
[2]
https://support.cloudbees.com/hc/en-us/articles/218576338-How-to-load-external-class-in-Groovy-Postbuild-action
Thanks
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/ff0b2050-518b-eddc-31e7-e6020622a43c%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
