| <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> | |
| <html> | |
| <head> | |
| <title></title> | |
| <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> | |
| <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> | |
| <meta name="ProgId" content="FrontPage.Editor.Document"> | |
| <link rel="stylesheet" href="../default_style.css" type="text/css"> | |
| </head> | |
| <body> | |
| <h1><a name="tlp">Eclipse Platform Project</a></h1> | |
| <p>The Eclipse Platform top level project is responsible for three subsystems: | |
| Platform, JDT, and PDE. There is a separate project for each subsystem, but | |
| these projects closely coordinate their development activities and provide | |
| unified releases and downloads.</p> | |
| <h2><a name="tlp_arch_overview">Architecture overview</a></h2> | |
| <table border="0" cellpadding="10" cellspacing="10" width="60%" align="center"> | |
| <tr> | |
| <td width="100%" align="left"> | |
| <p align="center"><span><img src="images/eclipse_platform_tlp.png" border="1" alt usemap="#eclipse_platform_tlp_Map" align="center" width="540" height="362"> | |
| <map name="eclipse_platform_tlp_Map"> | |
| <area shape="rect" alt="PDE subsystem" coords="436,148,510,222" href="#PDE"> | |
| <area shape="rect" alt="JDT susbsystem" coords="332,218,407,294" href="#JDT"> | |
| <area shape="rect" alt="Eclipse Platform susbsystem" coords="14,302,518,341" href="#Platform"></map> | |
| Figure 1. Eclipse Platform top level project is structured into 3 | |
| subsystems; Platform subsystem is used universally.</span></td> | |
| </tr> | |
| </table> | |
| <p>The following table summarizes what each of the subsystems do.</p> | |
| <div align="center"> | |
| <center> | |
| <table border="1" width="80%"> | |
| <tr> | |
| <th id="name" width="20%">Name</th> | |
| <th id="desc">Summary</th> | |
| </tr> | |
| <tr> | |
| <td headers="name"><a href="#Platform">Platform</a></td> | |
| <td headers="desc">The Eclipse Platform subsystem consists of essential | |
| core infrastructure and UI frameworks that form the nucleus of the IDE | |
| and other RCP applications. The notions of plug-in, extension point, | |
| workspace, and workbench are all defined by the Eclipse Platform.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name"><a href="#JDT">JDT</a></td> | |
| <td headers="desc">The JDT (Java Development Tools) subsystem consists of | |
| integrated tools for developing, testing, and debugging Java (J2SE) | |
| applications.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name"><a href="#PDE">PDE</a></td> | |
| <td headers="desc">PDE (Plug-in Development Environment) consists of | |
| integrated tools that assist in developing, testing, debugging, and | |
| packaging Eclipse plug-ins, features, products, and update sites.</td> | |
| </tr> | |
| </table> | |
| </center> | |
| </div> | |
| <h3><a name="tlp_bibliography">How to find out more</a><a></h3> | |
| <ul> | |
| <li>Articles | |
| <ul> | |
| <li><a href="http://www.eclipse.org/whitepapers/eclipse-overview.pdf"><i>Eclipse | |
| Platform Technical Overview</i> (pdf)</a></li> | |
| </ul> | |
| </li> | |
| <li>Online help books | |
| <ul> | |
| <li><a href="http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.platform.doc.user/">Workbench | |
| User Guide (3.0)</a></li> | |
| <li><a href="http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.platform.doc.isv/">Platform | |
| Plug-in Developer Guide (3.0)</a></li> | |
| <li><a href="http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.jdt.doc.user/">Java | |
| Development User Guide (3.0)</a></li> | |
| <li><a href="http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.jdt.doc.isv/">JDT | |
| Plug-in Developer Guide (3.0)</a></li> | |
| <li><a href="http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.pde.doc.user/">PDE | |
| Guide (3.0)</a></li> | |
| </ul> | |
| </li> | |
| <li>Books | |
| <ul> | |
| <li><a href="http://www.amazon.com/exec/obidos/ASIN/0321205758" target="_blank"><i>Contributing | |
| to Eclipse</i> by Erich Gamma and Kent Beck</a></li> | |
| <li><a href="http://www.eclipsefaq.org/chris/faq/" target="_blank"><i>Official | |
| Eclipse 3.0 FAQs</i> by John Arthorne and Chris Laffra</a></li> | |
| </ul> | |
| </li> | |
| </ul> | |
| <h3><a name="tlp_dependencies">Dependencies</a></h3> | |
| <h4>Internal dependencies (between subsystems within same top level project)</h4> | |
| <ul> | |
| <li>Eclipse Platform subsystem depends on: none</li> | |
| <li>JDT subsystem depends on: Eclipse Platform</li> | |
| <li>PDE subsystem depends on: Eclipse Platform and JDT</li> | |
| </ul> | |
| <h4>External dependencies (on subsystems in other top level projects)</h4> | |
| <ul> | |
| <li>Eclipse Platform subsystem depends on: none</li> | |
| <li>JDT subsystem depends on: none</li> | |
| <li>PDE subsystem depends on: none</li> | |
| </ul> | |
| <h3><a name="tlp_releases">Releases and downloads</a></h3> | |
| <p>There are two current releases of the 3 subsystems in the Eclipse Platform:</p> | |
| <ul> | |
| <li>3.0 family: current release is 3.0.1 (<a href="http://download.eclipse.org/downloads/drops/R-3.0.1-200409161125/index.php">download</a>)</li> | |
| <li>2.1 family: current release is 2.1.3 (<a href="http://download.eclipse.org/downloads/drops/R-2.1.3-200403101828/index.php">download</a>)</li> | |
| </ul> | |
| <h3><a name="tlp_user_forums">User forums</a></h3> | |
| <ul> | |
| <li>Platform | |
| <ul> | |
| <li><a href="news://news.eclipse.org/eclipse.platform">news://news.eclipse.org/eclipse.platform</a> | |
| for general discussions about Eclipse Platform</li> | |
| <li><a href="news://news.eclipse.org/eclipse.platform.swt">news://news.eclipse.org/eclipse.platform.swt</a> | |
| for more specific discussions about SWT</li> | |
| <li><a href="news://news.eclipse.org/eclipse.platform.rcp">news://news.eclipse.org/eclipse.platform.rcp</a> | |
| for more specific discussions about RCP</li> | |
| </ul> | |
| </li> | |
| <li>JDT | |
| <ul> | |
| <li><a href="news://news.eclipse.org/eclipse.tools.jdt">news://news.eclipse.org/eclipse.tools.jdt</a></li> | |
| </ul> | |
| </li> | |
| </ul> | |
| <h3><a name="tlp_bugs">How to report a bug</h3> | |
| <ul> | |
| <li>Platform - <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform">"Platform" | |
| product in eclipse.org bug database</a></li> | |
| <li>JDT - <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=JDT">"JDT" | |
| product in eclipse.org bug database</a></li> | |
| <li>PDE - <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=PDE">"PDE" | |
| product in eclipse.org bug database</a></li> | |
| </ul> | |
| <h3><a name="tlp_upcoming">Upcoming releases</h3> | |
| <p>The 3 subsystems in this top level project are developed, built, and released | |
| as a unit (same release schedule, shared downloads, etc.).</p> | |
| <ul> | |
| <li>Next major release: 3.1 (<a href="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html">plan</a>)</li> | |
| <li>Next maintenance release 3.0 family: 3.0.2 (<a href="http://www.eclipse.org/eclipse/development/eclipse_maintenance_schedule_3_0_x.html">plan</a>)</li> | |
| <li>Next maintenance release 2.1 family: none planned</li> | |
| </ul> | |
| <h3><a name="tlp_development_team">Development team</h3> | |
| <ul> | |
| <li><a href="http://eclipse.org/eclipse/team-leaders.html">PMC</a></li> | |
| <li><a href="http://eclipse.org/eclipse/commit.html">Committers and developers</a></li> | |
| </ul> | |
| <h2><a name="Platform">Platform</a></h2> | |
| <p>The Eclipse Platform subsystem provides the essential core infrastructure and | |
| UI frameworks that form the nucleus of the IDE and other RCP applications. The | |
| notions of plug-in, extension point, workspace, and workbench are all defined by | |
| the Eclipse Platform.</p> | |
| <p>The term "Eclipse Platform project" could refer to either the | |
| Eclipse Platform top level project as a whole or to the (sub)project responsible | |
| for developing the Eclipse Platform subsystem. The ambiguity is usually | |
| harmless.</p> | |
| <h3><a name="Platform_arch">Architecture</a></h3> | |
| <table border="0" cellpadding="10" cellspacing="10" width="60%" align="center"> | |
| <tr> | |
| <td width="100%" align="left"> | |
| <p align="center"><img src="images/platform_subsys.png" border="0" alt="Eclipse Platform subsystem" usemap="#platform_subsys_Map" align="bottom" width="540" height="328"> | |
| <map name="platform_subsys_Map"> | |
| <area shape="rect" alt="Platform Text" coords="33, 120, 134, 164" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-text-home/main.html"> | |
| <area shape="rect" alt="Releng " coords="381, 73, 489, 125" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-releng-home/main.html"> | |
| <area shape="rect" alt="Compare " coords="345, 169, 448, 214" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-compare-home/main.html"> | |
| <area shape="rect" alt="SWT " coords="242, 169, 341, 213" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-swt-home/main.html"> | |
| <area shape="rect" alt="CVS" coords="139, 169, 239, 214" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-vcm-home/main.html"> | |
| <area shape="rect" alt="Platform UI " coords="33, 170, 133, 214" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-ui-home/main.html"> | |
| <area shape="rect" alt="Platform Resources" coords="33, 218, 133, 261" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/main.html"> | |
| <area shape="rect" alt="Team " coords="137, 218, 236, 261" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-vcm-home/main.html"> | |
| <area shape="rect" alt="Search " coords="240, 219, 339, 262" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-search-home/main.html"> | |
| <area shape="rect" alt="Ant" coords="347, 218, 450, 261" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-ant-home/main.html"> | |
| <area shape="rect" alt="Platform Debug" coords="346, 265, 449, 307" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-debug-home/main.html"> | |
| <area shape="rect" alt="Update" coords="246, 264, 345, 306" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-update-home/main.html"> | |
| <area shape="rect" alt="Help" coords="139, 265, 238, 307" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-help-home/main.html"> | |
| <area shape="rect" alt="Platform Runtime" coords="30, 263, 130, 305" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/main.html"></map> | |
| Figure 2. Components making up Eclipse Platform subsystem.</p> | |
| </td> | |
| </tr> | |
| </table> | |
| <p>The Eclipse Platform subsystem has a number of components split along | |
| functional line and designed to work in concert. Unlike other component, the | |
| Releng component is not actually part of Eclipse Platform distributions; rather, | |
| it contains the specialized scripts and tools used to build those distributions.</p> | |
| <p>There are two important aspects that cross-cut the decomposition into | |
| components: Core/UI, and RCP/IDE. "Core" components are ones that have | |
| no GUI dependencies. Core components can be used in headless configurations. | |
| "UI" components are ones that require a GUI, and therefore cannot be | |
| used in headless configurations. This stratifies the components into Core and UI | |
| layers, with components in the core layer depending only on other component in | |
| the core layer. Several components have both Core and UI sides to them (e.g., | |
| Platform Debug); within them, their plug-ins are split up along Core and UI | |
| lines (e.g., org.eclipse.debug.core and org.eclipse.debug.ui).</p> | |
| <ul> | |
| <li>Pure Core components: Platform Runtime, Platform Resources</li> | |
| <li>Pure UI components: SWT, Platform UI</li> | |
| <li>Hybrid Core/UI components: Platform Text, Team, CVS, Help, Search, Update, | |
| Compare, Ant, Platform Debug</li> | |
| </ul> | |
| <p>The Eclipse Platform subsystem serves as both the base for IDE and non-IDE | |
| products. The Rich Client Platform (RCP) is the name used for those parts of the | |
| Eclipse Platform that are useful for writing arbitrary application programs | |
| based on Eclipse. Some components have both RCP and IDE sides to them (e.g., | |
| Platform UI); within them, their plug-ins are split up along RCP and IDE | |
| lines (e.g., org.eclipse.ui and org.eclipse.ui.ide).</p> | |
| <ul> | |
| <li>Pure RCP components: Platform Runtime, SWT</li> | |
| <li>Components with both RCP and IDE : Platform UI, Platform Text, Help, | |
| Update</li> | |
| <li>IDE components: Platform Resources, Team, CVS, Compare, Ant, Platform | |
| Debug, Search</li> | |
| </ul> | |
| <h3><a name="Platform_bibloigraphy">How to find out more</a></h3> | |
| <ul> | |
| <li>Articles | |
| <ul> | |
| <li><a href="http://www.eclipse.org/whitepapers/eclipse-overview.pdf"><i>Eclipse | |
| Platform Technical Overview</i> (pdf)</a></li> | |
| </ul> | |
| </li> | |
| <li>Online help books | |
| <ul> | |
| <li><a href="http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.platform.doc.user/">Workbench | |
| User Guide (3.0)</a></li> | |
| <li><a href="http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.platform.doc.isv/">Platform | |
| Plug-in Developer Guide (3.0)</a></li> | |
| </ul> | |
| </li> | |
| <li>Books | |
| <ul> | |
| <li><a href="http://www.amazon.com/exec/obidos/ASIN/0321205758" target="_blank"><i>Contributing | |
| to Eclipse</i> by Erich Gamma and Kent Beck</a></li> | |
| <li><a href="http://www.eclipsefaq.org/chris/faq/" target="_blank"><i>Official | |
| Eclipse 3.0 FAQs</i> by John Arthorne and Chris Laffra</a></li> | |
| </ul> | |
| </li> | |
| </ul> | |
| <h3><a name="Platform_dependencies">Dependencies</a></h3> | |
| <ul> | |
| <li>Eclipse Platform subsystem depends on: none</li> | |
| </ul> | |
| <h3><a name="Platform_releases">Releases and downloads</a></h3> | |
| <p>There are two current releases of the 3 subsystems in the Eclipse Platform. | |
| There are downloads for the Platform subsystem by itself as well as ones that | |
| bundle all 3 subsystems together (there are also separate RCP and SWT drops).</p> | |
| <ul> | |
| <li>3.0 family: current release is 3.0.1 (<a href="http://download.eclipse.org/downloads/drops/R-3.0.1-200409161125/index.php">download</a>)</li> | |
| <li>2.1 family: current release is 2.1.3 (<a href="http://download.eclipse.org/downloads/drops/R-2.1.3-200403101828/index.php">download</a>)</li> | |
| </ul> | |
| <h3><a name="Platform_user_forums">User forums</a></h3> | |
| <ul> | |
| <li>Platform | |
| <ul> | |
| <li><a href="news://news.eclipse.org/eclipse.platform">news://news.eclipse.org/eclipse.platform</a> | |
| for general discussions about Eclipse Platform</li> | |
| <li><a href="news://news.eclipse.org/eclipse.platform.swt">news://news.eclipse.org/eclipse.platform.swt</a> | |
| for more specific discussions about SWT</li> | |
| <li><a href="news://news.eclipse.org/eclipse.platform.rcp">news://news.eclipse.org/eclipse.platform.rcp</a> | |
| for more specific discussions about RCP</li> | |
| </ul> | |
| </li> | |
| </ul> | |
| <h3><a name="Platform_bugs">How to report bugs</a></h3> | |
| <ul> | |
| <li><a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform">"Platform" | |
| product in eclipse.org bug database</a></li> | |
| </ul> | |
| <h3><a name="Platform_development_team">Development team</a></h3> | |
| <ul> | |
| <li>Project lead is Kevin Haaland (IBM)</li> | |
| <li><a href="http://eclipse.org/eclipse/commit.html">Committers and developers</a></li> | |
| </ul> | |
| <h3><a name="Platform_upcoming">Upcoming releases</a></h3> | |
| <p>All subsystems in the Eclipse Platform top level project are developed, | |
| built, and released as a unit (same release schedule, shared downloads, etc.).</p> | |
| <ul> | |
| <li>Next major release: 3.1 (<a href="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html">plan</a>)</li> | |
| <li>Next maintenance release 3.0 family: 3.0.2 (<a href="http://www.eclipse.org/eclipse/development/eclipse_maintenance_schedule_3_0_x.html">plan</a>)</li> | |
| <li>Next maintenance release 2.1 family: none planned</li> | |
| </ul> | |
| <h3>Digging deeper</h3> | |
| <p>The Platform subsystem is broken down into components. (For historical | |
| reasons, each component operates much like a project unto its own, with its own | |
| set of committers, bug categories, and development team mailing lists.) Follow | |
| the component links to get detailed information about the component (including | |
| where to find source code, mailing list for communication within the development | |
| team).</p> | |
| <div align="center"> | |
| <center> | |
| <table border="1" width="80%"> | |
| <tr> | |
| <th id="name" width="20%" align="top">Name</th> | |
| <th id="desc">Summary</th> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="19"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/main.html">Platform | |
| Runtime</a> (historically Core)</td> | |
| <td headers="desc" height="19">The Platform Runtime component is the base | |
| of the Eclipse platform and implements the fundamental concepts of | |
| plug-ins and extension points, built atop an implementation of OSGi. The | |
| Platform Runtime also provides low-level facilities for managing things | |
| like concurrency, preferences, and content types.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="19"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/main.html">Platform | |
| Resources</a> (historically Core)</td> | |
| <td headers="desc" height="19">The Platform Resources component provides | |
| the basic notions of workspaces and projects for managing files in the | |
| local file system. It provides domain-independent mechanisms for | |
| creating, manipulating, and tracking these resources.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="15"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-swt-home/main.html">SWT</a></td> | |
| <td headers="desc" height="15">SWT is a widget toolkit for Java designed | |
| to provide efficient, portable access to the user-interface facilities | |
| of the operating systems on which it is implemented. In addition to the | |
| primary focus on native integration, the SWT component provides the | |
| custom controls that give Eclipse its distinctive look and feel.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="19"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-ant-home/main.html">Ant</a></td> | |
| <td headers="desc" height="19">The Ant component integrates Ant into | |
| Eclipse. It includes an Ant buildfile editor and mechanisms for | |
| configuring and executing Ant builds.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="19"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-compare-home/main.html">Compare</a></td> | |
| <td headers="desc" height="19">The Platform Compare component provides | |
| infrastructure for differencing and merging hierarchical structures and | |
| sequences of arbitrary objects, such as text lines, words, or | |
| characters. It also provides various UI elements (editors, views, | |
| dialogs) for navigating and merging differences.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="19"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-debug-home/main.html">Platform | |
| Debug</a></td> | |
| <td headers="desc" height="19">The Platform Debug component provides | |
| frameworks and APIs for building integrated debuggers in Eclipse. It | |
| includes both debug model infrastructure and a basic debugger UI that | |
| can be extended to define specific debuggers. It also includes a general | |
| framework for launching programs from an IDE.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="19"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-help-home/main.html">Help</a></td> | |
| <td headers="desc" height="19">The Platform Help component provides | |
| mechanisms for integrating documentation and context-sensitive help. | |
| Besides providing on-line help in the workbench, it can also be deployed | |
| as a stand-alone desktop help system or as an infocenter server that can | |
| be accessed remotely through any web browser.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="19"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-search-home/main.html">Search</a></td> | |
| <td headers="desc" height="19">The Search component defines the mechanisms | |
| for integrating search functionality into the workbench. It contributes | |
| textual searching, together with the UI infrastructure and building | |
| blocks for creating content-type-specific searches.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="19"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-text-home/main.html">Platform | |
| Text</a></td> | |
| <td headers="desc" height="19">The Platform Text component provides the | |
| facilities for manipulating and managing text files and documents. It | |
| contributes Eclipse's default text editor, together with the frameworks | |
| and building blocks for creating domain-specific text editors.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="19"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-ui-home/main.html">Platform | |
| UI</a></td> | |
| <td headers="desc" height="19">The Platform UI component supplies the | |
| workbench that provides the overall structure and presents an extensible | |
| user interface to the user. Some of the Platform APIs, frameworks, and | |
| building blocks are specific to Eclipse-based IDEs; most are available | |
| to all RCP applications.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="19"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-update-home/main.html">Update</a></td> | |
| <td headers="desc" height="19">The Update component manages the | |
| configuration of installed plug-ins. It provides the mechanisms for | |
| discovering, downloading, and installing new and updated plug-ins.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="19"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-vcm-home/main.html">Team</a></td> | |
| <td headers="desc" height="19">The Team component provides mechanisms for | |
| integrating version control tools that manage and track changes to files | |
| in a project.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="19"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-vcm-home/main.html">CVS</a></td> | |
| <td headers="desc" height="19">The CVS component integrates CVS into | |
| Eclipse, allowing the various versions of files in a project to be | |
| tracked and managed though a shared, remote CVS repository. In addition | |
| to supporting the traditional CVS commands, it also lets the user | |
| preview and visually merge changes between workspace and repository.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name" height="19"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-releng-home/main.html">Platform | |
| Releng</a></td> | |
| <td headers="desc" height="19">The Platform Releng component provides the | |
| specialized tools and Ant-based automated processes used to build | |
| Eclipse Platform project distributions for download.</td> | |
| </tr> | |
| </table> | |
| </center> | |
| </div> | |
| <h2><a name="JDT">JDT</a></h2> | |
| <p>The JDT (Java Development Tools) subsystem consists of integrated tools for | |
| developing, testing, and debugging Java (J2SE) applications. The JDT project is | |
| managed as part of the Eclipse Platform top level project.</p> | |
| <h3><a name="JDT_arch">Architecture</a></h3> | |
| <table border="0" cellpadding="10" cellspacing="10" width="60%" align="center"> | |
| <tr> | |
| <td width="100%" align="left"> | |
| <p align="center"><map name="jdt_subsys_Map"> | |
| <area shape="rect" alt="JDT UI" coords="340,83,450,134" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/jdt-ui-home/main.html"> | |
| <area shape="rect" alt="JDT Debug" coords="204,82,313,134" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/jdt-debug-home/main.html"> | |
| <area shape="rect" alt="JDT Core" coords="68,82,177,134" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/jdt-core-home/main.html"></map><img src="images/jdt_subsys.png" border="0" alt="JDT subsystem" usemap="#jdt_subsys_Map" width="540" height="181"> | |
| Figure 3. Components making up JDT subsystem.</td> | |
| </tr> | |
| </table> | |
| <p>The JDT Core component defines the non-UI infrastructure for compiling and | |
| analyzing Java code. The JDT UI component provides the user interface elements | |
| (wizards, views, editors) and infrastructure for editing, refactoring, browsing, | |
| and searching Java code. The JDT Debug component handles everything related to | |
| running and debugging Java programs.</p> | |
| <h3><a name="JDT_bibliography">How to find out more</a></h3> | |
| <ul> | |
| <li>Articles | |
| <ul> | |
| <li><a href="http://www.eclipse.org/whitepapers/eclipse-overview.pdf"><i>Eclipse | |
| Platform Technical Overview</i> (pdf)</a></li> | |
| </ul> | |
| </li> | |
| <li>Online help books | |
| <ul> | |
| <li><a href="http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.jdt.doc.user/">Java | |
| Development User Guide (3.0)</a></li> | |
| <li><a href="http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.jdt.doc.isv/">JDT | |
| Plug-in Developer Guide (3.0)</a></li> | |
| </ul> | |
| </li> | |
| <li>Books | |
| <ul> | |
| <li><a href="http://www.amazon.com/exec/obidos/ASIN/0321205758" target="_blank"><i>Contributing | |
| to Eclipse</i> by Erich Gamma and Kent Beck</a></li> | |
| <li><a href="http://www.eclipsefaq.org/chris/faq/" target="_blank"><i>Official | |
| Eclipse 3.0 FAQs</i> by John Arthorne and Chris Laffra</a>, Chapter 20</li> | |
| </ul> | |
| </li> | |
| </ul> | |
| <h3><a name="JDT_dependencies">Dependencies<a/></h3> | |
| <ul> | |
| <li>JDT subsystem depends on: <a href="#Platform">Platform</a></li> | |
| </ul> | |
| <h3><a name="JDT_releases">Releases and downloads</a></h3> | |
| <p>There are two current releases of the 3 subsystems in the Eclipse Platform. | |
| There are downloads for the JDT subsystem by itself as well as ones that bundle | |
| it with the Platform. </p> | |
| <ul> | |
| <li>3.0 family: current release is 3.0.1 (<a href="http://download.eclipse.org/downloads/drops/R-3.0.1-200409161125/index.php">download</a>)</li> | |
| <li>2.1 family: current release is 2.1.3 (<a href="http://download.eclipse.org/downloads/drops/R-2.1.3-200403101828/index.php">download</a>)</li> | |
| </ul> | |
| <h3><a name="JDT_user_forums">User forums</a></h3> | |
| <ul> | |
| <li>Platform | |
| <ul> | |
| <li><a href="news://news.eclipse.org/eclipse.tools.jdt">news://news.eclipse.org/eclipse.tools.jdt</a> | |
| for general discussions about JDT</li> | |
| </ul> | |
| </li> | |
| </ul> | |
| <h3><a name="JDT_bugs">How to report bugs</a></h3> | |
| <ul> | |
| <li><a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=JDT">"JDT" | |
| product in eclipse.org bug database</a></li> | |
| </ul> | |
| <h3><a name="JDT_development_team">Development team</a></h3> | |
| <ul> | |
| <li>Project lead is Philippe Mulet (IBM)</li> | |
| <li><a href="http://eclipse.org/eclipse/commit.html">Committers and developers</a></li> | |
| </ul> | |
| <h3><a name="JDT_upcoming">Upcoming releases</a></h3> | |
| <p>All subsystems in the Eclipse Platform top level project are developed, | |
| built, and released as a unit (same release schedule, shared downloads, etc.).</p> | |
| <ul> | |
| <li>Next major release: 3.1 (<a href="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html">plan</a>)</li> | |
| <li>Next maintenance release 3.0 family: 3.0.2 (<a href="http://www.eclipse.org/eclipse/development/eclipse_maintenance_schedule_3_0_x.html">plan</a>)</li> | |
| <li>Next maintenance release 2.1 family: none planned</li> | |
| </ul> | |
| <h3>Digging deeper</h3> | |
| <p>The JDT subsystem is broken down into components. (For historical reasons, | |
| each component operates much like a project unto its own, with its own set of | |
| committers, bug categories, and development team mailing lists.) Follow the | |
| component links to get detailed information about the component (including where | |
| to find source code, mailing list for communication within the development | |
| team).</p> | |
| <div align="center"> | |
| <center> | |
| <table border="1" width="80%"> | |
| <tr> | |
| <th id="name" width="20%">Name</th> | |
| <th id="desc">Summary</th> | |
| </tr> | |
| <tr> | |
| <td headers="name"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/jdt-core-home/main.html">JDT | |
| Core</a></td> | |
| <td headers="desc">The JDT Core component provides the Java-specific | |
| infrastructure of the Java IDE. It includes an incremental Java compiler | |
| and Java-centric models for navigating, analyzing, searching, and | |
| manipulating Java projects and source files.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/jdt-debug-home/main.html">JDT | |
| Debug</a></td> | |
| <td headers="desc">The Java Debug component provides an integrated Java | |
| debugger that supports debugging of Java programs running (either | |
| locally and remotely) on Java virtual machines with JDPA support.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/jdt-ui-home/main.html">JDT | |
| UI</a></td> | |
| <td headers="desc">The JDT UI component implements the user interface of | |
| the Java IDE. It includes the UI elements and infrastructure for | |
| editing, refactoring, browsing, and searching Java code.</td> | |
| </tr> | |
| </table> | |
| </center> | |
| </div> | |
| <h2><a name="PDE">PDE</a></h2> | |
| <p>PDE (Plug-in Development Environment) provides a set of integrated tools that | |
| assist in developing, testing, debugging, and packaging Eclipse plug-ins, | |
| features, products, and update sites. The PDE project is managed as part of the | |
| Eclipse Platform top level project.</p> | |
| <h3><a name="PDE_arch">Architecture</a></h3> | |
| <table border="0" cellpadding="10" cellspacing="10" width="60%" align="center"> | |
| <tr> | |
| <td width="100%" align="left"> | |
| <p align="center"><map name="pde_subsys_Map"> | |
| <area shape="rect" alt="PDE UI" coords="296,78,405,130" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/pde-ui-home/main.html"> | |
| <area shape="rect" alt="PDE Build" coords="127,78,236,130" href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/pde-build-home/main.html"></map><img src="images/pde_subsys.png" border="0" alt="PDE subsystem" usemap="#pde_subsys_Map" width="540" height="181"> | |
| Figure 4. Components making up PDE subsystem.</td> | |
| </tr> | |
| </table> | |
| <p>Most of the functionality is provided by the PDE UI component, which has the | |
| various special-purpose editors, views, and wizards for developing plug-ins. The | |
| PDE Build component has the low level mechanisms for generating Ant-based | |
| scripts for building and packaging plug-ins.</p> | |
| <h3><a name="PDE_bibloigraphy">How to find out more</a></h3> | |
| <ul> | |
| <li>Online help books | |
| <ul> | |
| <li><a href="http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.pde.doc.user/">PDE | |
| Guide (3.0)</a></li> | |
| </ul> | |
| </li> | |
| <li>Books | |
| <ul> | |
| <li><a href="http://www.amazon.com/exec/obidos/ASIN/0321205758" target="_blank"><i>Contributing | |
| to Eclipse</i> by Erich Gamma and Kent Beck</a></li> | |
| <li><a href="http://www.eclipsefaq.org/chris/faq/" target="_blank"><i>Official | |
| Eclipse 3.0 FAQs</i> by John Arthorne and Chris Laffra</a>, Chapter 4</li> | |
| </ul> | |
| </li> | |
| </ul> | |
| <h3><a name="PDE_dependencies">Dependencies</a></h3> | |
| <ul> | |
| <li>JDT subsystem depends on: <a href="#Platform">Platform</a> and <a href="#JDT">JDT</a></li> | |
| </ul> | |
| <h3><a name="PDE_releases">Releases and downloads</a></h3> | |
| <p>There are two current releases of the 3 subsystems in the Eclipse Platform. | |
| PDE is bundled with Platform and JDT. </p> | |
| <ul> | |
| <li>3.0 family: current release is 3.0.1 (<a href="http://download.eclipse.org/downloads/drops/R-3.0.1-200409161125/index.php">download</a>)</li> | |
| <li>2.1 family: current release is 2.1.3 (<a href="http://download.eclipse.org/downloads/drops/R-2.1.3-200403101828/index.php">download</a>)</li> | |
| </ul> | |
| <h3><a name="PDE_user_forums">User forums</a></h3> | |
| <ul> | |
| <li>Platform | |
| <ul> | |
| <li><a href="news://news.eclipse.org/eclipse.platform">news://news.eclipse.org/eclipse.platform</a> | |
| for general discussions about the Eclipse Platform, including PDE</li> | |
| </ul> | |
| </li> | |
| </ul> | |
| <h3><a name="PDE_bugs">How to report bugs</a></h3> | |
| <ul> | |
| <li><a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=PDE">"PDE" | |
| product in eclipse.org bug database</a></li> | |
| </ul> | |
| <h3><a name="PDE_development_team">Development team</a></h3> | |
| <ul> | |
| <li>Project lead is Dejan Glozic (IBM)</li> | |
| <li><a href="http://eclipse.org/eclipse/commit.html">Committers and developers</a></li> | |
| </ul> | |
| <h3><a name="PDE_upcoming">Upcoming releases</a></h3> | |
| <p>All subsystems in the Eclipse Platform top level project are developed, | |
| built, and released as a unit (same release schedule, shared downloads, etc.).</p> | |
| <ul> | |
| <li>Next major release: 3.1 (<a href="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html">plan</a>)</li> | |
| <li>Next maintenance release 3.0 family: 3.0.2 (<a href="http://www.eclipse.org/eclipse/development/eclipse_maintenance_schedule_3_0_x.html">plan</a>)</li> | |
| <li>Next maintenance release 2.1 family: none planned</li> | |
| </ul> | |
| <h3>Digging deeper</h3> | |
| <p>The PDE subsystem is broken down into components. (For historical reasons, | |
| each component operates much like a project unto its own, with its own set of | |
| committers, bug categories, and development team mailing lists.) Follow the | |
| component links to get detailed information about the component (including where | |
| to find source code, mailing list for communication within the development | |
| team).</p> | |
| <div align="center"> | |
| <center> | |
| <table border="1" width="80%"> | |
| <tr> | |
| <th id="name" width="20%">Name</th> | |
| <th id="desc">Summary</th> | |
| </tr> | |
| <tr> | |
| <td headers="name"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/pde-build-home/main.html">PDE | |
| Build</a></td> | |
| <td headers="desc">The PDE Build component generates automated Ant scripts | |
| for fetching, building, and packaging OSGi bundles, plug-ins, and | |
| features.</td> | |
| </tr> | |
| <tr> | |
| <td headers="name"><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/pde-ui-home/main.html">PDE | |
| UI</a></td> | |
| <td headers="desc">The PDE UI component provides integrated tools for | |
| developing, testing, debugging, and packaging Eclipse-specific artifacts | |
| including plug-ins, features, products, and update sites.</td> | |
| </tr> | |
| </table> | |
| </center> | |
| </div> | |
| </body> |