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> > <groupId>maven-plugins</groupId> > <artifactId>maven-cobertura-plugin</artifactId> > <type>plugin</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 about the xml-api thing? >> >> >> On Thu, Nov 14, 2013 at 9:29 AM, Stuart McCulloch <mccu...@gmail.com>wrote: >> >>> Try adding: >>> >>> <type>plugin</type> >>> >>> to those 2 dependency exclusions. >>> >>> ( the jaxen pom: >>> http://search.maven.org/remotecontent?filepath=jaxen/jaxen/1.1.3/jaxen-1.1.3.pomdeclares >>> those dependencies to be of type "plugin" ) >>> >>> On 14 Nov 2013, at 13:14, Jason Tesser wrote: >>> >>>> I have the following POM http://pastebin.com/P4TvzqJn but my exclusion >>> for >>>> <artifactId>abdera-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 missing >>>> I have altered the POM but I cleared my local cache and refreshed >>>> dependencies >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
