Suggestion
During the release preparation the feature org.eclipse.help always requires a version increment that currently has to be applied manually, see:
... because we don't want to check version increments of the entire this repository all the time.
At the same time it contains only Plug-ins from Equinox and the eclipse-platform git repository:
|
<plugin |
|
id="org.eclipse.equinox.http.jetty" |
|
version="0.0.0"/> |
|
|
|
<plugin |
|
id="org.eclipse.equinox.http.registry" |
|
version="0.0.0"/> |
|
|
|
<plugin |
|
id="org.eclipse.equinox.http.servlet" |
|
version="0.0.0"/> |
|
|
|
<plugin |
|
id="org.eclipse.equinox.jsp.jasper" |
|
version="0.0.0"/> |
|
|
|
<plugin |
|
id="org.eclipse.equinox.jsp.jasper.registry" |
|
version="0.0.0"/> |
|
|
|
<plugin |
|
id="org.eclipse.help.base" |
|
version="0.0.0"/> |
|
|
|
<plugin |
|
id="org.eclipse.help.ui" |
|
version="0.0.0"/> |
|
|
|
<plugin |
|
id="org.eclipse.help.webapp" |
|
version="0.0.0"/> |
|
|
|
<plugin |
|
id="org.eclipse.core.net" |
|
version="0.0.0"/> |
|
|
|
<plugin |
|
id="org.eclipse.equinox.security" |
|
version="0.0.0"/> |
Therefore I propose to move it 'down' to the eclipse-platform git repository so that the version increment workflow in that repository can handle it.
Due to the described content, I think this would be generally the more suitable location anyways.
Any objections or remarks?
I can offer to conduct that move, but wonder if I should preserve the history (e.g. by branch-filtering) or if it would be fine to just remove it here and add it back in the target repo (with an exact link to the source)?
Community
Suggestion
During the release preparation the feature
org.eclipse.helpalways requires a version increment that currently has to be applied manually, see:... because we don't want to check version increments of the entire this repository all the time.
At the same time it contains only Plug-ins from Equinox and the
eclipse-platformgit repository:eclipse.platform.releng.aggregator/eclipse.platform.releng/features/org.eclipse.help-feature/feature.xml
Lines 24 to 62 in 792093a
Therefore I propose to move it 'down' to the
eclipse-platformgit repository so that the version increment workflow in that repository can handle it.Due to the described content, I think this would be generally the more suitable location anyways.
Any objections or remarks?
I can offer to conduct that move, but wonder if I should preserve the history (e.g. by branch-filtering) or if it would be fine to just remove it here and add it back in the target repo (with an exact link to the source)?
Community