From 4dd16868c3fddca27134216154dd4327f0e995f0 Mon Sep 17 00:00:00 2001
From: jpotts <jeffpotts01@gmail.com>
Date: Thu, 23 Jun 2016 12:56:05 -0500
Subject: [PATCH] Update share pom to work around SDK issue, modify the readme
 to explain how to build the share AMP to work around the SDK issue, bump
 version to 0.0.3 without SNAPSHOT.

---
 readme.md                         |  6 +++---
 share-site-creators-repo/pom.xml  |  8 ++++----
 share-site-creators-share/pom.xml | 11 ++++++-----
 3 files changed, 13 insertions(+), 12 deletions(-)

diff --git a/readme.md b/readme.md
index 990aac6..ecd0040 100644
--- a/readme.md
+++ b/readme.md
@@ -17,7 +17,7 @@ Installation
 ------------
 There are two AMPs associated with this add-on. One is a "repo tier" AMP and the other is a "Share tier" AMP.
 
-For each of the two projects, use `mvn install` to create the AMP. By default the POM is set to depend on the latest Alfresco Community Edition using the default specified by the SDK. This has not been tested with Alfresco Enterprise Edition.
+For each of the two projects, use `mvn install` to create the AMP. When running with 5.1.f, you must specify `` when running maven commands for the Share tier AMP.
 
 ### Install the AMPs
 
@@ -29,11 +29,11 @@ Once the AMPs are deployed, start up Alfresco.
 
 ### Deploy the Module in Share
 
-After starting Alfresco with the AMPs deployed, you'll need to go to the [Share Module Deployment Console](http://localhost:8080/share/service/modules/deploy) to deploy the module. After you hit "Apply Changes", log out, then log back in. If you don't already have a group created with your username in it, the "Create Site" links should be gone, even if you are an administrator.
+After starting Alfresco with the AMPs deployed, the Share module should be deployed for you automatically. If you can still see "Create Sites" you may need to deploy the module manually. To do so, go to the [Share Module Deployment Console](http://localhost:8080/share/service/modules/deploy) to deploy the module. After you hit "Apply Changes", log out, then log back in. If you don't already have a group created with your username in it, the "Create Site" links should be gone, even if you are an administrator.
 
 ### Create and Populate the Group
 
-Now go create a new group with an ID of "GROUP_SITE_CREATORS". You can add individuals and groups to this group. For example, at the very least you will probably want to add ALFRESCO_ADMINISTRATORS to this group.
+The SITE_CREATORS group will be created for you automatically. If, for some reason, it does not get created, create a new group with an ID of "GROUP_SITE_CREATORS". You can add individuals and groups to this group. For example, at the very least you will probably want to add ALFRESCO_ADMINISTRATORS to this group.
 
 Using a Different Group Name
 ------------------------
diff --git a/share-site-creators-repo/pom.xml b/share-site-creators-repo/pom.xml
index 50e612f..a206b2c 100644
--- a/share-site-creators-repo/pom.xml
+++ b/share-site-creators-repo/pom.xml
@@ -4,7 +4,7 @@
     <modelVersion>4.0.0</modelVersion>
     <groupId>com.ecmarchitect</groupId>
     <artifactId>share-site-creators-repo</artifactId>
-    <version>0.0.2-SNAPSHOT</version>
+    <version>0.0.3</version>
     <name>share-site-creators-repo AMP project</name>
     <packaging>amp</packaging>
     <description>Changes the permissions so that only members of a specific group can create sites.</description>
@@ -27,9 +27,9 @@
         -->
         <!-- <alfresco.groupId>org.alfresco</alfresco.groupId> -->
         <!-- Defines the Alfresco version to work against.
-             Community versions are typically identified by major.minor.character (4.2.a) while Enterprise versions are identified by major.minor.digit (4.2.0)
-        <alfresco.version>5.0.d</alfresco.version>
-        <alfresco.data.location>alf_data_dev</alfresco.data.location> -->
+             Community versions are typically identified by major.minor.character (4.2.a) while Enterprise versions are identified by major.minor.digit (4.2.0) -->
+        <alfresco.version>5.1.f</alfresco.version>
+        <!--<alfresco.data.location>/absolute/path/to/alf_data_dev</alfresco.data.location>-->
         <!-- This controls which properties will be picked in src/test/properties for embedded run -->
         <env>local</env>
         <!-- Defines the target WAR artifactId to run this amp, only used with the -Pamp-to-war profile
diff --git a/share-site-creators-share/pom.xml b/share-site-creators-share/pom.xml
index fd09c12..52ce5e8 100644
--- a/share-site-creators-share/pom.xml
+++ b/share-site-creators-share/pom.xml
@@ -4,7 +4,7 @@
     <modelVersion>4.0.0</modelVersion>
     <groupId>com.ecmarchitect</groupId>
     <artifactId>share-site-creators-share</artifactId>
-    <version>0.0.2-SNAPSHOT</version>
+    <version>0.0.3</version>
     <name>share-site-creators-share AMP project</name>
     <packaging>amp</packaging>
     <description>Hides all &quot;create site&quot; links from all users except those belonging to a specific group.</description>
@@ -34,7 +34,7 @@
              Community versions are typically identified by major.minor.character (4.2.a),
              while Enterprise versions are identified by major.minor.digit (4.2.0)
         -->
-        <!--<alfresco.version>5.0.d</alfresco.version>-->
+        <alfresco.version>5.1.f</alfresco.version>
 
         <!-- Defines the log level used in log4j.properties -->
         <app.log.root.level>WARN</app.log.root.level>
@@ -68,9 +68,10 @@
             <scope>provided</scope>
         </dependency>
         <dependency>
-          <groupId>org.springframework.extensions.surf</groupId>
-          <artifactId>spring-surf-api</artifactId>
-          <scope>provided</scope>
+            <groupId>org.alfresco.surf</groupId>
+            <artifactId>spring-surf-api</artifactId>
+            <version>${dependency.surf.version}</version>
+            <scope>provided</scope>
         </dependency>
     </dependencies>