Paulex Yang wrote: > Tim > > Thank you to point out that. I did refer to the URL your provided. But > seems the JAPI report ignores some difference, for example, the > overridden information.
So it does, sorry Paulex. Stuart: is there some way to avoid JAPI taking inherited API signatures into account when doing the diff? kinda like the javadoc tool. > And I raised several JIRAs just for convenience to create patch, I > consider that a patch within smaller scope maybe introduce smaller risk, > especially while the SVN structure is not so stable:). Sure, I just saw a number of JIRAs appearing saying that the API was wrong and thought that was the end of it. A JIRA with a patch including implementation and test case is great! Regards, Tim > Tim Ellison wrote: >> Thanks for the JIRAs Paulex, but to save you a great deal of effort >> opening a new issue for every API that is missing ;-) I should point out >> already have the JAPI tool description of what we need to do [1] -- now >> if you were sending code to fix these issues ... :-) >> >> [1] http://www.kaffe.org/~stuart/japi/htmlout/h-jdk15-harmony >> >> Regards, >> Tim >> >> Paulex Yang (JIRA) wrote: >> >>> Three types in java.util.jar are not implemented in Harmony >>> ----------------------------------------------------------- >>> >>> Key: HARMONY-163 >>> URL: http://issues.apache.org/jira/browse/HARMONY-163 >>> Project: Harmony >>> Type: Bug >>> Components: Classlib Reporter: Paulex Yang >>> >>> >>> Three types: >>> public abstract class java/util/jar/Pack200 >>> public interface java/util/jar/Pack200$Packer >>> public interface java/util/jar/Pack200$Unpacker >>> are introduced in JSE 5, but not implemented in Harmony >>> >>> >> >> > > -- Tim Ellison ([EMAIL PROTECTED]) IBM Java technology centre, UK.
