Description Troy 2012-02-06 22:31:01 EST

Build Identifier: 20110916-0149

Eclipse suggests methods could be made static, even if they refer to non-static stuff, namely generic stuff.

It would be nice if it considered the non-static generics stuff when determining this error/warning.

Example class to reproduce the problem...


public class Foo<T> {
  private final T blah;

  public Foo( final T t ) {
    this.blah = t;
  }
  
  /**
   * @return the blah
   */
  public T getBlah() {
    return blah;
  }
  
  //......
  //......
  
  public List<T> doSomeBlahThing( final Object[] blahs ) {
    final List<T> result = new ArrayList<T>( blahs.length );
    for( final Object candidateBlah : blahs ) {
      result.add( (T) candidateBlah );
    }
    return result;
  }
}

Reproducible: Always

Steps to Reproduce:
1. Create a new java class called Foo
2. Ensure errors/warning for "Method can be static" is set to warning or above