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 it with the Forrst plugin. You would still be able to get all the Maven-generated content.
Forrest is not a built tool. It only replaces xdoc whether we keep Ant or go to Maven. Could this vote not be redone? Mavenization with xdoc plugin: [ ] +1 - I am in favor of using Maven and the xdoc plugin [ ] +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 the xdoc plugin Mavenization with the Forrest plugin: [ ] +1 - I am in favor of using Forrest instead of xdoc. [ ] +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 instead of xdoc. I'm assuming a move to Maven is inevitable? Don --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
