Olivier Lamy wrote: > The Maven team is pleased to announce the release of the Maven Site > Plugin, version 3.0-beta-1 for Maven 3. > This version is intended to be the first version of the Maven Site > Plugin for Maven 3 and it currently only works with Apache Maven > 3.0-beta-2. > > The Site Plugin is used to generate a site for the project. The > generated site also includes the project's reports that were configured > in the <reporting> section of the POM. > > The 3.x version of the Site Plugin has changed the way you configure > reports. You can read more about the new configuration mode at [1]. > > You should specify the version in the <build> section of your project's > POM: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-site-plugin</artifactId> > <version>3.0-beta-1</version> > </plugin> > > Release Notes - Maven Site Plugin - Version 3.0-beta-1 > > Bug > MSITE-456 - regression Site navigation not generated > MSITE-460 - error when using Maven 3.x with maven-site-plugin 3.x > MSITE-477 - <menu ref="modules"/> href's drop the leading character in > the href when staging a site > MSITE-490 - WARNING Deprecated API called - not > org.apache.maven.doxia.sink.Sink instance and no SinkFactory > available. Please update this plugin. > > Improvement > MSITE-436 - regenerate every page when site.xml (direct or parent) is > changed New Feature > MSITE-463 - Lithuanian translation > MSITE-465 - Add a site:effective-site goal (similar to help:effective-pom) > > Task > MSITE-478 - Attach site descriptor as an artifact, not metadata, to the > project MSITE-482 - Update to Doxia 1.1.3 > MSITE-487 - upgrade source to java 5 > > Users interested in testing this beta release should have a glance at > the compatibility notes for known differences between Maven 3.0 and > Maven 2.x: > https://cwiki.apache.org/confluence/x/sokr > > > Know limitations : > * deployment vith dav currently doesn't work. > > You must note that the default execution of site:attach-descriptor has > been removed from the built-in lifecycle bindings for projects with > packaging "pom". > So now, you have to define the following goal execution to restore the > intended behavior: > > <build> > <plugin> > <artifactId>maven-site-plugin</artifactId> > <version>3.0-beta-1</version> > <executions> > <execution> > <id>attach-descriptor</id> > <goals> > <goal>attach-descriptor</goal> > </goals> > </execution> > </executions> > </plugin> > </build> > > On the wiki page [2], you will find more information on how to > configure your POM in order to be able to continue building site with > both Maven 2.x and Maven 3.
Would be good to have a real activation element for the maven version though. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
