Well, the moment a class or interface is publicized - they are effectively immutable, especially in Java, where virtual-by-default can easily cause a newly introduced method in a base class clash with an unknowing derived class, resulting in ClassLoader exception. You are thus practically required to track transitive dependencies, regardless of deprecation or non-deprecation, no?
On Mar 2, 3:45 pm, Ricky Clarkson <[email protected]> wrote: > > For example, A colleague of mine (Ben Evans) was > > recently pondering having a versioned Thread class, which you could > > then deprecate 'forcing' developers to use something a little more > > modern than the Java 1.4 concept of a thread :) > > Is it a good idea to deprecate classes that the non-deprecated libraries you > actually use are built on? -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
