maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <stephen.alan.conno...@gmail.com>
Subject Re: maven-enforcer-plugin to ban a transitive provided dependency
Date Fri, 05 Apr 2013 11:29:35 GMT
provided scope is not transitive, so that is why the build will not fail
using the enforcer rule that scans transitive dependencies. You probably
will need to write your own rule if this is something that you need


On 5 April 2013 09:47, dsilve <davide.silvestre@gmail.com> wrote:

> Hi,
> I have the following scenario:
> my project (A) has a number of compile dependencies on other internal
> projects (B0, B1, B2 ...).
> I would like to break the build of A in case Bx has been built depending on
> an older release of A.
>
> So for instance:
>
> A:2.0-SNAPSHOT depends on B3:2.3
> and
> B3:2.3 depends on A:1.0 and this dependency is provided.
>
> I tried to use the maven-enforcer-plugin to break the build of A in case
> there is a transitive dependency whose groupId and artifactId are the same
> as A, but it doesn't work because the dependency A:1.0 is provided.
>
> Any suggestions?
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/maven-enforcer-plugin-to-ban-a-transitive-provided-dependency-tp5752733.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

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