This rule identifies a class that has the same name as a class it extends. This is likely to cause confusion.

Change the name of the subclass to make it more clear what its purpose is. It is normally possible to express how it is different to a superclass.

In this example references to ArrayList later on in the Players class could be confusing.

The example could be easily fixed by changing the Players.ArrayList class name to Players.PlayerList. This is more descriptive and it avoids confusion with the ArrayList class from Collections.

Robert C. Martin, Clean Code - A handbook of agile software craftsmanship, §17.N4. Prentice Hall, 2008.