As one of the main downstream users of Sisu would you prefer it to declare
a provided scope dependency to (sisu-)guice rather than the current compile
scope dependency?

Making it provided should make it easier to swap in alternative versions
while still documenting the dependency - and avoid lots of tedious
exclusions. The only downside I can see is that downstream users like the
Maven runtime would then need to explicitly remember to add the
(sisu-)guice dependency in their final application artifact/assembly (and
potentially in some tests) as it would no longer be transitively included.
(though that might be a good thing documentation-wise)

WDYT?

Reply via email to