Yes, silly me, I should have seen that. However, doesn't that mean that xml-apis-2.7.1 will always
be pulled in?
Thanks
Alan
On 1/6/2011 9:53 AM, Archie Cobbs wrote:
On Thu, Jan 6, 2011 at 11:33 AM, a...@mechnicality.com mailto:a...@mechnicality.com
a...@mechnicality.com
Yes, I think the latest xerces and xalan should just get their xml-apis from
xml-commons-externalshttp://ivyroundup.googlecode.com/svn/trunk/repo/modules/org.apache.xml/xml-commons-external/1.3.04/ivy.xml,
which exists for this purpose.
I've made this change in r1440.
-Archie
On Thu, Jan 6,
Hi
I don't know if this a bug in ivyde, a bug in ivyroundup or a problem with my dependency management
(I suspect the latter)
I've got a dependency on xalan-j which I'm getting from ivyroundup.
However, the xalan-j entry in my cache has the xml-apis-2.7.1 jar in it
Somewhere else in my
On Thu, Jan 6, 2011 at 11:33 AM, a...@mechnicality.com
a...@mechnicality.com wrote:
Also, looking at
http://ivyroundup.googlecode.com/svn/trunk/repo/modules/org.apache.xml/xalan-j/2.7.1/ivy.xmlwhy
are the xml-api jars showing up at all? the conf 'interp' should only
pull in xalan?
Not
