[T5.1.0.5] Problem with report-plugin on windows

[raucha]

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

After some research on the web I have tried to change all path entrys in the generated file component-report-javadoc-arguments.txt from '\' to '/' and executed the command line manually.

After that javadoc.exe worked fine so my question is how can I configure the way the report plugin generates the component-report-javadoc-arguments file to still use the Linux path delimiter even on a windows machine?

[Kalle Korhonen-2]

Same issue here. I'd hate to hack some replacement script together
just to work around this - I can verify that manually replacing
backslashes to forward ones works. Anybody with a good solution, for
example does this work any better with some specific Maven javadoc
plugin version on Windows ?

Kalle


On Wed, Sep 9, 2009 at 3:17 AM, raucha <A.Rauch@...> wrote:

>
> 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
>
> After some research on the web I have tried to change all path entrys in the
> generated file component-report-javadoc-arguments.txt from '\' to '/' and
> executed the command line manually.
>
> After that javadoc.exe worked fine so my question is how can I configure the
> way the report plugin generates the component-report-javadoc-arguments file
> to still use the Linux path delimiter even on a windows machine?
> --
> View this message in context: http://www.nabble.com/-T5.1.0.5--Problem-with-report-plugin-on-windows-tp25362108p25362108.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[buckofive]

Just as a reference for this thread the JIRA for this issue is here: https://issues.apache.org/jira/browse/TAP5-871