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

Bug 288560

Summary:	Build anywhere
Product:	[Eclipse Project] Platform	Reporter:	John Arthorne <john.arthorne>
Component:	Releng	Assignee:	Kim Moir <kim.moir>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P4	CC:	benno.baumgartner, bernhard.merkle, frederic_fusier, kim.moir, neale, overholt, remy.suen
Version:	3.5	Keywords:	plan
Target Milestone:	3.6
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:	247332
Bug Blocks:

Description John Arthorne

2009-09-03 16:04:10 EDT

The current Eclipse project build and test infrastructure is highly customized and
tailored to a particular build environment. We will invest in simplifying and streamlining our build and test infrastructure to allow it to run in other hardware environments and be initiated by more people.

Comment 1 Kim Moir

2009-10-06 15:32:28 EDT

*** Bug 247324 has been marked as a duplicate of this bug. ***

Comment 2 Bernhard Merkle

2009-11-30 18:26:59 EST

John, if I want to make refactorings of the eclipse Platform or JDT code, how can I verify that I did not break an public API ?

Comment 3 John Arthorne

2009-12-01 09:54:40 EST

(In reply to comment #2)
> John, if I want to make refactorings of the eclipse Platform or JDT code, how
> can I verify that I did not break an public API ?

This can easily be achieved using PDE's API tools. Here is some documentation:

http://help.eclipse.org/galileo/topic/org.eclipse.pde.doc.user/tasks/api_tooling_setup.htm

Comment 4 John Arthorne

2010-05-07 09:44:46 EDT

This plan item has been committed. We have decoupled our build from local hardware dependencies, and can now run our full Helios build (minus tests) on the eclipse.org build infrastructure. This allows all committers to perform test builds in the real build environment.