On 07/11/2006, at 3:07 AM, Kenney Westerhof wrote:
I don't think rollback is the way to go, but since we're almost
releasing 2.0.5 I'd like
to suggest that we merge the reporting api changes to the 2.0.x
branch.
That might be the best path forward, though I'm generally reluctant
to make such changes in a .0.x branch. Are you 110% certain there's
no backwards compat issues here?
Ideally I'd like to see the reporting api separated from the maven
core, since only
the site plugin uses it (and the reporting plugins themselves).
You're talking about the reporting-impl. Perhaps more of the classes
in the API JAR can be moved there, but the API itself is required by
Maven at this point (I wish it wasn't but it was never fully
decoupled due to the way reports are populated).
This would also remove doxia from the m2 core installation which is
again only used
by the reporting plugins/site plugin.
That's only the sink, same reason as above.
WDYT?
The latter changes would be good for 2.1 if you can work them out.
Thanks,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
