Minor doc and config changes

bedework.iml

@@ -7,6 +7,7 @@
       <excludeFolder url="file://$MODULE_DIR$/tmp/test-install" />
       <excludeFolder url="file://$MODULE_DIR$/tmp/tst" />
       <excludeFolder url="file://$MODULE_DIR$/tmp/wildfly" />
+      <excludeFolder url="file://$MODULE_DIR$/tmp/bw-event-registration" />
     </content>
   </component>
 </module>

build/quickstart/linux/bw.sh

@@ -139,9 +139,6 @@ usage() {
   echo "http://bedework.github.io/bedework/"
   echo "for information on configuring bedework."
   echo ""
-  echo "The location of the configuration for the deployment is set"
-  echo "in your maven settings.xml. The quickstart version is at"
-  echo "    <quickstart>/bedework/config/wildfly.deploy.properties"
   echo "  $PRG -cleanall      Do clean on all projects"
   echo "  $PRG -updateall     Does a git update of all projects"
   echo "  $PRG [-P PROFILE] <clean-build> [PROJECT] <options>"

build/quickstart/linux/installQS.sh

@@ -242,7 +242,6 @@ cat <<EOT >> "$qs"/profile.txt
       </activation>
       <properties>
         <org.bedework.deployment.basedir>$qs</org.bedework.deployment.basedir>
-        <org.bedework.deployment.properties>$qs/bedework/config/wildfly.deploy.properties</org.bedework.deployment.properties>
       </properties>
     </profile>
   </profiles>

old-docs/deployers/installing.md

@@ -38,7 +38,6 @@ Below is the contents of that settings.xml file. This must be in place before al
       </activation>
       <properties>
         <org.bedework.deployment.basedir>$qs</org.bedework.deployment.basedir>
-        <org.bedework.deployment.properties>$qs/bedework/config/wildfly.deploy.properties</org.bedework.deployment.properties>
       </properties>
     </profile>
   </profiles>
@@ -54,12 +53,9 @@ In many cases it is possible to simply cd in to the appropriate directory and do
 will build a lot of projects eventually building the client project which deploys an ear file.
 
 ### Deploying
-As part of the bedework project there is a maven plugin which uses a properties file to handle post-build deployment issues. Essentially the ear or war as built acts as a template for the deployer.
+As part of the bedework project there is a maven plugin which handles post-build deployment issues. 
 
 The deployment process may involve inserting filters for CAS, adding property values to web.xml files, cloning entire wars for calendar suites etc.
 
-The file **bedework/config/wildfly.deploy.properties** is the quickstart version of that file.
+When developing your own service the first thing to do is create a repository with your files.
 
-When developing your own service the first thing to do is create a repository with your files and copy the above file into that repository. Then set the **org.bedework.deployment.properties** value in your maven settings.xml to point to that file.
-
-DO NOT change the **org.bedework.deployment.basedir** property - unless you move the quickstart. This property is used to locate the wildfly instance.