Congrats on the release! Usage page <http://maven.apache.org/plugins/maven-clean-plugin/usage.html>refers to the previous version. It would be nice if it pointed to the latest one (or maybe even leave out version reference completely). Is site/documentation "refresh" part of the release procedure? Couldn't it be automated?
On Sun, Jan 11, 2009 at 1:48 AM, Brian Fox <bri...@apache.org> wrote: > The Maven team is pleased to announce the release of the Maven > Clean Plugin, version 2.3 > > This plugin is used to delete artifacts to provide a clean build. > > http://maven.apache.org/plugins/maven-clean-plugin/ > > You should specify the version in your project's plugin configuration: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-clean-plugin</artifactId> > <version>2.3</version> > </plugin> > > > Release Notes - Maven 2.x Clean Plugin - Version 2.3 > ** Sub-task > * [MCLEAN-35] - Upgrade plexus-utils to a new version > > ** Bug > * [MCLEAN-28] - maven-clean-plugin doesn't delete directories with > symlinks in them > * [MCLEAN-29] - Maven clean plugin doesn't filter resources from > exclude list > * [MCLEAN-31] - Always resolve relative path against the project's > base directory > * [MCLEAN-34] - NPE when forcing delete of directory > * [MCLEAN-36] - filesets with an absolute path directory are > ignored when !project.isExecutionRoot() > > ** Improvement > * [MCLEAN-37] - Make verbose mode default to Maven's global debug mode > > ** New Feature > * [MCLEAN-33] - Cannot Supress Default clean while still cleaning > > > > Enjoy, > > -The Maven team > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
