it depends what you do. For a war all should be provided (and BTW last one will not be useful at all). These snippets are mainly to reference the right dependency then up to you as a user to use the right scope (same applies to http://tomee.apache.org/ng/developer/testing/applicationcomposer/index.html, if you use for tests use test scope but if you use it for a standalone application compile is right).
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-05-31 14:41 GMT+02:00 tam <[email protected]>: > Dear colleagues, > > in the announcement of 7.0.0-M3, I found the recommended Maven setup: > > > > So, when upgrading to 7.0.0 Plus (not M3, but the final one), I used this > scheme, just leaving the -M3 part out. However, this yields a war file of > more than 140 MBytes, compared to less than 100 kByte if a make them all > providedCompile (I'm using Gradle). > > Is there a reason not to specify all three of them as provided? It appears > to me that I'm uploading the entire JEE stack with my war file. > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/EJB-libs-provided-or-not-tp4678686.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
