[Netcdftools-commit] SF.net SVN: netcdftools:[60] trunk/pom.xml

[<rob...@us...>]

Revision: 60
          http://netcdftools.svn.sourceforge.net/netcdftools/?rev=60&view=rev
Author:   robertbridle
Date:     2010-06-25 04:37:57 +0000 (Fri, 25 Jun 2010)

Log Message:
-----------
ANDSWRON-618 - Remove automated deployment of site to SourceForge this will now be a manual process.

Modified Paths:
--------------
    trunk/pom.xml

Modified: trunk/pom.xml
===================================================================
--- trunk/pom.xml	2010-06-25 02:44:49 UTC (rev 59)
+++ trunk/pom.xml	2010-06-25 04:37:57 UTC (rev 60)
@@ -2,10 +2,10 @@
 
 This pom.xml has been configured with the following dependencies:
 
-1.) plink.exe has been installed - you can specify the path to the plink.exe if its not on your system path, e.g.
+1.) gpg.exe needs to be installed on your system - you can specify the path to gpg.exe as follows:
     
-    mvn deploy site-deploy -Dexec.executable="C:\Program Files\PLink\plink.exe"
-    mvn release:prepare release:perform -Darguments="-Dexec.executable=C:\\Program Files\\PLink\\plink.exe"
+    SNAPSHOT Release: mvn deploy -Dgpg.executable="C:\Progra~1\GNU\GnuPG\gpg.exe"
+    Test Release:     mvn release:prepare release:perform -Dusername="<insert svn username here>" -Darguments="-Dgpg.executable=C:\\Progra~1\\GNU\\GnuPG\\gpg.exe"
 
 2.) Our Maven settings.xml contains the credentials for: accessing SCM; running GPG (not currently used); site deployment to SourceForge; and deploying to repositories, e.g.
 
@@ -43,6 +43,9 @@
   </activeProfiles>
 </settings>
 
+3.) This pom.xml is not configured to perform site deployment or file releases (see commented out sections), 
+these steps will need to be performed manually.
+
 -->
 <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">
   <modelVersion>4.0.0</modelVersion>
@@ -295,13 +298,14 @@
         </executions>
       </plugin>
       
+      <!-- WE NOW PERFORM A MANUAL SITE DEPLOY TO SOURECFORGE -->
       <!-- Run script to create SourceForge shell so that site can be uploaded via SCP  -->
+      <!--
       <plugin>
         <groupId>org.codehaus.mojo</groupId>
         <artifactId>exec-maven-plugin</artifactId>
         <version>1.1</version>
         <executions>
-          <!-- create a shell on SourceForge -->
           <execution>
             <id>create_shell_on_sourceforge</id>
             <phase>pre-site</phase>
@@ -320,7 +324,6 @@
               </arguments>
             </configuration>
           </execution>
-          <!-- Change ownership of htdocs directory so that site can be unploaded -->
           <execution>
             <id>change_htdocs_ownership</id>
             <phase>pre-site</phase>
@@ -341,12 +344,35 @@
           </execution>
         </executions>
       </plugin>
+      -->
       
       <!-- 2.0-beta-9 used to overcome bug when tagging a release (http://jira.codehaus.org/browse/SCM-406)  -->
       <plugin>
         <artifactId>maven-release-plugin</artifactId>
-        <version>2.0-beta-9</version>    
+        <version>2.0-beta-9</version>
+        <configuration>
+          <goal>deploy</goal> <!-- Because we have a populated <site> element, the site-deploy goal will execute. We specify that only the deploy goal should execute, since we will perform site-deploys manually -->
+        </configuration>        
       </plugin>
+      
+      <!--  This will sign the artifacts before being deployed to the release repository. note: the variables ${gpg.keyname} and ${gpg.passphrase} are retrieved from local file: settings.xml  -->
+      <plugin>
+         <groupId>org.apache.maven.plugins</groupId>
+         <artifactId>maven-gpg-plugin</artifactId>
+         <configuration>
+           <keyname>${gpg.keyname}</keyname>
+           <passphrase>${gpg.passphrase}</passphrase>
+         </configuration>
+         <executions>
+           <execution>
+             <id>sign-artifacts</id>
+             <phase>verify</phase>
+             <goals>
+               <goal>sign</goal>
+             </goals>
+           </execution>
+         </executions>
+      </plugin>
 
     </plugins>
   </build>


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.