The only reason to do this from my PoV is if the plugin requires features only available in Maven 3.
There are still a significant number of users who use Maven 2.2.1, yeah I would love to get them to jump up to 3.0.4, but I acknowledge that is something that may be beyond their control. Forcing plugin dependencies up without a valid driving requirement is just forcing unnecessary pain on the end users. IMHO features should drive the upgrading of dependencies, nothing else. -Stephen On 30 July 2012 12:44, Stanislav Ochotnicky <[email protected]> wrote: > Hi everyone, > > I am wondering what is general feeling about updating maven plugins from > depending on Maven 2.x artifacts to their Maven 3.x counterparts. > > I am aware not all m2 artifacts have equivalents in m3 (i.e. > maven-project, maven-artifact-manager and few others). Things have moved > around somewhat (i.e. few classes from maven-artifact moved to -core or > -compat). > > However, if someone provided patches, with builds and unit tests working > and all that jazz, would there be willingness to work on making this > transition happen? Or is the time not right just yet? > > Note that we've been running maven-3.0.4 and ~60 maven plugins without > maven-core,maven-artifact and quite few other 2.x artifacts, for about a > year and everything works as far as we are concerned (limited use case > of Fedora Linux apply of course) > > For the record full list of maven 2.x artifacts we still keep is: > * maven-artifact-manager > * maven-error-diagnostics > * maven-model > * maven-monitor > * maven-plugin-descriptor > * maven-plugin-registry > * maven-profile > * maven-project > * maven-toolchain > > -- > Stanislav Ochotnicky <[email protected]> > Software Engineer - Base Operating Systems Brno > > PGP: 7B087241 > Red Hat Inc. http://cz.redhat.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
