Message-ID: <1287884119.2071.1369275891036.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2070_1920490322.1369275891036" ------=_Part_2070_1920490322.1369275891036 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
To use the jetty jspc plugin, you need to put a <plugin> element i=
n your pom.xml for it, and also to configure the
war plugin so=
that it uses the
web.xml file produced by the jspc plugin.
Your pom.xml will look like this:
Note: change the <version> tag value to match your prefer= ed jetty jspc plugin release.
|New configuration parameters|
New configuration parameters will be available from jetty-6.1.10 onwards= , to allow you to control the file extensions of the jsps which are compile= d. Here's an example:
The above would compile all jsp files in the webapp with extensions of .= foo and .bah, but ignore those with .roo and .bar extensions. This can be u= seful if you have chosen something other than the usual .jsp and .jspx file= extensions.
For a full listing of the <configuration> items supported by this = plugin, see jspc parameter reference.
Invoking the plugin will now be done by simply building your webapp to a=
t least the
However, as compiling jsps is usually done during preparation for a prod= uction release and not usually done during development, it is more convenie= nt to put the plugin setup inside a <profile> which which can be deli= berately invoked during prep for production .
For example, the following profile will only be invoked if the flag
So, the following invocation would cause your code to be compiled, the j= sps to be compiled, the <servlet> and <servlet-mapping>s insert= ed in the web.xml and your webapp assembled into a war:------=_Part_2070_1920490322.1369275891036--