Hi, >That said, it is an interesting challenge -- aligning the projects is like >aligning the stars -- and good inter-project communications (tough in OSS) >are critical to this. I don't know if the Java language allowed the >class/methods to be marked as deprecated, 'cos I'm sure compiler warning >would have moved things along.
I like the stars analogy ;) I'm not sure what you mean by the rest of the paragraph: Java does allow methods and classes to be deprecated, log4j has marked them as deprecated, and Java does generate compile-time warnings by default if your classes use deprecated code (and javac gives you full details if you add -deprecation to its commands). People using Priority or Category directly have been getting deprecation warnings every time they compile their code for years now. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
