You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by vs...@apache.org on 2008/01/09 19:22:30 UTC

svn commit: r610493 - /maven/site/trunk/src/site/apt/developers/release/releasing.apt

Author: vsiveton
Date: Wed Jan  9 10:22:01 2008
New Revision: 610493

URL: http://svn.apache.org/viewvc?rev=610493&view=rev
Log:
o fixed link

Modified:
    maven/site/trunk/src/site/apt/developers/release/releasing.apt

Modified: maven/site/trunk/src/site/apt/developers/release/releasing.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/developers/release/releasing.apt?rev=610493&r1=610492&r2=610493&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/developers/release/releasing.apt (original)
+++ maven/site/trunk/src/site/apt/developers/release/releasing.apt Wed Jan  9 10:22:01 2008
@@ -79,7 +79,7 @@
 +-----+
 
  <<IMPORTANT NOTE:>> Be sure that the generated artifacts respect the
- {{{http://www.apache.org/dev/release.html}Apache release rules}}: NOTICE and LICENSE files should be present in
+ {{{http://www.apache.org/dev/release.html#distribute-raw-artifact}Apache release rules}}: NOTICE and LICENSE files should be present in
  the META-INF directory within the jar. For -sources artifacts, be sure that your pom does NOT use the
  maven-source-plugin:2.0.3 which is broken. The recommended version at this time is 2.0.4.
 
@@ -165,7 +165,7 @@
 
  <<Note:>> Be sure to generate and deploy the site using the same version of the release. Typically, you need to check out the tag (or go to <<<target/checkout>>>)
   and call <<<mvn site -Preporting site:deploy>>>.
- 
+
  []
 
  After that you can continue with step 8 in the