maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <>
Subject Re: I wish we had a way to declare a dependency that wouldn't participate in the classpath
Date Sun, 13 Dec 2015 08:25:33 GMT

On Saturday 12 December 2015, Benson Margulies <>

> Sometimes, we want to declare a dependency without changing a classpath.
> Project A builds an OSGi bundle and a Karaf feature (classifier
> 'feature', type 'xml').
> Project B wants to consume the feature. it wants to declare the
> feature descriptor as a dependency, to (a) ensure reactor order, and
> (b) make the dependency information available to plugins.
> But it does _not_ want A's OSGi bundle and it's dependencies in the
> classpath.
> The only way out is to exclude them, one-by-one. And when someone adds
> a dependency to A, you have to maintain the exclusion list.
> Another example is the tomcat plugin: it needs wars as dependencies,
> and similarly it needs to avoid having their dependencies in the
> classpath.
> To me, this calls out for another scope.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: <javascript:;>
> For additional commands, e-mail: <javascript:;>

Sent from my phone

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