You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Olivier Lamy <ol...@apache.org> on 2010/08/11 00:25:42 UTC

[ANN] Release Maven Site Plugin 3.0-beta-1 for maven 3

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.

You must note this version is a beta. You will find more informations
on migration [4]

-- 
The Maven  Team

[1] https://cwiki.apache.org/confluence/x/sokr Section "New Configuration"
[2] https://cwiki.apache.org/confluence/x/sokr Section "Using
maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x with
Maven 3.x"
[4] https://cwiki.apache.org/confluence/x/hQ1kAQ

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


Re: Maven 3 - site plugin?

Posted by Dennis Lundberg <de...@apache.org>.
On 2010-08-11 17:48, Nord, James wrote:
> Hi all,
> 
> Does the new site plugin pick up the config for the reporting plugins from plugin management or build section?

If I understand the wiki correctly, Maven 3 + Site Plugin 3 should pick
up configuration from the build section. Haven't tried that though.
Please try it and report how it goes.

> 
> That is with maven 2 if I want to have a checkstyle report in the project site but also be able to generate it from the command line "mvn checkstyle:checkstyle" I need to configure checkstyle twice, once in the <reporting> section and once in the build/plugins section.  Is this still the case with Maven3 and the inline configuration of the site plugin?  If not what do I configure to only need to configure checkstyle the once?
> 
> Regards,
> 
>         /James
> 
> -----Original Message-----
> From: Olivier Lamy [mailto:olamy@apache.org]
> Sent: 10 August 2010 23:26
> To: Maven Users List; announce@maven.apache.org
> Cc: Maven Developers List
> Subject: [ANN] Release Maven Site Plugin 3.0-beta-1 for maven 3
> 
> 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.
> 
> You must note this version is a beta. You will find more informations
> on migration [4]
> 
> --
> The Maven  Team
> 
> [1] https://cwiki.apache.org/confluence/x/sokr Section "New Configuration"
> [2] https://cwiki.apache.org/confluence/x/sokr Section "Using
> maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x with
> Maven 3.x"
> [4] https://cwiki.apache.org/confluence/x/hQ1kAQ
> 
> 
> **************************************************************************************
> This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
> 
> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
> **************************************************************************************
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-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: Maven 3 - site plugin?

Posted by Tony Chemit <ch...@codelutin.com>.
Le Wed, 11 Aug 2010 12:18:38 -0400,
Jason van Zyl <ja...@sonatype.com> a écrit :

> It will not be in the next version of the POM.

You mean next stable of the plugin ?

> 
> On Aug 11, 2010, at 12:00 PM, Tony Chemit wrote:
> 
> > Le Wed, 11 Aug 2010 16:48:18 +0100,
> > "Nord, James" <JN...@nds.com> a écrit :
> > 
> >> Hi all,
> >> 
> >> Does the new site plugin pick up the config for the reporting plugins from plugin management or build section?
> >> 
> >> That is with maven 2 if I want to have a checkstyle report in the project site but also be able to generate it from the command line "mvn checkstyle:checkstyle" I need to configure checkstyle twice, once in the <reporting> section and once in the build/plugins section.  Is this still the case with Maven3 and the inline configuration of the site plugin?  If not what do I configure to only need to configure checkstyle the once?
> >> 
> > reporting section is still available for maven 3.
> > 
> >> Regards,
> >> 
> >>        /James
> >> 
> >> -----Original Message-----
> >> From: Olivier Lamy [mailto:olamy@apache.org]
> >> Sent: 10 August 2010 23:26
> >> To: Maven Users List; announce@maven.apache.org
> >> Cc: Maven Developers List
> >> Subject: [ANN] Release Maven Site Plugin 3.0-beta-1 for maven 3
> >> 
> >> 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.
> >> 
> >> You must note this version is a beta. You will find more informations
> >> on migration [4]
> >> 
> >> --
> >> The Maven  Team
> >> 
> >> [1] https://cwiki.apache.org/confluence/x/sokr Section "New Configuration"
> >> [2] https://cwiki.apache.org/confluence/x/sokr Section "Using
> >> maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x with
> >> Maven 3.x"
> >> [4] https://cwiki.apache.org/confluence/x/hQ1kAQ
> >> 
> >> 
> >> **************************************************************************************
> >> This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
> >> 
> >> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
> >> **************************************************************************************
> >> 
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >> 
> > 
> > 
> > 
> > -- 
> > Tony Chemit
> > --------------------
> > tél: +33 (0) 2 40 50 29 28
> > email: chemit@codelutin.com  
> > http://www.codelutin.com 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> > 
> 
> Thanks,
> 
> Jason
> 
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
> 
> Simplex sigillum veri. (Simplicity is the seal of truth.)
> 
> 
> 



-- 
Tony Chemit
--------------------
tél: +33 (0) 2 40 50 29 28
email: chemit@codelutin.com  
http://www.codelutin.com 

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


Re: Maven 3 - site plugin?

Posted by Jason van Zyl <ja...@sonatype.com>.
It will not be in the next version of the POM.

On Aug 11, 2010, at 12:00 PM, Tony Chemit wrote:

> Le Wed, 11 Aug 2010 16:48:18 +0100,
> "Nord, James" <JN...@nds.com> a écrit :
> 
>> Hi all,
>> 
>> Does the new site plugin pick up the config for the reporting plugins from plugin management or build section?
>> 
>> That is with maven 2 if I want to have a checkstyle report in the project site but also be able to generate it from the command line "mvn checkstyle:checkstyle" I need to configure checkstyle twice, once in the <reporting> section and once in the build/plugins section.  Is this still the case with Maven3 and the inline configuration of the site plugin?  If not what do I configure to only need to configure checkstyle the once?
>> 
> reporting section is still available for maven 3.
> 
>> Regards,
>> 
>>        /James
>> 
>> -----Original Message-----
>> From: Olivier Lamy [mailto:olamy@apache.org]
>> Sent: 10 August 2010 23:26
>> To: Maven Users List; announce@maven.apache.org
>> Cc: Maven Developers List
>> Subject: [ANN] Release Maven Site Plugin 3.0-beta-1 for maven 3
>> 
>> 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.
>> 
>> You must note this version is a beta. You will find more informations
>> on migration [4]
>> 
>> --
>> The Maven  Team
>> 
>> [1] https://cwiki.apache.org/confluence/x/sokr Section "New Configuration"
>> [2] https://cwiki.apache.org/confluence/x/sokr Section "Using
>> maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x with
>> Maven 3.x"
>> [4] https://cwiki.apache.org/confluence/x/hQ1kAQ
>> 
>> 
>> **************************************************************************************
>> This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
>> 
>> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
>> **************************************************************************************
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>> 
> 
> 
> 
> -- 
> Tony Chemit
> --------------------
> tél: +33 (0) 2 40 50 29 28
> email: chemit@codelutin.com  
> http://www.codelutin.com 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Simplex sigillum veri. (Simplicity is the seal of truth.)




Re: Maven 3 - site plugin?

Posted by Tony Chemit <ch...@codelutin.com>.
Le Wed, 11 Aug 2010 16:48:18 +0100,
"Nord, James" <JN...@nds.com> a écrit :

> Hi all,
> 
> Does the new site plugin pick up the config for the reporting plugins from plugin management or build section?
> 
> That is with maven 2 if I want to have a checkstyle report in the project site but also be able to generate it from the command line "mvn checkstyle:checkstyle" I need to configure checkstyle twice, once in the <reporting> section and once in the build/plugins section.  Is this still the case with Maven3 and the inline configuration of the site plugin?  If not what do I configure to only need to configure checkstyle the once?
> 
reporting section is still available for maven 3.

> Regards,
> 
>         /James
> 
> -----Original Message-----
> From: Olivier Lamy [mailto:olamy@apache.org]
> Sent: 10 August 2010 23:26
> To: Maven Users List; announce@maven.apache.org
> Cc: Maven Developers List
> Subject: [ANN] Release Maven Site Plugin 3.0-beta-1 for maven 3
> 
> 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.
> 
> You must note this version is a beta. You will find more informations
> on migration [4]
> 
> --
> The Maven  Team
> 
> [1] https://cwiki.apache.org/confluence/x/sokr Section "New Configuration"
> [2] https://cwiki.apache.org/confluence/x/sokr Section "Using
> maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x with
> Maven 3.x"
> [4] https://cwiki.apache.org/confluence/x/hQ1kAQ
> 
> 
> **************************************************************************************
> This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
> 
> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
> **************************************************************************************
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 



-- 
Tony Chemit
--------------------
tél: +33 (0) 2 40 50 29 28
email: chemit@codelutin.com  
http://www.codelutin.com 

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


Maven 3 - site plugin?

Posted by "Nord, James" <JN...@nds.com>.
Hi all,

Does the new site plugin pick up the config for the reporting plugins from plugin management or build section?

That is with maven 2 if I want to have a checkstyle report in the project site but also be able to generate it from the command line "mvn checkstyle:checkstyle" I need to configure checkstyle twice, once in the <reporting> section and once in the build/plugins section.  Is this still the case with Maven3 and the inline configuration of the site plugin?  If not what do I configure to only need to configure checkstyle the once?

Regards,

        /James

-----Original Message-----
From: Olivier Lamy [mailto:olamy@apache.org]
Sent: 10 August 2010 23:26
To: Maven Users List; announce@maven.apache.org
Cc: Maven Developers List
Subject: [ANN] Release Maven Site Plugin 3.0-beta-1 for maven 3

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.

You must note this version is a beta. You will find more informations
on migration [4]

--
The Maven  Team

[1] https://cwiki.apache.org/confluence/x/sokr Section "New Configuration"
[2] https://cwiki.apache.org/confluence/x/sokr Section "Using
maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x with
Maven 3.x"
[4] https://cwiki.apache.org/confluence/x/hQ1kAQ


**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************

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


Maven 3 - site plugin?

Posted by "Nord, James" <JN...@nds.com>.
Hi all,

Does the new site plugin pick up the config for the reporting plugins from plugin management or build section?

That is with maven 2 if I want to have a checkstyle report in the project site but also be able to generate it from the command line "mvn checkstyle:checkstyle" I need to configure checkstyle twice, once in the <reporting> section and once in the build/plugins section.  Is this still the case with Maven3 and the inline configuration of the site plugin?  If not what do I configure to only need to configure checkstyle the once?

Regards,

        /James

-----Original Message-----
From: Olivier Lamy [mailto:olamy@apache.org]
Sent: 10 August 2010 23:26
To: Maven Users List; announce@maven.apache.org
Cc: Maven Developers List
Subject: [ANN] Release Maven Site Plugin 3.0-beta-1 for maven 3

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.

You must note this version is a beta. You will find more informations
on migration [4]

--
The Maven  Team

[1] https://cwiki.apache.org/confluence/x/sokr Section "New Configuration"
[2] https://cwiki.apache.org/confluence/x/sokr Section "Using
maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x with
Maven 3.x"
[4] https://cwiki.apache.org/confluence/x/hQ1kAQ


**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************

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


Re: [ANN] Release Maven Site Plugin 3.0-beta-1 for maven 3

Posted by Tony Chemit <ch...@codelutin.com>.
Le Wed, 11 Aug 2010 00:25:42 +0200,
Olivier Lamy <ol...@apache.org> a écrit :

> 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>

there is an error in this configuration (the *plugins* section is missing) , it should be :

      <build>
        <plugins>
          <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>
        </plugins>
      </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.
> 
> You must note this version is a beta. You will find more informations
> on migration [4]
> 



-- 
Tony Chemit
--------------------
tél: +33 (0) 2 40 50 29 28
email: chemit@codelutin.com  
http://www.codelutin.com 

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