Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Received-SPF: neutral (herse.apache.org: 204.127.225.93 is neither permitted
 nor denied by domain of hoju@visi.com)
Message-Id: <7.0.1.0.0.20061221120930.0578f8c8@visi.com>
Date: Thu, 21 Dec 2006 12:20:03 -0600
To: "Ant Users List" <user@ant.apache.org>
From: Jacob Kjome <hoju@visi.com>
Subject: Re: please update the next release of Ant 1.7 to Xerces 2.9.0
In-Reply-To: <458A5E79.50604@apache.org>
References: <B07F6610DABEA8438092ED2058D7F16603E1F18B@z011134.bk.fin.local>
 <45753D92.1040906@volantis.com>
 <y1uk6169ugd.fsf@v30161.1blu.de>
 <1165338812.4575a8bce3bc1@my.visi.com>
 <7.0.1.0.0.20061219234809.0501ce58@visi.com>
 <4589198C.9060604@hpl.hp.com>
 <1166633403.458969bb47541@my.visi.com>
 <458A5E79.50604@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 04:14 AM 12/21/2006, you wrote:
 >Jacob Kjome wrote:
 >> Quoting Steve Loughran <steve_loughran@hpl.hp.com>:
 >
 >We've just upgraded in SVN_HEAD, BTW.

Excellent!  Thanks :-)

 >
 >
 >>
 >>> Incidentally, does xerces now depend on this serializer.jar? That is,
 >>> does it need to be included in the distro? Or are its classes merged
 >>> into xerces and xalan? These are the kind of thing we need to understand
 >>> before we ship
 >>>
 >>
 >> No, there's no dependency in Xerces.  It's loaded via reflection by
 >Xerces.  But
 >> they have deprecated their native serializer classes in favor of the
 >shared one
 >> provided by the Xalan team.  If serializer.jar is in the path, it
 >will be used.
 >>  If not, the deprecated Xerces native serialization will be used
 >(assuming one
 >> isn't directly referencing the Xerces native serializer API rather than
 >> properly using the interfaces, such as JAXP or DOM3LS).  I'm not clear on
 >> whether the same will be true for the next Xalan release (2.7.1, I
 >think [1])?
 >> They may actually depend directly on serializer.jar (or maybe they'll
 >> incorporate it within xalan.jar?).  I guess we'll find out when 
they make the
 >> release official.
 >>
 >> Jake
 >>
 >> [1] http://svn.apache.org/viewvc/xalan/java/tags/xalan-j_2_7_1/
 >
 >OK. So we ought to hold off to see what xalan does. if they build it in,
 >it should be the only copy on the classpath to avoid version problems
 >

Makes sense.  Just to be clear, are you saying that you would include 
serializer.jar in Ant's lib directory if Xalan doesn't ship with it 
included in their jar, but not include serializer.jar in Ant's lib 
directory if Xalan does include it in their jar, even though Ant 
doesn't ship Xalan?  Hmm... I might alert the Xalan team to this.  I 
suspect this might more than just an Ant-specific concern.  I'll 
report back with any information I find.


Jake

 >
 >-steve
 >
 >---------------------------------------------------------------------
 >To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
 >For additional commands, e-mail: user-help@ant.apache.org
 >
 >
 > 


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org