Brett Porter wrote:
On 10/03/2008, at 6:07 AM, Dennis Lundberg wrote:
I have tested this on four different plugins. There were a couple of
typos in the generated report, which I fixed in r635325.
I'm assuming that can wait for the next release?
Normally I'd let it wait, but in this case it's the first thing that the
end user meets, when looking at the documentation for a reporting
plugin. Here's what it looks like for the project-info-reports plugin:
project-info-reports:dependencies
Note: This Mojo should be used has a Maven report.
Also, since we managed to catch it prior to the actual release, why not
include it in the release? I know it involves a new vote and staging
etc, but it improves the perceived quality of our software.
/**
* The converter to use.
*
* @component
*/
private Maven1Converter converter;
This was included as a parameter in the report using plugin-plugin
2.3, but it is excluded from the report using 2.4. Is this the correct
behavior?
That's correct, components are not configurable by the user (and
@readonly is implied)
OK, thanks for clarifying that.
- Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
