Laying out the project is really important...
What I used to do is run jetty as a java app by creating a launch
configuration that:
- has jetty/ext/ant.jar,jasper-compiler.jar,jasper-runtime.jar,
jetty/lib/javax.servlet.jar,org.mortbay.jetty.jar,org.mortbay.jmx.jar in
classpath
- a jetty.xml config in {project}/etc pointing to my {project}/{src}/context
- run (or debug) class org.mortbay.jetty.Server, setting as work dir the
{project} dir
(The above are what the jettylauncher plugin automagically does...)
Nowadays,
- I run jetty externally with mvn jetty:run.
- Instead of enabling caching, I enable the reset service
- Whenever I recompile in idea, maven's jetty plugin restarts the context.
Kevin Menard wrote:
> Ryan Cuprak wrote:
>>
>> Hello,
>> Have you tried:
>> export JAVA_OPTS="-Dorg.apache.tapestry.disable-caching=true"
>> (then start tomcat)
>> This disables page caching so that you can see changes immediately.
>
> Heh, I figured someone was going to mention this. Yes, I have that
> option enabled. The "problem" is that IDEA has to work out of an
> exploded directory, as far as I can tell. So, changes to my "context"
> directory (contains all template & page files) don't get copied over
> until I build. Note, that I don't have to redeploy the Web app, since
> the caching is disabled, but I do need a way to update the files in
> that exploded directory. Perhaps I just have my project laid out
> oddly -- I did start with a Spindle template.
>
--
Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / J2EE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
