[
https://issues.jboss.org/browse/JBIDE-10187?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10187:
---------------------------------------------
Turns out JDT is actually behaving according to 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."
So yeah, I suggest our quickfix for this that will add @SuppressWarnings will check the
preference for unknown suppresswarnings if it is Ignore. if not we ask if the user wish to
Ignore these and then we toggle that flag for them. Otherwise just add @suppresswarnings.
Add support for a @SuppressWarnings for CDI "No bean is eligible
for injection" warning
---------------------------------------------------------------------------------------
Key: JBIDE-10187
URL:
https://issues.jboss.org/browse/JBIDE-10187
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: CDI
Affects Versions: 3.3.0.M4
Reporter: Cody Lerum
Assignee: Alexey Kazakov
Fix For: 3.3.0.Beta1
Would be nice to place a
@SuppressWarning("ambigiousinjection") or similar on an injection point that
tooling can't figure out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira