| How to properly build a re-branded Eclipse distribution [message #9625] |
Tue, 01 July 2008 18:51 |
 Jason Woods
Messages: 29
Registered: July 2009 |
Junior Member |
|
|
What is the recommended way to properly build (in a headless environment)
a re-branded version of Eclipse (the full IDE version) with an additional
set of user-defined features and plugins (in 3.4)? The end product of
this build needs to be a full Eclipse IDE distribution like you would pull
from the Eclipse website.
Dating back several years, we have always built using a custom build
script that would build our plugin source against an Eclipse installation
on the build machine. It would then package everything up into a
packaging directory, which would typically involve nothing much more than
a copying of files from the build dir and the eclipse install dir. This
would then be shoved through an install target to build an installer image.
With this whole p2 thing we can no longer just drop our built plugins and
features into a plugins directory and have it work. Putting our code into
the "dropins" folder doesn't seem appropriate in this case either.
Is PDE build capable of building an entire eclipse distribution, or does
it just build plugins/features?
Is there a better mechanism, or do we just update our build script to edit
the bundles.info file, etc.?
|
|
|
Powered by
FUDForum. Page generated in 0.02507 seconds
] 
Search
Help
Register
Login
Home
