Well in the absolute we should make all tomee/lib dependencies not available to apps.We don't do it (for all actually) because we want to be aligned on standard java classloader to stay simple. But relying on it you develop an app for a particular tomee version which means upgrading tomee can break your app. This sounds to me really dangerous and apps should be able to override container versions for its needs so a BOM sounds like a big master where it doesn't make that much sense. Commons-lang is a good example. We need to check it for 1.7.0 but we can desire to remove it and only rely on commons-lang3 if possible.
Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-05-09 1:05 GMT+02:00 Jean-Louis Monteiro <[email protected]>: > The only quick and usable solution is to create a BOM or so, from our maven > projects. > > For every Java EE API (+ impl provided by tomee and additional libs), you > should only use the all-in-one API jar from OpenEJB. > You should not rely on IMPL. > > But, that said, you can of course have direct dependencies to transitive > dependancies. > For example, if you need commons-lang, we have one as well in TomEE. > > We have a classloader checker you could activate so that you get a warning > AFAIR when you embedded container provided lib or classes into your app. > Would that help in short term? > > openejb.check.classloader=true > openejb.check.classloader.verbose=true > > Can be regular system properties or added to the system.properties file. > > Jean-Louis > > > > > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Tue, May 6, 2014 at 9:54 AM, aurelien.leboulanger < > [email protected]> wrote: > >> what i want it's to avoid duplication or conflits between my Maven >> dependencies and libraries provided at runtime by TomEE. >> Can i manage this problem more efficiently than just check all TomEE >> librairies and add a provided scope if it exist in my maven POMs ? >> >> >> >> -- >> View this message in context: >> http://openejb.979440.n4.nabble.com/Maven-tomEE-tp4669168p4669177.html >> Sent from the OpenEJB Dev mailing list archive at Nabble.com. >>
