I see, then: 1. You can add them in the exclusion so it will be there but not scanned 2. you can use a profile (or with gradle script it in the build file) to not add them in the plugin classpath 3. IIRC there is an applicationScopes option to control it but you will loose application compile scoped dependencies which is never what you want
Last point is vaading compiler shouldn't be compile scope since you rarely need it at runtime so it sounds more like a setup issue. Does that options work or at least make sense? Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-11-29 12:09 GMT+01:00 aibar <[email protected]>: > > > Short output: > > > > *vaadin-sass-compiler* is a compile time dependency of *vaadin-server* and > *flute* is a compile time dependency of *vaadin-sass-compiler* > > *Test project* https://github.com/aibar/tomee-includes-compile-time.git > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/Container-deployClasspathAsWebApp-is- > including-compile-time-deps-tp4680652p4680656.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
