Got it. Would you believe this bug was introduced back in November 2004 and nobody noticed? :( It appears I also checked it in without the slightest comment about what I was doing.
I cunningly decided that actually adding new abstract methods is okay on a class that has no public or protected constructors, because all subclasses must be provided within the package and therefore are likely to be updated with the new method at the same time as the original class is. I figured this would account for classes that are intended to be returned from factory methods and never implemented externally. What I forgot to account for was the fact that interfaces never have constructors... I'm checking in a fix now and I'll rerun today's (CVS) comparison... Stuart. On 11/7/05, Stuart Ballard <[EMAIL PROTECTED]> wrote: > According to japi these methods are present in 1.5 (well, I only > checked a couple) so that explains why they aren't showing up in the > classpath-vs-jdk14 error report. > > What it doesn't explain is why they aren't showing up in the > jdk14-vs-jdk15 error report. I don't have an explanation for that just > yet but I'll keep investigating... > > Stuart. > -- > http://sab39.dev.netreach.com/ > -- http://sab39.dev.netreach.com/ _______________________________________________ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
