On 2020-07-29T12:22:33 +0200
Michael Osipov wrote:
>
> I think your usage is correct. Maybe the docs aren't sharp enough saying
> that those case just examples which require a provided scope. You can,
> of course, improve the docs in such a fashion.
> Out of couriosity, can you give you can exam
Well the use case appears to be the same as Gradle’s compileOnly, which as the
name states, it’s used for compilation only and it’s not required for
execution. Also, dependencies set in compileOnly are never exported to
consumers, so in a way, with current Maven semantics Gradle’s compileOnly ~=
Am 2020-07-29 um 12:18 schrieb Elliotte Rusty Harold:
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 dependen
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
