Bug

• [JETTY-1495] - JETTY-129 is not resolved.
• [JETTY-1497] - jetty-jspc-maven-plugin has problems with spaces in classpath filenames
• [JETTY-1499] - WEB-INF/classes not scanned with mvn jetty:run-war
• [JETTY-1500] - form parameters from multipart request not available via request.getParameter
• [JETTY-1504] - HttpServletResponseWrapper ignored when using asyncContext?

Improvement

• [JETTY-1498] - Add ability to put <scope>provided</scope> artifacts on system classpath for jetty-jspc-maven-plugin

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.

Release Notes - Jetty - Version 8.1.3 <h2> Bug </h2> <ul> <li>[<a href='http://jira.codehaus.org/browse/JETTY-1495'>JETTY-1495</a>] - JETTY-129 is not resolved. </li> <li>[<a href='http://jira.codehaus.org/browse/JETTY-1497'>JETTY-1497</a>] - jetty-jspc-maven-plugin has problems with spaces in classpath filenames </li> <li>[<a href='http://jira.codehaus.org/browse/JETTY-1499'>JETTY-1499</a>] - WEB-INF/classes not scanned with mvn jetty:run-war </li> <li>[<a href='http://jira.codehaus.org/browse/JETTY-1500'>JETTY-1500</a>] - form parameters from multipart request not available via request.getParameter </li> <li>[<a href='http://jira.codehaus.org/browse/JETTY-1504'>JETTY-1504</a>] - HttpServletResponseWrapper ignored when using asyncContext? </li> </ul> <h2> Improvement </h2> <ul> <li>[<a href='http://jira.codehaus.org/browse/JETTY-1498'>JETTY-1498</a>] - Add ability to put &lt;scope&gt;provided&lt;/scope&gt; artifacts on system classpath for jetty-jspc-maven-plugin </li> </ul>