|How to properly build a full branded Eclipse install? [message #506498]
||Thu, 07 January 2010 17:50
| Jason Woods
Registered: July 2009
Prior to p2, we use to take an existing pristine Eclipse SDK download, copy it into a staging directory (and remove some of the unnecessary plugins), and add some custom plugins of our own, etc. into it. We rebranded it via changes to the config.ini file. The result was basically zipped up and put into an installer.|
Doing the same thing now with p2 still sort of works, but we are unable to use the Software Update mechanism...it complains about "This installation has not been configured properly for Software Updates".
So what is the proper way now to package/build a full rebranded Eclipse SDK (without having to rebuild all of Eclipse or use any sort of remote update site)?
[Updated on: Thu, 07 January 2010 12:50]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01703 seconds