I do recall a "shoot-out" between Maven and Forrest for the web site, and we
seemed to prefer Forrest. In discussions with Dion, he noted that Maven's
primary benefit was process and build related, and that we could seamlessly
use Forrest with Maven, getting what appeared to be the best of both worlds.
Dion has been working on a project file for James so that we can see the
benefits of Maven. As Danny says on our list (which is where this should be
discussed), we'd like to hear more about our build and web publishing
options so that we can make the informed selection.
For example, if we have james-site, james-mailet and james-server, and we
want james-site to be populated with HTML generated from javadocs in
james-mailet and james-server, is Maven able to handle such a thing? Is
Forrest?
Unlike Jakarta, our sub-projects are related. Is Maven's report generator
capable of giving us integrated reports across our sub-projects, or is it
only capable of separate reports? We will have dependencies such that
james-mailet will produce one or more jar files that james-server depends
upon. Will Maven handle that? How?
Right now, everytime I generate the build, every javadoc page is regenerated
for publication, even though the javadoc hasn't changed. Will Maven clean
up that idiotic process? Will Forrest?
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
