ng=20
        the EclipseME Code</A>=20
        <LI><A=20
        =
href=3D"http://eclipseme.org/docs/developer/index.html#building">Building=
=20
        the EclipseME Binaries</A>=20
        <LI><A=20
        =
href=3D"http://eclipseme.org/docs/developer/index.html#patches">Creating =

        Patches</A>=20
        <LI><A =
href=3D"http://eclipseme.org/docs/developer/anatomy.html">Anatomy=20
        of the EclipseME Code</A>=20
        <LI><A=20
        =
href=3D"http://eclipseme.org/docs/developer/extending.html">Extending =
the=20
        EclipseME Code</A>=20
        <LI><A=20
        =
href=3D"http://eclipseme.org/docs/developer/api/index.html">EclipseME =
Core=20
        API Reference</A> </LI></OL>
      <H2 id=3Dbrowsing>Browsing the EclipseME Code</H2>
      <P>Versions 1.6.2 and later of EclipseME are being developed in =
the=20
      Sourceforge Subversion repository. While the previous versions =
still exist=20
      in Sourceforge CVS for historical purposes, no further development =
is=20
      occurring within CVS. A description of how to generically access =
the=20
      EclipseME SVN archive can be found <A=20
      href=3D"http://sourceforge.net/svn/?group_id=3D86829" =
target=3D_blank>here</A>,=20
      and you can browse the contents of the EclipseME SVN archive by =
clicking=20
      <A href=3D"http://eclipseme.svn.sourceforge.net/viewvc/eclipseme/" =

      target=3D_blank>here</A>. </P>
      <H2 id=3Ddownloading>Downloading the EclipseME Code</H2>
      <P>If you're going to do any development on EclipseME, you will =
need to=20
      use a Subversion client. The best way to interact with SVN from =
Eclipse is=20
      to use one of the two Subversion plugins. The Subversive project =
can be=20
      found <A=20
      =
href=3D"http://www.polarion.org/index.php?page=3Doverview&amp;project=3Ds=
ubversive">here</A>,=20
      while the Subclipse project is hosted by <A=20
      href=3D"http://subclipse.tigris.org/">tigris.org</A>. These =
directions will=20
      assume the use of the Subversive plugin. If you prefer Subclipse, =
please=20
      translate these directions accordingly. </P>
      <H3>Creating the EclipseME SVN Repository Location</H3>
      <P>Refer to the plugin documentation for further instructions on =
creating=20
      a new SVN Repository Location within the SVN Repositories View. =
Specify=20
      the following information when creating the repository location: =
</P>
      <TABLE border=3D1>
        <TBODY>
        <TR>
          <TD class=3Dbold>Item</TD>
          <TD class=3Dbold>Contents</TD></TR>
        <TR>
          <TD>URL</TD>
          =
<TD>https://eclipseme.svn.sourceforge.net/svnroot/eclipseme</TD></TR>
        <TR>
          <TD>User</TD>
          <TD>anonymous</TD></TR>
        <TR>
          <TD>Password</TD>
          <TD>(leave this empty)</TD></TR></TBODY></TABLE>
      <H3>Checking Out the EclipseME Project</H3>
      <P>The EclipseME project source control contains three top-level =
folders.=20
      The separation is very simple:=20
      <UL></UL>
      <LI>eclipseme-src<BR>The source code for EclipseME=20
      <LI>eclipseme-tools<BR>The source code for some tools used in the=20
      development of EclipseME=20
      <LI>eclipseme-web<BR>The HTML and other source code that makes up =
the the=20
      eclipseme.org web site=20
      <P>Development of EclipseME only requires the source code provided =
by the=20
      eclipseme-src folder from SVN. To set up for development, do the=20
      following: </P>
      <OL>
        <LI>Expand the newly created EclipseME SVN repository location.=20
        <LI>Expand the <SPAN class=3Dbold>trunk</SPAN> branch within the =
EclipseME=20
        SVN repository location.=20
        <LI>Right-click on the eclipseme-src project and choose <SPAN=20
        class=3Dkeyword>Check Out</SPAN> from the context menu. =
</LI></OL>
      <P>At this point, the code has been checked out into your =
workspace, but=20
      it is not yet setup such that Eclipse can be used for developing =
the code.=20
      The Eclipse Plugin Development Environment (PDE) requires that =
each plugin=20
      and feature is imported into the workspace as a project. The best =
way to=20
      do this is to "share" the code with the eclipseme-src project that =
