svn commit: r1397624 - /activemq/activemq-website/README

[ch...@apache.org]

Author: chirino
Date: Fri Oct 12 15:51:06 2012
New Revision: 1397624

URL: http://svn.apache.org/viewvc?rev=1397624&view=rev
Log:
Update readme

Modified:
    activemq/activemq-website/README

Modified: activemq/activemq-website/README
URL: http://svn.apache.org/viewvc/activemq/activemq-website/README?rev=1397624&r1=1397623&r2=1397624&view=diff
==============================================================================
--- activemq/activemq-website/README (original)
+++ activemq/activemq-website/README Fri Oct 12 15:51:06 2012
@@ -1,9 +1,9 @@
 
-This is the start of an export utility to export the CXF
+This is the start of an export utility to export the ACTIVEMQ
 confluence spaces to the sites.    To run this manually, you need to 
-have a copy of the CXF website checked out to a local directory:
+have a copy of the ActiveMQ website checked out to a local directory:
 
-svn checkout https://svn-master.apache.org/repos/infra/websites/production/cxf/content
+svn checkout https://svn-master.apache.org/repos/infra/websites/production/activemq/content
 
 Build:
 mvn install
@@ -24,13 +24,9 @@ done in one of two ways:
         </profile>
 
 To export the space:
-mvn -Pconfluence exec:java -Dcxf.site.output=/path/to/content
+mvn package exec:java  -Pconfluence -Dsite.output=/path/to/content
 should appear in /path/to/content/
 
-In the confluence profile above, you could add a property like:
-   <cxf.site.output>/path/to/content</cxf.site.output>
-to simplify passing that into the command.
-
 When you commit any changes in the content directory, the changes 
 should be "live" fairly quickly due to the svnpubsub process.