-
Notifications
You must be signed in to change notification settings - Fork 130
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
Issue with code fence > 3 in markdown comment #3006
Conversation
Test case for eclipse-jdt/eclipse.jdt.core#3006 Also by: Stephan Herrmann <[email protected]>
Test case for eclipse-jdt/eclipse.jdt.core#3006 Also by: Stephan Herrmann <[email protected]>
Test case for eclipse-jdt/eclipse.jdt.core#3006 Also by: Stephan Herrmann <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see no fault, but some questions for improving our understanding of the strategy.
...core.compiler.batch/src/org/eclipse/jdt/internal/compiler/parser/IMarkdownCommentHelper.java
Show resolved
Hide resolved
....core.compiler.batch/src/org/eclipse/jdt/internal/compiler/parser/AbstractCommentParser.java
Show resolved
Hide resolved
I have no idea why the build is failing. Only theory I can think of is the compilation pref has changed somehow (tycho?). |
This:
is used only inside javadoc, so if javadoc analysis doesn't find the reference, then it will be marked as unused. Did anyone just change javadoc analysis? ;-P |
OK, I see that setting the linePtr indiscriminately is wrong. Will take a look. |
Something's messed up in my last commit that undid the changes to one file. This needs another attempt. |
Test case for eclipse-jdt/eclipse.jdt.core#3006 Also by: Stephan Herrmann <[email protected]>
Test case for eclipse-jdt/eclipse.jdt.core#3006 Also by: Stephan Herrmann <[email protected]>
What it does
Fixes #3004
How to test
Author checklist