| Summary: | Change "versioning" of rcp.config feature to use qualifier of v${buildTimestamp} | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | David Williams <david_williams> |
| Component: | Releng | Assignee: | David Williams <david_williams> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | arunkumar.thondapu, lshanmug |
| Version: | 4.5 | ||
| Target Milestone: | 4.5 M7 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 434596 | ||
*** Bug 458572 has been marked as a duplicate of this bug. *** |
"We" do not really use this feature any more (or, much) ... but when ever the "launchers" are changed, this feature needs it's qualifier updated to "pick them up", else it is "swaped out" for previous feature (no change being detected, in Git) and this is a source of "over complication", trying to coordinate with other teams, etc., for stuff in "unrelated repositories". In theory, perhaps the feature could be "moved" to same repo as launchers, but, since we hardly need it (and may not at all, in future) that seems like overkill. Instead, I propose to simply update the qualifier every build, similar to how we do for "branding bundles" and "root features". Namely, configure the versioning plugin <plugin> <groupId>org.eclipse.tycho</groupId> <artifactId>tycho-packaging-plugin</artifactId> <version>${tycho.version}</version> <configuration> <format>'v${buildTimestamp}'</format> </configuration> </plugin>