[
https://issues.jboss.org/browse/JBIDE-10187?page=com.atlassian.jira.plugi...
]
Alexey Kazakov commented on JBIDE-10187:
----------------------------------------
There is a problem.
As soon as you add some custom warning in the @SuppressWarning like
@SuppressWarning("ambigiousinjection") Eclipe marks it as a warning:
Unsupported @SuppressWarnings("ambigiousinjection")
So "fixing" one warning we get another one.
The list of supported warnings is hardcoded in Eclipse JDT so we can't extend it :(
He had an idea to introduce a general feature for our Validation framework. We would add a
default quick fix for all our validation problems for Java files which suggests to
suppress the warning via adding @SuppressWarnings("<problemType>") to the
java element. Our validators would ignore such problems in the element.
But it doesn't make sense to suppress one warning and get another one :(
The only way to avoid adding this warning "Unsupported @SuppressWarnings" is to
set the corresponding preferences to IGNORE along with adding
@SuppressWarnings("<warningId>")
What do you guys think?
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