Jump to: navigation, search

Difference between revisions of "Jetty/Contributor/Building"

Line 1: Line 1:
{{Jetty Contributors}}
+
{{Jetty Contributor}}
  
 
==Source Control==
 
==Source Control==

Revision as of 02:27, 29 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.