New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot set breakpoint in eclipse #450

Closed
lombokissues opened this Issue Jul 14, 2015 · 10 comments

Comments

Projects
None yet
1 participant
@lombokissues
Collaborator

lombokissues commented Jul 14, 2015

Migrated from Google Code (issue 377)

@lombokissues

This comment has been minimized.

Show comment
Hide comment
@lombokissues

lombokissues Jul 14, 2015

Collaborator

👤 ludvikk   🕗 May 28, 2012 at 13:57 UTC

What steps will reproduce the problem?
1.Create blank project using eclipse eclipse-java-indigo-SR1-win32-x86_64
2.Add getter to Main class
3.Add a breakpoint to main method

What is the expected output? What do you see instead?
Break point should be set to main method. Instead it is set to @ Getter.

What version of the product are you using? On what operating system?
lombok 0.11.0 / Windows 7

Please provide any additional information below.

Collaborator

lombokissues commented Jul 14, 2015

👤 ludvikk   🕗 May 28, 2012 at 13:57 UTC

What steps will reproduce the problem?
1.Create blank project using eclipse eclipse-java-indigo-SR1-win32-x86_64
2.Add getter to Main class
3.Add a breakpoint to main method

What is the expected output? What do you see instead?
Break point should be set to main method. Instead it is set to @ Getter.

What version of the product are you using? On what operating system?
lombok 0.11.0 / Windows 7

Please provide any additional information below.

@lombokissues

This comment has been minimized.

Show comment
Hide comment
@lombokissues

lombokissues Jul 14, 2015

Collaborator

👤 ludvikk   🕗 May 28, 2012 at 14:25 UTC

Additional info: this only occurs if property is not defined at the beginning of the class.

When I move @ Getter to the beginning, I can set breakpoint.

Still, this is a defect...

Collaborator

lombokissues commented Jul 14, 2015

👤 ludvikk   🕗 May 28, 2012 at 14:25 UTC

Additional info: this only occurs if property is not defined at the beginning of the class.

When I move @ Getter to the beginning, I can set breakpoint.

Still, this is a defect...

@lombokissues

This comment has been minimized.

Show comment
Hide comment
@lombokissues

lombokissues Jul 14, 2015

Collaborator

👤 ludvikk   🕗 May 29, 2012 at 08:49 UTC

Additional info:
Setting breakpoint after last @ Getter works.
Setting breakpoint before last @ Getter sets breakpoint to the nearest follwing @ Getter

Hope this gets fixed soon ;-)

Collaborator

lombokissues commented Jul 14, 2015

👤 ludvikk   🕗 May 29, 2012 at 08:49 UTC

Additional info:
Setting breakpoint after last @ Getter works.
Setting breakpoint before last @ Getter sets breakpoint to the nearest follwing @ Getter

Hope this gets fixed soon ;-)

@lombokissues

This comment has been minimized.

Show comment
Hide comment
@lombokissues

lombokissues Jul 14, 2015

Collaborator

👤 ludvikk   🕗 May 29, 2012 at 10:23 UTC

Additional info:
"3.Add a breakpoint to main method" means add a line breakpoint inside main method. Method entry breakpoint actually works properly.

Collaborator

lombokissues commented Jul 14, 2015

👤 ludvikk   🕗 May 29, 2012 at 10:23 UTC

Additional info:
"3.Add a breakpoint to main method" means add a line breakpoint inside main method. Method entry breakpoint actually works properly.

@lombokissues

This comment has been minimized.

Show comment
Hide comment
@lombokissues

lombokissues Jul 14, 2015

Collaborator

👤 ludvikk   🕗 Jun 12, 2012 at 08:17 UTC

This bug has proved to be such a showstopper during debugging that we've decided to remove Lombok from our projects.

Collaborator

lombokissues commented Jul 14, 2015

👤 ludvikk   🕗 Jun 12, 2012 at 08:17 UTC

This bug has proved to be such a showstopper during debugging that we've decided to remove Lombok from our projects.

@lombokissues

This comment has been minimized.

Show comment
Hide comment
@lombokissues

lombokissues Jul 14, 2015

Collaborator

👤 r.spilker   🕗 Jul 02, 2012 at 21:22 UTC

Issue #240 has been merged into this issue.

Collaborator

lombokissues commented Jul 14, 2015

👤 r.spilker   🕗 Jul 02, 2012 at 21:22 UTC

Issue #240 has been merged into this issue.

@lombokissues

This comment has been minimized.

Show comment
Hide comment
@lombokissues

lombokissues Jul 14, 2015

Collaborator

👤 grootjans   🕗 Jul 02, 2012 at 21:29 UTC

Fixed with 3c0ed22.

This should be part of the next release. An earlier fix, of issue #228 caused this.

Collaborator

lombokissues commented Jul 14, 2015

👤 grootjans   🕗 Jul 02, 2012 at 21:29 UTC

Fixed with 3c0ed22.

This should be part of the next release. An earlier fix, of issue #228 caused this.

@lombokissues lombokissues added this to the 0.11.1 milestone Jul 14, 2015

@lombokissues

This comment has been minimized.

Show comment
Hide comment
@lombokissues

lombokissues Jul 14, 2015

Collaborator

👤 ludvikk   🕗 Jul 12, 2012 at 08:39 UTC

This hasn't been fixed in lombok-0.11.2.jar.

In original example:

01> import lombok.Getter;
02> public class Main {
03> public static void main(String[] args) {
04> Main m = new Main ();
05> int y = m.getX();
06> }
07> @ Getter
08> int x;
09> }

setting breakpoint to on line 5 sets it on line 8.

Collaborator

lombokissues commented Jul 14, 2015

👤 ludvikk   🕗 Jul 12, 2012 at 08:39 UTC

This hasn't been fixed in lombok-0.11.2.jar.

In original example:

01> import lombok.Getter;
02> public class Main {
03> public static void main(String[] args) {
04> Main m = new Main ();
05> int y = m.getX();
06> }
07> @ Getter
08> int x;
09> }

setting breakpoint to on line 5 sets it on line 8.

@lombokissues

This comment has been minimized.

Show comment
Hide comment
@lombokissues

lombokissues Jul 14, 2015

Collaborator

👤 ludvikk   🕗 Aug 28, 2012 at 07:44 UTC

My mistake - I forgot to update Eclipse plugin.
I can confirm fix works.

Thanks

Collaborator

lombokissues commented Jul 14, 2015

👤 ludvikk   🕗 Aug 28, 2012 at 07:44 UTC

My mistake - I forgot to update Eclipse plugin.
I can confirm fix works.

Thanks

@lombokissues

This comment has been minimized.

Show comment
Hide comment
@lombokissues

lombokissues Jul 14, 2015

Collaborator

End of migration

Collaborator

lombokissues commented Jul 14, 2015

End of migration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment