development/index.php - gerrit/www.eclipse.org/tm - Git at Google


            
            <?php  																														require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); 	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); 	$App 	= new App();	$Nav	= new Nav();	$Menu 	= new Menu();		include($App->getProjectCommon());    # All on the same line to unclutter the user's desktop'


            	#*****************************************************************************

            
            	#

            
            	# development/index.php

            
            	#

            
            	# Author: 		Martin Oberhuber

            
            	# Date:			2006-02-10

            
            	#

            
            	# Description: TM developer resources page

            
            	#

            
            	#

            
            	#****************************************************************************


            	#

            
            	# Begin: page-specific settings.  Change these.

            
            	$pageTitle 		= "TM Developer Resources";

            
            	$pageKeywords	= "developer,resources,device,target";

            
            	$pageAuthor		= "Martin Oberhuber";


            	# Add page-specific Nav bars here

            
            	# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)

            
            	# $Nav->addNavSeparator("My Page Links", 	"downloads.php");

            
            	# $Nav->addCustomNav("My Link", "mypage.php", "_self", 3);

            
            	# $Nav->addCustomNav("Google", "http://www.google.com/", "_blank", 3);


            	# End: page-specific settings

            
            	#


            	# Paste your HTML content between the EOHTML markers!

            
            	$html = <<<EOHTML


            <div id="maincontent">

            
            	<div id="midcolumn">

            
            	<h1>$pageTitle</h1>


            		<div class="homeitem">

            
            			<h3>Development Tools</h3>

            
            				<ul class="midlist">

            
            					<li><b><a

            
            						href="/tm/development/cvs_setup.php">CVS Repository</a></b><br/>

            
            						TM development is managed in

            
            						<!-- two CVS repositories:

            
            						<ul class="midlist">

            
            							<li>The <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.core/?cvsroot=Tools_Project">Core Repository</a>

            
            						    <li>The <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.rse/?cvsroot=Tools_Project">RSE Repository</a>

            
            						</ul>

            
            						-->

            
            						the <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.rse/?cvsroot=Tools_Project">RSE</a> and

            
            						<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.core/?cvsroot=Tools_Project">Core</a> Repositories.

            
            						To populate an Eclipse workspace with our code, best use our

            
            						<a href="/tm/development/cvs_setup.php">Team Project Sets</a>.

            
            						A

            
            						<a href="http://download.eclipse.org/tm/downloads/drops/N-changelog/index.html">

            
            						CVS Changelog</a> is available, and you can subscribe to commit notifications on

            
            						<a href="https://dev.eclipse.org/mailman/listinfo/tm-cvs-commit">tm-cvs-commit</a>.</li>

            
            					<li><a href="/tm/development/bug_process.php" target="_self"><b>Bug Process</b></a><br>

            
            					   View <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Target+Management&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit">all open</a> issues

            
            					   | <a target="_top" href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Target%20Management&version=unspecified&component=RSE">Submit new</a> bugs

            
            					   | Request an <a target="_top" href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Target%20Management&version=unspecified&component=RSE&rep_platform=All&op_sys=All&priority=P3&bug_severity=enhancement&form_name=enter_bug">enhancement</a>

            
            					</li>

            
            					<li><b><a

            
            						href="http://www.eclipse.org/webtools/development/apiscanner/apiscanner.html">Eclipse API Scanner</a></b><br/>Describe the API of a component and scan plug-ins for API

            
            						violations (from the <a href="http://www.eclipse.org/webtools"

            
            						target="_self">WebTools</a> project).</li>

            
            					<li><b><a href="http://www.eclipse.org/webtools/development/piitools/piitools.html">Check

            
            						Unused Properties Tool</a></b> <br>

            
            						Scan property files for unused messages (from the <a

            
            							href="http://www.eclipse.org/webtools" target="_self">WebTools</a>

            
            						project).</li>

            
            					<li><b><a href="http://www.eclipse.org/eclipse/platform-core/downloads.html">Core

            
            						Tools</a></b> <br>

            
            						Useful utilities from the Platform team. Consider adding their

            
            						<a href="http://www.eclipse.org/eclipse/platform-core/downloads.html#updates">

            
            						update site</a> to your configuration.</li>

            
            					<li><b><a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.rse/releng/org.eclipse.rse.build/README_build.txt?revision=1.2&root=Tools_Project">

            
            						Building RSE</a></b><br/>

            
            						Instructions how to perform unattended builds of TM / RSE.</li>

            
            					<li><b><a

            
            						href="http://wiki.eclipse.org/Platform-releng">Release Engineering</a></b> <br>

            
            						See the instructions, FAQs and help from the Platform-Releng team.</li>

            
            					<!-- Dashboard is currently not useful.

            
            					<li><b><a

            
            						href="http://www.eclipse.org/projects/dashboard/dashboard_detail.php?project=tools.tm">Project

            
            						Dashboard</a></b> <br>

            
            						View generated project statistics.</li>

            
            					-->

            
            					<li><b><a

            
            						href="https://dev.eclipse.org/committers">Eclipse Committer

            
            						Tools</a></b> <br>

            
            						Information on infrastructure status, file path information,

            
            						FAQs, etc. [login required]</li>

            
            				</ul>

            
            		</div>

            
            		<div class="homeitem">

            
            			<h3>Development Resources</h3>

            
            				<ul class="midlist">

            
            					<li><b><a href="/tm/development/committer_howto.php">Committer HOWTO</a></b><br>

            
            						Simple cookbook instructions for performing basic tasks properly.

            
            						Committers need to follow check-in conventions and IP Due Diligence as outlined

            
            						<a href="/tm/development/committer_guide.php">here</a>.

            
            						</li>

            
            					<li><b><a href="http://wiki.eclipse.org/API_Central">API Guidelines</a></b><br>

            
            						Look <a href="http://help.eclipse.org/help30/topic/org.eclipse.platform.doc.isv/reference/misc/api-usage-rules.html">

            
            						here</a> for general Eclipse API rules of engagement. We strive to achieve

            
            						<a href="http://www.eclipse.org/projects/dev_process/eclipse-quality.php">

            
            						Eclipse Quality</a>, as outlined in the draft of

            
            						<a href="http://www.eclipse.org/projects/dev_process/Eclipse%20Quality%20APIs%20v2.pdf">

            
            						Eclipse Quality APIs</a>.

            
            						</li>

            
            					<li><b><a href="http://wiki.eclipse.org/Development_Conventions_and_Guidelines">

            
            					    Development Conventions and Guidelines</a></b><br>

            
            						Coding standards, naming conventions, and other

            
            						guidelines used by the Platform. TM will use these conventions

            
            						until such time as deviation is required.</li>

            
            			    	<li><b><a href="http://www.eclipse.org/downloads/download.php?file=/tm/presentations/2006-9-29_SummitEurope_TMOverview.pdf">

            
            						Architectural Overview</a></b><br>

            
            						A high level summary of the components and their architecture.</li>

            
            					<li><b><a

            
            							href="http://www.eclipse.org/tm/doc/TM_Use_Cases_v1.1c.pdf">Project

            
            						Requirements</a></b> <br>

            
            						Look here for a list of the project use cases and their

            
            						priorities.</li>

            
            					<li><b><a

            
            						href="http://www.eclipse.org/tools/eclipsetools-charter.php">Charter</a></b>

            
            						<br>

            
            						As a Tools subproject, the TM project abides by the

            
            						<a href="/tools/eclipsetools-charter.php">Tools Project charter</a> and the

            
            						<a href="http://www.eclipse.org/projects/dev_process/Eclipse_Standard_TopLevel_Charter_v1.0.php">

            
            						Eclipse Standard Charter</a>.</li>

            
            					<li><b><a

            
            							href="/tm/development/contributors.php">Contributors

            
            						and Committers</a></b> <br>

            
            						List of TM Project contributors and committers.</li>

            
            				</ul>

            
            		</div>

            
            	</div>


            	<div id="rightcolumn">

            
            		<div class="sideitem">

            
            			<h6>Getting started</h6>

            
            			<ul>

            
            				<li><a href="http://www.eclipse.org/downloads/download.php?file=/tm/presentations/2006-9-29_SummitEurope_TMOverview.pdf"

            
            					target="_self">TM Overview Slides</a></li>

            
            				<li><a href="http://www.eclipse.org/project-slides/TM_3.0_Release_Review.pdf" target="_self">

            
            				    TM 3.0 Release Review Slides</a></li>

            
            				<li><a href="http://www.eclipse.org/downloads/download.php?file=/tm/presentations/TM_2.0_Release_Review.ppt" target="_self">

            
            				    TM 2.0 Release Review Slides</a></li>

            
            				<li><a

            
            					href="/tm/doc/TM_Use_Cases_v1.1c.pdf"

            
            					target="_top">TM Use Cases Document</a></li>

            
            				<!-- <li><a href="/tm/development/index.php">Developer Resources</a></li> -->

            
            				<li><a href="/tm/doc/index.php">Developer Documents</a></li>

            
            			</ul>

            
            		</div>

            
            	</div>

            
            </div>


            EOHTML;


            	# Generate the web page

            
            	$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);

            
            ?>
	<?php require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); $App = new App(); $Nav = new Nav(); $Menu = new Menu(); include($App->getProjectCommon()); # All on the same line to unclutter the user's desktop'

	#*****************************************************************************
	#
	# development/index.php
	#
	# Author: Martin Oberhuber
	# Date: 2006-02-10
	#
	# Description: TM developer resources page
	#
	#
	#****************************************************************************

	#
	# Begin: page-specific settings. Change these.
	$pageTitle = "TM Developer Resources";
	$pageKeywords = "developer,resources,device,target";
	$pageAuthor = "Martin Oberhuber";

	# Add page-specific Nav bars here
	# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)
	# $Nav->addNavSeparator("My Page Links", "downloads.php");
	# $Nav->addCustomNav("My Link", "mypage.php", "_self", 3);
	# $Nav->addCustomNav("Google", "http://www.google.com/", "_blank", 3);

	# End: page-specific settings
	#

	# Paste your HTML content between the EOHTML markers!
	$html = <<<EOHTML

	<div id="maincontent">
	<div id="midcolumn">
	<h1>$pageTitle</h1>

	<div class="homeitem">
	<h3>Development Tools</h3>
	<ul class="midlist">
	<li><b><a
	href="/tm/development/cvs_setup.php">CVS Repository</a></b><br/>
	TM development is managed in
	<!-- two CVS repositories:
	<ul class="midlist">
	<li>The <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.core/?cvsroot=Tools_Project">Core Repository</a>
	<li>The <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.rse/?cvsroot=Tools_Project">RSE Repository</a>
	</ul>
	-->
	the <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.rse/?cvsroot=Tools_Project">RSE</a> and
	<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.core/?cvsroot=Tools_Project">Core</a> Repositories.
	To populate an Eclipse workspace with our code, best use our
	<a href="/tm/development/cvs_setup.php">Team Project Sets</a>.
	A
	<a href="http://download.eclipse.org/tm/downloads/drops/N-changelog/index.html">
	CVS Changelog</a> is available, and you can subscribe to commit notifications on
	<a href="https://dev.eclipse.org/mailman/listinfo/tm-cvs-commit">tm-cvs-commit</a>.</li>
	<li><a href="/tm/development/bug_process.php" target="_self"><b>Bug Process</b></a><br>
	View <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=Target+Management&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit">all open</a> issues
	\| <a target="_top" href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Target%20Management&version=unspecified&component=RSE">Submit new</a> bugs
	\| Request an <a target="_top" href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Target%20Management&version=unspecified&component=RSE&rep_platform=All&op_sys=All&priority=P3&bug_severity=enhancement&form_name=enter_bug">enhancement</a>
	</li>
	<li><b><a
	href="http://www.eclipse.org/webtools/development/apiscanner/apiscanner.html">Eclipse API Scanner</a></b><br/>Describe the API of a component and scan plug-ins for API
	violations (from the <a href="http://www.eclipse.org/webtools"
	target="_self">WebTools</a> project).</li>
	<li><b><a href="http://www.eclipse.org/webtools/development/piitools/piitools.html">Check
	Unused Properties Tool</a></b> <br>
	Scan property files for unused messages (from the <a
	href="http://www.eclipse.org/webtools" target="_self">WebTools</a>
	project).</li>
	<li><b><a href="http://www.eclipse.org/eclipse/platform-core/downloads.html">Core
	Tools</a></b> <br>
	Useful utilities from the Platform team. Consider adding their
	<a href="http://www.eclipse.org/eclipse/platform-core/downloads.html#updates">
	update site</a> to your configuration.</li>
	<li><b><a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.rse/releng/org.eclipse.rse.build/README_build.txt?revision=1.2&root=Tools_Project">
	Building RSE</a></b><br/>
	Instructions how to perform unattended builds of TM / RSE.</li>
	<li><b><a
	href="http://wiki.eclipse.org/Platform-releng">Release Engineering</a></b> <br>
	See the instructions, FAQs and help from the Platform-Releng team.</li>
	<!-- Dashboard is currently not useful.
	<li><b><a
	href="http://www.eclipse.org/projects/dashboard/dashboard_detail.php?project=tools.tm">Project
	Dashboard</a></b> <br>
	View generated project statistics.</li>
	-->
	<li><b><a
	href="https://dev.eclipse.org/committers">Eclipse Committer
	Tools</a></b> <br>
	Information on infrastructure status, file path information,
	FAQs, etc. [login required]</li>
	</ul>
	</div>
	<div class="homeitem">
	<h3>Development Resources</h3>
	<ul class="midlist">
	<li><b><a href="/tm/development/committer_howto.php">Committer HOWTO</a></b><br>
	Simple cookbook instructions for performing basic tasks properly.
	Committers need to follow check-in conventions and IP Due Diligence as outlined
	<a href="/tm/development/committer_guide.php">here</a>.
	</li>
	<li><b><a href="http://wiki.eclipse.org/API_Central">API Guidelines</a></b><br>
	Look <a href="http://help.eclipse.org/help30/topic/org.eclipse.platform.doc.isv/reference/misc/api-usage-rules.html">
	here</a> for general Eclipse API rules of engagement. We strive to achieve
	<a href="http://www.eclipse.org/projects/dev_process/eclipse-quality.php">
	Eclipse Quality</a>, as outlined in the draft of
	<a href="http://www.eclipse.org/projects/dev_process/Eclipse%20Quality%20APIs%20v2.pdf">
	Eclipse Quality APIs</a>.
	</li>
	<li><b><a href="http://wiki.eclipse.org/Development_Conventions_and_Guidelines">
	Development Conventions and Guidelines</a></b><br>
	Coding standards, naming conventions, and other
	guidelines used by the Platform. TM will use these conventions
	until such time as deviation is required.</li>
	<li><b><a href="http://www.eclipse.org/downloads/download.php?file=/tm/presentations/2006-9-29_SummitEurope_TMOverview.pdf">
	Architectural Overview</a></b><br>
	A high level summary of the components and their architecture.</li>
	<li><b><a
	href="http://www.eclipse.org/tm/doc/TM_Use_Cases_v1.1c.pdf">Project
	Requirements</a></b> <br>
	Look here for a list of the project use cases and their
	priorities.</li>
	<li><b><a
	href="http://www.eclipse.org/tools/eclipsetools-charter.php">Charter</a></b>
	<br>
	As a Tools subproject, the TM project abides by the
	<a href="/tools/eclipsetools-charter.php">Tools Project charter</a> and the
	<a href="http://www.eclipse.org/projects/dev_process/Eclipse_Standard_TopLevel_Charter_v1.0.php">
	Eclipse Standard Charter</a>.</li>
	<li><b><a
	href="/tm/development/contributors.php">Contributors
	and Committers</a></b> <br>
	List of TM Project contributors and committers.</li>
	</ul>
	</div>
	</div>

	<div id="rightcolumn">
	<div class="sideitem">
	<h6>Getting started</h6>
	<ul>
	<li><a href="http://www.eclipse.org/downloads/download.php?file=/tm/presentations/2006-9-29_SummitEurope_TMOverview.pdf"
	target="_self">TM Overview Slides</a></li>
	<li><a href="http://www.eclipse.org/project-slides/TM_3.0_Release_Review.pdf" target="_self">
	TM 3.0 Release Review Slides</a></li>
	<li><a href="http://www.eclipse.org/downloads/download.php?file=/tm/presentations/TM_2.0_Release_Review.ppt" target="_self">
	TM 2.0 Release Review Slides</a></li>
	<li><a
	href="/tm/doc/TM_Use_Cases_v1.1c.pdf"
	target="_top">TM Use Cases Document</a></li>
	<!-- <li><a href="/tm/development/index.php">Developer Resources</a></li> -->
	<li><a href="/tm/doc/index.php">Developer Documents</a></li>
	</ul>
	</div>
	</div>
	</div>

	EOHTML;


	# Generate the web page
	$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
	?>