On Thu, Aug 18, 2005 at 11:10:59PM +1000, Brett Porter wrote:
> This will mean changing all the reports derived from it.
Yes it will, but we can be deprecated for now.
> Are you sure the reporting api doesn't use getProject() anywhere?
I'm not entirely sure what you're refering to, but this is a
Trygve Laugstøl wrote:
Hi
While looking at the latest JavaDoc issue I was looking around in the
JavadocReport class and noticed that it used the MavenProject all over.
The usage could easily be replaced with read-only expressions from the
project except for the AbstractMavenReport that actuall
This will mean changing all the reports derived from it.
Are you sure the reporting api doesn't use getProject() anywhere?
- Brett
Trygve Laugstøl wrote:
>Hi
>
>While looking at the latest JavaDoc issue I was looking around in the
>JavadocReport class and noticed that it used the MavenProject a
Hi
While looking at the latest JavaDoc issue I was looking around in the
JavadocReport class and noticed that it used the MavenProject all over.
The usage could easily be replaced with read-only expressions from the
project except for the AbstractMavenReport that actually requires an
method MavenP
