> -----Original Message----- > From: Magesh Umasankar [mailto:[EMAIL PROTECTED]
> Yes, as well as Ant's way - when you run in verbose mode, you > get messages logged at verbose level. In debug mode, you > get messages logged at debug level (this includes verbose, of > course). I am just suggesting a new log level called 'deprecated'. > When ant is run with -deprecated set, it would show the > deprecated messages. Currently, we have verbose < debug. > I am suggesting we make it such that deprecated < verbose < debug. > So when one runs in deporeacted, verbose or debug mode, > one gets to see the deprecated warning. Information are displayed as WARN when running a build file. Having a flag to switch on/off deprecated stuff is a bad thing to me. It is deprecated so show it. That's it. I'm having a hard time in my company fighting against the use of deprecated methods because some people are too lazy to figure out the non-deprecated methods and prefer to turn off deprecation rather than using the right methods. It's just like people using Vector/Hashtable when there is no synchronization involved. They use it because they are too lazy looking at 'new things' What puzzle me is that this attitude is mainly present for somewhat 'beginner' developpers that only knew Java2 and that never had the JDK 1.1 target in mind. Human like shooting themselves in the foot. :-) Stephane -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
