Folks,
maybe it's tangential to your discussion or event irrelevant, however
what about considering JBoss Modules?
TL;DR; Modular classloading instead of hierarchical.
Hierarchical classloading was giving us headaches in JBoss AS 5.x,
modular classloading used since AS7 and in Wildfly solves all various pains.
You can basically separate various parts of the platform, isolate
dependencies in multiple modules, design what will be exposed, what not.
It's basically very very very much simplified OSGi, that gives you
certain modularity and separation.
Doc:
https://docs.jboss.org/author/display/MODULES/Introduction
Github:
https://github.com/jboss-modules/jboss-modules
Or have a look at older presentation, since slide 25 to understand the
concept graphically:
http://www.slideshare.net/dandreadis/jboss-as7-reloaded
HTH
Cheers,
Vaclav
On 6.2.2015 16:29, Jesse Glick wrote:
On Fri, Feb 6, 2015 at 10:05 AM, Nigel Magnay <[email protected]> wrote:
What's the current story with guava?
Hell.
I.E: if you're pluginFirstClassLoader and a later-than-core guava in
WEB-INF/lib, will this work?
If you are very careful.
I notice jclouds-plugin goes to lengths to shade its dependency. It'd be
nice if the jenkins plugin manager could do that (the shading) at
deploy-time
It is easy enough to shade dependencies using the Maven plugin, there
is no need for any runtime tricks.
--
Vaclav Tunka
Enterprise Application Platforms
JBoss by Red Hat
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" 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-dev/54DA1357.7000605%40redhat.com.
For more options, visit https://groups.google.com/d/optout.
