--- Ted Husted <[EMAIL PROTECTED]> wrote: > Don Brown wrote: > > Further, deciding between Forrest and Maven isn't an either/or > situation. > > There exists a Forrest plugin for Maven and it would be easy to > integrate > > Maven's reports into a Forrest site build. > > <.../> > > > If we did decide to go with Forrest, I'm willing to convert the old > site > > over and help handle any integration. I'm most definately not an > expert > > at Forrest, but am familiar with Cocoon and thankfully, Forrest is > pretty > > easy. > > +1 > > This sounds like a nice stepping stone. We can try Forrest now and > migrate the build to Maven as soon as someone is ready to volunteer for > that. > > Outside of the Jakarta Commons Sandbox, Forrest and Maven are equally > popular among other Apache products. Using both might be the best of > both worlds.
Or it may be a complete nightmare. So then we would have Forrest, Maven, and Ant builds all competing for attention. I am definitely against using multiple build processes; let's just pick one and stick with it. The Forrest features Don mentioned aren't significant to me and I'm already familiar with Maven so I'm leaning towards Maven but I really don't care as long as the build is as easy as "maven jar" or equivalent. But please let's not try to maintain multiple build processes. David > > -Ted. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
