I think I've been misunderstood. I am referring to the <configuration> element that can contain whatever is necessary for configuration. If the site is generated through a plugin, then by all means, configure the plugin. See my first response.
Paul On Sat, Mar 8, 2008 at 3:05 AM, Benjamin Bentmann <[EMAIL PROTECTED]> wrote: > > Why does the configuration option require a bump in version? > > The primary place for configurations regarding the build is the POM. A > new option means a change to the POM schema, a new schema means to bump > the > version. > > > it is a perfect fit for 2.0.x as well. > > Besides, you proposed to break the current behavior by defaulting to "the > correct way" (btw, "correct" appears to be wrong term here, it's merely a > matter of supporting different use cases equally easy). Breaking changes > should not happen for a maintenance release like Maven 2.0.x. > > > Benjamin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
