a different class loader for each plug-in.
Yes. If you want to share a library among two plugins, you need to factor
it into a third plugin they can depend on.
--
*Uri Scheiner*
Functional Architect | *Nolio*
*O*:972 (9) 9597307
*E:*:u...@noliosoft.com
Find out more about Nolio:
Website
Hi all,
I have a quick question regarding the architecture of Jenkins. Sometimes,
there may be different plugins that are dependent on the same 3rd party
libraries and I wanted to understand how the architecture responds to
this.
When a user creates a new plugin, he needs to define the
Yes, you can workaround it if you strip your config.jelly and leave just
one f:section element that wraps the entire form
On Thu, Oct 11, 2012 at 8:18 PM, Jesse Glick jgl...@cloudbees.com wrote:
On 10/03/2012 06:34 AM, Uri Scheiner wrote:
I've noticed that when adding a post-build plugin
Hi,
It seems like I found the problem - I had an 'Advanced' element
(f:advanced) under a separated f:section. It worked fine with the
previous UI.
You need to be very careful with the tags you're using in the config.jelly
file..
Uri
On Tue, Oct 9, 2012 at 8:46 PM, Uri Scheiner u
Hi All,
I developed a plugin that runs after the build finished. It worked fine in
build 1.443. However, I now see that it does not work on Chrome and Firefox
(only IE) when using the latest builds - I get the following javaScript
error when trying to add the plugin to the project:
*Uncaught
