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.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/SonatypeNexus
http://twitter.com/SonatypeM2E
----------------------------------------------------------
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
