On 16/06/2009, at 10:09 PM, Jason van Zyl wrote:
On 16-Jun-09, at 12:42 PM, Brett Porter wrote:
On 14/06/2009, at 3:53 PM, Jason van Zyl wrote:
What we can do internally for people who want to use their POMs
"as-is" with 3.x is to provide some internal mapping from the POM
to the configuration element of the new site-plugin. When 3.0 is
release no one should have to change their POMs i.e flip all the
configuration into the maven-site-plugin configuration but they
will have to use the new version of the site-plugin.
What about using the site lifecycle (which could be moved to the
site plugin if they can be loaded from there easily) so that the
reports become normal plugin goals? The advantage is that it works
with Maven 2.x today.
I'm not sure what you're talking about, it's going to work exactly
as it does in 2.x.
Yep, sorry I misread what you meant by mapping.
Still, as an implementation method, utilising the lifecycle and normal
plugin goals to generate the data needed, then having the site plugin
only render tie that up together rather than managing execution (as it
does via the core now) would give more flexibility for the future.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
