I know there's already a thread on doing a headless build, but that's a year old and it didn't help me solve the problem.
I want to find out how to run a headless eclipse on a (Linux) server and invoke the 'Generate Build Files' and 'Build Head' methods on the PluginBuilder plugin I've created.
I've had a look at the RubyEclipse SVN repository as mentioned in the old thread (http://rubyeclipse.svn.sourceforge.net/viewvc/rubyeclipse/trunk/org.rubypeople.rdt.build/cruiseControl/ is the correct URL), but I didn't see anything there to help.
Thanks
Steven Dick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do not know exactly what your question is, so I just describe the process, please let me know where you need further information.
1) In your regular development environment you create a new pluginbuilder project, most of the scripts for running the headless builds are now available there
2) You select the features you want to build from the features in your workspace
3) You generate the build files: pluginbuilder creates/updates the remaining files for the headless build, mainly the scripts/map files for accessing the repository
If you want to build on a server, you can copy all the files over and just add/modify the build_local.properties file where you find the os/ws/arch, location of Eclipse installation or Eclipse zip file and some more specifics for your environment. Then start the build on your linux server with ant from the command line. There is also a build target in build.xml which you can call from cruise control.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the quick reply. I think I now understand where I was going wrong.
My goal was to do both the build file generation and build invocation on the headless server. That way I can avoid having the developers re-generate the build files manually if they add a new plug-in to a feature to be built.
That's not a major problem, as the PluginBuilder is better than our current automated PDE build process.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know there's already a thread on doing a headless build, but that's a year old and it didn't help me solve the problem.
I want to find out how to run a headless eclipse on a (Linux) server and invoke the 'Generate Build Files' and 'Build Head' methods on the PluginBuilder plugin I've created.
I've had a look at the RubyEclipse SVN repository as mentioned in the old thread (http://rubyeclipse.svn.sourceforge.net/viewvc/rubyeclipse/trunk/org.rubypeople.rdt.build/cruiseControl/ is the correct URL), but I didn't see anything there to help.
Thanks
Steven Dick
I do not know exactly what your question is, so I just describe the process, please let me know where you need further information.
1) In your regular development environment you create a new pluginbuilder project, most of the scripts for running the headless builds are now available there
2) You select the features you want to build from the features in your workspace
3) You generate the build files: pluginbuilder creates/updates the remaining files for the headless build, mainly the scripts/map files for accessing the repository
Now you have everything in place to start a headless build with ANT, for an example see
http://pluginbuilder.svn.sourceforge.net/viewvc/pluginbuilder/trunk/org.pluginbuilder.build
If you want to build on a server, you can copy all the files over and just add/modify the build_local.properties file where you find the os/ws/arch, location of Eclipse installation or Eclipse zip file and some more specifics for your environment. Then start the build on your linux server with ant from the command line. There is also a build target in build.xml which you can call from cruise control.
Thanks for the quick reply. I think I now understand where I was going wrong.
My goal was to do both the build file generation and build invocation on the headless server. That way I can avoid having the developers re-generate the build files manually if they add a new plug-in to a feature to be built.
That's not a major problem, as the PluginBuilder is better than our current automated PDE build process.