Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Jetty/Howto/Jars"
m |
|||
| (One intermediate revision by one other user not shown) | |||
| 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. | ||
| Line 6: | Line 9: | ||
|steps= | |steps= | ||
| − | === | + | === Using Start.jar === |
| − | You can use the 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. | + | 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| | + | During development, the [[Jetty/Howto/Use_Jetty_with_Maven|maven]] build tool is ideal for accessing Jetty Jars and their dependencies. |
| − | === Aggregate Jars === | + | === Using Aggregate Jars === |
| − | Aggregate Jars combine many smaller Jars into a single Jar | + | |
| + | 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. | Aggregate Jars are available as a Maven artifact under the org.eclipse.jetty.aggregate group ID. | ||
| Line 26: | Line 30: | ||
* jetty-servlet | * jetty-servlet | ||
* jetty-webapp | * jetty-webapp | ||
| + | |||
}} | }} | ||
Latest revision as of 14:53, 23 April 2013
Introduction
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