Very nice! Here's a nitpick. Shouldn't it be "User Guide" like the engine, not "Users Guide" (which is grammatically incorrect? Referring to the menu at the left.
WILL On 5/23/07, Henning P. Schmiedehausen <[EMAIL PROTECTED]> wrote:
Claude Brisson <[EMAIL PROTECTED]> writes: >I had to disable the JIRA report. For some reason, maven freezes on it >(locally as well as on velocity.zones): >[DEBUG] Generating /home/claude/projects/velocity/dvsl/target/site/jira- report.html >[INFO] Generate "Jira Report" report. >[INFO] JIRA lives at: https://issues.apache.org/jira >[INFO] The JIRA URL https://issues.apache.org/jira/browse/DVSL doesn't include a pid, trying to extract it from JIRA. >[INFO] Successfully reached JIRA. >[DEBUG] Found the pid 12310670 at https://issues.apache.org/jira/browse/DVSL >[INFO] Downloading https://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss&pid=12310670sorter/field=issuekey&sorter/order=ASC&tempMax=100&reset=true&decorator=none >[INFO] Downloading successful >I first thought it was because there were no issues but it's not the >case. Also, this url looks rather strange to me: there is a missing '&' >after pid=12310670 (and I saw the same problem while running "mvn site" >on the engine). This is http://jira.codehaus.org/browse/MCHANGES-63; one of my patches that actually got applied to the maven code base at some point. However, maven-changes-plugin-2.0-beta-3 is not yet released. What a shame. Adding the explicit version to the pom makes it work. However, this can not yet be checked in to general svn because of the not released plugin. I added the version to the dvsl tree on the zone and now the maven reports builds happily. If you go to the engine tree (~velocity/deploy/velocity-engine-site) and do a "svn diff" you will see that the engine tree has the same local patch. All of our locally built sites should have this patch until maven-site and maven-changes have new releases. You probably start to understand now, why "maven 2" became a sensitive subject for me at some point. And why I will not agree to any attempts to move to a straight maven build without fallback in the near to mid future for our production releases. Maven works well for us in a tightly controlled environment like the zone. Handing a maven build out to the general community is a recipe for disaster. It is not ready for this, no matter what its advocates say. Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design | Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n "Save the cheerleader. Save the world." --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com
