Hi Benjamin,
2009/8/2 Benjamin Bentmann <[email protected]>:
> This also requires to bump the <prerequsites> on Maven, e.g. older Maven
> versions don't support MavenProject.clone() and will die with a linkage
> error upon executing the mojo.
Right and it is why I bump to 2.0.9 dep!
> Consider to output the error message at error level in both cases. I mean
> the severity of the message remains the same whether the plugin additionally
> dumps the stack trace or not. Somebody who greps the log output for ERROR
> would otherwise miss this information when debug logging was enabled.
Well make sense.
>
>> + clone.getOriginalModel().getReporting().setOutputDirectory(
>> tmpReportingOutputDirectory.getAbsolutePath() );
>
> Hm, maybe you could solve this without a temp model and simplify the code: I
> see the Site Plugin's outputDirectory parameter can be configured via the
> system property siteOutputDirectory. Adding this to the forked invocation
> should do equally well, shouldn't it?
Nope, it is why I created a temp pom file and set the reporting output dir.
Think about plugins which use ${project.reporting.outputDirectory} in
there conf.
Cheers
Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
