This is the same problem as issue 243. I don't believe the fix in r1738 was
successful, as it doesn't remove the compile-time ambiguity. With the current
HEAD I still see the following compile-time warnings:
reference to update is ambiguous, both method
<T>update(T,com.google.code.morphia.query.UpdateOperations<T>) in
com.google.code.morphia.Datastore and method
<T>update(com.google.code.morphia.query.Query<T>,com.google.code.morphia.query.U
pdateOperations<T>) in com.google.code.morphia.Datastore match
Note that this only appears when running javac, the Play! precompile phase
works just fine. However, I believe the two method signatures are indeed
identical after type erasure.
Original issue reported on code.google.com by wagner.d...@gmail.com on 13 Jul 2012 at 7:41
Original issue reported on code.google.com by
wagner.d...@gmail.com
on 13 Jul 2012 at 7:41