-pedantic: Add hint that Eclipse restart is required #6511
+6
−5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adjust description of the warning, so at least it is mentioned somewhere. unfortunatelly I could not figure out how to reliably sync the Processor.pendatic field with the .bnd files on change. The problem is that Processor.pendatic can be set via .bnd files but also via Processor.setPedantic(boolean) e.g. from testcases, there is some magic caching going on in Processor.begin() and Processor.getProperties() which I was not able to figure out, what to call so that the Workspace Refresh Button behaves the same as an Eclipse restart. Signed-off-by: Christoph Rueger <[email protected]> Update pedantic.md
chrisrueger
force-pushed
the
6507-pedantic-change-requires-eclipse-restart
branch
from
faf0f1d to
18e8178
Compare
chrisrueger
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #6507
This is not really a fix, but a band-aid.
Adjust description of the warning, so at least it is mentioned somewhere. unfortunatelly I could not figure out how to reliably sync the
Processor.pendaticfield with the.bndfiles on change. The problem is thatProcessor.pedanticcan be set via.bndfiles but also viaProcessor.setPedantic(boolean)e.g. from testcases, there is some magic hen-egg-caching going on inProcessor.begin()andProcessor.getProperties()If anybody has a better idea, feel free.