Jump to: navigation, search

Difference between revisions of "Jetty/Contributor/Building"

(Build and Project Infrastructure SCMURLs)
Line 9: Line 9:
 
These are the URLs to the GIT repositories for the Jetty code. For people who are working on the Jetty project, as well as for people who are interested in examining or modifying the Jetty code for their own projects.  
 
These are the URLs to the GIT repositories for the Jetty code. For people who are working on the Jetty project, as well as for people who are interested in examining or modifying the Jetty code for their own projects.  
  
* http://git.eclipse.org/gitroot/jetty/org.eclipse.jetty.project.git -  Jetty Project Repository
+
* http://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git -  Jetty Project Repository
  
 
=== Build and Project Infrastructure SCMURLs  ===
 
=== Build and Project Infrastructure SCMURLs  ===
Line 15: Line 15:
 
These are the URLs for Jetty-related code and metadata. These are not needed to use Jetty; these are primarily of use for people who are working with Jetty-the-project (as opposed to using Jetty-the-server in their own projects).  
 
These are the URLs for Jetty-related code and metadata. These are not needed to use Jetty; these are primarily of use for people who are working with Jetty-the-project (as opposed to using Jetty-the-server in their own projects).  
  
* http://git.eclipse.org/gitroot/jetty/org.eclipse.jetty.parent.git -  Administrative pom.xml file  
+
* http://git.eclipse.org/c/jetty/org.eclipse.jetty.parent.git -  Administrative pom.xml file  
* http://git.eclipse.org/gitroot/jetty/org.eclipse.jetty.toolchain.git -  Build related artifacts that release separately, common assembly descriptors, remote resources, etc.  
+
* http://git.eclipse.org/c/jetty/org.eclipse.jetty.toolchain.git -  Build related artifacts that release separately, common assembly descriptors, remote resources, etc.  
* http://git.eclipse.org/gitroot/jetty/org.eclipse.jetty.sandbox.git - Non-mainline project development, working area for experimentation, etc  
+
* http://git.eclipse.org/c/jetty/org.eclipse.jetty.sandbox.git - Non-mainline project development, working area for experimentation, etc  
* http://git.eclipse.org/gitroot/jetty/org.eclipse.jetty.releng.git  - Project definition for generating an eclipse p2 update site  
+
* http://git.eclipse.org/c/jetty/org.eclipse.jetty.releng.git  - Project definition for generating an eclipse p2 update site  
* http://git.eclipse.org/gitroot/jetty/org.eclipse.jetty.admin.git - Files associated with the development of Jetty -- code styles, formatting, etc.
+
* http://git.eclipse.org/c/jetty/org.eclipse.jetty.admin.git - Files associated with the development of Jetty -- code styles, formatting, etc.
 +
* http://git.eclipse.org/c/jetty/org.eclipse.jetty.wtp.git - jetty wtp plugin
 +
 
  
 
== Build  ==
 
== Build  ==

Revision as of 14:06, 6 July 2011


Source Control

Jetty uses a few of different development trunks for its artifacts.

Primary Interest SCMURLs

These are the URLs to the GIT repositories for the Jetty code. For people who are working on the Jetty project, as well as for people who are interested in examining or modifying the Jetty code for their own projects.

Build and Project Infrastructure SCMURLs

These are the URLs for Jetty-related code and metadata. These are not needed to use Jetty; these are primarily of use for people who are working with Jetty-the-project (as opposed to using Jetty-the-server in their own projects).


Build

Jetty uses Apache Maven 2.x for managing its build and primary project metadata.

Building Jetty should simply be a matter of changing into the relevant directory and executing the following commands:

 svn co svn://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk /my_work_dir/jetty
 cd /my_work_dir/jetty
 mvn install

All relevant dependencies will be downloaded into your local repository automatically.

Building with Eclipse

This section remains to be written, but is basically a matter of installing m2eclipse for an equivalent eclipse plugin and importing the maven project.