Difference between revisions of "Jetty/Contributor/Building"

From Eclipsepedia

Jump to: navigation, search
m (cleaned up svn link list)
Line 1: Line 1:
{{Jetty Contributor}}
+
{{Jetty Contributor}}  
  
==Source Control==
+
== Source Control ==
  
Jetty uses a few of different development trunks for its artifacts.
+
Jetty uses a few of different development trunks for its artifacts.  
  
===Primary Interest SCMURLs===
+
=== Primary Interest SCMURLs ===
These are the URLs to the SVN 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.
+
  
<div class="unbounded-list">
+
These are the URLs to the SVN 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://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/trunk Jetty7 development trunk  
</div>
+
* http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/branches/jetty-8 - Jetty8 development trunk
 +
 
 +
=== Build and Project Infrastructure SCMURLs  ===
  
===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).  
 
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).  
  
<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.
+
* 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/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/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 ==
  
Jetty uses [http://maven.apache.org Apache Maven 2.x] for managing its build and primary project metadata.
+
Jetty uses [http://maven.apache.org 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:
+
Building Jetty should simply be a matter of changing into the relevant directory and executing the following commands:  
  
 
   svn co http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk /my_work_dir/jetty
 
   svn co http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk /my_work_dir/jetty
Line 34: Line 32:
 
   mvn install
 
   mvn install
  
All relevant dependencies will be downloaded into your local repository automatically.
+
All relevant dependencies will be downloaded into your local repository automatically.  
  
==Building with Eclipse==
+
== 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.
 
This section remains to be written, but is basically a matter of installing m2eclipse for an equivalent eclipse plugin and importing the maven project.

Revision as of 14:43, 26 July 2010


Contents

Source Control

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

Primary Interest SCMURLs

These are the URLs to the SVN 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 http://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.