Sounds like a bug...
On 14/07/2006 6:13 AM, Dennis Lundberg wrote:
Thanks, now it's working better. But I have one component that slips
through. Do I need to change it? It looks like this:
/**
* @component
*/
private MavenProjectHelper projectHelper;
A component should not b
Thanks, now it's working better. But I have one component that slips
through. Do I need to change it? It looks like this:
/**
* @component
*/
private MavenProjectHelper projectHelper;
A component should not be included in the report, right? But this one is.
--
Dennis Lundberg
Yep, that's right. I'll push up a snapshot now.
On 12/07/2006 7:33 PM, Dennis Lundberg wrote:
Brett Porter wrote:
Thanks - is it definitely the inheritence? If so, that's a bug.
No, it's not the inheritance. I spoke too soon.
There are two other factors:
- a bug that meant a parameter witho
Brett Porter wrote:
Thanks - is it definitely the inheritence? If so, that's a bug.
No, it's not the inheritance. I spoke too soon.
There are two other factors:
- a bug that meant a parameter without expression didn't appear (I
committed Edwin's fix yesterday, but didn't deploy a snapshot)
Thanks - is it definitely the inheritence? If so, that's a bug.
There are two other factors:
- a bug that meant a parameter without expression didn't appear (I
committed Edwin's fix yesterday, but didn't deploy a snapshot)
- readonly and components are now omitted by design
Definitely needs to
Dennis Lundberg wrote:
Hi
I've found a problem using the new plugin plugin. The "new look" for the
mojo documentation doesn't include everything that it used to.
I'm documenting the jar plugin. This plugin has an AbstractJarMojo which
the JarMojo extends. The abstract class has many paramete
Hi
I've found a problem using the new plugin plugin. The "new look" for the
mojo documentation doesn't include everything that it used to.
I'm documenting the jar plugin. This plugin has an AbstractJarMojo which
the JarMojo extends. The abstract class has many parameters that don't
get inclu
