Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 253269

Summary:	make start.sh build.xml
Product:	z_Archived	Reporter:	Andrew Overholt <overholt>
Component:	Dash Athena	Assignee:	Common Build Inbox <dash.commonbuilder-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	gunnar, nboldt, pwebster, richard.gronback
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	252028, 253268

Description Andrew Overholt

2008-11-03 14:52:04 EST

For cron-driven (or CC-driven or whatever) we can have a simple shell script that wraps build.xml but we should preferably launch directly from ant.

Comment 1 Nick Boldt

2009-01-16 12:14:44 EST

slip

Comment 2 Nick Boldt

2009-02-16 13:05:58 EST

OK, we're not quite pure ant yet, but we're a lot closer.

Now, start.sh is little more than a wrapper for buildAll.xml, as it does this:

* create build dir
* check out three required releng projects (or symlink them if they already exist locally)
* collect commandline vars and feed them to the ant script (if not set in project's build.properties)
   * bare minimum is now projectid & version - everything else should be settable in build.properties, including URLs for dependencies.
* calculate which ant and java runtime to use when launching Eclipse's AntRunner for the ant script

There are also two wrappers for this script:

* start_logger.sh, which runs start.sh and dumps the results to a buildlog.txt in the build folder
* org.eclipse.dash.commonbuilder.releng/hudson/*.sh, which call start.sh from Hudson.

To make this pure Ant, I think we'll either need some Eclipse launchers so that the whole thing cab be run within a running Eclipse instance, or perhaps a build.xml in the project's releng folder which sets some default variables (projectid, version) and calls buildAll.xml to run the build. These could also be set in a launcher config, but that's not as "in Eclipse or out of Eclipse" portable, and I'd like this to be as "run anywhere" as possible.

Comment 3 Nick Boldt

2009-02-26 01:40:03 EST

For the moment, start.sh will continue to be used for headless- and Hudson-based builds.

For building in Eclipse, however, users can run a simple build.xml.

Here's an example build.xml, complete with launch config (build.xml.launch):

http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.dash/athena/org.eclipse.dash.commonbuilder/org.eclipse.gef.releng/?root=Technology_Project

Closing bug, as we can now build from within Eclipse w/o the need for start.sh.