Mailing-List: contact commons-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <3F9F2F50.7030009@latte.harvard.edu>
Date: Tue, 28 Oct 2003 22:09:04 -0500
From: "Mark R. Diggory" <mdiggory@latte.harvard.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.5) Gecko/20030925
MIME-Version: 1.0
To: Shane Curcuru <shane_curcuru@yahoo.com>
CC: commons-dev@xml.apache.org
Subject: Re: Resolver component release 1.1 coming up
References: <5.2.0.9.0.20031028211745.01f2f7a8@curcuru.com>
In-Reply-To: <5.2.0.9.0.20031028211745.01f2f7a8@curcuru.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

I've been using it in combination with Xerces, Xalan and Saxon via JAXP 
and it works wonderfully, I have absolutely no complaints or bug encounters.

Cheers!

Shane Curcuru wrote:
> Since we've had a Resolver beta 1.1b1 out for a while now with no 
> complaints, as soon as I have time I plan to bump the version number to 
> 1.1 and make an official release.  I'll make sure there's both a Version 
> class available as well as sticking the version number in the jar manifest.
> 
> Any other comments/requests?  Hopefully the release will be at the 
> appropriate time for the Ant community to version-match with it for 
> their 1.6 release.
> 
> Sorry about the Xalan issue: I was hoping someone from that team could 
> comment.  Resolver is just a pretty simple service provider: I think 
> it's up to the applications that use it to ensure the correct one gets 
> plugged into the right places (i.e. TransformerFactory vs. 
> Transformers).  If I get free time (ha!) I'll see if I can get someone 
> else to look into it.
> 
> I'd love to get at least a simplistic Resolver automated test running, 
> but don't have time right now.
> 
> - Shane
> 

-- 
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu