svn commit: r1583158 - /maven/site/trunk/content/apt/developers/retirement-plan-plugins.apt

[hb...@apache.org]

Author: hboutemy
Date: Sun Mar 30 15:37:22 2014
New Revision: 1583158

URL: http://svn.apache.org/r1583158
Log:
fixed typo for links

Modified:
    maven/site/trunk/content/apt/developers/retirement-plan-plugins.apt

Modified: maven/site/trunk/content/apt/developers/retirement-plan-plugins.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/developers/retirement-plan-plugins.apt?rev=1583158&r1=1583157&r2=1583158&view=diff
==============================================================================
--- maven/site/trunk/content/apt/developers/retirement-plan-plugins.apt (original)
+++ maven/site/trunk/content/apt/developers/retirement-plan-plugins.apt Sun Mar 30 15:37:22 2014
@@ -96,7 +96,7 @@ I will continue with the steps required 
   retired. This allows us to make a clean break. The person who wants to retire
   a plugin is the one who does the final release. Below you will find the extra
   steps that you need to follow when retiring a plugin, in addition to
-  {{{./release/maven-project-release-procedure.html}}our standard release process}.
+  {{{./release/maven-project-release-procedure.html}our standard release process}}.
 
 * Make the final release
 
@@ -127,7 +127,7 @@ but has moved to the <Organization> <Pro
   [[1]] Add " (RETIRED)" at the end of <<<\<project\>>>>/<<<\<name\>>>> in the
   plugin's <<<pom.xml>>>. This will show up on every page of the generated site.
 
-  [[1]] Go ahead with {{{./release/maven-project-release-procedure.html}}the standard release process},
+  [[1]] Go ahead with {{{./release/maven-project-release-procedure.html}the standard release process}},
   making sure that you follow the exceptions mentioned above regarding the site deployment.
 
   [[1]] When updating the plugins page, move Maven Foo Plugin to under the
@@ -141,7 +141,7 @@ but has moved to the <Organization> <Pro
 
   [[1]] Remove the plugin from the <<<\<modules\>>>> section of the plugins aggregator POM.
 
-  [[1]] Remove any jobs from Continuous Integration servers like {{{http://builds.apache.org/}}ASF Jenkins farm}.
+  [[1]] Remove any jobs from Continuous Integration servers like {{{http://builds.apache.org/}ASF Jenkins farm}}.
   Plugins normally don't have separate jobs, but check anyway just to make sure.
 
   [[1]] Move the source code in Subversion. <Where to> depends on which scenario