blob: fdebe6b40be7dbbf995a479d9588a24bcdf559fe [file] [log] [blame]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="" type="text/css">
<title>Contributing a port to an Eclipse build</title>
<span style="font-weight: bold;">Contributing an Eclipse port</span><br>
<i><b>DRAFT </b></i>
<p>Last updated: August 22, 2007</p>
The Eclipse platform team has limited hardware and platform resources
to compile and produce builds of Eclipse on a wide variety of
platforms. This document describes the mechanism to provide a build for
a operating system-windowing system-architecture (os-ws-arch) that is
not currently built by the platform team.
<p>In assuming this role, teams
or individuals will be expected to perform the following tasks. .&nbsp; <br>
<li>Meet; <a href="">legal
<li>Garner PMC support for new port.</li>
<li>Become a <a href="">committer</a> and sign the associated legal documents.
<li>Contribute the new swt fragment.</li>
<li>Contribute patches required for build and run Eclipse on the
new platform.</li>
<li>Run the build and conduct automated tests during the test pass of each <a href="">milestone</a></li>
<li>Investigate, provide patches and resolve platform specific bugs.</li>
<li>Upload a tested build for inclusion in upcoming Eclipse
platform <a href="">milestones</a> and
releases to the infrastructure.<a
These conditions must be met before a port will be provided on<br>
The process to include an external build on is as follows:<br>
<li>Open a <a href="">bug</a> with the
Product Platform and Component Releng describing the os-ws-arch platform
to be used for the build.&nbsp; The
platform releng team will arrange for PMC approval of support of this new
drop. Once approved, a
new project may need to be created to provide swt libraries for this
will also need to be approved as a committer by the PMC to have commit
rights to new platform-specific libraries
required by your contributed build. As part of this progress, you will
agree to the <a href="">committer
due diligence guidelines</a>.</li>
<li>Once approval is granted, use the&nbsp; <a
Build</a> or <a
Fetch build</a> scripts to generate a SDK build.&nbsp; Incorporate platform
specific patches in these scripts and test the resultant build.&nbsp; A
bug describing the patches to ensure that the build runs should be
opened with Product Platform and Component Releng.&nbsp; We will
incorporate these patches into our build scripts or ensure that they
are included in other teams code base as appropriate. </li>
<li>The cvs tag of&nbsp; the builder projects (org.eclipse.releng,
org.eclipse.releng.eclipsebuilder and org.eclipse.releng.basebuilder)
that was used to create the build will be listed on the test results
page of the build. Refer to the <a href="">platform
releng build schedule</a> if you need additional information about upcoming builds </li>
<li><a mailto="">Run the automated tests for
your platform after you have
successfully completed the build.</a></li>
<li>Request a ftp account on from <a
href=""></a> </li>
<li>Copy the build to the staging area for eclipse downloads. </li>
<tt>/home/data/httpd/download-staging.priv/eclipse/downloads/&lt;your organization&gt;</tt>
<li>Once you have pushed your
files to the server, notify the releng team that your file available. They
will move it to the appropriate directory so it's available for download