diff --git a/docs/advanced-topics/upgrading.md b/docs/advanced-topics/upgrading.md index f7a48e4c..efcd312e 100644 --- a/docs/advanced-topics/upgrading.md +++ b/docs/advanced-topics/upgrading.md @@ -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 -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 -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. ## 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 @@ -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 -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. @@ -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 - - ${alfresco.groupId} - alfresco-repository - + ``` + + ${alfresco.groupId} + alfresco-repository + + ``` to: - - ${alfresco.groupId} - alfresco-remote-api - provided - + ``` + + ${alfresco.groupId} + alfresco-remote-api + provided + + ``` 3. Remove the `spring-context` dependency from the target pom.xml: - - org.springframework - spring-context - 3.2.17.RELEASE - test - + ``` + + org.springframework + spring-context + 3.2.17.RELEASE + test + + ``` 4. Under dependencyManagement, the platform distribution dependency needs to have its artifactId updated. Change: - - ${alfresco.groupId} - alfresco-platform-distribution - ${alfresco.platform.version} - pom - import - + ``` + + ${alfresco.groupId} + alfresco-platform-distribution + ${alfresco.platform.version} + pom + import + + ``` to: - - ${alfresco.groupId} - ${alfresco.bomDependencyArtifactId} - ${alfresco.platform.version} - pom - import - + ``` + + ${alfresco.groupId} + ${alfresco.bomDependencyArtifactId} + ${alfresco.platform.version} + pom + import + + ``` 5. The `maven-resources-plugin` needs the outputDirectory adjusted. Change: