Community
Participate
Working Groups
Arrays //1 .asList("abc", "ab","c"). //2 .stream() //3 .forEach(System.out::println); //4 Arrays.asList("a", "b", "c").stream() //5 .filter(s -> s.length() > 0) //6 .filter(x -> x.charAt(0) > 1) //7 .filter(k -> k.indexOf(0) < 0) //8 .filter(p -> !p.isBlank()) //9 .forEach(System.out::println); //10 Toggling on line 1 and 5 toggles the breakpoint correctly. Toggling on line 2,3 or 4 toggles the breakpoint at line 4 where as it should toggle at the selected line. Toggling on line 6,7,,8,9 or 10 toggles the breakpoint at line 10 where as it should toggle at the selected line.
I don't know if this is related or not but I'm experiencing similar behaviour in an anonymous class: columns.add(new DataColumn<SecuritiesRelease, SubSubject>(new StringResourceModel("subSubject", SecuritiesElasticAdminPanel.this), true, "subSubject") { private static final long serialVersionUID = 2685835547177682476L; @Override public Component wrap(SecuritiesRelease obj, int idx) { if (null != obj) { // line 1. where I want the breakpoint if (null != obj.getSubSubject() && !obj.getSubSubject().isEmpty()) { StringJoiner joiner = new StringJoiner(","); ... return new Label(WicketIdConstants.TMP, Model.of(joiner.toString())); } } return new Label(WicketIdConstants.TMP); } }.setSize(7f)); // line 2. where I get the breakpoint Toggling on line 1 where I want the breakpoint I get a breakpoint set at line 2. The process does not stop at all on line 2 either. I've noticed something. My code uses fluent api thus, at the last line (line 2) I have 'setSize(7f)'. If I remove that piece of code then toggling line 1 sets the breakpoint at line 1 where I want it, but when 'setSize(7f)' exists the breakpoint is set on line 2. Since the fluent API is used tremendously in my code it practically makes eclipse unusable for me. Version: 2022-03 (4.23.0) Build id: 20220310-1457 openjdk version "11.0.14.1" 2022-02-08 OpenJDK Runtime Environment (build 11.0.14.1+1-Ubuntu-0ubuntu1.20.04) OpenJDK 64-Bit Server VM (build 11.0.14.1+1-Ubuntu-0ubuntu1.20.04, mixed mode, sharing)
(In reply to Shai Bentin from comment #1) > I don't know if this is related or not but I'm experiencing similar > behaviour in an anonymous class: > > columns.add(new DataColumn<SecuritiesRelease, SubSubject>(new > StringResourceModel("subSubject", SecuritiesElasticAdminPanel.this), true, > "subSubject") { > private static final long serialVersionUID = 2685835547177682476L; > > @Override > public Component wrap(SecuritiesRelease obj, int idx) { > if (null != obj) { // line 1. where I want the breakpoint > if (null != obj.getSubSubject() && !obj.getSubSubject().isEmpty()) { > StringJoiner joiner = new StringJoiner(","); > ... > return new Label(WicketIdConstants.TMP, Model.of(joiner.toString())); > } > } > return new Label(WicketIdConstants.TMP); > } > }.setSize(7f)); // line 2. where I get the breakpoint > > Toggling on line 1 where I want the breakpoint I get a breakpoint set at > line 2. The process does not stop at all on line 2 either. > > I've noticed something. > > My code uses fluent api thus, at the last line (line 2) I have > 'setSize(7f)'. If I remove that piece of code then toggling line 1 sets the > breakpoint at line 1 where I want it, but when 'setSize(7f)' exists the > breakpoint is set on line 2. > > Since the fluent API is used tremendously in my code it practically makes > eclipse unusable for me. > > Version: 2022-03 (4.23.0) > Build id: 20220310-1457 > > openjdk version "11.0.14.1" 2022-02-08 > OpenJDK Runtime Environment (build 11.0.14.1+1-Ubuntu-0ubuntu1.20.04) > OpenJDK 64-Bit Server VM (build 11.0.14.1+1-Ubuntu-0ubuntu1.20.04, mixed > mode, sharing) Can you provide a simple reproducible scenario?
Created attachment 288445 [details] TestClassA
Created attachment 288446 [details] The main test class
Attached are two files. Load them in latest eclipse and you should see the problem. In my eclipse it happens
(In reply to Shai Bentin from comment #5) > Attached are two files. Load them in latest eclipse and you should see the > problem. In my eclipse it happens Thank you for the snippet, I can reproduce.
Will this be fixed for the June release? It seems quite high prioruty to me.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
