On Tue, Jan 19, 2016 at 6:45 AM, Ullrich Hafner <[email protected]> wrote: > Since this is targeted for 2.0
I do not see any reason to delay this change until 2.0. We can take advantage of it immediately. > are there also plans to avoid the dependency > hell in future Jenkins releases within this pom or is this something that > needs to be addressed somewhere else? Currently the Jenkins war exposes all > dependencies (and transitive…) to the plug-ins. Not a POM issue. Needs to be addressed in core’s `ClassLoader`s. -- 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/CANfRfr0e81RLN8iK1QiBuexjHHWFV6CxQE4jir0aOs9TjQvoBQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
