diff --git a/doc/maven.xml b/doc/maven.xml
index df3e17494e..01666901a5 100644
--- a/doc/maven.xml
+++ b/doc/maven.xml
@@ -25,6 +25,78 @@
xmlns:maven="jelly:maven"
>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+-----------------------------------------------------------
+ ACEGI SECURITY OFFICIAL RELEASE ZIP CREATION
+-----------------------------------------------------------
+
+First check the following are valid build properties:
+
+ Using keystore...: ${signature.keystore}
+ Using storepass..: ${signature.storepass}
+ Using alias......: ${signature.alias}
+
+The procedure to generate an official release ZIP is:
+
+ 1. cd ACEGI_SECURITY/docs
+ 2. maven clean multiproject:clean multiproject:artifact
+ 3. maven multiproject:site
+ 4. maven acegizip
+ 5. check ACEGI_SECURITY/target/*.zip looks correct
+ 6. maven site:sshdeploy
+ 7. ftp the ACEGI_SECURITY/target/*.zip to SourceForge
+ 8. release the FTPed file via the File Release System
+
+Failure to follow this procedure will cause out-of-date
+content (or missing content) in the official release ZIP.
+
+It would be nice if a single goal could do all this, but
+Maven throws an OutOfMemoryError. :-(
+
+
+
diff --git a/readme.txt b/readme.txt
index c1eabd5c61..f1d273169f 100644
--- a/readme.txt
+++ b/readme.txt
@@ -21,7 +21,7 @@ in this release. You can do so using the following command:
"jarsigner -verify -verbose -certs jar_file_name"
-Of course, replace the jar_file_name with "dist/acegi-security.jar" or the
+Of course, replace the jar_file_name with "acegi-security-XXXXX.jar" or the
appropriate path to the Acegi Security JAR to be validated.
Until further notice, all Acegi Security official releases are signed by:
@@ -37,31 +37,28 @@ are provided below) for further assistance.
BUILDING
-------------------------------------------------------------------------------
-Acegi Security is built using Maven. Please check building instructions at
-http://acegisecurity.sourceforge.net
+Acegi Security is built using Maven. Please read the "Building with Maven" page
+at http://acegisecurity.sourceforge.net. This page is also included in the
+/docs directory of official release ZIPs.
-------------------------------------------------------------------------------
QUICK START
-------------------------------------------------------------------------------
-Copy samples/contact/dist/contacts.war into your container webapps directory.
-Then visit http://localhost:8080/contacts/ and click "Manage". The Acegi
-Security System for Spring secures this small application by protecting both
-the method invocations of business objects, and also the HTTP URLs.
+We recommend you visit http://acegisecurity.sourceforge.net and read the
+"Suggested Steps" page. This page is also included in the /docs directory of
+official release ZIPs.
-------------------------------------------------------------------------------
DOCUMENTATION
-------------------------------------------------------------------------------
-Please refer to the Reference Guide and JavaDocs at http://acegisecurity.sourceforge.net.
+http://acegisecurity.sourceforge.net has a wide range of articles about Acegi
+security, including links to external resources. A copy of this web site is
+included in the /docs directory of official release ZIPs.
--------------------------------------------------------------------------------
-ADDING ACEGI SECURITY TO YOUR OWN APPLICATION
--------------------------------------------------------------------------------
-
-Take a look in samples/quick-start. There we give you the fragments to add to
-your existing web.xml and applicationContext.xml, along with a couple of files
-that need to be added to your WAR file.
+Be sure to read the Reference Guide, which is available from the web site (and
+/docs directory as described above). Every class also has thorough JavaDocs.
-------------------------------------------------------------------------------
OBTAINING SUPPORT