Hello, I don't have anything against a quick fix, just want to understand: do we report bugs to the concurrent package owner?
Thanks! On Thu, May 8, 2008 at 3:09 PM, Alexey Varlamov <[EMAIL PROTECTED]> wrote: > 2008/5/8, Tim Ellison <[EMAIL PROTECTED]>: > > > Alexey Varlamov wrote: > > > Foilks, > > > there is an issue HARMONY-5807, Apache Hadoop cannot compile on > > > Harmony due to non-generic signature in concurrent package. The issue > > > seems trivial to fix, but how should we handle it given this is > > > external code? > > > > > > > In this case I suggest we just re-implement the offending interface in our > > 'enhanced' area and the build system will use it in preference to the one > we > > pick up from 'standard'. > > Yeah, I've thought the same. Only unclear bit is how should it be laid > in SVN - modules/concurrent is svn:externalized - do you have any > tricks in mind? > > > > > I've attached a patch to the JIRA. > > > > > > Regards, > > Tim > > > > > > > > > FYI, JAPI report shows there are 3 issues in total [1]: > > > > > > interface java.util.concurrent.Delayed: implements > > > java.lang.Comparable<java.util.concurrent.Delayed> in > > JDK_5.0, but > > > implements raw java.lang.Comparable in Harmony_5.0 > > > method java.util.concurrent.ConcurrentHashMap.clone(): > > throws > > > java.lang.CloneNotSupportedException in JDK_5.0, but > > doesn't throw > > > java.lang.CloneNotSupportedException in Harmony_5.0 > > > method > > java.util.concurrent.PriorityBlockingQueue.comparator(): > > type > > > java.util.Comparator<? super T> in JDK_5.0, but type > > > java.util.Comparator in Harmony_5.0 > > > > > > [1] > > > http://people.apache.org/~smishura/latest-harmony-japi.html#pkg_java_util_concurrent > > > > > > -- > > > Alexey > > > > > > > > > -- With best regards, Alexei
