Wayne
the answer is simple; look at
http://search.maven.org/remotecontent?filepath=org/opensaml/opensaml/2.2.3/opensaml-2.2.3.pom
and see how opensaml's dependency on xalan is defined.
That is to say if I get you right :::
if I have a dependency on opensaml I need to exclude in my project
: AW: [mvn] bad artifacs returned
Wayne
the answer is simple; look at
http://search.maven.org/remotecontent?filepath=org/opensaml/opensaml/2.2.3/opensaml-2.2.3.pom
and see how opensaml's dependency on xalan is defined.
That is to say if I get you right :::
if I have a dependency on opensaml I
Ron
I would not say that - because I just found out that the artifact
org/apache/rampart/rampart-project/1.6.2/rampart-project-1.6.1.pom
has the following snippet in it. AND
My project so far depends on this artifact and it comes from apache !
Now I will check if I can make it without this
And opensaml-2.2.3.pom has a reference as well
repositories
repository
idshibboleth.internet2.edu/id
nameInternet2/name
layoutdefault/layout
urlhttp://shibboleth.internet2.edu/downloads/maven2/url
snapshots
That is why one should not put repo definitions in poms.
The people at fault are the opensaml authors.
It is also why you mirror ALL references to repos that Maven makes so
that they all go to your repo manager and then your repo manager will
decide what external repos should be consulted.
