Community
Participate
Working Groups
Build Identifier: 8.0.0.M2 The level of configuration abilities that the Jetty plugin provides is awesome. I use 8.0.0.M2 to work on a modular Servlet 3.0 project and my workflow is greatly simplified thanks to the ability to specify extra classpaths. Here is how my configuration looks like: <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>jetty-maven-plugin</artifactId> <version>8.0.0.M2</version> <configuration> <webAppConfig> <extraClasspath>${basedir}/target/classes;${basedir}/../module1/target/classes;${basedir}/../module2/target/classes</extraClasspath> </webAppConfig> </configuration> </plugin> I'm using jetty:run goal and this configuration allows me to reload modular classpath resources (html, js, css) while the application is running. Such a setup is much better compared to a workflow of stopping the server, building a module jar and starting the server again. This enhancement request is about adding some trimming of the strings that are specified in the extraClasspath parameter. As the number of modules grows the parameter lines gets too long and it will be much more readable if I can set it up like this: <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>jetty-maven-plugin</artifactId> <version>8.0.0.M2</version> <configuration> <webAppConfig> <extraClasspath> ${basedir}/target/classes; ${basedir}/../module1/target/classes; ${basedir}/../module2/target/classes </extraClasspath> </webAppConfig> </configuration> </plugin> Configuration like this simply fails because of the formatting. My investigation showed that the improvement can be done in the WebAppClassLoader.addClassPath(String classPath) where the tokenized paths can be simply trimmed. The importance of this request is really minor but I hope that it may positively affect other similar cases. Here is a link to the actual POM file where I use this functionality: https://github.com/asual/summer/blob/master/sample/pom.xml Reproducible: Always
Fixed in jetty-7 svn rev 3271.
Resolved -> Closed