It's actually repeatable, and is caused by my adding a "<?>" wildcard to
the declaration of the DummyOutputCollector to make Eclipse happy.
public class DummyOutputCollector<K extends WritableComparable, V
extends Writable>
implements OutputCollector<K,V> {
works but has an Eclipse warning "WritableComparable is a raw type.
References to generic type WritableComparable<T> should be parameterized"
public class DummyOutputCollector<K extends WritableComparable<?>, V
extends Writable>
implements OutputCollector<K,V> {
makes Eclipse happy but throws the mvn compiler errors on other classes
which use it with IntWritable and LongWritable K values. Probably should
have paid more attention to Josh Bloch's generics tutorial I attended
last year.
On 6/7/10 5:51 PM, Benson Margulies wrote:
I guess mvn &eclipse writing class files at the same time
On Jun 7, 2010, at 8:22 PM, Jeff Eastman <[email protected]>
wrote:
Another local phenomenon. Clean checkout is happy again.
On 6/7/10 4:53 PM, Sean Owen wrote:
I don't see this on the command line or in IntelliJ FWIW...
(Mac OS X 10.6.x / Java 6 / etc.)
On Tue, Jun 8, 2010 at 12:05 AM, Jeff Eastman
<[email protected]> wrote:
Some of these classes I have touched in porting to 20.2 but not
nearly all.
Anybody know what is happening here? Eclipse is a happy camper with
all of
these classes (esp. TestCanopyCreation which runs fine in it). I'm on
r952477 doing mvn clean installs.
