Oh. I got caught out attempting to manage two sets of changes in one client -- one quick one that I committed today and MAHOUT-175. I didn't commit part of the change that happens to affect this file in MAHOUT-175. I just overlooked that it did in fact overlap, didn't think it did.
If nobody minds too much, will commit MAHOUT-175 and then all is well. I think it would not compile to just commit this one file by itself. On Wed, Sep 9, 2009 at 3:25 PM, Sean Owen<sro...@gmail.com> wrote: > I am certain that's my fault, but not sure how I missed it since I had > to update some other code in examples/. Will hit it ASAP. > > On Wed, Sep 9, 2009 at 3:10 PM, Grant Ingersoll<gsing...@apache.org> wrote: >> Anyone else seeing: >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Compilation failure >> ./mahout-clean/examples/src/main/java/org/apache/mahout/cf/taste/example/netflix/NetflixFileDataModel.java:[137,23] >> org.apache.mahout.cf.taste.example.netflix.NetflixFileDataModel.MovieIDIterator is >> not abstract and does not override abstract method skip(int) in >> org.apache.mahout.cf.taste.impl.common.SkippingIterator >> >> >> >> ./mahout-clean/examples/src/main/java/org/apache/mahout/cf/taste/example/netflix/NetflixFileDataModel.java:[137,23] >> org.apache.mahout.cf.taste.example.netflix.NetflixFileDataModel.MovieIDIterator is >> not abstract and does not override abstract method skip(int) in >> org.apache.mahout.cf.taste.impl.common.SkippingIterator >> >> >
