OK, it should be fixed now.
It seems I messed up the original ChatOps requests
On Wednesday, April 10, 2019 at 6:10:59 PM UTC+3, Nikolas Falco wrote:
>
> No write access yet
>
> Il giorno lunedì 8 aprile 2019 16:10:58 UTC+2, Oleg Nenashev ha scritto:
>>
>> Hi,
>>
>> It should be fixed now.
On Wed, Apr 10, 2019 at 6:44 PM Stephen Connolly
wrote:
> If the “classboxed” dependencies have scope=provided then they shouldn’t be
> transitive and you could leave them unshaded.
True. `war/pom.xml` would need to be massaged to bundle them.
> The JenkinsRule would just need to setup the
On Thu, Apr 11, 2019 at 4:10 AM Ullrich Hafner wrote:
> [shading does not] prevent developers to use the shaded classes, they are
> still there, just with another package name
True, but the Jenkins plugin class loader can refuse to serve such
classes, so any such mistake would immediately fail
I am trying to call some Java code in our plugin from the jenkinsfile to
parse XML (I have been able to parse it in the jenkinsfile but would like
to abstract the implementation from the pipeline). I am passing an XML file
to a method that works fine when this file is passed from within the
