Hi Sanne
If it is only this one class then revert it back - there was nothing major there anyway,
except for some type params that could be inferred rather than being made explicit.
Cheers
Manik
On 9 Feb 2010, at 19:50, Sanne Grinovero wrote:
Hi all,
the eclipse compiler is not as clever as Intellij's one; since this change
http://fisheye.jboss.org/browse/Infinispan/trunk/core/src/main/java/org/i...
Infinispan core is not building any more in eclipse; could I revert
these changes, or change the <? extends T> types to <T> in method
signatures?
for example:
public static <T> Set<T> immutableSetCopy(Set<? extends T> set) {
could be changed to:
public static <T> Set<T> immutableSetCopy(Set<T> set) {
Alternatives:
1) change the signature
2) revert the change
3) introducing an explicit cast like:
return Collections.singleton(set.iterator().next());
to
return (Set<T>) Collections.singleton(set.iterator().next());
The commit log from Manik sais "IntelliJ Inspection refactoring", and
while he changed several classes I'm only having trouble with this one
class, in three methods.
Of course, this is not important as it doesn't affect the real build
and there is an issue open on the eclipse tracker;
I'm also switching slowly to intelliJ and building from commandline
maven, but could be annoying for others.
Sanne
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org