[
https://issues.jboss.org/browse/JBIDE-10187?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10187:
---------------------------------------------
Looking at
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.jdt.doc.isv/...
I would say we should follow the eclipse/javac conventions of all lowercase names and use
of - as "space".
And the names are actually more or less descriptive and I think that will be problematic
for us to do if we have a unique suppresswarning for *every* option we have now. Can't
some of these be grouped instead of every unique option?
And I think we should prefix these with jbt- or cdi- to make it clear its not part of the
standard suppresswarning list.
Add support for a @SuppressWarnings
-----------------------------------
Key: JBIDE-10187
URL:
https://issues.jboss.org/browse/JBIDE-10187
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: common/jst/core
Affects Versions: 3.3.0.M4
Reporter: Cody Lerum
Assignee: Daniel Azarov
Fix For: 3.3.0.Beta1
Attachments: Add_(a)SuppressWarnings.png, Add_(a)SuppressWarnings2.png,
Add_(a)SuppressWarnings2.png, Add_(a)SuppressWarnings3.png, Add_(a)SuppressWarnings3.png,
ButtonNameBorrowedFromProject.png, ManySuggestionsToAddSuppressWarnings.png
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