Jordan,
In general, if I use raw types it is for a good reason, like I want it to be *really* generic. Normally I'll even add documentation to say why I am doing it. So... you'll find raw generics related to ListComponents in some production code, mostly the materials and reflectivity code. Please don't change them without triple checking first what they will do. Not every warning that Eclipse complains about is worth heeding.
That being said, I'm fine with the updates to the tests so long as they still pass. I was simply lazy there
Keep in mind that the code example you show is a strawman argument: that code will fail fast with an exception at runtime, so it is still checked and nothing bad will actually happen. It's not like in C where it will either cause SIGSEGV or run with automatically casted values that compute invalid results.
I'll have to look at the ListEventListener piece. Casting to <Object> is worse than not specifying the type if the generic can be a primitive (<int>, <double>) because primitives are not Objects. I'm not sure that is the case here, so it is probably fine. This is the same reason that I extracted the Identifiable interface from ICEObject years ago because I needed an Identifiable that was not an ICEObject. The result was about three hours of unplanned work to fix casts to ICEObject across the code.