You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by "alan@mechnicality.com" <al...@mechnicality.com> on 2011/01/06 18:33:34 UTC
Problem with Xalan-2.7.1 and ivyroundup
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 project there's a xml-apis-2.9.1 dependency.
I'm using a configuration called 'web' to retrieve the jars required to be in the web app into the
war/WEB-INF/lib folder
I'm doing this with the retrieve tab in IvyDE
However, although the dependency report says that xml-apis-2.7.1 is evicted, its still turning up in
the lib folder, together with the 2.9.1 version. Generally speaking its a very bad idea to have to
versions of the same jar in the lib folder!
Here's the line in the ivy.xml file which pulls in the xalan-j - I've set transitive="false" but
thats having no effect - mainly because I think that the xml-api jar is not actually a dependency of
xalan but rather part of the module.
Can anyone suggest how to fix this (short of just deleting the offending jar each time.)
<dependency org="org.apache.xml" name="xalan-j" rev="2.7.1" conf="web->interp" transitive="false"/>
Also, looking at
http://ivyroundup.googlecode.com/svn/trunk/repo/modules/org.apache.xml/xalan-j/2.7.1/ivy.xml why are
the xml-api jars showing up at all? the conf 'interp' should only pull in xalan?
Thanks
Alan
Re: Problem with Xalan-2.7.1 and ivyroundup
Posted by "alan@mechnicality.com" <al...@mechnicality.com>.
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, alan@mechnicality.com <ma...@mechnicality.com>
> <alan@mechnicality.com <ma...@mechnicality.com>> wrote:
>
> Also, looking at
> http://ivyroundup.googlecode.com/svn/trunk/repo/modules/org.apache.xml/xalan-j/2.7.1/ivy.xml
> why are the xml-api jars showing up at all? the conf 'interp' should only pull in xalan?
>
>
> Not sure about your other questions, but this is happening because the config 'interp' extends the
> config 'xml-apis'...
>
> -Archie
>
> --
> Archie L. Cobbs
>
--
Alan Chaney
CTO and Founder, Mechnicality, Inc.
www.mechnicality.com
Re: Problem with Xalan-2.7.1 and ivyroundup
Posted by Archie Cobbs <ar...@dellroad.org>.
Yes, I think the latest xerces and xalan should just get their xml-apis from
xml-commons-externals<http://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, 2011 at 6:22 PM, Alan Chaney <al...@writingshow.com> wrote:
>
> Hi Archie
>
> A little bit more experimentation reveals that the problem is nothing to do
> with IyvDE (I ran it again with ivy ant scripts)
>
> Its actually that xerces 2.9.1 ALSO has the xml-apis.jar in its published
> artifacts list on ivyroundup.
>
> It seems that the problem is that one part of my project requires xerces
> and another part requires xalan. Currently roundup has 2.7.1 xalan and 2.9.1
> xerces, so as xml-api is part of the published artifacts (rather than being
> a dependency) then both versions are pulled in.
>
> Any suggestions as to what I might do to fix this?
>
> Thanks in advance
>
> Alan
>
>
>
> On 1/6/2011 9:53 AM, Archie Cobbs wrote:
>
>> On Thu, Jan 6, 2011 at 11:33 AM, alan@mechnicality.com<
>> alan@mechnicality.com> wrote:
>>
>> Also, looking at
>>>
>>> http://ivyroundup.googlecode.com/svn/trunk/repo/modules/org.apache.xml/xalan-j/2.7.1/ivy.xmlwhyare the xml-api jars showing up at all? the conf 'interp' should only
>>> pull in xalan?
>>>
>>> Not sure about your other questions, but this is happening because the
>> config 'interp' extends the config 'xml-apis'...
>>
>> -Archie
>>
>>
>
--
Archie L. Cobbs
Re: Problem with Xalan-2.7.1 and ivyroundup
Posted by Alan Chaney <al...@writingshow.com>.
Hi Archie
A little bit more experimentation reveals that the problem is nothing to do with IyvDE (I ran it
again with ivy ant scripts)
Its actually that xerces 2.9.1 ALSO has the xml-apis.jar in its published artifacts list on ivyroundup.
It seems that the problem is that one part of my project requires xerces and another part requires
xalan. Currently roundup has 2.7.1 xalan and 2.9.1 xerces, so as xml-api is part of the published
artifacts (rather than being a dependency) then both versions are pulled in.
Any suggestions as to what I might do to fix this?
Thanks in advance
Alan
On 1/6/2011 9:53 AM, Archie Cobbs wrote:
> On Thu, Jan 6, 2011 at 11:33 AM, alan@mechnicality.com<
> alan@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 sure about your other questions, but this is happening because the
> config 'interp' extends the config 'xml-apis'...
>
> -Archie
>
Re: Problem with Xalan-2.7.1 and ivyroundup
Posted by Archie Cobbs <ar...@dellroad.org>.
On Thu, Jan 6, 2011 at 11:33 AM, alan@mechnicality.com <
alan@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 sure about your other questions, but this is happening because the
config 'interp' extends the config 'xml-apis'...
-Archie
--
Archie L. Cobbs