Rob mentioned something about Struts being setup for Maven already and I asked for clarification. If that's true then I see no point in complicating things with another build tool. Also, it seems that Maven in some ways is a superset of Forrest functionality. It handles the website plus the jar builds.
The more tools involved means it's harder to understand the build process which limits the number of people willing to put up with it and work on Struts. My personal goal (and I hope the group's as well) is to have *one* easy to use tool that builds all of Struts. I don't care if this is Ant, Maven, or Forrest as long as it's only one of them.
David
Yes, but the goals around here are achieved by people willing to do the work.
If Rob wants to do the work of migrating to Maven, for whatever reason, that's fine with me. A lot of people I respect use Maven, it can't suck that badly. If Don wants to do the work of migrating to Forrest, that's fine too. A lot of people I respect use Forrest, so it can't suck that badly either.
But, if we're just looking for a "one-tool solution that builds all of Struts", we already have one. To change a page in the docs, you edit the corresponding XML page. To add to the menu, edit the project.xml for that directory. Run the Ant target. Done.
If we want Struts to be even easier to build for newbies, then we should bring back the struts-lib distribution. Download that with the source, and you were ready to rock.
-Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
