Why is "trimToSize" considered an update method? It doesn't actually update the contents of a collection (ArrayList/Vector), but only optimizes the storage space that is used for the collection.

It currently uses a lookup in a HashMap which is faster than pattern matching. Also add, set, insert and remove don't cover all cases, it also needs to match clear, retain, offer and load. Do you think it would work significantly better if the inspection would recognize patterns?
I'll add setProperty to the list. I have no idea why trimToSize is considered an update method and I'll remove that.

I will also add getProperty(), propertyNames(), save(), store(), storeToXml() and enumeration() as query methods and loadFromXml() as update method.

Well, I didn't mean to replace the current list with only those patterns, but considering that other Collection spin-offs might stick to such a naming scheme it would reduce the chance for false positives - as in the setProperty() case I stumbled across. Maybe it's not worth the effort though.

At this moment I would consider it too much effort. If you were willing and had time to implement it I would definately add it however. If not I will close this request, now that I expanded the update and query lists.

You can close it. if I come across another case where a pattern might help I'll give it a go.

Thanks Sascha. If you ever want to give it a go, start in the CollectionQueryCalledVisitor and CollectionUpdateCalledVisitor classes.

I just realized that the title of this issue is wrong (I can't edit it though): it should of course be "Contents of Collection are queried, but never updated ...".
Darn browser-history :(

And now you go and focus attention on it. I never noticed it before. This won't do.