[
https://issues.jboss.org/browse/JBIDE-11582?page=com.atlassian.jira.plugi...
]
Alexey Kazakov commented on JBIDE-11582:
----------------------------------------
These problems are not the same. Each of them has a unique location.
In Bean1.java both problems in the same line but if you click on the problem in Problems
view you will see that it points to the particular parameter.
Check out the following code:
{code}
public class A {
private String s, s;
}
{code}
You will see two JDT problems with the same message, source, line number, etc. And I think
this is correct. It's the same situation when both variables together cause the
problem. So JDT should mark them both. We do the same.
One CDI validation problem per one validation issue should be
reported instead of two identical ones
----------------------------------------------------------------------------------------------------
Key: JBIDE-11582
URL:
https://issues.jboss.org/browse/JBIDE-11582
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 3.3.0.Beta2
Reporter: Jaroslav Jankovič
Assignee: Alexey Kazakov
Fix For: 3.3.0.Beta3
There are many examples of validation problems which are reported twice, with the same
description, resource, path, location, type and also quick fix proposals. In this
situation I think there is no need to obtain two identical validation errors.
Examples of such a situation:
{code:title=Bean1.java|borderStyle=solid}
public class Bean1() {
public void foo(@Observes String param1, @Disposes String param2) {
}
}
{code}
{code:title=Bean2.java|borderStyle=solid}
public class Bean2() {
@Inject
public Bean2(@Observes String param) {
}
}
{code}
--
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