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 ~= Maven provided scope + <optional>true</optional>.
Sent from my primitive tricorder > On 29 Jul 2020, at 12:22, Michael Osipov <[email protected]> wrote: > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
