Maven: +1 Forrest: -0 Forrest plug-in: Possibly, but not yet. I'm more interested in streamlining the build and I don't consider the website production to be broken, so Forrest is not a big priority for me. I'm not saying never, but I see Maven as more of a priority and would rather wait and see on Forrest.
I'd like to add Maven now, learn from the experience on 1.x and then use that to optimize the project organization and build process for version 2. Steve > -----Original Message----- > From: James Mitchell [mailto:[EMAIL PROTECTED] > Sent: October 1, 2003 9:58 PM > To: Struts Developers List > Subject: [Vote] Choosing a build/doc gen tool(s) [was: Re: The Forrest > Option] > > > Most of us have given (or at least hinted at) our opinions, so > let's give a > show of hands: > > Mavenization: > [X] +1 - I am in favor of using Maven for build/dist/test/etc. > [ ] +0 - I agree, but cannot help at this time. > [ ] -0 - I don't agree, but not enough to give a -1. > [ ] -1 - I am not in favor of using Maven for build/dist/test/etc. > > Forrestization: > [X] +1 - I am in favor of using Forrest for site generation. > [ ] +0 - I agree, but cannot help at this time. > [ ] -0 - I don't agree, but not enough to give a -1. > [ ] -1 - I am not in favor of using Forrest for site generation. > > Other: > [X] - I would like to pursue the Maven-with-Forrest-as-a-plugin idea. > > > (If I left out any, please add them) > > > > One question I have about all this, (and please forgive me if I > missed it in > any of the messages in this thread) how does using either approach affect > the generation of the .tld from our source? > > > > > -- > James Mitchell > Software Engineer / Struts Evangelist > http://www.struts-atlanta.org > 678.910.8017 > 770.822.3359 > AIM:jmitchtx --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
