Jump to: navigation, search

Difference between revisions of "Jetty/Howto/Jars"

< Jetty‎ | Howto
m
 
Line 1: Line 1:
 
{{Jetty Howto
 
{{Jetty Howto
 
|introduction=
 
|introduction=
 +
 +
{{Jetty TODO}}
 +
 
Jetty is decomposed into many Jars providing utilities, HTTP, server, client, servlets and many optional features.  It can be difficult to track which Jars are required and their dependencies.  
 
Jetty is decomposed into many Jars providing utilities, HTTP, server, client, servlets and many optional features.  It can be difficult to track which Jars are required and their dependencies.  
  

Latest revision as of 14:53, 23 April 2013



Introduction

Warning2.png
Some or all of this content remains to be ported to Jetty 9 Documentation.
If you are interested in migrating this content see our contribution guide or contact us.


Jetty is decomposed into many Jars providing utilities, HTTP, server, client, servlets and many optional features. It can be difficult to track which Jars are required and their dependencies.

The Jetty Dependencies reference explains the Jetty Jar structure.


Steps

Using Start.jar

You can use the he individual Jetty Jars directly by constructing your own classpath, or you can use the start.jar utility to build a classpath.

Using Maven

During development, the maven build tool is ideal for accessing Jetty Jars and their dependencies.

Using Aggregate Jars

Aggregate Jars combine many smaller Jars into a single Jar, reducing the number of Jars required. They are especially useful when you are embedding Jetty in other applications since it might be inconvenient and/or verbose to include the many small Jars that comprise Jetty.

Aggregate Jars are available as a Maven artifact under the org.eclipse.jetty.aggregate group ID.

The aggregate jars available are:

  • jetty-all
  • jetty-all-server
  • jetty-client
  • jetty-plus
  • jetty-server
  • jetty-servlet
  • jetty-webapp