From 89d4d3fd9a7a749ae39039fe86cd4c0015e3ed69 Mon Sep 17 00:00:00 2001
From: Michael Wallach <michael.wallach@alfresco.com>
Date: Wed, 3 Jun 2020 10:34:14 -0400
Subject: [PATCH] Added section 'another option for installing 3rd Party AMPs'

---
 docs/advanced-topics/amps.md | 62 ++++++++++++++++++++++++++++++++++++
 1 file changed, 62 insertions(+)

diff --git a/docs/advanced-topics/amps.md b/docs/advanced-topics/amps.md
index 13c87b16..521042c7 100644
--- a/docs/advanced-topics/amps.md
+++ b/docs/advanced-topics/amps.md
@@ -169,6 +169,68 @@ Here is an example of how to install Florian Maul's Javascript Console.
 </project>
 ```
 
+Another option for installing 3rd party AMPs to the projects is to have the amps local to the project. In this approach the amp file, the amp local to the project will be copied and applied from the Docker file. To use local amp you need to:
+    1. Modify the <project>-platform-docker/pom.xml
+    2. Copy the amp file into <project>-platform-docker/src/main/docker
+
+
+in the build element of ./workshop-sdk4-platform-docker/pom.xml,
+exclude *.amp in the copy-and-filter-docker-resources execution step:
+```
+                <artifactId>maven-resources-plugin</artifactId>
+                <executions>
+                    <execution>
+                        <id>copy-and-filter-docker-resources</id>
+                        <phase>validate</phase>
+                        <goals>
+                            <goal>copy-resources</goal>
+                        </goals>
+                        <configuration>
+                            <outputDirectory>${project.build.directory}</outputDirectory>
+                            <resources>
+                                <resource>
+                                    <directory>src/main/docker</directory>
+                                    <filtering>true</filtering>
+                                    <excludes>
+                                        <exclude>**/*.jar</exclude>
+                                        <exclude>**/*.so</exclude>
+                                        <exclude>**/*.gz</exclude>
+                                        <exclude>**/*.amp</exclude>            
+                                    </excludes>
+                                </resource>
+                            </resources>
+                        </configuration>
+                    </execution>
+```
+
+include *.amp in the copy-and-filter-docker-resources-non-filtered
+
+```
+                    <execution>
+                        <id>copy-and-filter-docker-resources-non-filtered</id>
+                        <phase>validate</phase>
+                        <goals>
+                            <goal>copy-resources</goal>
+                        </goals>
+                        <configuration>
+                            <outputDirectory>${project.build.directory}</outputDirectory>
+                            <resources>
+                                <resource>
+                                    <directory>src/main/docker</directory>
+                                    <filtering>false</filtering>
+                                    <includes>
+                                        <include>**/*.jar</include>
+                                        <include>**/*.so</include>
+                                        <include>**/*.gz</include>
+                                        <include>**/*.amp</include>
+                                    </includes>
+                                </resource>
+                            </resources>
+                        </configuration>
+                    </execution>
+```
+
+
 ## Controlling the order AMPs are applied
 
 Under some specific circumstances it is necessary to apply different AMPs in a development project in a precise order. The default configuration of the