Re: Need help with backwards incompatible resolver change

On 18 Nov 2002, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > Ant could switch to the 1.1 resolver code Done. Stefan

Re: Need help with backwards incompatible resolver change

On Fri, 15 Nov 2002, Craeg K. Strong <[EMAIL PROTECTED]> wrote: > With these two simple changes, the code will work with the > new resolver. But not with the old one, right? I think the cleaner solution was to re-add static methods to CatalogManager and Debug, make them deprecated and let them d

Re: Need help with backwards incompatible resolver change

On 18 Nov 2002, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > I'll see whether I can put together a patch to resolver today - if I > can't I'll tell you why 8-) Well, I certainly cannot re-introduce a static setIgnoreMissingProperties method to CatalogManager as there now already is a non-static me

Re: Need help with backwards incompatible resolver change

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / Craeg K Strong <[EMAIL PROTECTED]> was heard to say: | Yikes! I checked out the new xml-commons resolver code and it looks like | two things tripped me up: Sigh. I did try to keep things backwards compatible, but I guess I failed just a bit. | | (

Re: Need help with backwards incompatible resolver change

Yikes! I checked out the new xml-commons resolver code and it looks like two things tripped me up: (1) Change in debug messages old way: Debug.message(1, "a debug message"); new way: catalogManager.debug.message(1,"a debug message") (2) CatalogManager no longer available as a static instance o

Need help with backwards incompatible resolver change

Hi, Craeg Strong's patch that added resolver support to Ant worked for almost a week, but now it doesn't anymore 8-( Ant builds happily against the 1.0 release of resolver.jar, but with the current CVS code, this here happens: What is