maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Siveton" <vincent.sive...@gmail.com>
Subject Re: svn commit: r462647 - in /maven/site/trunk/src/site/apt/developers: ./ committer-documentation-plugins.apt committer-environment.apt committer-settings.apt committer-testing-plugins.apt index.apt pmc-gpg-keys.apt pmc-release-process.apt
Date Wed, 11 Oct 2006 00:34:28 GMT
Hi,

As already discussed on the mailing list, here is a first draft for a
Developers centre.

Here is the staging site
http://people.apache.org/~vsiveton/developers-centre/developers/

All comments are welcome!

Cheers,

Vincent

2006/10/10, vsiveton@apache.org <vsiveton@apache.org>:
> Author: vsiveton
> Date: Tue Oct 10 17:28:35 2006
> New Revision: 462647
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=462647
> Log:
> MNG-2600: Create a Developers centre
>
> o first try
>
> Added:
>    maven/site/trunk/src/site/apt/developers/
>    maven/site/trunk/src/site/apt/developers/committer-documentation-plugins.apt   (with props)
>    maven/site/trunk/src/site/apt/developers/committer-environment.apt   (with props)
>    maven/site/trunk/src/site/apt/developers/committer-settings.apt   (with props)
>    maven/site/trunk/src/site/apt/developers/committer-testing-plugins.apt   (with props)
>    maven/site/trunk/src/site/apt/developers/index.apt   (with props)
>    maven/site/trunk/src/site/apt/developers/pmc-gpg-keys.apt   (with props)
>    maven/site/trunk/src/site/apt/developers/pmc-release-process.apt   (with props)
>
> Added: maven/site/trunk/src/site/apt/developers/committer-documentation-plugins.apt
> URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/developers/committer-documentation-plugins.apt?view=auto&rev=462647
> ==============================================================================
> --- maven/site/trunk/src/site/apt/developers/committer-documentation-plugins.apt (added)
> +++ maven/site/trunk/src/site/apt/developers/committer-documentation-plugins.apt Tue Oct 10 17:28:35 2006
> @@ -0,0 +1,44 @@
> + ------
> + Developers centre - Documentation Plugins Strategies
> + ------
> + Vincent Siveton
> + ------
> + October 2006
> + ------
> +
> + ~~ Copyright 2006 The Apache Software Foundation.
> + ~~
> + ~~ Licensed under the Apache License, Version 2.0 (the "License");
> + ~~ you may not use this file except in compliance with the License.
> + ~~ You may obtain a copy of the License at
> + ~~
> + ~~      http://www.apache.org/licenses/LICENSE-2.0
> + ~~
> + ~~ Unless required by applicable law or agreed to in writing, software
> + ~~ distributed under the License is distributed on an "AS IS" BASIS,
> + ~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> + ~~ See the License for the specific language governing permissions and
> + ~~ limitations under the License.
> +
> + ~~ NOTE: For help with the syntax of this file, see:
> + ~~ http://maven.apache.org/guides/mini/guide-apt-format.html
> +
> +
> +Introduction
> +
> + A {{{../guides/development/guide-plugin-documentation.html}Guide to the Plugin Documentation Standard}} was created.
> + This document is intended to verify it during the Plugins development.
> +
> +Verify Plugin Documentation
> +
> + The {{{../plugins/maven-docck-plugin}maven-docck-plugin}} checks that a project complies with the Plugin Documentation Standard.
> +
> + You <<should>> verify that all Plugin documentation respects this standard. The maven-docck-plugin can be run:
> +
> ++-----+
> +mvn docck:check
> ++-----+
> +
> +References
> +
> + * {{{http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Documentation}Maven Plugin Documentation}}
>
> Propchange: maven/site/trunk/src/site/apt/developers/committer-documentation-plugins.apt
> ------------------------------------------------------------------------------
>    svn:eol-style = native
>
> Propchange: maven/site/trunk/src/site/apt/developers/committer-documentation-plugins.apt
> ------------------------------------------------------------------------------
>    svn:keywords = "Author Date Id Revision"
>
> Added: maven/site/trunk/src/site/apt/developers/committer-environment.apt
> URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/developers/committer-environment.apt?view=auto&rev=462647
> ==============================================================================
> --- maven/site/trunk/src/site/apt/developers/committer-environment.apt (added)
> +++ maven/site/trunk/src/site/apt/developers/committer-environment.apt Tue Oct 10 17:28:35 2006
> @@ -0,0 +1,118 @@
> + ------
> + Developers centre - Commiter Environment
> + ------
> + Vincent Siveton
> + ------
> + October 2006
> + ------
> +
> + ~~ Copyright 2006 The Apache Software Foundation.
> + ~~
> + ~~ Licensed under the Apache License, Version 2.0 (the "License");
> + ~~ you may not use this file except in compliance with the License.
> + ~~ You may obtain a copy of the License at
> + ~~
> + ~~      http://www.apache.org/licenses/LICENSE-2.0
> + ~~
> + ~~ Unless required by applicable law or agreed to in writing, software
> + ~~ distributed under the License is distributed on an "AS IS" BASIS,
> + ~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> + ~~ See the License for the specific language governing permissions and
> + ~~ limitations under the License.
> +
> + ~~ NOTE: For help with the syntax of this file, see:
> + ~~ http://maven.apache.org/guides/mini/guide-apt-format.html
> +
> +
> +Introduction
> +
> + This document is intended to set up the Maven committer environment.
> +
> +Subversion Configuration
> +
> + Before committing files in subversion repository, you need to read the
> + {{{http://www.apache.org/dev/version-control.html#https-svn}Committer Subversion Access}}
> + document and you must set your svn client with this properties file : {{{svn-eol-style.txt}svn-eol-style.txt}}
> +
> +{Maven Code Style}
> +
> + The following sections show how to set up the code style for Maven in IDEA and Eclipse.
> + It is strongly preferred that patches use this style before they are spplied.
> +
> +* IntelliJ IDEA 4.5+
> +
> + Download <<<{{{maven-idea-codestyle.xml}maven-idea-codestyle.xml}}>>> and copy it to
> + <<<~/.IntelliJIDEA/config/codestyles>>> then restart IDEA. On Windows, try
> + <<<C:\Documents and Settings\<username>\.IntelliJIDEA\config\codestyles>>>
> +
> + After this, restart IDEA and open the settings to select the new code style.
> +
> +* Eclipse 3.2+
> +
> + Download <<<{{{maven-eclipse-codestyle.xml}maven-eclipse-codestyle.xml}}>>>.
> +
> + After this, select Window \> Preferences, and open up the configuration for Java \> Code
> + Style \> Code Formatter. Click on the button labeled Import... and select the file you
> + downloaded. Give the style a name, and click OK.
> +
> +Setting up SSH public/private keys
> +
> + By default, SSH (Secure Shell) asks to type password each time, i.e.:
> +
> ++-----+
> +>ssh vsiveton@apache.org
> +Password:
> ++-----+
> +
> + SSH can be set up with public/private key pairs so that you don't have to type the password each time.
> + You need to execute the following on your development machine:
> +
> ++-----+
> +> ssh-keygen -t dsa
> +Generating public/private dsa key pair.
> +Enter file in which to save the key (~/.ssh/id_dsa): (just type return)
> +Enter passphrase (empty for no passphrase): (just type return)
> +Enter same passphrase again: (just type return)
> +Your identification has been saved in ~/.ssh/id_dsa
> +Your public key has been saved in ~/.ssh/id_dsa.pub
> +The key fingerprint is:
> +ec:06:c7:44:9e:a6:2c:c0:8a:87:04:07:a0:5b:94:d2 YOUR_MACHINE_USERNAME @ YOUR_MACHINE_DOMAIN
> ++-----+
> +
> + Then, paste the content of the local <<<~/.ssh/id_dsa.pub>>> file into the file
> + <<</home/YOUR_APACHE_USERNAME/.ssh/authorized_keys>>> on the Apache remote host.
> +
> + <<Note>>: under Cygwin, it is located at <<<\{cygwin.install.path\}\home\YOUR_MACHINE_USERNAME\.ssh>>>. You need
> + to copy the content of <<<\{cygwin.install.path\}\home\YOUR_MACHINE_USERNAME\.ssh>>> into
> + <<<C:\Documents and Settings\YOUR_MACHINE_USERNAME\.ssh>>> for Maven.
> +
> + To test the installation, try to log again on Apache. No more password should be asked.
> +
> ++-----+
> +>ssh vsiveton@apache.org
> +Last login: Tue Oct 10 03:50:10 2006 from ipXXX-XXX-XXX-XXX
> +Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
> +        The Regents of the University of California.  All rights reserved.
> +
> +FreeBSD 6.1-RELEASE (SMP-turbo) #0: Thu May 11 11:50:25 PDT 2006
> +
> +This is an Apache Software Foundation server.
> +For more information, see http://www.apache.org/dev/
> +
> +Time to change your password? Type "passwd" and follow the prompts.
> +                -- Dru <genesis@istar.ca>
> +-bash-2.05b$
> ++-----+
> +
> +Usefull softwares
> +
> + The Maven Team uses several software. Here is a partial list:
> +
> + * {{{http://www.cygwin.com/}Cygwin}}: collection of free software tools to allow various versions of Microsoft
> +  Windows to act somewhat like a Unix system
> +
> + * {{{http://winscp.net/}Winscp}}: SFTP client for Windows.
> +
> + * {{{http://tortoisesvn.tigris.org/}Tortoisesvn}}: Subversion client, implemented as a windows shell extension.
> +
> + * {{{http://www.gnupg.org/}GnuPG}}: GNU Privacy Guard.
>
> Propchange: maven/site/trunk/src/site/apt/developers/committer-environment.apt
> ------------------------------------------------------------------------------
>    svn:eol-style = native
>
> Propchange: maven/site/trunk/src/site/apt/developers/committer-environment.apt
> ------------------------------------------------------------------------------
>    svn:keywords = "Author Date Id Revision"
>
> Added: maven/site/trunk/src/site/apt/developers/committer-settings.apt
> URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/developers/committer-settings.apt?view=auto&rev=462647
> ==============================================================================
> --- maven/site/trunk/src/site/apt/developers/committer-settings.apt (added)
> +++ maven/site/trunk/src/site/apt/developers/committer-settings.apt Tue Oct 10 17:28:35 2006
> @@ -0,0 +1,66 @@
> + ------
> + Developers centre - Committer Settings
> + ------
> + Vincent Siveton
> + ------
> + October 2006
> + ------
> +
> + ~~ Copyright 2006 The Apache Software Foundation.
> + ~~
> + ~~ Licensed under the Apache License, Version 2.0 (the "License");
> + ~~ you may not use this file except in compliance with the License.
> + ~~ You may obtain a copy of the License at
> + ~~
> + ~~      http://www.apache.org/licenses/LICENSE-2.0
> + ~~
> + ~~ Unless required by applicable law or agreed to in writing, software
> + ~~ distributed under the License is distributed on an "AS IS" BASIS,
> + ~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> + ~~ See the License for the specific language governing permissions and
> + ~~ limitations under the License.
> +
> + ~~ NOTE: For help with the syntax of this file, see:
> + ~~ http://maven.apache.org/guides/mini/guide-apt-format.html
> +
> +
> +Introduction
> +
> + This document is intended to set up the Maven committer settings, i.e. the <<<$\{user.home\}/.m2/settings.xml>>>.
> +
> +Enable Apache Servers
> +
> + Maven uses several servers configuration to deploy snapshots, releases and documentation on the Apache servers.
> + You need to tell to Maven what your Apache username is.
> +
> ++-----+
> +<settings>
> +...
> +  <servers>
> +    <!-- To publish a snapshot of some part of Maven -->
> +    <server>
> +      <id>apache.snapshots</id>
> +      <username> <!-- YOUR APACHE USERNAME --> </username>
> +      <filePermissions>664</filePermissions>
> +      <directoryPermissions>775</directoryPermissions>
> +    </server>
> +    <!-- To publish a website of some part of Maven -->
> +    <server>
> +      <id>apache.website</id>
> +      <username> <!-- YOUR APACHE USERNAME --> </username>
> +      <filePermissions>664</filePermissions>
> +      <directoryPermissions>775</directoryPermissions>
> +    </server>
> +    <!-- To publish a release of some part of Maven - ONLY FOR PMC -->
> +    <server>
> +      <id>apache.releases</id>
> +      <username> <!-- YOUR APACHE USERNAME --> </username>
> +      <filePermissions>664</filePermissions>
> +      <directoryPermissions>775</directoryPermissions>
> +    </server>
> +    ...
> +  </servers>
> +</settings>
> ++-----+
> +
> + You also need to be a member of the group <<<apcvs>>> and <<<maven>>> on people.apache.org.
>
> Propchange: maven/site/trunk/src/site/apt/developers/committer-settings.apt
> ------------------------------------------------------------------------------
>    svn:eol-style = native
>
> Propchange: maven/site/trunk/src/site/apt/developers/committer-settings.apt
> ------------------------------------------------------------------------------
>    svn:keywords = "Author Date Id Revision"
>
> Added: maven/site/trunk/src/site/apt/developers/committer-testing-plugins.apt
> URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/developers/committer-testing-plugins.apt?view=auto&rev=462647
> ==============================================================================
> --- maven/site/trunk/src/site/apt/developers/committer-testing-plugins.apt (added)
> +++ maven/site/trunk/src/site/apt/developers/committer-testing-plugins.apt Tue Oct 10 17:28:35 2006
> @@ -0,0 +1,395 @@
> + ------
> + Developers centre - Testing Plugins Strategies
> + ------
> + Vincent Siveton
> + ------
> + October 2006
> + ------
> +
> + ~~ Copyright 2006 The Apache Software Foundation.
> + ~~
> + ~~ Licensed under the Apache License, Version 2.0 (the "License");
> + ~~ you may not use this file except in compliance with the License.
> + ~~ You may obtain a copy of the License at
> + ~~
> + ~~      http://www.apache.org/licenses/LICENSE-2.0
> + ~~
> + ~~ Unless required by applicable law or agreed to in writing, software
> + ~~ distributed under the License is distributed on an "AS IS" BASIS,
> + ~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> + ~~ See the License for the specific language governing permissions and
> + ~~ limitations under the License.
> +
> + ~~ NOTE: For help with the syntax of this file, see:
> + ~~ http://maven.apache.org/guides/mini/guide-apt-format.html
> +
> +
> +Introduction
> +
> + Currently, Maven only supports unit testing out of the box. This document is intended to help Maven Developers to
> + test Plugins with Unit Tests, Integration Tests or Functional tests.
> +
> + <<Note>>: It is a <<DRAFT>> document, only the unit testing part is more official.
> +
> +Unit Tests
> +
> + Typically, these tests will be executed with the <<<test>>> phase.
> +
> +* Junit
> +
> + Globally, you need to create a *Test (by convention) class which <<<extends TestCase>>>.
> +
> + If you need Plexus container services, you need to <<<extends PlexusTestCase>>> instead of TestCase.
> +
> +* maven-plugin-testing-harness
> +
> + The {{{https://svn.apache.org/repos/asf/maven/shared/trunk/maven-plugin-testing-harness}maven-plugin-testing-harness}}
> + is attended to test the <<<org.apache.maven.reporting.AbstractMavenReport#execute()>>> implementation.
> +
> + Globally, you need to include <<<maven-plugin-testing-harness>>> as dependency, and create a *MojoTest (by convention)
> + class which <<<extends AbstractMojoTestCase>>>.
> +
> ++-----+
> +...
> +  <dependencies>
> +    ...
> +    <dependency>
> +      <groupId>org.apache.maven.shared</groupId>
> +      <artifactId>maven-plugin-testing-harness</artifactId>
> +      <version>1.0-beta-1</version>
> +      <scope>test</scope>
> +    </dependency>
> +    ...
> +  </dependencies>
> +...
> ++-----+
> ++-----+
> +public class YourMojoTest
> +    extends AbstractMojoTestCase
> +{
> +    /**
> +     * @see junit.framework.TestCase#setUp()
> +     */
> +    protected void setUp() throws Exception {
> +
> +        // required for mojo lookups to work
> +        super.setUp();
> +    }
> +
> +    /**
> +     * @throws Exception
> +     */
> +    public void testMojoGoal() throws Exception
> +    {
> +        File testPom = new File( getBasedir(),
> +          "src/test/resources/unit/basic-test/basic-test-plugin-config.xml" );
> +
> +        YourMojo mojo = (YourMojo) lookupMojo ( "yourGoal", testPom );
> +
> +        assertNotNull( mojo );
> +    }
> +}
> ++-----+
> +
> + For more information, please refer to {{{http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Harness}Maven Plugin Harness Wiki}}
> +
> +Integration testing
> +
> + These tests require the artifact, so they should be run before the <<<install>>> phase, in the <<<integration-test>>>
> + phase.
> +
> +* maven-it-plugin
> +
> + The {{{https://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-it-plugin/}maven-it-plugin}} is used directly
> + in the <<<integration-test>>> phase.
> +
> + <<Note>>: this it plugin can not be used to test a plugin that is being built for the first time (i.e. with no
> + release). In this case, you could, for instance, defined an it-snapshot of the plugin with <<<maven-install-plugin>>>.
> + during the <<<pre-integration-test>>> phase.
> +
> ++-----+
> +<project
> +  xmlns="http://maven.apache.org/POM/4.0.0"
> +  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> +  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> +                      http://maven.apache.org/maven-v4_0_0.xsd">
> +  ...
> +  <artifactId>maven-XXX-plugin</artifactId>
> +  <packaging>maven-plugin</packaging>
> +  <version>1.0-SNAPSHOT</version>
> +  <description>Test Report plugin in the site phase</description>
> +  ...
> +  <build>
> +    <plugins>
> +      ...
> +      <plugin>
> +        <groupId>org.apache.maven.plugins</groupId>
> +        <artifactId>maven-it-plugin</artifactId>
> +        <version>1.0-alpha-1-SNAPSHOT</version>
> +        <configuration>
> +          <integrationTestsDirectory>${basedir}/src/it</integrationTestsDirectory>
> +          <includes>
> +            <include>**/pom.xml</include>
> +          </includes>
> +          <goals>site</goals>
> +        </configuration>
> +        <executions>
> +          <execution>
> +            <phase>integration-test</phase>
> +            <goals>
> +              <goal>test</goal>
> +            </goals>
> +          </execution>
> +        </executions>
> +      </plugin>
> +
> +      <!-- Need to install IT snapshot of maven-XXX-plugin -->
> +      <plugin>
> +        <groupId>org.apache.maven.plugins</groupId>
> +        <artifactId>maven-install-plugin</artifactId>
> +        <version>2.2-SNAPSHOT</version>
> +        <executions>
> +          <execution>
> +            <id>it-test</id>
> +            <phase>pre-integration-test</phase>
> +            <goals>
> +              <goal>install-file</goal>
> +            </goals>
> +            <configuration>
> +              <file>${basedir}/target/maven-XXX-plugin-1.0-SNAPSHOT.jar</file>
> +              <groupId>org.apache.maven.plugins</groupId>
> +              <artifactId>maven-XXX-plugin</artifactId>
> +              <version>1.0-it-SNAPSHOT</version> <!-- IT SNAPSHOT -->
> +              <packaging>maven-plugin</packaging>
> +              <pomFile>${basedir}/pom.xml</pomFile>
> +            </configuration>
> +          </execution>
> +        </executions>
> +      </plugin>
> +
> +      <!-- Testing the result of the it pom.xml -->
> +      <plugin>
> +        <groupId>org.apache.maven.plugins</groupId>
> +        <artifactId>maven-surefire-plugin</artifactId>
> +        <executions>
> +          <execution>
> +            <id>it-test</id>
> +            <phase>post-integration-test</phase>
> +            <goals>
> +              <goal>test</goal>
> +            </goals>
> +            <configuration>
> +              <includes>
> +                <include>**/*TestIt.class</include>
> +              </includes>
> +            </configuration>
> +          </execution>
> +        </executions>
> +      </plugin>
> +    </plugins>
> +  </build>
> +  ...
> +</project>
> ++-----+
> +
> + The it pom should use the it snapshot:
> +
> ++-----+
> +<project xmlns="http://maven.apache.org/POM/4.0.0"
> +    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> +  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> +                      http://maven.apache.org/maven-v4_0_0.xsd">
> +...
> +  <reporting>
> +    <outputDirectory>
> +      ${basedir}/../../../../../target/it/it1/target/site
> +    </outputDirectory>
> +    <plugins>
> +      <plugin>
> +        <groupId>org.apache.maven.plugins</groupId>
> +        <artifactId>maven-XXX-plugin</artifactId>
> +        <version>1.0-it-SNAPSHOT</version>
> +      </plugin>
> +    </plugins>
> +  </reporting>
> +...
> +</project>
> ++-----+
> +
> +* maven-plugin-test-plugin
> +
> + The {{{https://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-plugin-test-plugin/}maven-plugin-test-plugin}}
> + is attended to staging/unstaging plugin into local repository for pre/post-integration-test.
> +
> + You need to configure the <<<maven-plugin-test-plugin>>> and the <<<maven-surefire-plugin>>>:
> +
> ++-----+
> +<project
> +  xmlns="http://maven.apache.org/POM/4.0.0"
> +  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> +  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> +                      http://maven.apache.org/maven-v4_0_0.xsd">
> +  ...
> +  <artifactId>maven-XXX-plugin</artifactId>
> +  <packaging>maven-plugin</packaging>
> +  <version>1.0-SNAPSHOT</version>
> +  <description>Test Report plugin in the site phase</description>
> +  <prerequisites>
> +    <maven>2.0.4</maven>
> +  </prerequisites>
> +  ...
> +  <dependencies>
> +    ...
> +    <!-- Due to the Maven 2.0.4 prerequisites.
> +    By default, maven-plugin-test-plugin uses 2.0.1 -->
> +    <dependency>
> +      <groupId>org.apache.maven</groupId>
> +      <artifactId>maven-embedder</artifactId>
> +      <version>2.0.4</version>
> +      <scope>test</scope>
> +    </dependency>
> +    <dependency>
> +      <groupId>org.apache.maven</groupId>
> +      <artifactId>maven-core</artifactId>
> +      <version>2.0.4</version>
> +      <scope>test</scope>
> +    </dependency>
> +  </dependencies>
> +  <build>
> +    <plugins>
> +      ...
> +      <plugin>
> +        <groupId>org.apache.maven.plugins</groupId>
> +        <artifactId>maven-plugin-test-plugin</artifactId>
> +        <version>1.0-SNAPSHOT</version>
> +        <executions>
> +          <execution>
> +            <id>pre-it-test</id>
> +            <phase>pre-integration-test</phase>
> +            <goals>
> +              <goal>stage</goal>
> +            </goals>
> +          </execution>
> +          <execution>
> +            <id>post-it-test</id>
> +            <phase>post-integration-test</phase>
> +            <goals>
> +              <goal>unstage</goal>
> +            </goals>
> +          </execution>
> +        </executions>
> +      </plugin>
> +
> +      <!-- Testing the result of the it pom.xml -->
> +      <plugin>
> +        <groupId>org.apache.maven.plugins</groupId>
> +        <artifactId>maven-surefire-plugin</artifactId>
> +        <executions>
> +          <execution>
> +            <id>it-test</id>
> +            <phase>integration-test</phase>
> +            <goals>
> +              <goal>test</goal>
> +            </goals>
> +            <configuration>
> +              <includes>
> +                <include>**/*TestIt.class</include>
> +              </includes>
> +            </configuration>
> +          </execution>
> +        </executions>
> +      </plugin>
> +    </plugins>
> +  </build>
> +  ...
> +</project>
> ++-----+
> +
> + The *TestIt classes could use the Maven Embedder to provide tests:
> +
> ++-----+
> +public class MyMojoTestIt
> +    extends PlexusTestCase
> +{
> +    /**
> +     * @throws Exception
> +     */
> +    public void testDefaultProject()
> +        throws Exception
> +    {
> +        MavenEmbedder maven = new MavenEmbedder();
> +        ClassLoader classLoader = Thread.currentThread().getContextClassLoader();
> +        maven.setClassLoader( classLoader );
> +        maven.setLogger( new MavenEmbedderConsoleLogger() );
> +        maven.setOffline( true );
> +        maven.setLocalRepositoryDirectory( getTestFile( "target/local-repo" ) );
> +        maven.start();
> +
> +        File itbasedir = new File( getBasedir(), "src/it/it1" );
> +        MavenProject pom =
> +          maven.readProjectWithDependencies( new File( itbasedir, "pom.xml" ) );
> +
> +        EventMonitor eventMonitor =
> +          new DefaultEventMonitor(
> +            new PlexusLoggerAdapter(
> +              new MavenEmbedderConsoleLogger() ) );
> +        maven.execute( pom,
> +          Collections.singletonList(
> +            "org.apache.maven.plugins:maven-XXX-plugin:1.0-SNAPSHOT:yourGoal" ),
> +          eventMonitor,
> +          new ConsoleDownloadMonitor(),
> +          null,
> +          itbasedir );
> +
> +        maven.stop();
> +    }
> +}
> ++-----+
> +
> + <<Note>>: The {{{https://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-plugin-management-plugin/}maven-plugin-management-plugin}}
> + is similar to <<<maven-plugin-test-plugin>>>.
> +
> +Functionnal testing
> +
> +* maven-invoker
> +
> + The {{{https://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-invoker-plugin/}maven-invoker-plugin}}
> + is attended to invoke maven and to provide some BeanShell tests.
> +
> ++-----+
> +<project
> +  xmlns="http://maven.apache.org/POM/4.0.0"
> +  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> +  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> +                      http://maven.apache.org/maven-v4_0_0.xsd">
> +  ...
> +  <build>
> +    <plugins>
> +      <plugin>
> +        <groupId>org.apache.maven.plugins</groupId>
> +        <artifactId>maven-invoker-plugin</artifactId>
> +        <version>1.0-SNAPSHOT</version>
> +        <configuration>
> +          <debug>true</debug>
> +          <projectsDirectory>src/it</projectsDirectory>
> +          <pomIncludes>
> +            <pomInclude>**/pom.xml</pomInclude>
> +          </pomIncludes>
> +          <postBuildHookScript>verify.bsh</postBuildHookScript>
> +        </configuration>
> +        <executions>
> +          <execution>
> +            <phase>integration-test</phase>
> +            <goals>
> +              <goal>run</goal>
> +            </goals>
> +          </execution>
> +        </executions>
> +      </plugin>
> +      ...
> +    </plugins>
> +  </build>
> +  ...
> +</project>
> ++-----+
> +
>
> Propchange: maven/site/trunk/src/site/apt/developers/committer-testing-plugins.apt
> ------------------------------------------------------------------------------
>    svn:eol-style = native
>
> Propchange: maven/site/trunk/src/site/apt/developers/committer-testing-plugins.apt
> ------------------------------------------------------------------------------
>    svn:keywords = "Author Date Id Revision"
>
> Added: maven/site/trunk/src/site/apt/developers/index.apt
> URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/developers/index.apt?view=auto&rev=462647
> ==============================================================================
> --- maven/site/trunk/src/site/apt/developers/index.apt (added)
> +++ maven/site/trunk/src/site/apt/developers/index.apt Tue Oct 10 17:28:35 2006
> @@ -0,0 +1,72 @@
> + ------
> + Developers centre
> + ------
> + Vincent Siveton
> + ------
> + October 2006
> + ------
> +
> + ~~ Copyright 2006 The Apache Software Foundation.
> + ~~
> + ~~ Licensed under the Apache License, Version 2.0 (the "License");
> + ~~ you may not use this file except in compliance with the License.
> + ~~ You may obtain a copy of the License at
> + ~~
> + ~~      http://www.apache.org/licenses/LICENSE-2.0
> + ~~
> + ~~ Unless required by applicable law or agreed to in writing, software
> + ~~ distributed under the License is distributed on an "AS IS" BASIS,
> + ~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> + ~~ See the License for the specific language governing permissions and
> + ~~ limitations under the License.
> +
> + ~~ NOTE: For help with the syntax of this file, see:
> + ~~ http://maven.apache.org/guides/mini/guide-apt-format.html
> +
> +
> +Introduction
> +
> + These pages attempt to list all resources and information related to the Maven development. It contains information
> + aimed at developers, committers and PMC members.
> +
> + If you cannot find your answers here, feel free to ask the {{{mailto:dev@maven.apache.org}Maven Developer List}}.
> +
> +* Contributors Resources
> +
> +  * {{{../guides/development/guide-helping.html}Guide to helping with Maven}}
> +
> +  * {{{../guides/development/guide-m2-development.html}Developing Maven 2}}
> +
> +  * {{{../continuous-integration.html}Continuous Integration}}
> +
> +* Committers Resources
> +
> +** General Resources
> +
> +  * {{{../welcome-to-new-committers.html}Guide for new Maven committers}}
> +
> +  * {{{committer-environment.html}Committer Environment}}
> +
> +  * {{{committer-settings.html}Committer Settings}}
> +
> +** Maven Plugins Resources
> +
> +  * {{{committer-testing-plugins.html}Testing Plugins Strategies}}
> +
> +  * {{{committer-documentation-plugins.html}Documentation Plugins Strategies}}
> +
> +* PMC Resources
> +
> +  * {{{pmc-gpg-keys.html}Making GPG Keys}}
> +
> +  * {{{pmc-release-process.html}Release Process}}
> +
> +* Others Resources
> +
> +  * {{{http://people.apache.org/~vgritsenko/stats/projects/maven.html}Maven Web Stats}}
> +
> +  * {{{http://people.apache.org/~coar/mlists.html#maven.apache.org}Maven Mailing List Stats}}
> +
> +  * {{{http://www.apache.org/dev/}ASF Development Infrastructure Information}}
> +
> +  * {{{http://www.apache.org/foundation/}About the Apache Software Foundation}}
>
> Propchange: maven/site/trunk/src/site/apt/developers/index.apt
> ------------------------------------------------------------------------------
>    svn:eol-style = native
>
> Propchange: maven/site/trunk/src/site/apt/developers/index.apt
> ------------------------------------------------------------------------------
>    svn:keywords = "Author Date Id Revision"
>
> Added: maven/site/trunk/src/site/apt/developers/pmc-gpg-keys.apt
> URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/developers/pmc-gpg-keys.apt?view=auto&rev=462647
> ==============================================================================
> --- maven/site/trunk/src/site/apt/developers/pmc-gpg-keys.apt (added)
> +++ maven/site/trunk/src/site/apt/developers/pmc-gpg-keys.apt Tue Oct 10 17:28:35 2006
> @@ -0,0 +1,155 @@
> + ------
> + Developers centre - PMC Making GPG Keys
> + ------
> + Vincent Siveton
> + ------
> + October 2006
> + ------
> +
> + ~~ Copyright 2006 The Apache Software Foundation.
> + ~~
> + ~~ Licensed under the Apache License, Version 2.0 (the "License");
> + ~~ you may not use this file except in compliance with the License.
> + ~~ You may obtain a copy of the License at
> + ~~
> + ~~      http://www.apache.org/licenses/LICENSE-2.0
> + ~~
> + ~~ Unless required by applicable law or agreed to in writing, software
> + ~~ distributed under the License is distributed on an "AS IS" BASIS,
> + ~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> + ~~ See the License for the specific language governing permissions and
> + ~~ limitations under the License.
> +
> + ~~ NOTE: For help with the syntax of this file, see:
> + ~~ http://maven.apache.org/guides/mini/guide-apt-format.html
> +
> +
> +Introduction
> +
> + You need to add your GPG keys in {{https://svn.apache.org/repos/asf/maven/KEYS}} before a release. Here are some
> + useful {{{http://www.gnupg.org/}GnuPG}} commands to generate your Keys.
> +
> +* gpg --gen-key
> +
> ++-----+
> +>gpg --gen-key
> +gpg (GnuPG) 1.4.5; Copyright (C) 2006 Free Software Foundation, Inc.
> +This program comes with ABSOLUTELY NO WARRANTY.
> +This is free software, and you are welcome to redistribute it
> +under certain conditions. See the file COPYING for details.
> +
> +gpg: keyring `C:/Documents and Settings/Siveton Vincent/Application Data/gnupg\secring.gpg'
> +created
> +gpg: keyring `C:/Documents and Settings/Siveton Vincent/Application Data/gnupg\pubring.gpg'
> +created
> +Please select what kind of key you want:
> +   (1) DSA and Elgamal (default)
> +   (2) DSA (sign only)
> +   (5) RSA (sign only)
> +Your selection? 1
> +DSA keypair will have 1024 bits.
> +ELG-E keys may be between 1024 and 4096 bits long.
> +What keysize do you want? (2048) 2048
> +Requested keysize is 2048 bits
> +Please specify how long the key should be valid.
> +         0 = key does not expire
> +      <n>  = key expires in n days
> +      <n>w = key expires in n weeks
> +      <n>m = key expires in n months
> +      <n>y = key expires in n years
> +Key is valid for? (0) 0
> +Key does not expire at all
> +Is this correct? (y/N) y
> +
> +You need a user ID to identify your key; the software constructs the user ID
> +from the Real Name, Comment and Email Address in this form:
> +    "Heinrich Heine (Der Dichter) <heinrichh@duesseldorf.de>"
> +
> +Real name: Vincent Siveton
> +Email address: vsiveton@apache.org
> +Comment:
> +You selected this USER-ID:
> +    "Vincent Siveton <vsiveton@apache.org>"
> +
> +Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
> +You need a Passphrase to protect your secret key.
> +
> +You don't want a passphrase - this is probably a *bad* idea!
> +I will do it anyway.  You can change your passphrase at any time,
> +using this program with the option "--edit-key".
> +
> +We need to generate a lot of random bytes. It is a good idea to perform
> +some other action (type on the keyboard, move the mouse, utilize the
> +disks) during the prime generation; this gives the random number
> +generator a better chance to gain enough entropy.
> +++++++++++++++++++++.++++++++++..+++++++++++++++++++++++++++++++++++++++++++++++
> ++++.+++++++++++++++.++++++++++++++++++++..+++++++++++++++>++++++++++............
> +.........................+++++
> +We need to generate a lot of random bytes. It is a good idea to perform
> +some other action (type on the keyboard, move the mouse, utilize the
> +disks) during the prime generation; this gives the random number
> +generator a better chance to gain enough entropy.
> +.+++++++++++++++..++++++++++++++++++++....+++++.++++++++++.++++++++++.++++++++++
> ++++++.+++++++++++++++++++++++++++++++++++.+++++.++++++++++++++++++++++++++++++>+
> ++++++++++>+++++>+++++......................................................>++++
> ++......<.+++++........................+++++^^^
> +gpg: C:/Documents and Settings/Siveton Vincent/Application Data/gnupg\trustdb.gpg: trustdb
> +created
> +gpg: key 07DDB702 marked as ultimately trusted
> +public and secret key created and signed.
> +
> +gpg: checking the trustdb
> +gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
> +gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
> +pub   1024D/07DDB702 2006-10-10
> +      Key fingerprint = 71F6 F555 8A61 71C4 330D  B868 84F4 D470 07DD B702
> +uid                  Vincent Siveton <vsiveton@apache.org>
> +sub   2048g/D2814A59 2006-10-10
> +
> ++-----+
> +
> +* gpg --list-sigs
> +
> ++-----+
> +>gpg --list-sigs "Vincent Siveton" && gpg --armor --export "Vincent Siveton"
> +pub   1024D/07DDB702 2006-10-10
> +uid                  Vincent Siveton <vsiveton@apache.org>
> +sig 3        07DDB702 2006-10-10  Vincent Siveton <vsiveton@apache.org>
> +sub   2048g/D2814A59 2006-10-10
> +sig          07DDB702 2006-10-10  Vincent Siveton <vsiveton@apache.org>
> +
> +-----BEGIN PGP PUBLIC KEY BLOCK-----
> +Version: GnuPG v1.4.5 (MingW32)
> +
> +mQGiBEUrnAsRBACQDiYGc1IQmkENLO9iznBg8otGPEbzqQozT5tsip5mB30f6Mc/
> +uuLxJkLdna7Ul3goIXDtCeLJq38gHvruNtVNR6S+juJFkd5sLEH8UJ18PbKuo/9I
> +KGlzjtCYUUDC48czRr0efhqd54NH8ydNdpaZ76NGPPYfpXtk7kKgH/nPiwCgxozK
> +IG2frMuWIvdFafbqdAl7y/sD/1Csf0r9jtHEeXOuyhm8jCGrSwzLbHUGKPUQP37P
> +ajECHoWp6HnvHEEEpgVl+UjfZvrcVhzUoP+3r5HAugqERfkzK8AWc7qjIRjf64kU
> +sjvto31G2KYz17Y8K9y4LkRkUspu8uw903pKnW/QELg4vvPVaEYpVVIdS6+cUreu
> +V0hOA/4tW7T/GpzSbQmjvnIRQ7GVHbQeXsANwrS6NmGYIxafN9P9dfHV+eUieTu6
> +rvMP9coOhTYyEKZksrXw2MmXx5SzgxsXT0g4wDXbwxPYFfIdGUzFMobnVXiZ3G8l
> +JEl9cML0cg3ZL1SoDmVf2iG3e3Yxxsne4AE1SU+0bbq0t7rqALQlVmluY2VudCBT
> +aXZldG9uIDx2c2l2ZXRvbkBhcGFjaGUub3JnPohgBBMRAgAgBQJFK5wLAhsDBgsJ
> +CAcDAgQVAggDBBYCAwECHgECF4AACgkQhPTUcAfdtwLP3gCbB/V1afp8hzxgirCS
> +d2r6zCkJQ2IAoLKD/RIkkerNintYzrubJliJKBsRuQINBEUrnBgQCAD1+Sx+sBDL
> +1XCDtxQGsrZmMnJJVK/w4TPa/8weJkuZ1GSpINOjInmqESuehvCLoOoyfcuDVXlR
> +PUZhKZLPEKfJlFptGNK19oTO/CoQN+SJLwR41FoumsBaf1YSSRpAukyx2J6cUxqf
> +uWrK/T8PmgDw4YzmY96tev//41eZ5tSOxpoUM8ypnTaShtS9pjgHijEG0b7wBqeU
> +e1OGOiLHgKyjEJUmlTaLm1SxJ84eq0uAvYb+rb/QoWWLpjvr2/mo1kzUvCPgo3fh
> +kgOxCxsC9QD836Mi5HFK6CRYU3yAFu5+/jM+LJzELy3u7uMuOSP6yuiK8WXopdbN
> +WHOiJQfdc2gTAAMFCADdljjAG7L+8de6JzsEduKErKqWlTEWa99n1knaGKzdUUOP
> +WrKxwqgI6PAJbxOfG4vBdDa6M6+nySJDMybQsOCFyNx91/7jYkgkmv8Jkt8CTW4z
> +P4HKlFYMAFpU95ftpTAAMAlr+t+nZRTHi94/VHMv4yLGzB/xapbzToHKuUt1Yqom
> +Ncio5px7RVoicn13/i/GeY72fIdC2LRGo6PXlmmDQemoAnUw0RJoEtzapb0j/tWd
> +BdAtQQX/Ks7qhk4aDDHGgO+CdHAB8PLHDpMpUX5Zc9JX1xhyJcS8d/LPUpXtt9WN
> +eekqDpx+jNmySJr6os7rPAkjx6jDUvHPiuKdT4aviEkEGBECAAkFAkUrnBgCGwwA
> +CgkQhPTUcAfdtwJL9ACgmLuDxE+oZaMhyFSmXWN0fM36Bd8AoLYrvwydB9+nNnhJ
> +85TjkMPTgjp9
> +=Hg4C
> +-----END PGP PUBLIC KEY BLOCK-----
> ++-----+
> +
> + You need to append this result to {{https://svn.apache.org/repos/asf/maven/KEYS}}.
> +
> + You can read more about {{{http://www.apache.org/dev/release-signing.html#faq}Checksums And Signatures}}.
>
> Propchange: maven/site/trunk/src/site/apt/developers/pmc-gpg-keys.apt
> ------------------------------------------------------------------------------
>    svn:eol-style = native
>
> Propchange: maven/site/trunk/src/site/apt/developers/pmc-gpg-keys.apt
> ------------------------------------------------------------------------------
>    svn:keywords = "Author Date Id Revision"
>
> Added: maven/site/trunk/src/site/apt/developers/pmc-release-process.apt
> URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/developers/pmc-release-process.apt?view=auto&rev=462647
> ==============================================================================
> --- maven/site/trunk/src/site/apt/developers/pmc-release-process.apt (added)
> +++ maven/site/trunk/src/site/apt/developers/pmc-release-process.apt Tue Oct 10 17:28:35 2006
> @@ -0,0 +1,218 @@
> + ------
> + Developers centre - PMC Release Process
> + ------
> + Vincent Siveton
> + ------
> + October 2006
> + ------
> +
> + ~~ Copyright 2006 The Apache Software Foundation.
> + ~~
> + ~~ Licensed under the Apache License, Version 2.0 (the "License");
> + ~~ you may not use this file except in compliance with the License.
> + ~~ You may obtain a copy of the License at
> + ~~
> + ~~      http://www.apache.org/licenses/LICENSE-2.0
> + ~~
> + ~~ Unless required by applicable law or agreed to in writing, software
> + ~~ distributed under the License is distributed on an "AS IS" BASIS,
> + ~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> + ~~ See the License for the specific language governing permissions and
> + ~~ limitations under the License.
> +
> + ~~ NOTE: For help with the syntax of this file, see:
> + ~~ http://maven.apache.org/guides/mini/guide-apt-format.html
> +
> +
> +Introduction
> +
> + This document gives step-by-step instructions for releasing a part of Maven. The primary audience is Maven PMC.
> +
> +Prerequisite
> +
> + Be sure that:
> +
> + * you have all Maven servers defined in your settings.xml. For more information, please refer to
> + {{{committer-settings.html}Committer settings}}.
> +
> + * you have created your GPG keys. For more information, please refer to {{{pmc-gpg-keys.html}Making GPG Keys}}.
> +
> +Release Process for Part Of Maven
> +
> + [[1]] Make sure there are <<NO>> snapshots in the poms to be released.
> +
> + [[2]] Publish a snapshot:
> +
> ++-----+
> +>mvn deploy
> +...
> +[INFO] [deploy:deploy]
> +[INFO] Retrieving previous build number from apache.snapshots
> +...
> ++-----+
> +
> + <<Note>>: You could verify the deployment under Maven Snapshot repository on Apache.
> +
> ++-----+
> +http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-XXX-plugin/2.1/
> ++-----+
> +
> + [[3]] Propose a vote on the dev list with the closed issues, the issues left and the staging site. For instance:
> +
> ++-----+
> +To: "Maven Developers List" <dev@maven.apache.org>
> +Subject: [VOTE] Release Maven XXX plugin version 2.1
> +
> +Hi,
> +
> +We solved N issues:
> +http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=XXX&styleName=Html&version=XXX
> +
> +There are still a couple of issues left in JIRA:
> +http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=XXX&status=1
> +
> +Staging site:
> +http://people.apache.org/~YOUR_APACHE_USERNAME/maven-XXX-plugin/
> +
> +Vote open for 72 hours, based on:
> +maven-XXX-plugin-2.1-20061005.000031-3.jar  (rev 453071)
> +
> +[ ] +1
> +[ ] +0
> +[ ] -1
> +
> ++-----+
> +
> + Once a vote is successful, post the result to the dev list.
> +
> + [[4]] Prepare the release
> +
> ++-----+
> +>mvn release:prepare \
> +  -Dtag=maven-XXX-plugin-2.1 \
> +  -B \
> +  -DtagBase=https://svn.apache.org/repos/asf/maven/plugins/tags \
> +  -Dusername=YOUR_APACHE_USERNAME
> +...
> ++-----+
> +
> + <<Note>>: a release.properties file should be generated with release configuration. DO NOT DELETE IT before release.
> +
> + [[5]] Perform the release.
> +
> + It should deploy several JARS (maven-XXX-plugin-2.1.jar, maven-XXX-plugin-2.1-javadoc.jar
> + and maven-XXX-plugin-2.1-sources.jar), maven-XXX-plugin-2.1.pom and their associated md5 and sha1 files.
> +
> ++-----+
> +>mvn release:perform
> +...
> ++-----+
> +
> + <<Note>>: Maven could stop after <<<[INFO] [deploy:deploy]>>>. You need to review your authentification settings
> + for Apache (SSH public/private keys) or your servers in the settings.xml. You could try also the following
> + (NOT recommended) :
> +
> ++-----+
> +>cd target/checkout
> +>mvn deploy site-deploy --no-plugin-updates -DperformRelease=true
> ++-----+
> +
> + <<Note>>: You could verify the deployment under Maven Rsync repository on Apache.
> +
> ++-----+
> +http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/maven/plugins/maven-XXX-plugin/2.1/
> ++-----+
> +
> + [[6]] Sign Releases
> +
> + Signatures for all varieties of release need to be created. The signature files should be named after the original
> + with the .asc suffix.
> +
> ++-----+
> +>cd target/checkout/target
> +>gpg --armor --output maven-XXX-plugin-2.1-javadoc.jar.asc --detach-sig \
> +    maven-XXX-plugin-2.1-javadoc.jar
> +You need a passphrase to unlock the secret key for user: "Vincent Siveton <vsiveton@apache.org>"
> +1024-bit DSA key, ID XXXXXXXX, created 2006-10-09
> +>gpg --armor --output maven-XXX-plugin-2.1.jar.asc --detach-sig \
> +    maven-XXX-plugin-2.1.jar
> +...
> +>gpg --armor --output maven-XXX-plugin-2.1-sources.jar.asc --detach-sig \
> +    maven-XXX-plugin-2.1-sources.jar
> +...
> ++-----+
> +
> + <<Note>>: You could also sign all required files with the following scripts:
> +
> ++-----+
> +# Unix OS
> +>cd target/checkout/target
> +>for i in *.jar; do gpg --output $i.asc --detach-sig --armor $i; done
> ++-----+
> ++-----+
> +# Windows OS
> +>cd target/checkout/target
> +>for %i in (*.jar) do gpg --output %i.asc --detach-sig --armor %i
> ++-----+
> +
> + <<Note>>: You could verify the signatures with the following
> +
> ++-----+
> +>gpg --verify maven-javadoc-plugin-2.1.jar.asc maven-javadoc-plugin-2.1.jar
> +gpg: Signature made 10/09/06 11:22:35 using DSA key ID XXXXXXXX
> +gpg: Good signature from "Vincent Siveton <vsiveton@apache.org>"
> ++-----+
> +
> + [[7]] Upload Sign Releases
> +
> + Upload the detached signature files (.asc) for these releases to m2-ibiblio-rsync-repository directory on
> + Apache, i.e.:
> +
> ++-----+
> +/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/maven/plugins/maven-XXX-plugin/2.1/
> ++-----+
> +
> + [[8]] Review Website
> +
> + Wait for the files to arrive at
> +
> ++-----+
> +http://maven.apache.org/plugins/maven-XXX-plugin
> ++-----+
> +
> + [[9]] Update Jira
> +
> + Go to Admin section in Jira for the <<<maven-XXX-plugin>>> project and mark <<<2.1>>> version as release.
> +
> + [[10]] Create Announcements. For instance:
> +
> ++-----+
> +From: YOUR_APACHE_EMAIL
> +To: announce@maven.apache.org, users@maven.apache.org
> +Cc: dev@maven.apache.org
> +Subject: [ANN] Maven XXX Plugin 2.1 for Maven 2 Released
> +
> +The Maven team is pleased to announce the release of the Maven XXX Plugin, version 2.1
> +
> +http://maven.apache.org/plugins/maven-XXX-plugin/
> +
> +You can run mvn -U to get the latest version of the plugin, or specify
> +the version in your project's plugin configuration:
> +
> +<plugin>
> + <groupId>org.apache.maven.plugins</groupId>
> + <artifactId>maven-XXX-plugin</artifactId>
> + <version>2.1</version>
> +</plugin>
> +
> +Release Notes - Maven 2.x XXX Plugin - Version 2.1
> +
> +(Copy Here Release Notes in Text Format from Jira)
> +
> +Enjoy,
> +
> +-The Maven team
> +
> ++-----+
> +
> + [[11]] Celebrate :o)
>
> Propchange: maven/site/trunk/src/site/apt/developers/pmc-release-process.apt
> ------------------------------------------------------------------------------
>    svn:eol-style = native
>
> Propchange: maven/site/trunk/src/site/apt/developers/pmc-release-process.apt
> ------------------------------------------------------------------------------
>    svn:keywords = "Author Date Id Revision"
>
>
>

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


Mime
View raw message