inteligr8/alfresco-sdk
1
0
Fork 0
mirror of https://github.com/Alfresco/alfresco-sdk.git synced 2025-10-08 14:51:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Formatting tweaks and example project name change

Browse Source
This commit is contained in:
Jeff Potts
2019-01-29 13:46:21 +00:00
parent 185c4ad2bd
commit 5d1fb4f4d9
1 changed files with 45 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

80
docs/advanced-topics/upgrading.md
View File

@@ -21,21 +21,21 @@ For example, you might create a new project called "test-aio-400" to use as a ba
## Copy run scripts from base to target ## Copy run scripts from base to target
1. Copy run.bat and run.sh from base to target project 1. Copy run.bat and run.sh from base to target project.
## Copy the docker directory from base into target ## Copy the docker directory from base into target
1. Recursively copy the docker directory from base into target 1. Recursively copy the docker directory from base into target.
2. Clean up references in the docker-compose.yml file 2. Clean up references in the docker-compose.yml file.
In the docker directory copied from the base, edit the docker-compose.yml file to change references to the base project name to the target project name. In the docker directory copied from the base, edit the docker-compose.yml file to change references to the base project name to the target project name.
## Copy the platform-docker directory into target ## Copy the platform-docker directory into target
1. Recursively copy the *-platform-docker directory into target 1. Recursively copy the \*-platform-docker directory into target
2. Rename the directory. The name of the directory should follow the same pattern as the existing project. For example, if the existing project is test-aio-301 then the platform-docker directory should be called test-aio-301-platform-docker. 2. Rename the directory. The name of the directory should follow the same pattern as the existing project. For example, if the existing project is upgrade-test then the platform-docker directory should be called upgrade-test-platform-docker.
## Clean up references in the platform-docker directory in target ## Clean up references in the platform-docker directory in target
@@ -46,7 +46,7 @@ In the docker directory copied from the base, edit the docker-compose.yml file t
## Copy the share-docker directory into target ## Copy the share-docker directory into target
1. Recursively copy the *-share-docker directory into target 1. Recursively copy the \*-share-docker directory into target
Similar to previous step, the directory should follow the same pattern as the existing project. Similar to previous step, the directory should follow the same pattern as the existing project.
@@ -67,47 +67,57 @@ Need to smartly do this merge so that target project maintains its dependencies,
3. Replace the `alfresco-repository` dependency as follows. Change 3. Replace the `alfresco-repository` dependency as follows. Change
<dependency> ```
<groupId>${alfresco.groupId}</groupId> <dependency>
<artifactId>alfresco-repository</artifactId> <groupId>${alfresco.groupId}</groupId>
</dependency> <artifactId>alfresco-repository</artifactId>
</dependency>
```
to: to:
<dependency> ```
<groupId>${alfresco.groupId}</groupId> <dependency>
<artifactId>alfresco-remote-api</artifactId> <groupId>${alfresco.groupId}</groupId>
<scope>provided</scope> <artifactId>alfresco-remote-api</artifactId>
</dependency> <scope>provided</scope>
</dependency>
```
3. Remove the `spring-context` dependency from the target pom.xml: 3. Remove the `spring-context` dependency from the target pom.xml:
<dependency> ```
<groupId>org.springframework</groupId> <dependency>
<artifactId>spring-context</artifactId> <groupId>org.springframework</groupId>
<version>3.2.17.RELEASE</version> <artifactId>spring-context</artifactId>
<scope>test</scope> <version>3.2.17.RELEASE</version>
</dependency> <scope>test</scope>
</dependency>
```
4. Under dependencyManagement, the platform distribution dependency needs to have its artifactId updated. Change: 4. Under dependencyManagement, the platform distribution dependency needs to have its artifactId updated. Change:
<dependency> ```
<groupId>${alfresco.groupId}</groupId> <dependency>
<artifactId>alfresco-platform-distribution</artifactId> <groupId>${alfresco.groupId}</groupId>
<version>${alfresco.platform.version}</version> <artifactId>alfresco-platform-distribution</artifactId>
<type>pom</type> <version>${alfresco.platform.version}</version>
<scope>import</scope> <type>pom</type>
</dependency> <scope>import</scope>
</dependency>
```
to: to:
<dependency> ```
<groupId>${alfresco.groupId}</groupId> <dependency>
<artifactId>${alfresco.bomDependencyArtifactId}</artifactId> <groupId>${alfresco.groupId}</groupId>
<version>${alfresco.platform.version}</version> <artifactId>${alfresco.bomDependencyArtifactId}</artifactId>
<type>pom</type> <version>${alfresco.platform.version}</version>
<scope>import</scope> <type>pom</type>
</dependency> <scope>import</scope>
</dependency>
```
5. The `maven-resources-plugin` needs the outputDirectory adjusted. Change: 5. The `maven-resources-plugin` needs the outputDirectory adjusted. Change: