Jump to: navigation, search

Difference between revisions of "Jetty/Contributor/Building"

(changed URL for "svn co" as dev.eclipse.org is apparently not currently supporting the HTTP protocol for subversion checkouts. "svn://" works fine.)
m
(9 intermediate revisions by 3 users not shown)
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 several development trunks for its artifacts.  They are mirrored on github through http://github.com/eclipse, or you can look through them via the Eclipse setup at the URLs below.  
  
 
=== 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.  
+
These are the URLs to the GIT repositories for the Jetty code. They are 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://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git - Jetty Project Repository
* 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  ===
Line 16: Line 16:
 
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://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty-parent/trunk -  Administrative pom.xml file  
+
* http://git.eclipse.org/c/jetty/org.eclipse.jetty.parent.git -  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://git.eclipse.org/c/jetty/org.eclipse.jetty.toolchain.git -  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://git.eclipse.org/c/jetty/org.eclipse.jetty.sandbox.git - 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://git.eclipse.org/c/jetty/org.eclipse.jetty.releng.git - 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://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  ==
  
Jetty uses [http://maven.apache.org Apache Maven 2.x] for managing its build and primary project metadata.  
+
Jetty-7.x uses JDK6 to build. The artifacts produced are run-time compatible with JDK5. Jetty-8.x builds with JDK6 and produces artifacts that are runtime compatible with JDK6.  This is because servlet 3.0 requires JDK6.
 +
 
 +
Jetty uses [http://maven.apache.org Apache Maven 3.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 svn://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk /my_work_dir/jetty
+
   git clone <scm url>
   cd /my_work_dir/jetty
+
   cd <new directory>
 
   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.
+
See [[Jetty/Howto/Develop_with_Eclipse|Developing Jetty in Eclipse]].

Revision as of 16:15, 23 February 2012



Source Control

Jetty uses several development trunks for its artifacts. They are mirrored on github through http://github.com/eclipse, or you can look through them via the Eclipse setup at the URLs below.

Primary Interest SCMURLs

These are the URLs to the GIT repositories for the Jetty code. They are 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-7.x uses JDK6 to build. The artifacts produced are run-time compatible with JDK5. Jetty-8.x builds with JDK6 and produces artifacts that are runtime compatible with JDK6. This is because servlet 3.0 requires JDK6.

Jetty uses Apache Maven 3.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:

 git clone <scm url>
 cd <new directory>
 mvn install

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

Building with Eclipse

See Developing Jetty in Eclipse.