Re: my plans for torque and turbine

[Dan Diephouse]

I was trying to think why I didn't do it this way. The reason I chose to do it my way was that when you modify a template, you have to run the maven war:webapp goal everytime - which, needless to say, is quite time-consuming. Is this what you do? Or do you modify the templates in the "in-situ" directory and copy the them back into the src directory? Or is there a better way?

Regards,

- Dan Diephouse

Age Mooy wrote:

I don't think it it very wise to compile to and work in the src/webapp
directory.... that is what the ${maven.build.dir}is for. The war:webapp
goal does exactly what you need, but it uses maven's own directory
structure standards.

My src tree looks like this:

src
+java
+schema (used by the Torque plugin)
+test
+webapp
  +logs
  +resources
  +templates
  +WEB-INF
    +conf
    web.xml

If you run the war:webapp goal with this kind of src dir structure it
will generate a complete webapp directory structure under
${maven.build.dir}/${pom.id} for you, including the compiled classes and
the dependent lib files.
This directory structure is an exact copy of what would apear inside the
generated war if you ran the war:war goal.

You can point tomcat at the new webapp dir in your target directory and
keep you src dirs clean...

You can customize this with preGoals and postGoals if you'd rather store
the conf dir in src/conf, etc.

Age

PS
All of this is available in maven beta 7

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>