You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Dennis Lundberg <de...@apache.org> on 2009/12/22 07:40:16 UTC

[ANN] Maven Site Plugin 2.1 Released

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
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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [ANN] Maven Site Plugin 2.1 Released

Posted by Lukas Theussl <lt...@gmail.com>.
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ć <ss...@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 <lt...@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.connolly@gmail.com> wrote:
> >
> > > 2009/12/22 Stephen Connolly <st...@gmail.com>
> > >
> > > >
> > > >
> > > > 2009/12/22 Dennis Lundberg <de...@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-unsubscribe@maven.apache.org
> > > >> For additional commands, e-mail: users-help@maven.apache.org
> > > >>
> > > >>
> > > >
> > >
> >
>

Re: [ANN] Maven Site Plugin 2.1 Released

Posted by Dennis Lundberg <de...@apache.org>.
Stevo Slavic' wrote:
> Could 2.0.11 be released that would support using maven-site-plugin 2.1?

The short answer is no. The long answer requires an explanation about
Doxia dependencies in Maven Core. You can read something about it at:

http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan

> Otherwise there would be no java <1.5 compatible stable maven that could use
> maven-site-plugin 2.1+.

Maven 2.1.0 is java < 1.5.

> 
> Regards,
> Stevo.
> 
> On Tue, Dec 22, 2009 at 9:15 AM, Lukas Theussl <lt...@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.connolly@gmail.com> wrote:
>>
>>> 2009/12/22 Stephen Connolly <st...@gmail.com>
>>>
>>>>
>>>> 2009/12/22 Dennis Lundberg <de...@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-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: [ANN] Maven Site Plugin 2.1 Released

Posted by Stevo Slavić <ss...@gmail.com>.
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 <lt...@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.connolly@gmail.com> wrote:
>
> > 2009/12/22 Stephen Connolly <st...@gmail.com>
> >
> > >
> > >
> > > 2009/12/22 Dennis Lundberg <de...@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-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: users-help@maven.apache.org
> > >>
> > >>
> > >
> >
>

Re: [ANN] Maven Site Plugin 2.1 Released

Posted by Brett Porter <br...@apache.org>.
http://jira.codehaus.org/browse/MNG-4167

If 2.1.0 is working for you, then it is fine - but upgrading is still a good idea.

On 23/12/2009, at 5:46 PM, <su...@wipro.com> wrote:

> Stephen, why is it that maven is recommending not to use 2.1.0.
> 
> Will you have a link that hints major issues with it? When I downloaded
> Maven, this page http://maven.apache.org/download.html was recommending
> 2.1.0 also.
> 
> Now I see that it is removed from that page.
> 
> -----Original Message-----
> From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> Sent: Tuesday, December 22, 2009 3:24 PM
> To: Maven Developers List
> Subject: Re: [ANN] Maven Site Plugin 2.1 Released
> 
> http://maven.apache.org/download.html
> 
> There are only two official release versions listed:
> 
> 2.0.10
> 2.2.1
> 
> These are the current recommended versions of Maven to run.
> 
> Yes the prereq is 2.1.0, but AFAIK we are recommending that nobody use
> 2.1.0 or 2.2.0
> 
> -Stephen
> 
> 2009/12/22 Lukas Theussl <lt...@gmail.com>
> 
>> 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.connolly@gmail.com> wrote:
>> 
>>> 2009/12/22 Stephen Connolly <st...@gmail.com>
>>> 
>>>> 
>>>> 
>>>> 2009/12/22 Dennis Lundberg <de...@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-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>> 
>>>>> 
>>>> 
>>> 
>> 
> 
> Please do not print this email unless it is absolutely necessary. 
> 
> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 
> 
> WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 
> 
> www.wipro.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


RE: [ANN] Maven Site Plugin 2.1 Released

Posted by su...@wipro.com.
Stephen, why is it that maven is recommending not to use 2.1.0.

Will you have a link that hints major issues with it? When I downloaded
Maven, this page http://maven.apache.org/download.html was recommending
2.1.0 also.

Now I see that it is removed from that page. 

-----Original Message-----
From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com] 
Sent: Tuesday, December 22, 2009 3:24 PM
To: Maven Developers List
Subject: Re: [ANN] Maven Site Plugin 2.1 Released

http://maven.apache.org/download.html

There are only two official release versions listed:

2.0.10
2.2.1

These are the current recommended versions of Maven to run.

Yes the prereq is 2.1.0, but AFAIK we are recommending that nobody use
2.1.0 or 2.2.0

-Stephen

2009/12/22 Lukas Theussl <lt...@gmail.com>

> 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.connolly@gmail.com> wrote:
>
> > 2009/12/22 Stephen Connolly <st...@gmail.com>
> >
> > >
> > >
> > > 2009/12/22 Dennis Lundberg <de...@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-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: users-help@maven.apache.org
> > >>
> > >>
> > >
> >
>

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: [ANN] Maven Site Plugin 2.1 Released

Posted by Stephen Connolly <st...@gmail.com>.
http://maven.apache.org/download.html

There are only two official release versions listed:

2.0.10
2.2.1

These are the current recommended versions of Maven to run.

Yes the prereq is 2.1.0, but AFAIK we are recommending that nobody use 2.1.0
or 2.2.0

-Stephen

2009/12/22 Lukas Theussl <lt...@gmail.com>

> 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.connolly@gmail.com> wrote:
>
> > 2009/12/22 Stephen Connolly <st...@gmail.com>
> >
> > >
> > >
> > > 2009/12/22 Dennis Lundberg <de...@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-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: users-help@maven.apache.org
> > >>
> > >>
> > >
> >
>

Re: [ANN] Maven Site Plugin 2.1 Released

Posted by Lukas Theussl <lt...@gmail.com>.
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.connolly@gmail.com> wrote:

> 2009/12/22 Stephen Connolly <st...@gmail.com>
>
> >
> >
> > 2009/12/22 Dennis Lundberg <de...@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-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
>

Re: [ANN] Maven Site Plugin 2.1 Released

Posted by Stephen Connolly <st...@gmail.com>.
2009/12/22 Stephen Connolly <st...@gmail.com>

>
>
> 2009/12/22 Dennis Lundberg <de...@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>

Re: [ANN] Maven Site Plugin 2.1 Released

Posted by Dennis Lundberg <de...@apache.org>.
Stephen Connolly wrote:
> 2009/12/22 Dennis Lundberg <de...@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.
> 
> -Stephen

Like Lukas said, we are not recommending any particular version of
Maven, simply stating the minimum version required:

"the plugin now requires at least Maven 2.1.x to run, you cannot use it
with older Maven"

> 
> 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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: [ANN] Maven Site Plugin 2.1 Released

Posted by Stephen Connolly <st...@gmail.com>.
2009/12/22 Dennis Lundberg <de...@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.

-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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>