The rule of thumb is "plugins don't interact" at this point. We're
planning alternatives in 2.x that don't degenerate to the fragility of
m1, but for now I'd suggest configuring it with the same default
location, and just test if the files exist.
There are some limitations to this:
- its dependant on report order after clean
- duplicates config if the location is changed
If you only need it to work inside the site, you can also look up the
<reporting> section and read the plugin config directly (obtain it from
the ${project.reporting} variable).
- Brett
Mike Perham wrote:
> Anyone? Bueller?
>
> -----Original Message-----
> From: Mike Perham
> Sent: Thursday, January 12, 2006 6:16 PM
> To: Maven Developers List
> Subject: determining if report output is available?
>
> http://jira.codehaus.org/browse/MPLUGIN-9
>
> This is a good suggestion to link to javadoc if it is available. The
> exact same functionality is required in PMD to link to the JXR output.
> Is there a way for a report plugin to determine if another report plugin
> is "active"? How do we get the output location for the other report in
> order to build relative links between the reports?
>
> mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
> commands, e-mail: [EMAIL PROTECTED]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
