James Mitchell wrote:
I thought that one of the Forrest Committters said that the Forrest
plug-in for Maven
is most likely broken ?
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
It might be broken, but then again, we aren't using Maven today anyways.
I asked him about it, and he said last he heard it was working, some
people reported it buggy, but since no one was using it, it was staying
in jira until someone could put time into it. If we moved to Forrest, I
would
Steve Raeburn wrote:
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.
If the people voting +1 are ready to roll up their collective sleeves
and give Maven a try, then that would be fine with me.
Husted [mailto:[EMAIL PROTECTED]
Sent: October 2, 2003 10:18 AM
To: Struts Developers List
Subject: Re: [Vote] Choosing a build/doc gen tool(s) [was: Re: The
Forrest Option]
Steve Raeburn wrote:
I'd like to add Maven now, learn from the experience on 1.x and then
use that to optimize
I believe the question is not between maven and forrest, but rather
between Anakia/xdoc and forrest. It is entirely possible to even use all
the report output from Maven and include it in a forrest build of the
website. Default Maven uses the xdoc plugin. All forrest would be doing
is replacing
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
