Community
Participate
Working Groups
Error: Syntax error on token "}", delete this token. When you delete it, save project and put it again it works. When you clean up the project it works.
Moving to JDT Core to look at. Please provide sample code to reproduce the problem or at least take a screenshot of the issue.
Is it really needed?
(In reply to h m from comment #2) > Is it really needed? Yes, please. What you described seems related to a specific code and without a reproducible testcase, it is impossible for us to work on this.
Created attachment 288450 [details] error
Created attachment 288451 [details] error 2
It is often on the same classes and doesn't happen all the time. If you have some debug method I can try it.
It may be related to /* */ comments, as both of the classes that have this error right now has them.
Created attachment 288452 [details] another errors
(In reply to h m from comment #7) > It may be related to /* */ comments, as both of the classes that have this > error right now has them. Can you attach the testcase as source code? Images don't really help us when it comes to testcases.
I don't want to share my source code here, it happens everyday, so it's easy to test. I'm pretty sure it happens then there are comments in there.
(In reply to h m from comment #10) > I don't want to share my source code here, it happens everyday, so it's easy > to test. I'm pretty sure it happens then there are comments in there. You don't have to do that. You only have to extract it to a smaller test project or code and share it with us. There has to be something about your project/code/set-up that it only occurs with your workspace. Obviously, it's not a problem for others. So, please see if you can put it in a small reproducible testcase.
Both classes have /* */ comments inside the method, maybe that's the case?
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.
