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/Feature/Jetty Jspc Maven Plugin"
(→Configuration) |
(→Configuration) |
||
| Line 7: | Line 7: | ||
Here's the basic setup required to put the jspc plugin into your build: | Here's the basic setup required to put the jspc plugin into your build: | ||
| − | + | <pre> | |
<plugin> | <plugin> | ||
<groupId>org.mortbay.jetty</groupId> | <groupId>org.mortbay.jetty</groupId> | ||
| Line 23: | Line 23: | ||
</executions> | </executions> | ||
</plugin> | </plugin> | ||
| − | + | </pre> | |
The configurable parameters are | The configurable parameters are | ||
| Line 65: | Line 65: | ||
Taking all the default settings, here's how to configure the war plugin to use the generated web.xml that includes all of the jsp servlet declarations: | Taking all the default settings, here's how to configure the war plugin to use the generated web.xml that includes all of the jsp servlet declarations: | ||
| − | + | <pre> | |
<plugin> | <plugin> | ||
<groupId>org.apache.maven.plugins</groupId> | <groupId>org.apache.maven.plugins</groupId> | ||
| Line 73: | Line 73: | ||
</configuration> | </configuration> | ||
</plugin> | </plugin> | ||
| − | + | </pre> | |
=== Precompiling Jsps with Overlayed Wars === | === Precompiling Jsps with Overlayed Wars === | ||
Revision as of 03:42, 23 September 2009
Jetty Jspc Maven Plugin
This plugin will help you pre-compile your jsps and works in conjunction with the maven war plugin to put them inside an assembled war.
Configuration
Here's the basic setup required to put the jspc plugin into your build:
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-jspc-maven-plugin</artifactId>
<version>7.0.0</version>
<executions>
<execution>
<id>jspc</id>
<goals>
<goal>jspc</goal>
</goals>
<configuration>
</configuration>
</execution>
</executions>
</plugin>
The configurable parameters are
| Parameter Name | Default Value | Meaning |
|---|---|---|
| webXmlFragment | "${basedir}/target/webfrag.xml" | xxx |
| packageRoot | "jsp" | xxx |
| webAppSourceDirectory | "${basedir}/src/main/webapp" | xx |
| webXml | "${basedir}/src/main/webapp/WEB-INF/web.xml" | xx |
| includes | "**\/*.jsp, **\/*.jspx" | xx |
| excludes | "**\/.svn\/**" | xx |
| classesDirectory | "${project.build.outputDirectory}" | x |
| generatedClasses | "${project.build.outputDirectory}" | x |
| keepSources | false | xx |
| validateXml | false | x |
| suppressSmap | true | x |
| ignoreJspFragmentErrors | false | x |
| schemaResourcePrefix | x | |
| insertionMarker | x | |
| verbose | false | x |
| mergeFragment | true | x |
Taking all the default settings, here's how to configure the war plugin to use the generated web.xml that includes all of the jsp servlet declarations:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<webXml>${basedir}/target/web.xml</webXml>
</configuration>
</plugin>