Details
Improvement
Resolved
Major
Description
Hi, I know some people like these because even in Groovy they parameterize their collections, but most people don't and this leads to unnecessary warnings.
I think the best choice for this is to leave the choice to the user: just get a per-project checkbox where you can activate or deactivate these warnings. This way everyone is happy (I am not currently, as these warnings really bother me 
Thanks.
Activity
Andrew Eisenberg
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Original Estimate | 0 minutes [ 0 ] | |
| Summary | Add an option to disable Map or List parameterized warnings | Add an option to disable parameterized type warnings |
| Remaining Estimate | 0 minutes [ 0 ] |
Andy Clement
made changes -
| Attachment | patch.txt [ 46135 ] |
Andy Clement
made changes -
| Assignee | James E. Ervin [ jervin ] | Andy Clement [ aclement ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
off by default now - I've only ever seen people complaining about it.
patch attached makes it configurable, this is not currently integrated. If anyone cares down the line we can make it configurable.
let me know if you still see them after picking up a dev build in a day or so. I've currently only prevented the raw reference messages, not sure which you were seeing as you didn't say.