Enforce qualifier update to pick-up JDT extension-point doc fixes #1209
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
|
Why don't bump the version instead? |
It already has been bump for the 4.29 stream. |
It is not forbidden to bump it more than once ;-) |
Yes, but personally I find it a bit odd, nevertheless there is no strong reason not to do it. But what's the disadvantage of using the forceQualifierUpdate.txt? I would say, that use cases like this are its purpose. |
|
Checking the build results (I replayed the build to include the jdt.doc.isv bundle) looks very promising. The leading space was gone in the html page. 🎉 |
This was referenced Jul 9, 2023
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.
So that the changes from eclipse-jdt/eclipse.jdt.debug#278 are picked up to fix eclipse-platform/eclipse.platform#561.