On 5/6/06, Torsten Curdt <[EMAIL PROTECTED]> wrote:
On 5/6/06, Torsten Curdt <[EMAIL PROTECTED]> wrote:
> > The technique in JXR and Javadoc is going to be similar to PMD and
> > taglist. Same for checkstyle too.
>
> Ok ...here is number one:
>
> http://jira.codehaus.org/browse/MPMD-28 :-)
Number two:
http://jira.codehaus.org/browse/MTAGLIST-6
Number three has a bigger impact
http://jira.codehaus.org/browse/MNG-2280
...and I am also not totally sure it is the correct way of
doing it. The other option was to create an AbstractXXXReport
in the project info plugin and then have all the reports extend that.
The check could be in that abstract class.
On the other hand I think it is a quite common requirement to control
execution in a multi project environment. So this AbstractXXXReport
should then at least go into the reporting component.
Somehow it would be nice to have better control of the inheritance.
What about a special attribute for applicable for ALL tags?
<plugin inherit="no">
...
</plugin>
...
<organization inherit="yes">
....
</organization>
WDYT?
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
