Jason,
I believe that your 2nd pastebin output reflects a bug in the gradle
mechanism for determining dependencies.
The problem that you have referred to is that you have marked 2 maven
plugins to be excluded from the transitive dependencies of
abdera-client, because you are seeing the
I have the following POM http://pastebin.com/P4TvzqJn but my exclusion for
artifactIdabdera-client/artifactId are not being respected. Actually
only 2 of them are not
the 2 not working are maven-plugins and maven-plugins
they are coming down anyways
see http://pastebin.com/c59HM8Bj
what am I
Try adding:
typeplugin/type
to those 2 dependency exclusions.
( the jaxen pom:
http://search.maven.org/remotecontent?filepath=jaxen/jaxen/1.1.3/jaxen-1.1.3.pom
declares those dependencies to be of type plugin )
On 14 Nov 2013, at 13:14, Jason Tesser wrote:
I have the following POM
you are referring to the maven-plugins I think
But what about the xml-api thing?
On Thu, Nov 14, 2013 at 9:29 AM, Stuart McCulloch mccu...@gmail.com wrote:
Try adding:
typeplugin/type
to those 2 dependency exclusions.
( the jaxen pom:
Also that doesn't work. Invalid POM
cannot say
exclusion
groupIdmaven-plugins/groupId
artifactIdmaven-cobertura-plugin/artifactId
typeplugin/type
/exclusion
On Thu, Nov 14, 2013 at 9:32 AM, Jason Tesser jasontes...@gmail.com wrote:
you are referring to the maven-plugins I think
But what
Stuart McCulloch wrote:
Try adding:
typeplugin/type
to those 2 dependency exclusions.
Nice try. Violates schema.
( the jaxen pom:
http://search.maven.org/remotecontent?filepath=jaxen/jaxen/1.1.3/jaxen-1.1.3.pom
declares those dependencies to be of type plugin )
On 14 Nov 2013,
You mean the POM relocation to an other version number is not fully supported
in Gradle message?
If you look at the pom it has a relocation element (bit like a symbolic link):
http://search.maven.org/remotecontent?filepath=xml-apis/xml-apis/2.0.2/xml-apis-2.0.2.pom
Doh, sorry - worth a try :)
You could try forcing jaxen to 1.1.4 (using dependencyManagement) as that
version doesn't have those odd plugin dependencies
On 14 Nov 2013, at 14:36, Jason Tesser wrote:
Also that doesn't work. Invalid POM
cannot say
exclusion
groupIdmaven-plugins/groupId
BTW, I ran your pom.xml through:
mvn dependency:tree
using Maven3 and the exclusions for those 2 maven-plugins were respected, which
suggests your exclusion issue might also be specific to Gradle.
On 14 Nov 2013, at 14:53, Stuart McCulloch wrote:
You mean the POM relocation to an
