isEqualTo should not use generics

[assertj]

isEqualTo should not use generics

[twillouer]

Nothing can extend String :P

[joel-costigliola]

Yep, that's right :) but the second line compiles without problems.
Anyway, the main point here is to show that the last 3 assertThat don't compile.

[joel-costigliola]

William, your solution works but it still relies on generics which is root of the problem.
Sorry, the issue was not clear, let's take another example with an Employee class inheriting from Person to show where is the problem :

Employee bill = new Employee("Bill", 50, "micro$oft");
assertThat(bill).isEqualTo(bill); // OK
// now let's view billou as a Person and not an Employee anymore
Person billou = bill;
// next line leads to a compile error although bill and billou are exactly the same.
assertThat(bill).isEqualTo(billou); 

The idea here is simply to use an Object instead of generic parameter A in AbstractAssert.
I know we loose type checking here but I'm not sure if it was really useful (please tell me if you disagree).

This issue is just a step toward less generics and will be followed by others to remove generics in assertions methods parameter like contains (but one step at a time)

Note that AbstractAssert generic parameter must be kept for assertions based on Condition.

Thanks for the effort though !