Difference between revisions of "Jetty/Howto/Jars"

From Eclipsepedia

< Jetty‎ | Howto
Jump to: navigation, search
(New page: The core of Jetty has no external dependencies other than the servlet-api, but it does have several optional 3rd party jars. The individual jetty jars may be used directly by construct...)
 
m
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The core of Jetty has no external dependencies other than the servlet-api, but it does have several optional 3rd party jars.  
+
{{Jetty Howto
 +
|introduction=
 +
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 individual jetty jars may be used directly by constructing your own classpath, or the [[Jetty/Feature/Start.jar|start.jar]] utility can be used to build a classpath.  The aggregate jars may also used to reduce the number of jars required. During development, the [[Jetty/Howto/Use_Jetty_with_Maven|maven]] build tool is ideal for accessing jetty jars and their dependencies.
+
The [[Jetty/Reference/Dependencies|Jetty Dependencies]] reference explains the Jetty Jar structure.
  
The [[Jetty/Reference/Dependencies|Jetty Dependencies]] reference explains the jars.
+
|steps=
 +
=== Using Start.jar ===
 +
 
 +
You can use the he individual Jetty Jars directly by constructing your own classpath, or you can use the [[Jetty/Feature/Start.jar|start.jar]] utility to build a classpath.
 +
 
 +
=== Using Maven ===
 +
During development, the [[Jetty/Howto/Use_Jetty_with_Maven|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
 +
 
 +
 
 +
}}

Revision as of 17:46, 6 February 2012



Contents

Introduction

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