It's rather the site plugin that could be made compatible with maven 2.0.x I guess. It would require some shading wizadry [1] that I am not familiar with and a lot of testing that we didn't have time for...
-Lukas [1] http://maven.apache.org/doxia/developers/maven-integration.html On Tue, Dec 22, 2009 at 9:49 AM, Stevo Slavić <ssla...@gmail.com> wrote: > Could 2.0.11 be released that would support using maven-site-plugin 2.1? > Otherwise there would be no java <1.5 compatible stable maven that could > use > maven-site-plugin 2.1+. > > Regards, > Stevo. > > On Tue, Dec 22, 2009 at 9:15 AM, Lukas Theussl <ltheu...@gmail.com> wrote: > > > There is no recommendation to use anything as far as I can read. It > simply > > says that the prereq to run the plugin has been set to 2.1.0, so people > > using 2.0.x don't even have to try. > > > > -Lukas > > > > > > On Tue, Dec 22, 2009 at 8:43 AM, Stephen Connolly < > > stephen.alan.conno...@gmail.com> wrote: > > > > > 2009/12/22 Stephen Connolly <stephen.alan.conno...@gmail.com> > > > > > > > > > > > > > > > 2009/12/22 Dennis Lundberg <denn...@apache.org> > > > > > > > > The Maven team is pleased to announce the release of the Maven Site > > > >> Plugin, version 2.1 > > > >> > > > >> If you consider upgrading to maven-site-plugin-2.1, please note that > > > >> there have been a couple of important changes. First, the plugin now > > > >> requires at least Maven 2.1.x to run, you cannot use it with older > > Maven > > > >> > > > > > > > > Dennis, > > > > > > > > Are we sure we want to recommend that people use 2.1.x? > > > > > > > > The only 2.1.x released is 2.1.0 which has serious issues. AFAIK, > the > > > > recommended versions of maven are 2.0.10 and 2.2.1. IIRC, anything > in > > > the > > > > range [2.1.0,2.2.1) is considered borked. > > > > > > > > > > Not to mention that a lot of the old embedded versions of maven have a > > > version number of 2.1.x and they are not even api compatible with 2.1.0 > > > (which is another good reason to avoid [2.1.0,2.2.1) > > > > > > -Stephen > > > > > > > > > > > -Stephen > > > > > > > > versions. Second, and most notable, maven-site-plugin-2.1 has been > > > >> upgraded to use Doxia 1.1, which has seen a lot of major changes > > itself. > > > >> > > > >> 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. > > > >> > > > >> http://maven.apache.org/plugins/maven-site-plugin/ > > > >> > > > >> You should specify the version in your project's plugin > configuration: > > > >> > > > >> <plugin> > > > >> <groupId>org.apache.maven.plugins</groupId> > > > >> <artifactId>maven-site-plugin</artifactId> > > > >> <version>2.1</version> > > > >> </plugin> > > > >> > > > >> > > > >> Release Notes - Maven 2.x Site Plugin - Version 2.1 > > > >> > > > >> ** Sub-task > > > >> * [MSITE-299] - Add Doxia logging support > > > >> > > > >> ** Bug > > > >> * [MSITE-141] - Possible security hole when deploying site > > > >> * [MSITE-169] - links to modules where not working if a modules > dir > > > >> is used > > > >> * [MSITE-194] - xdoc's <head/> gets rendered in the HTML body, > not > > > >> in head > > > >> * [MSITE-210] - DoxiaFilter does not set output encoding > > > >> * [MSITE-257] - Double quote character rendered as entity, which > > > >> breaks JavaScript > > > >> * [MSITE-276] - Links on Modules are completely broken on > > site:stage > > > >> * [MSITE-288] - xdoc translation, <param> tag is removed from > > > >> generated html > > > >> * [MSITE-293] - Submodule inherit menu but this should not > happend > > > >> * [MSITE-339] - site:deploy fails on HP-UX due to invalid chmod > > > option > > > >> * [MSITE-380] - Chmod following scp transfer performs poorly as > > time > > > >> goes on > > > >> * [MSITE-381] - Multi-project site navigation suddenly broken > > > >> * [MSITE-395] - Maven site multi module url problem > > > >> * [MSITE-396] - Site Deployment with scpexe fails because of > chmod > > > >> exit code > > > >> * [MSITE-404] - site:stage creates wrong links on Linux > > > >> * [MSITE-406] - jetty in site run holds unnecessary file lock in > > > >> windows > > > >> * [MSITE-409] - Incorrect URLs in multi-module project > > > >> * [MSITE-415] - site goal should fail on AptParseException > > > >> * [MSITE-430] - site:run ignores inputEncoding > > > >> > > > >> ** Improvement > > > >> * [MSITE-30] - site:deploy incompatibilities with m1.02 > > > >> * [MSITE-167] - Allow users to provide 'href' attribute to be > used > > a > > > >> section or subsection anchor > > > >> * [MSITE-436] - regenerate every page when site.xml (direct or > > > >> parent) is changed > > > >> * [MSITE-437] - How format-specific files are created and linked > is > > > >> not 100% clear > > > >> > > > >> ** New Feature > > > >> * [MSITE-33] - Add a sitemap > > > >> * [MSITE-47] - validate input format of docs > > > >> > > > >> ** Task > > > >> * [MSITE-298] - Update to Doxia 1.1.1 > > > >> * [MSITE-353] - Remove the workaround for MSITE-289 when we > upgrade > > > >> to Doxia Sitetools 1.1 > > > >> * [MSITE-368] - remove copy of reporting-api SinkFactory class > > > >> * [MSITE-419] - Update to Doxia 1.1.2 > > > >> > > > >> > > > >> Enjoy, > > > >> > > > >> -The Maven team > > > >> > > > >> > > > >> > > > >> > --------------------------------------------------------------------- > > > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > >> For additional commands, e-mail: users-h...@maven.apache.org > > > >> > > > >> > > > > > > > > > >
