[RelEng] Update qualifier of o.e.help.webapp during release preparation #2153
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.
As noted in #2134 (comment), the
o.e.help.webappproject currently needs a qualifier update during preparation of a new release cycle as the content of the generated jsp files changes then.This extends the individual release preparation script for this repo do apply that update.
As it would be even better to avoid qualifier updates (and thus version updates), without content change I tried to investigate where the content of the differing generated files has changed. Comparing the class files respectively the java source files from which they are compiled, showed that for example
org/eclipse/help/internal/webapp/jsp/advanced/advanced_jsp.javacontains the following lines:and the value put for the
/advanced/header.jsphas changed.But I don't know how that value is computed and how a change just because of a parent version change could be prevented?
If anybody has an idea and knows how we could enhance the build, please let me know, since I would be happy to avoid an enforced qualifier update.