Jump to: navigation, search

Difference between revisions of "Jetty/Contributor/Building"

Line 1: Line 1:
 +
{{Jetty Contributors}}
 +
 
==Source Control==
 
==Source Control==
  
Line 4: Line 6:
  
 
===Primary Interest SCMURLs===
 
===Primary Interest SCMURLs===
 +
<div class="unbounded-list">
 
; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk : Jetty7 development trunk
 
; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk : Jetty7 development trunk
 
; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/branches/jetty-8 : Jetty8 development trunk
 
; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/branches/jetty-8 : Jetty8 development trunk
 +
</div>
  
 
===Build and Project Infrastructure SCMURLs===
 
===Build and Project Infrastructure SCMURLs===
 +
<div class="unbounded-list">
 
; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty-parent/trunk : Administrative pom.xml file
 
; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty-parent/trunk : Administrative pom.xml file
 
; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty-toolchain/trunk : Build related artifacts that release separately, common assembly descriptors, remote resources, etc.
 
; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty-toolchain/trunk : Build related artifacts that release separately, common assembly descriptors, remote resources, etc.
Line 13: Line 18:
 
; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty-update-site/trunk : Project definition for generating an eclipse p2 update site
 
; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty-update-site/trunk : Project definition for generating an eclipse p2 update site
 
; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/admin : Files associated with the development of Jetty -- code styles, formatting, etc.
 
; http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/admin : Files associated with the development of Jetty -- code styles, formatting, etc.
 +
</div>
  
 
==Build==
 
==Build==
Line 18: Line 24:
 
Jetty uses [http://maven.apache.org Apache Maven] for managing its build and primary project metadata.   
 
Jetty uses [http://maven.apache.org Apache Maven] for managing its build and primary project metadata.   
  
Building jetty should simply be a matter of running changing into the relevant directory and running:
+
Building Jetty should simply be a matter of changing into the relevant directory and running:
  
> <tt>mvn install</tt>
+
  mvn install
  
 
All relevant dependencies will be downloaded into your local repository automatically.
 
All relevant dependencies will be downloaded into your local repository automatically.

Revision as of 04:12, 23 June 2009


Source Control

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

Primary Interest SCMURLs

Build and Project Infrastructure SCMURLs

http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty-parent/trunk 
Administrative pom.xml file
http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty-toolchain/trunk 
Build related artifacts that release separately, common assembly descriptors, remote resources, etc.
http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/sandbox/trunk 
Non-mainline project development, working area for experimentation, etc
http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty-update-site/trunk 
Project definition for generating an eclipse p2 update site
http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/admin 
Files associated with the development of Jetty -- code styles, formatting, etc.

Build

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

Building Jetty should simply be a matter of changing into the relevant directory and running:

 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.