Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 203585 - Make Version info of lancher configurable by product branding
Summary: Make Version info of lancher configurable by product branding
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 154088
  Show dependency tree
 
Reported: 2007-09-17 09:01 EDT by Yves Harms CLA
Modified: 2019-11-14 03:45 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yves Harms CLA 2007-09-17 09:01:49 EDT 
Build ID: I20070625-1500

Please make the version info of the lancher executable (eclipse.exe) configurable.
The version info should be editable in the product file for the build.
On Mac OSX we can patch the info.plist in our headless build script but on windows the info is coded into the binary exe file.

Why is this useful and even important for some rcp customers ?
Some software products used by our corporate customers for application distribution use the version info of the executable to determine the product version.
Comment 1 Torsten Witte CLA 2012-01-16 16:49:17 EST 
In https://bugs.eclipse.org/bugs/show_bug.cgi?id=294827 it seems that it is possible to set the VERSIONINFO of the launcher, but it is not shown how to do that.
Comment 2 Lars Vogel CLA 2019-11-14 03:45:15 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.