The optional <xmlvalidate> task will validate XML files against DTD's.
As for checking something more detailed like appenders exist for the
categories defined - you're probably on your own there, unless Log4j has
some built-in API to verify a configuration file.
Erik
----- Original Message -----
From: "Thomas Tuft Muller" <[EMAIL PROTECTED]>
To: "Ant Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, December 11, 2001 6:12 AM
Subject: RE: Log4j xml config evaluation
> Sorry, I didn't emphasize that I meant log4j *XML* files. I'd define
> evaulating a log4j XML file as 1) determing that it's a valid XML file
> according to the log4j dtd, and 2) when applied it will result in a valid
> log4j configuration (i.e. all appenders defined for the categories exist
> etc. I guess part 2 of my definition applies to a log4j property file as
> well).
>
> --
>
> Thomas
>
>
> | -----Original Message-----
> | From: Erik Hatcher [mailto:[EMAIL PROTECTED]]
> | Sent: 11 December 2001 11:04
> | To: Ant Users List; [EMAIL PROTECTED]
> | Subject: Re: Log4j xml config evaluation
> |
> |
> | What do you mean by "evaluate"?
> |
> | A Log4j configuration file is simply a properties file, so you
> | could load it
> | into Ant properties using <property file="..."/> or manipulate it using
> | <propertyfile>
> |
> | But there is nothing specific to do anything special with Log4j
> | configuration files beyond that.
> |
> | Erik
> |
> | ----- Original Message -----
> | From: "Thomas Tuft Muller" <[EMAIL PROTECTED]>
> | To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> | Sent: Tuesday, December 11, 2001 5:25 AM
> | Subject: Log4j xml config evaluation
> |
> |
> | > Hi,
> | >
> | > I'm using Log4j and Ant, and since the log4j configuration files in
our
> | > system is starting to get quite chunky, it would be nice to evaulate
the
> | > log4j files during the build process. Does ant have any tasks for
doing
> | > this, or if not; what's the best way to evaulate a log4j.xml file?
> | >
> | > Regards,
> | >
> | > --
> | >
> | > Thomas
> | >
> | >
> | >
> | >
> |
*************************************************************************
> | > Copyright ERA Technology Ltd. 2001. (www.era.co.uk). All rights
> | reserved.
> | > Confidential. No liability whatsoever is accepted for any loss or
damage
> | > suffered as a result of accessing this message or any attachments.
> | >
> | > --
> | > To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
> >
> >
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
>
> *************************************************************************
> Copyright ERA Technology Ltd. 2001. (www.era.co.uk). All rights reserved.
> Confidential. No liability whatsoever is accepted for any loss or damage
> suffered as a result of accessing this message or any attachments.
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
