maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Charles Honton <>
Subject Re: Reactor safe/rally points
Date Tue, 07 Nov 2017 01:17:56 GMT
So doesn’t this require a new directive such as ‘<compile transitive=false”> scope
or similar regardless of safe/rally points?   And to provide backwards compatibility, there
must be a split between the legacy consumer view of the pom and the new producer view of the
> On Nov 5, 2017, at 11:30 PM, Stephen Connolly <>
>> In the first case, the module creating a shaded jar can mark its
>> constituent jars as optional; preventing the transitive dependencies.
> Ha! That does not do what you think it does.
> Optional dependencies are still there but only as a version constraint that
> gets applied if something else brings the dependency into the tree in as a
> non-optional dependency.
> Normally you need a complex deep tree to see the effect (as most people use
> version hints rather than specifications... and with hints, closest wins,
> whereas specifications are globally merged)
> Provided scope is more correct, but shade doesn’t operate on provided
> scope... and anyway iirc that also pushes the constraint as transitive.
> With shade, the dependency is removed.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message