Martin Poeschl wrote:
docs are really important .. so having a document describing how to organize a turbine app + a maven pluginI've been using Turbine with Maven since beta 7 was released. Maven makes it incredibly easy to generate a war file. Since you don't really want to copy a war file each time you make a change, I hacked together a method for "in-situ" development. I have a directory structure like this:
(we also could offer a build.xml for people preferring ant) sounds like a good replacement for the tdk ...
i haven't looked at all usefull maven goals to produce a web-app .. maybe we just need the torque plugin + a sample project.xml + maven.xml
src
+-conf
+-java
+-webapp
+-templates
+-images
+-javascript
Then I wrote a small maven plugin which generates a WEB-INF directory in src/webapp. It copies over the libraries I'm using, as well as the configuration files from src/conf. In my IDE (Eclipe) I tell it to generate the classes in src/webapp/WEB-INF/classes. I also point Tomcat to src/webapp as the document root.
Alternatively, I suppose one wouldn't need to work in the src directory. We could create a directory called /situ and then generate all the files in it. Also, I think Jason has some plans for a Summit plugin of some sorts, but I don't believe anything is firm. No matter what, it is _very_ easy to create a plugin, so it should be no problem. Any thoughts on how a plugin should be done?
My thoughts are:
turbine:generate - generate an "in-situ" webapp from the src dir
turbine:generate-dirs - generate a directory structure with configuration files
turbine:clean - remove the "in-situ" webapp
- Dan
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
