On 11/16/06, Brett Porter <[EMAIL PROTECTED]> wrote:
On 16/11/2006, at 3:37 AM, Xavier Hanin wrote: >> There is also the apt format >> (http://maven.apache.org/guides/mini/guide-apt-format.html). >> Which are >> simple text wiki like, that you can store in your repository >> (allowing to >> send path). > > > I like this kind of format, very easy to write with a plain text > editor. > What I don't like is to need to launch and wait for the generation. We have mvn site:run for that purpose. It starts up a Jetty instance and adds a servlet filter that will render them on the fly.
Sounds nice, thanks for the tip! I'll give it a try. Pretty
sure forrest has something similar. > > But I don't know if it can be used easily without maven (It would > be amazing >> to use maven to manage the documention. That would clearly >> indicate that >> ivy and maven have different scope). > > > It would mean that contributors would need both ant and maven > installed. I > don't mind, I have both, but I'm not sure it's worth it. It would be reasonably straightforward to wrap the Maven independent Doxia code in an ant task - it's just waiting for a contributor (*hint* *hint*). I've been told my ant task writing sucks.
If we choose to use this kind of documentation I'm pretty suree you'll see such a volunteer poping up :) Xavier We would need to refactor some of the site.xml inheritence to support
non-Maven project structures, and also refactor the site:run code as it depends on the maven project as well. Certainly achievable. You know where to find us if you are interested :) Cheers, Brett
