Eclipse Community Forums: Equinox » How to properly build a full branded Eclipse install?

Home » Eclipse Projects » Equinox » How to properly build a full branded Eclipse install?

How to properly build a full branded Eclipse install? [message #506498]

Thu, 07 January 2010 12:50

Eclipse User

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 07:50] by Moderator

Re: How to properly build a full branded Eclipse install? [message #506683 is a reply to message #506498]

Fri, 08 January 2010 12:50

Eclipse User

Hello,

Maybe you could have a look at EPP, which is used to package official Eclipse IDE distributions.
Otherwise, you can simply download an Eclipse distribution and add your favourite features and plugins using p2 director (see eclipse wiki).
Or, you can alse think about creating your own RCP product.

HTH

--
Mickael Istria - BonitaSoft S.A.
http://www.bonitasoft.com/products/downloads.php

Re: How to properly build a full branded Eclipse install? [message #506730 is a reply to message #506498]

Fri, 08 January 2010 21:53

Eclipse User

The message "This installation has not been configured properly for Software Updates" refers to a missing system property.

Try adding -Declipse.p2.profile=<some_profile_id> to your launch. I think the RCP build would have created a profile named "profile" for you, but you can verify that by checking in your <product build results folder>/eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry.
Software updates should work now..

Re: How to properly build a full branded Eclipse install? [message #507552 is a reply to message #506498]

Wed, 13 January 2010 14:51

Eclipse User

We use a product plugin to create the e4 SDK builds at
http://download.eclipse.org/e4/downloads/

Basically we get the entire Eclipse SDK/Equinox SDK into a local p2
site, build our features into an p2 site, and then create our product
from both p2 repos.

The work is mostly done in our build.properties and
http://dev.eclipse.org/viewcvs/index.cgi/e4/releng/org.eclip se.e4.builder/builder/general/customTargets.xml?view=co

PW

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .platform.doc.isv/guide/workbench.htm

Previous Topic:	Web application
Next Topic:	EJB call on WAS with an RAP application

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 26 02:41:16 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter