Return-Path: Delivered-To: apmail-tapestry-dev-archive@www.apache.org Received: (qmail 77358 invoked from network); 23 Nov 2009 14:42:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Nov 2009 14:42:04 -0000 Received: (qmail 94211 invoked by uid 500); 23 Nov 2009 14:42:03 -0000 Delivered-To: apmail-tapestry-dev-archive@tapestry.apache.org Received: (qmail 94135 invoked by uid 500); 23 Nov 2009 14:42:03 -0000 Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tapestry.apache.org Delivered-To: mailing list commits@tapestry.apache.org Received: (qmail 94126 invoked by uid 99); 23 Nov 2009 14:42:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Nov 2009 14:42:03 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Nov 2009 14:42:00 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 920AF234C04C for ; Mon, 23 Nov 2009 06:41:39 -0800 (PST) Message-ID: <263306654.1258987299583.JavaMail.jira@brutus> Date: Mon, 23 Nov 2009 14:41:39 +0000 (UTC) From: "Ville Virtanen (JIRA)" To: commits@tapestry.apache.org Subject: [jira] Updated: (TAP5-871) Generation of Component Reference failed on Windows In-Reply-To: <505252899.1254487165509.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/TAP5-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ville Virtanen updated TAP5-871: -------------------------------- Attachment: component_report_patch.patch component_report.zip Just ran in to this problem and got too frustrated, so I just rolled my own.. Attached is zip that contains corrected version of tapestry-component-report. You can copy it to your .m2 directory to the correct location and then you are on your way. Ugly solution was to replace builder.append(path); to if(SystemUtils.IS_OS_WINDOWS) { builder.append(path.replace("\\", "/")); } else { builder.append(path); } in line 839 in ComponentReport.java. This results corrected component-report-javadoc-arguments.txt file in windows but leaves the generation untouched in other platforms. Also attached patch that corrects this problem that shouldn't exist at all if maven was coded correctly? > Generation of Component Reference failed on Windows > --------------------------------------------------- > > Key: TAP5-871 > URL: https://issues.apache.org/jira/browse/TAP5-871 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-component-report > Affects Versions: 5.1.0.5 > Reporter: Armin Rauch > Attachments: component_report.zip, component_report_patch.patch > > > The maven site generation on my CI machine (which is running Linux) works well while using the tapestry-component-report plugin. If I try to stage the site on my windows development machine I encounter the following error during > mvn site:stage -DstagingDirectory=C:\fullsite > ...... > [INFO] Cobertura Report generation was successful. > [INFO] Generating "Component Reference" report. > [INFO] Running JavaDoc to collect component parameter data ... > 1 error > [INFO] ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] ------------------------------------------------------------------------ > [INFO] Error during page generation > Embedded error: Error rendering Maven report: Javadoc exit code: 1 - javadoc: error - Cannot find doclet class org.apache.tapestry.mojo.ParametersDocl > et > Command line was: cmd.exe /X /C "c:\Programme\Java\jdk1.5.0_17\jre\..\bin\javadoc.exe @target/component-report-javadoc-arguments.txt" > [INFO] ------------------------------------------------------------------------ > [INFO] For more information, run Maven with the -e switch > I have tried to change all path entrys in the generated file component-report-javadoc-arguments.txt from '\' to '/' and executed the failing command line manually. Javadoc worked with the modified file. The generation of said file should be changed to a different path seperator. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.