This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
There should be a way to suppress warnings from Netbeans about "The column name of the persistent field is a SQL-99 keyword". Ideally using @SupressWarnings
Tomasz, I guess this is yours.
I suggest the following: - it will possible to suppress warnings on the following levels "jpa", "ejb" and "jaxws" - errors will not be suppressed open questions: - should hints associated with suppressed warnings be still available (examples: create persistence unit..., implement java.io.Serializable) problems: - there is a number of checks that operate on class level. To be compliant with java.lang.SupressWarnings semantics, if a class is annotated with @SuppressWarnings we will have to suppress warnings for all the class members as well, which may not be desirable - we will be introducing new warning names ("jpa", "ejb" and "jaxws"). According to the spec: "The presence of unrecognized warning names is not an error: Compilers must ignore any warning names they do not recognize. They are, however, free to emit a warning if an annotation contains an unrecognized warning name." In practice numerous static analysis tools define their own warning names, such as "PMD"
Doesn't javac in fact warn about unrecognized warning names? FindBugs uses @SuppressWarnings... but in a different package... sometimes. It's a mess. See: https://sourceforge.net/tracker/?func=detail&aid=1557422&group_id=96405&atid=614693
Does it mean there is no "clean" solution? I will ask the AVK team if the were thinking of anything similar
We have never done any thing like @SuppressWarnings in AVK. In the pre-annotation days we thought of providing a mechanism to users to suppress running some assertions by listing them in a user supplied XML file, but that was never implemented. The suggestion to use SuppressWarnings for NetBeans verification module sounds good to me. If we deicide to use an annotation, we should use java.lang.SuppressWarnings, otherwise user's code become non-portable. Another option would be to encode the information in comments, similar to what pragmas are in some languages. Thanks, Sahoo
When (and if) this is implemented, consider re-adding the "entity field must be encapsulated" warning, which was removed in issue 124225.
As a side-note, FindBugs already uses @SuppressWarnings to suppress its own warnings.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss