On May 10, 2009, at 12:02 AM, Adam Murdoch wrote:
Hi,
I have some questions/comments about the JettyPlugin:
* I'd like to enable JSP support. This amounts to adding the
appropriate jars to the jetty plugin classpath (i.e. lib dir in the
Gradle distribution). Is there any reason these aren't already there?
No. Except that our distribution is getting bigger. It's time for 0.8 :)
* Do we need the JettyRunWarExploded tasks? Isn't it doing the same
thing as JettyRun (or JettyRunWar), just with different configuration?
We can get rid of it.
* Should the JettyPlugin configure the 'jettyRunExploded' task to
actually build and explode the WAR?
* Do we need the useTestClasspath option on the JettyRun task? You
can configure the task to set the classpath and classesDir
properties to their test equivalents, instead.
No
* Do we need the systemProperties property of the Jetty* tasks? You
can use .doFirst { } to set the properties instead.
Right
* The tasks scan for changes to the project build file. This is both
pointless, in that a build is not actually triggered when it
changes, and inaccurate, in that the build file is not the only
thing which determines what ends up in the web app.
We should rebuild.
* We should replace the scanning with Tom's change detection.
Yes.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
