Re: transitive dependency exclude not working how I expect

2014-05-16 Thread Marc De Boeck 
As far as I know, the exclude element works fine for us, also in the case
of such transitive dependencies.
Maybe you received javax.servlet via another dependency ?

As a workaround (or a test), you could add your exclude element(s)
directly under (but at bottom of) the dependencies element of moduleA.
This way, you don't care if the exclude is for spring-security or for some
other module. On the other hand, you might forget after a while the exact
reason why the exclude element is there.

Regards,
Marc



2014-05-09 0:17 GMT+02:00 Zac Jacobson pie@gmail.com:

 In my ivy.xml files, I have a module moduleA with a dependency like this:

  dependency org=org.springframework name=spring-security
  rev=3.1.2 
  exclude org=javax.servlet/
  /dependency


 And when I resolve, javax.servlet is not included, as I expected.

 Next, I have moduleB  with a dependency back to moduleA

  dependency org=myOrg name=moduleA/


 I was surprised that when I run resolve, javax.servlet shows up for
 moduleB. Is this expected? Is there a flag I'm missing to keep the excludes
 in tact from depending modules?

 I see this for both Ivy 2.4.0 rc1 and 2.3.0

 Thanks,
 Zac

Re: transitive dependency exclude not working how I expect

2014-05-16 Thread Zac Jacobson 
Sorry for the chatter, I figured it out once I took a break form it: I had
an exclude that put the org value in the module attribute, so that's why it
was still getting included.


On Thu, May 8, 2014 at 3:17 PM, Zac Jacobson pie@gmail.com wrote:

 In my ivy.xml files, I have a module moduleA with a dependency like this:

 dependency org=org.springframework name=spring-security
 rev=3.1.2 
 exclude org=javax.servlet/
 /dependency


 And when I resolve, javax.servlet is not included, as I expected.

 Next, I have moduleB  with a dependency back to moduleA

 dependency org=myOrg name=moduleA/


 I was surprised that when I run resolve, javax.servlet shows up for
 moduleB. Is this expected? Is there a flag I'm missing to keep the excludes
 in tact from depending modules?

 I see this for both Ivy 2.4.0 rc1 and 2.3.0

 Thanks,
 Zac