Anyone?
I didn’t expect to have to require a plugin-first classloader unless the
conflicting library was in core?
Is my use pf persisting 3rd party classes via xStream broken by design (can we
only persist internal to the plugin classes?)
Is this just a case of requiring shading of the cucumber
Hi Peter,
Interestingly enough we are planning on pushing results back from the cucumber
plugin to another system – so I wonder if there is some commonality that the
plugin should expose rather than requiring many plugins parsing the same files.
/James
From: jenkinsci-dev@googlegroups.com [m