I have been messing around with the build framework inside PDE and
have been able to successfully build EclipseFP from the command line.
There are some unresolved issues, though.
The current automatically generated .zip includes all of our plugins,
with the exception of core.jparser. This one presents some issues
because of the need of an intermediate build phase to translate the
parser grammar to java source code.
The other issue is the need to manually organize the build structure.
The build scripts from PDE expect a tree with two directories:
features and plugins. The plugin projects go under the 'plugins' dir
and the feature projects go under the 'features' dir. When building an
eclipse "official" component, this distribution is done automatically
by the script that fetches the sources from CVS. At least this is the
conclusion I have come to. It happens that our code-base isn't
CVS-controlled, so we need to do the distribution ourselves.
I haven't published the code because I wasn't able to remove that
dependency to my personal environment from the build script for
jparser yet. For the most curious, the latest code can be found on my
I'll be working a little more on this. This is the current status.
The build scripts are ready on the jparser branch.
A new project net.sf.eclipsefp.haskell.build was created on our source
tree. It includes a README file with detailed instructions on how to
There is a shell script for starting everything under Linux. Maybe
someone could contribute a Windows version if there is need for one.
I think this changes are ready to be merged back into the main
development branch. Please let me know if there is interest.
Get latest updates about Open Source Projects, Conferences and News.