Per Maven docs provided scope "is much like compile, but indicates you expect the JDK or a container to provide the dependency at runtime. For example, when building a web application for the Java Enterprise Edition, you would set the dependency on the Servlet API and related Java EE APIs to scope provided because the web container provides those classes. A dependency with this scope is added to the classpath used for compilation and test, but not the runtime classpath. It is not transitive."
My team has noticed a number of artifacts using provided as more of a compileOnly scope. That is, they want the dependency on the compile time classpath, but do not want it on the runtime classpath. They do not expect the web container, JVM, or anything else to put it on the runtime classpath. Is this an acceptable use of provided, and if so should we update the docs? Or is this a hack and misuse of provided scope that is likely to cause problems? -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
