I think Jenkins uses a different class loader for each plug-in. Ulli
Am 25.11.2012 um 12:35 schrieb Uri Scheiner <[email protected]>: > 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 libraries that the > plugin is dependent on. I would like to know how Jenkins handles thiswhen the > library is already used by another plugin. What if the plugin is using a > different version of the library? I was wondering if the case is solved by a > different class loader per plugin, but that might not be scalable. > > > Thanks, > > Uri > > >