was=20
      just checked out. To import the plugin projects: </P>
      <OL>
        <LI>Choose <SPAN class=3Dkeyword>File -&gt; Import...</SPAN>=20
        <LI>Expand the <SPAN class=3Dkeyword>General</SPAN> category.=20
        <LI>Select <SPAN class=3Dkeyword>Existing Projects into =
Workspace</SPAN>.=20
        <LI>Press the <SPAN class=3Dkeyword>Next</SPAN> button.=20
        <LI>Enter or browse to <SPAN=20
        class=3Ddirectory>[workspace-root]/eclipseme-src/plugins</SPAN> =
for the=20
        root directory.=20
        <LI>Press the <SPAN class=3Dkeyword>Refresh</SPAN> button and =
allow=20
        Eclipse to locate all of the plugin projects.=20
        <LI>Select all of the plugin projects that were located (this =
should be=20
        the default).=20
        <LI>Make sure that <SPAN class=3Dkeyword>Copy projects into=20
        workspace</SPAN> is not enabled.=20
        <LI>Press the <SPAN class=3Dkeyword>Finish</SPAN> button to =
initiate the=20
        import. </LI></OL>
      <P>At this point, the Eclipse should have imported and compiled =
the plugin=20
      projects. The "<A=20
      =
href=3D"http://eclipseme.org/docs/developer/anatomy.html">Anatomy</A>" =
page=20
      provides a brief description of the plugins. </P>
      <H2 id=3Ddebugging>Debugging the EclipseME Code</H2>
      <P>The code may be edited and debugged using the standard Eclipse=20
      mechanisms for working with Eclipse plugins. Refer to the Eclipse =
Plugin=20
      Development Environment (PDE) help for further information on =
developing=20
      plugins for Eclipse. </P>
      <H2 id=3Dbuilding>Building the EclipseME Site Distribution =
Archive</H2>
      <P>After development of any new functionality is complete, the =
EclipseME=20
      distribution archive can be built using the provided Ant build =
file. The=20
      Ant build file can be found in <SPAN=20
      class=3Ddirectory>[workspace-root]/build/build.xml</SPAN>. The Ant =
file can=20
      be launched outside (provided the necessary Ant properties are set =
to=20
      point to the Eclipse home location) or inside of Eclipse. The =
easiest way=20
      to launch the build is to use the provided <SPAN=20
      class=3Ddirectory>[workspace-root]/build/Build EclipseME Site=20
      Archive.launch</SPAN>. You can launch via the <SPAN =
class=3Dkeyword>External=20
      Tools</SPAN> launcher on the Eclipse toolbar. From the Eclipse =
<SPAN=20
      class=3Dkeyword>Run</SPAN> menu, select <SPAN =
class=3Dkeyword>External=20
      Tools</SPAN> and then <SPAN class=3Dkeyword>External =
Tools...</SPAN> again=20
      from the submenu. This will display a dialog similar to the =
following:=20
      </P><IMG alt=3Dscreenshot=20
      src=3D"http://eclipseme.org/docs/developer/building.png">=20
      <P>Select the item labeled <SPAN class=3Dbold>Build EclipseME Site =

      Archive</SPAN> and press the <SPAN class=3Dbold>Run</SPAN> button. =
This will=20
      start the process of packaging up the EclipseME distribution =
archive. The=20
      output archive will be placed in <SPAN=20
      =
class=3Ddirectory>[workspace-root]/output/eclipseme.feature</SPAN>. </P>
      <OL></OL>
      <P>Typically, once you have build the site archive once, <SPAN=20
      class=3Dbold>Build EclipseME Site Archive</SPAN> will then appear =
directly=20
      in your <SPAN class=3Dkeyword>Run / External Tools</SPAN> menu. =
</P>
      <H2 id=3Dpatches>Creating Patches</H2>
      <P>If you've followed along this far and managed to make a change =
in=20
      EclipseME that you feel should be included for other users, the =
best way=20
      to provide that change to the maintainers is with a patch file. =
Patches=20
      can be created by: </P>
      <OL>
        <LI>Select the project that contains the changes to be =
submitted.=20
        <LI>Open the context menu and choose <SPAN class=3Dkeyword>Team =
-&gt;=20
        Create Patch...</SPAN>=20
        <LI>Select <SPAN class=3Dkeyword>Save in file system</SPAN> and =
provide a=20
        file system location into which the patch file can be written.=20
        <LI>Press the <SPAN class=3Dkeyword>Finish</SPAN> button to =
generate the=20
        patch. </LI></OL>
      <P>Submitting patches once they have been created is done using =