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. >
