| Summary: | branding plugins buildId aren't updated | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Technology] CBI | Reporter: | Paul Webster <pwebster> | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Component: | prototype | Assignee: | CBI Dummy user <cbi.prototype-inbox> | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Severity: | normal | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Priority: | P3 | CC: | andrea.ross, igor, jan.sievers, john.arthorne, thanh.ha | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Version: | 1.0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Hardware: | PC | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Bug Depends on: | 395932, 395933, 395934 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Bug Blocks: | 372792 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Description
Paul Webster
This shows up in the Help>About dialog for all branded features. PW Created attachment 222079 [details]
buildid replacement patch
I took a first try at this issue by using the maven-antrun-plugin to replace @build@ with ${unqualifiedVersion}.${buildQualifier} which results in a buildid of "3.8.0.v20120523-1245". What should we use as the buildid?
Problem I see with this patch however is the token replace task modifies the about.mappings so the next time someone runs a build it won't replace the buildid unless they "git checkout about.mappings" to reset the file. Is there perhaps a better plugin for replacing tokens to use in this case?
Comment on attachment 222079 [details]
buildid replacement patch
As far as I can tell, buildid will be replaced in the source file, i.e. the file will appear as modified in "git status" after the build.
Igor, is the other way to deal with this to write something in the maven-cbi-plugin that could copy that file into dir/target, replace the token, but still use it as the about.mappings resource? PW This would required code changes in tycho. one way to do this would be with maven-resource-plugin:
<properties>
<build>${unqualifiedVersion}.${buildQualifier}</build>
</properties>
<build>
<resources>
<resource>
<directory>.</directory>
<filtering>true</filtering>
<includes>
<include>about.mappings</include>
</includes>
</resource>
</resources>
</build>
I verified this does the replacement in target/classes/about.mappings but unfortunately we can't include that via bin.includes in the jar. See tycho bug 362252
Created attachment 223599 [details]
patch
this is kind of a hack but works without having to replace file content in-place
Created attachment 223713 [details]
jdt patch
Created attachment 223714 [details]
pde patch
Created attachment 223715 [details]
platform.common patch
Created attachment 223716 [details]
platform patch
Created attachment 223717 [details]
platform.releng patch
Created attachment 223718 [details]
platform.resources patch
Created attachment 223719 [details]
platform.runtime patch
Created attachment 223720 [details]
platform.ua patch
I attached patches that use a profile "update-branding-plugins" which needs to be activated manually to trigger the build to update the about.mappings files. This patch is based on the original patch that used antrun to replace the token in about.mappings. Created attachment 223964 [details]
jdt.patch v2
Created attachment 223965 [details]
pde.ui.patch v2
Created attachment 223966 [details]
platform.common.patch v2
Created attachment 223967 [details]
platform.patch v2
Created attachment 223968 [details]
platform.releng.patch v2
Created attachment 223969 [details]
platform.resources.patch v2
Created attachment 223970 [details]
platform.runtime.patch v2
Created attachment 223972 [details]
platform.ua.patch v2
After discussing with Paul this morning. We decided that the @build@ variable should be replaced with the ${buildId} variable, the attached updated patches were modified to use ${buildId}.
Created attachment 223987 [details]
jdt.patch v3
Created attachment 223988 [details]
pde.ui.patch v3
Created attachment 223989 [details]
platform.common.patch v3
Created attachment 223990 [details]
platform.patch v3
Created attachment 223991 [details]
platform.releng.patch v3
Created attachment 223992 [details]
platform.resources.patch v3
Created attachment 223993 [details]
platform.runtime.patch v3
Created attachment 223994 [details]
platform.ua.patch v3
(In reply to comment #28) > Created attachment 223989 [details] > platform.common.patch v3 This one failed to apply to the latest R4_2_maintenance of eclipse.platform.common PW (In reply to comment #29) > Created attachment 223990 [details] > platform.patch v3 Released as http://git.eclipse.org/c/platform/eclipse.platform.git/commit/?h=R4_2_maintenance&id=7c1dc22e9beeefc53bb137f7891dc125605cae6d and http://git.eclipse.org/c/platform/eclipse.platform.git/commit/?h=R3_8_maintenance&id=6f8f39c2b84fc251aa22ee0149bfe3f657eba676 Thanh, forgot to set you as the author, I'll get it right next time. PW (In reply to comment #30) > Created attachment 223991 [details] > platform.releng.patch v3 Released with http://git.eclipse.org/c/platform/eclipse.platform.releng.git/commit/?h=R4_2_maintenance&id=ab0e829b33b8daf81b7b36372ddc792aec8721f7 and http://git.eclipse.org/c/platform/eclipse.platform.releng.git/commit/?h=R3_8_maintenance&id=8756742b7114af0fc110b098ed5813f0184860fe PW Created attachment 224072 [details]
platform.common.patch v4
Updated patch to apply against latest R4_2_maintenance branch.
(In reply to comment #32) > Created attachment 223993 [details] > platform.runtime.patch v3 Released as http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/?h=R4_2_maintenance&id=8bac5c35cf2b4c6162076bd6a203a72800721804 We didn't branch e.p.runtime for 3.8.x and John says this particular fix is not important enough for that. PW (In reply to comment #33) > Created attachment 223994 [details] > platform.ua.patch v3 Released as http://git.eclipse.org/c/platform/eclipse.platform.ua.git/commit/?h=R3_8_maintenance&id=0fbf4122097e87d0a8694576adbc626dffd797a2 PW (In reply to comment #37) > Created attachment 224072 [details] > platform.common.patch v4 Released http://git.eclipse.org/c/platform/eclipse.platform.common.git/commit/?h=R4_2_maintenance&id=5a266c23075d8a8bdf06143a8e7a9f5d3775fc80 and http://git.eclipse.org/c/platform/eclipse.platform.common.git/commit/?h=R3_8_maintenance&id=e5f4de8cf713f9fabadd5e8e47b2dc811062f19b PW All of these patches have been applied. Is this one done? (In reply to comment #41) > All of these patches have been applied. Is this one done? Yes the patches have been applied. Setting this bug to resolved. |