...
| Tip |
|---|
available since jetty-6.1.12.rc2 and jetty-7.0.0pre3 jetty-6.1.12rc1 has a bug (JETTY-683) that is fixed on 6.1.12.rc2. |
It can be configured by passing Resource[], String[], or String (csv) in the constructor.
The primary resource(first in the list) is the main resource.
...
| Tip |
|---|
When maven fails to dependency-inject overloaded resources, use: Note that for the other webapp sources, you can add them to the plugin's extra scan targets for dynamic reload. |
...
Example
Scenario:
| Code Block |
|---|
WebAppX:
/foo.jsp
/bar.jsp
/WEB-INF/web.xml
WebAppY:
/bar.jsp
/baz.jsp
/WEB-INF/web.xml
/WEB-INF/sitemesh.xml
|
Configuration:
<resources>webappY/src/main/webapp, webappX/src/main/webapp</resources>
...
| Code Block |
|---|
When Y(first resource) extends/overrides X, you get: /foo.jsp /bar.jsp (Y) /baz.jsp /WEB-INF/web.xml (Y) /WEB-INF/sitemesh.xml |
Overlays
| Tip |
|---|
available since jetty-6.1.12.rc3 and jetty-7.0.0pre4 |
When using mvn jetty:run, you don't need to configure anything.
Just add a dependency like:
| Code Block |
|---|
<dependency>
<groupId>org.dojotoolkit</groupId>
<artifactId>dojo-war</artifactId>
<version>1.2-SNAPSHOT</version>
<type>war</type>
</dependency>
<dependency>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-test</artifactId>
<version>6.1.12.rc3</version>
<type>war</type>
</dependency>
|
If configured manually, it would look like:
| Code Block |
|---|
<resources>src/main/webapp,/home/johndoe/path/to/dojo-war/dir,/home/johndoe/path/to/jetty-test/dir</resources>
|
The order of the overlays depends on how you arrange the war dependencies in your pom.xml (top to bottom)