yes, note also that if you really rely on jettison you can evaluate the fact to provide it. TomEE uses it internally to provide json support out of the box but doesn't provide it as an API.
In other words we can get rid of it and use boon or jacksong if we want (realistically we'll not do it before tomee 2.0 but that's the idea). Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-05-05 17:14 GMT+02:00 aurelien.leboulanger <[email protected]>: > What i want with maven is to check that my dependencies will be not in my > webapps if this dependencies already provide by tomEE in the classpath. > > for example i have a dependency to jettison > > <dependency> > <groupId>org.codehaus.jettison</groupId> > <artifactId>jettison</artifactId> > <version>${jettison.version}</version> > </dependency> > > But i know that tomEE already provide this dependency so i doesn't want to > build my war with this dependency whereas the container tomEE provide it at > runtime. > > You prefer this solution, with a provided scope (instead of try to include > only one dependency that retrieve all libraries provided by tomEE) ? > > <dependency> > <groupId>org.codehaus.jettison</groupId> > <artifactId>jettison</artifactId> > <version>${jettison.version}</version> > <scope>provided</scope> > </dependency> > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Maven-tomEE-tp4669168p4669172.html > Sent from the OpenEJB Dev mailing list archive at Nabble.com.
