mirror of
https://github.com/Alfresco/alfresco-sdk.git
synced 2025-07-31 17:39:14 +00:00
Renaming modules in AIO archetype:
[artifactId]-plaform-jar -> [artifactId]-platform [artifactId]-share-jar -> [artifactId]-share integration-tests -> [artifactId]-integration-tests
This commit is contained in:
Piotr Anders
@@ -10,9 +10,9 @@
|
||||
</requiredProperty>
|
||||
</requiredProperties>
|
||||
<modules>
|
||||
<module id="${rootArtifactId}-platform-jar"
|
||||
name="${rootArtifactId}-platform-jar"
|
||||
dir="__rootArtifactId__-platform-jar">
|
||||
<module id="${rootArtifactId}-platform"
|
||||
name="${rootArtifactId}-platform"
|
||||
dir="__rootArtifactId__-platform">
|
||||
<fileSets>
|
||||
<fileSet filtered="false" packaged="false" encoding="UTF-8">
|
||||
<directory>src/main/assembly</directory>
|
||||
@@ -50,9 +50,9 @@
|
||||
</fileSets>
|
||||
</module>
|
||||
|
||||
<module id="${rootArtifactId}-share-jar"
|
||||
name="${rootArtifactId}-share-jar"
|
||||
dir="__rootArtifactId__-share-jar">
|
||||
<module id="${rootArtifactId}-share"
|
||||
name="${rootArtifactId}-share"
|
||||
dir="__rootArtifactId__-share">
|
||||
<fileSets>
|
||||
<fileSet filtered="false" packaged="false" encoding="UTF-8">
|
||||
<directory>src/main/assembly</directory>
|
||||
@@ -97,7 +97,9 @@
|
||||
</fileSets>
|
||||
</module>
|
||||
|
||||
<module id="integration-tests" name="integration-tests" dir="integration-tests">
|
||||
<module id="${rootArtifactId}-integration-tests"
|
||||
name="${rootArtifactId}-integration-tests"
|
||||
dir="__rootArtifactId__-integration-tests">
|
||||
<fileSets>
|
||||
<fileSet filtered="true" packaged="true" encoding="UTF-8">
|
||||
<directory>src/main/java</directory>
|
||||
|
||||
@@ -22,7 +22,7 @@
|
||||
that is generated for the AIO project -->
|
||||
<dependency>
|
||||
<groupId>${groupId}</groupId>
|
||||
<artifactId>${rootArtifactId}-platform-jar</artifactId>
|
||||
<artifactId>${rootArtifactId}-platform</artifactId>
|
||||
<version>${version}</version>
|
||||
<scope>test</scope>
|
||||
</dependency>
|
||||
@@ -19,7 +19,7 @@
|
||||
<dependencies>
|
||||
<dependency>
|
||||
<groupId>${groupId}</groupId>
|
||||
<artifactId>${rootArtifactId}-platform-jar</artifactId>
|
||||
<artifactId>${rootArtifactId}-platform</artifactId>
|
||||
<version>${version}</version>
|
||||
</dependency>
|
||||
</dependencies>
|
||||
@@ -50,7 +50,7 @@
|
||||
</artifactItem>
|
||||
<artifactItem>
|
||||
<groupId>${groupId}</groupId>
|
||||
<artifactId>integration-tests</artifactId>
|
||||
<artifactId>${rootArtifactId}-integration-tests</artifactId>
|
||||
<version>${version}</version>
|
||||
<classifier>tests</classifier>
|
||||
<overWrite>false</overWrite>
|
||||
|
||||
@@ -26,12 +26,12 @@ disabledPlugins=Hibernate,Spring
|
||||
#
|
||||
# Load web application resources (such as HTML, JSP, CSS, ...) from this directory prior to default processing.
|
||||
# Use this setting to set to serve resources from source directory directly (e.g. src/main/webapp).
|
||||
extraWebappContext=/usr/local/tomcat/hotswap-agent/${rootArtifactId}-platform-jar/target/classes/META-INF/resources;
|
||||
extraWebappContext=/usr/local/tomcat/hotswap-agent/${rootArtifactId}-platform/target/classes/META-INF/resources;
|
||||
|
||||
# Load static web resources from different directory.
|
||||
#
|
||||
# This setting is dependent on application server plugin(Jetty, Tomcat, JBoss, ...)
|
||||
webappDir=/usr/local/tomcat/hotswap-agent/${rootArtifactId}-platform-jar/target/classes/META-INF/resources;
|
||||
webappDir=/usr/local/tomcat/hotswap-agent/${rootArtifactId}-platform/target/classes/META-INF/resources;
|
||||
|
||||
# Watch for changes in a directory (resources only).
|
||||
#
|
||||
|
||||
@@ -10,7 +10,7 @@
|
||||
<platformModules>
|
||||
<moduleDependency>
|
||||
<groupId>${project.groupId}</groupId>
|
||||
<artifactId>some-platform-jar</artifactId>
|
||||
<artifactId>some-platform</artifactId>
|
||||
<version>${project.version}</version>
|
||||
<type>amp</type>
|
||||
</moduleDependency>
|
||||
@@ -10,7 +10,7 @@ any existing web resources in the Alfresco.WAR.
|
||||
`
|
||||
<moduleDependency>
|
||||
<groupId>${project.groupId}</groupId>
|
||||
<artifactId>some-platform-jar</artifactId>
|
||||
<artifactId>some-platform</artifactId>
|
||||
<version>${project.version}</version>
|
||||
<type>amp</type>
|
||||
</moduleDependency>
|
||||
@@ -19,7 +19,7 @@
|
||||
<dependencies>
|
||||
<dependency>
|
||||
<groupId>${groupId}</groupId>
|
||||
<artifactId>${rootArtifactId}-share-jar</artifactId>
|
||||
<artifactId>${rootArtifactId}-share</artifactId>
|
||||
<version>${version}</version>
|
||||
</dependency>
|
||||
</dependencies>
|
||||
|
||||
@@ -27,12 +27,12 @@ disabledPlugins=Hibernate,Spring
|
||||
#
|
||||
# Load web application resources (such as HTML, JSP, CSS, ...) from this directory prior to default processing.
|
||||
# Use this setting to set to serve resources from source directory directly (e.g. src/main/webapp).
|
||||
extraWebappContext=/usr/local/tomcat/hotswap-agent/${rootArtifactId}-share-jar/target/classes/META-INF/resources;
|
||||
extraWebappContext=/usr/local/tomcat/hotswap-agent/${rootArtifactId}-share/target/classes/META-INF/resources;
|
||||
|
||||
# Load static web resources from different directory.
|
||||
#
|
||||
# This setting is dependent on application server plugin(Jetty, Tomcat, JBoss, ...)
|
||||
webappDir=/usr/local/tomcat/hotswap-agent/${rootArtifactId}-share-jar/target/classes/META-INF/resources;
|
||||
webappDir=/usr/local/tomcat/hotswap-agent/${rootArtifactId}-share/target/classes/META-INF/resources;
|
||||
|
||||
# Watch for changes in a directory (resources only).
|
||||
#
|
||||
|
||||
@@ -10,7 +10,7 @@
|
||||
<shareModules>
|
||||
<moduleDependency>
|
||||
<groupId>${project.groupId}</groupId>
|
||||
<artifactId>some-share-jar</artifactId>
|
||||
<artifactId>some-share</artifactId>
|
||||
<version>${project.version}</version>
|
||||
<type>amp</type>
|
||||
</moduleDependency>
|
||||
@@ -10,7 +10,7 @@ any existing web resources in the Share.WAR.
|
||||
`
|
||||
<moduleDependency>
|
||||
<groupId>${project.groupId}</groupId>
|
||||
<artifactId>some-share-jar</artifactId>
|
||||
<artifactId>some-share</artifactId>
|
||||
<version>${project.version}</version>
|
||||
<type>amp</type>
|
||||
</moduleDependency>
|
||||
@@ -93,12 +93,12 @@ EXIT /B 0
|
||||
:build_share
|
||||
docker-compose -f "%COMPOSE_FILE_PATH%" kill ${rootArtifactId}-share
|
||||
docker-compose -f "%COMPOSE_FILE_PATH%" rm -f ${rootArtifactId}-share
|
||||
call %MVN_EXEC% clean install -DskipTests -pl ${rootArtifactId}-share-jar
|
||||
call %MVN_EXEC% clean install -DskipTests -pl ${rootArtifactId}-share
|
||||
EXIT /B 0
|
||||
:build_acs
|
||||
docker-compose -f "%COMPOSE_FILE_PATH%" kill ${rootArtifactId}-acs
|
||||
docker-compose -f "%COMPOSE_FILE_PATH%" rm -f ${rootArtifactId}-acs
|
||||
call %MVN_EXEC% clean install -DskipTests -pl ${rootArtifactId}-platform-jar
|
||||
call %MVN_EXEC% clean install -DskipTests -pl ${rootArtifactId}-platform
|
||||
EXIT /B 0
|
||||
:tail
|
||||
docker-compose -f "%COMPOSE_FILE_PATH%" logs -f
|
||||
@@ -107,7 +107,7 @@ EXIT /B 0
|
||||
docker-compose -f "%COMPOSE_FILE_PATH%" logs --tail="all"
|
||||
EXIT /B 0
|
||||
:test
|
||||
call %MVN_EXEC% verify -pl integration-tests
|
||||
call %MVN_EXEC% verify -pl ${rootArtifactId}-integration-tests
|
||||
EXIT /B 0
|
||||
:purge
|
||||
docker volume rm -f ${rootArtifactId}-acs-volume
|
||||
|
||||
@@ -43,13 +43,13 @@ build() {
|
||||
build_share() {
|
||||
docker-compose -f ${symbol_dollar}COMPOSE_FILE_PATH kill ${rootArtifactId}-share
|
||||
yes | docker-compose -f ${symbol_dollar}COMPOSE_FILE_PATH rm -f ${rootArtifactId}-share
|
||||
${symbol_dollar}MVN_EXEC clean install -DskipTests=true -pl ${rootArtifactId}-share-jar,${rootArtifactId}-share-docker
|
||||
${symbol_dollar}MVN_EXEC clean install -DskipTests=true -pl ${rootArtifactId}-share,${rootArtifactId}-share-docker
|
||||
}
|
||||
|
||||
build_acs() {
|
||||
docker-compose -f ${symbol_dollar}COMPOSE_FILE_PATH kill ${rootArtifactId}-acs
|
||||
yes | docker-compose -f ${symbol_dollar}COMPOSE_FILE_PATH rm -f ${rootArtifactId}-acs
|
||||
${symbol_dollar}MVN_EXEC clean install -DskipTests=true -pl ${rootArtifactId}-platform-jar,${rootArtifactId}-platform-docker
|
||||
${symbol_dollar}MVN_EXEC clean install -DskipTests=true -pl ${rootArtifactId}-platform,${rootArtifactId}-platform-docker
|
||||
}
|
||||
|
||||
tail() {
|
||||
@@ -61,7 +61,7 @@ tail_all() {
|
||||
}
|
||||
|
||||
test() {
|
||||
${symbol_dollar}MVN_EXEC verify -pl integration-tests
|
||||
${symbol_dollar}MVN_EXEC verify -pl ${rootArtifactId}-integration-tests
|
||||
}
|
||||
|
||||
case "${symbol_dollar}1" in
|
||||
|
||||
@@ -66,7 +66,7 @@ do is modify the `pom.xml` file of the corresponding docker module / project in
|
||||
<dependencies>
|
||||
<dependency>
|
||||
<groupId>org.alfresco</groupId>
|
||||
<artifactId>sample-module-platform-jar</artifactId>
|
||||
<artifactId>sample-module-platform</artifactId>
|
||||
<version>1.0-SNAPSHOT</version>
|
||||
<type>amp</type>
|
||||
</dependency>
|
||||
@@ -91,7 +91,7 @@ do is modify the `pom.xml` file of the corresponding docker module / project in
|
||||
<artifactItems>
|
||||
<artifactItem>
|
||||
<groupId>org.alfresco</groupId>
|
||||
<artifactId>sample-module-platform-jar</artifactId>
|
||||
<artifactId>sample-module-platform</artifactId>
|
||||
<version>1.0-SNAPSHOT</version>
|
||||
<overWrite>false</overWrite>
|
||||
<outputDirectory>${project.build.directory}/extensions</outputDirectory>
|
||||
@@ -180,7 +180,7 @@ Here is an example of how to install Florian Maul's Javascript Console.
|
||||
<dependencies>
|
||||
<dependency>
|
||||
<groupId>org.alfresco</groupId>
|
||||
<artifactId>sample-module-platform-jar</artifactId>
|
||||
<artifactId>sample-module-platform</artifactId>
|
||||
<version>1.0-SNAPSHOT</version>
|
||||
</dependency>
|
||||
|
||||
|
||||
@@ -100,8 +100,8 @@ the hot reloading tools fail):
|
||||
- "${acs.debug.port}:8888"
|
||||
volumes:
|
||||
- alf-acs-volume:/usr/local/tomcat/alf_data
|
||||
- ../../../sample-project-platform-jar/target/classes:/usr/local/tomcat/hotswap-agent/sample-project-platform-jar/target/classes
|
||||
- ../../../integration-tests/target/test-classes:/usr/local/tomcat/hotswap-agent/integration-tests/target/test-classes
|
||||
- ../../../sample-project-platform/target/classes:/usr/local/tomcat/hotswap-agent/sample-project-platform/target/classes
|
||||
- ../../../sample-project-integration-tests/target/test-classes:/usr/local/tomcat/hotswap-agent/sample-project-integration-tests/target/test-classes
|
||||
...
|
||||
```
|
||||
|
||||
@@ -177,8 +177,8 @@ the hot reloading tools fail):
|
||||
- "${acs.debug.port}:8888"
|
||||
volumes:
|
||||
- alf-acs-volume:/usr/local/tomcat/alf_data
|
||||
- ../../../sample-project-platform-jar/target/classes:/usr/local/tomcat/hotswap-agent/sample-project-platform-jar/target/classes
|
||||
- ../../../integration-tests/target/test-classes:/usr/local/tomcat/hotswap-agent/integration-tests/target/test-classes
|
||||
- ../../../sample-project-platform/target/classes:/usr/local/tomcat/hotswap-agent/sample-project-platform/target/classes
|
||||
- ../../../sample-project-integration-tests/target/test-classes:/usr/local/tomcat/hotswap-agent/sample-project-integration-tests/target/test-classes
|
||||
...
|
||||
```
|
||||
|
||||
@@ -268,7 +268,7 @@ model.put(“fromJava”,”HelloFromMe”);
|
||||
A number of log messages appear in the Alfresco project terminal, for example:
|
||||
|
||||
```
|
||||
HOTSWAP AGENT: 14:10:29.887 DEBUG (org.hotswap.agent.watch.nio.WatcherNIO2) - Watch event 'ENTRY_MODIFY' on '/usr/local/tomcat/hotswap-agent/sample-project-platform-jar/target/classes/com/example/platformsample/HelloWorldWebScript.class' --> HelloWorldWebScript.class
|
||||
HOTSWAP AGENT: 14:10:29.887 DEBUG (org.hotswap.agent.watch.nio.WatcherNIO2) - Watch event 'ENTRY_MODIFY' on '/usr/local/tomcat/hotswap-agent/sample-project-platform/target/classes/com/example/platformsample/HelloWorldWebScript.class' --> HelloWorldWebScript.class
|
||||
HOTSWAP AGENT: 14:10:30.319 DEBUG (org.hotswap.agent.command.impl.SchedulerImpl) - Executing pluginManager.hotswap([class com.example.platformsample.HelloWorldWebScript])
|
||||
HOTSWAP AGENT: 14:10:30.368 RELOAD (org.hotswap.agent.config.PluginManager) - Reloading classes [com.example.platformsample.HelloWorldWebScript] (autoHotswap)
|
||||
HOTSWAP AGENT: 14:10:30.387 DEBUG (org.hotswap.agent.plugin.jdk.JdkPlugin) - Flushing com.example.platformsample.HelloWorldWebScript from introspector
|
||||
|
||||
@@ -42,7 +42,7 @@ _Note that a license is required. In this step you will be able to request a tri
|
||||
|
||||
|
||||
8. Select `Help > JRebel > Configuration > Projects` and select the checkbox to enable JRebel and the remote server support for required projects (the complete
|
||||
project in case of the Platform Jar archetype or the `PROJECT_ARTIFACT_ID-platform-jar` and `integration-tests` modules in case of the All-In-One archetype).
|
||||
project in case of the Platform Jar archetype or the `PROJECT_ARTIFACT_ID-platform` and `PROJECT_ARTEFACTID-integration-tests` modules in case of the All-In-One archetype).
|
||||
|
||||
|
||||
|
||||
@@ -65,7 +65,7 @@ _Note that a license is required. In this step you will be able to request a tri
|
||||
|
||||
|
||||
8. Open the JRebel Panel and select the checkbox to enable JRebel and the remote server support for required projects (the complete project in case of the
|
||||
Platform Jar archetype or the `PROJECT_ARTIFACT_ID-platform-jar` and `integration-tests` modules in case of the All-In-One archetype).
|
||||
Platform Jar archetype or the `PROJECT_ARTIFACT_ID-platform` and `PROJECT_ARTEFACTID-integration-tests` modules in case of the All-In-One archetype).
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -67,7 +67,7 @@ module using the `maven-dependency-plugin`. The configuration is done in the fil
|
||||
</artifactItem>
|
||||
<artifactItem>
|
||||
<groupId>org.alfresco</groupId>
|
||||
<artifactId>integration-tests</artifactId>
|
||||
<artifactId>PROJECT_ARTEFACTID-integration-tests</artifactId>
|
||||
<version>1.0-SNAPSHOT</version>
|
||||
<classifier>tests</classifier>
|
||||
<overWrite>false</overWrite>
|
||||
@@ -149,7 +149,7 @@ the environment.
|
||||
|
||||
This integration test verifies the existence of the `DemoComponent` component deployed in the Alfresco Content Services instance. You can find the definition
|
||||
of the `DemoComponent` as a custom component of a project created with the All-In-One archetype. For more details, see the class definition in
|
||||
`PROJECT_ARTEFACTID-platform-jar/src/main/java/com/example/platformsample/DemoComponent.java`.
|
||||
`PROJECT_ARTEFACTID-platform/src/main/java/com/example/platformsample/DemoComponent.java`.
|
||||
|
||||
The integration test retrieves the `DemoComponent` bean from the Alfresco Content Services instance (see `testGetCompanyHome()`), and requests the Company
|
||||
Home component. In addition, some Java assertions check if Company Home is identified correctly and has seven children stored in it.
|
||||
|
||||
@@ -172,9 +172,9 @@ If everything has been configured correctly, you should see something similar to
|
||||
[INFO] Parameter: groupId, Value: com.acme
|
||||
[INFO] Parameter: artifactId, Value: my-all-in-one
|
||||
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
|
||||
[INFO] Parent element not overwritten in /Users/Alfresco/my-all-in-one/my-all-in-one-platform-jar/pom.xml
|
||||
[INFO] Parent element not overwritten in /Users/Alfresco/my-all-in-one/my-all-in-one-share-jar/pom.xml
|
||||
[INFO] Parent element not overwritten in /Users/Alfresco/my-all-in-one/integration-tests/pom.xml
|
||||
[INFO] Parent element not overwritten in /Users/Alfresco/my-all-in-one/my-all-in-one-platform/pom.xml
|
||||
[INFO] Parent element not overwritten in /Users/Alfresco/my-all-in-one/my-all-in-one-share/pom.xml
|
||||
[INFO] Parent element not overwritten in /Users/Alfresco/my-all-in-one/my-all-in-one-integration-tests/pom.xml
|
||||
[INFO] Parent element not overwritten in /Users/Alfresco/my-all-in-one/my-all-in-one-platform-docker/pom.xml
|
||||
[INFO] Parent element not overwritten in /Users/Alfresco/my-all-in-one/my-all-in-one-share-docker/pom.xml
|
||||
[INFO] Executing META-INF/archetype-post-generate.groovy post-generation script
|
||||
|
||||
@@ -20,7 +20,7 @@ The ACS container is not starting properly and it is showing Java compatibility
|
||||
```
|
||||
org.springframework.beans.factory.CannotLoadBeanClassException:
|
||||
Error loading class [com.example.platformsample.Demo] for bean with name 'com.example.Demo' defined in class path resource
|
||||
[alfresco/module/sample-project-platform-jar/context/service-context.xml]:
|
||||
[alfresco/module/sample-project-platform/context/service-context.xml]:
|
||||
problem with class file or dependent class; nested exception is java.lang.UnsupportedClassVersionError:
|
||||
com/example/platformsample/Demo has been compiled by a more recent version of the Java Runtime (class file version 55.0),
|
||||
this version of the Java Runtime only recognizes class file versions up to 52.0 (unable to load class [com.example.platformsample.Demo])
|
||||
|
||||
@@ -20,7 +20,7 @@ my-all-in-one-project
|
||||
├── run.sh
|
||||
├── docker
|
||||
| └── docker-compose.yml
|
||||
├── integration-tests
|
||||
├── my-all-in-one-project-integration-tests
|
||||
| ├── pom.xml
|
||||
│ └── src
|
||||
│ ├── main
|
||||
@@ -47,7 +47,7 @@ my-all-in-one-project
|
||||
│ ├── hotswap-agent.properties
|
||||
│ └── license
|
||||
│ └── README.md
|
||||
├── my-all-in-one-project-platform-jar
|
||||
├── my-all-in-one-project-platform
|
||||
│ ├── pom.xml
|
||||
│ └── src
|
||||
│ ├── main
|
||||
@@ -74,7 +74,7 @@ my-all-in-one-project
|
||||
│ │ │ │ ├── helloworld.get.html.ftl
|
||||
│ │ │ │ └── helloworld.get.js
|
||||
│ │ │ └── module
|
||||
│ │ │ └── my-all-in-one-project-platform-jar
|
||||
│ │ │ └── my-all-in-one-project-platform
|
||||
│ │ │ ├── alfresco-global.properties
|
||||
│ │ │ ├── context
|
||||
│ │ │ │ ├── bootstrap-context.xml
|
||||
@@ -107,7 +107,7 @@ my-all-in-one-project
|
||||
│ ├── hotswap-agent.properties
|
||||
│ ├── log4j.properties
|
||||
│ └── share-config-custom.xml
|
||||
└── my-all-in-one-project-share-jar
|
||||
└── my-all-in-one-project-share
|
||||
├── pom.xml
|
||||
└── src
|
||||
├── main
|
||||
@@ -120,15 +120,15 @@ my-all-in-one-project
|
||||
│ │ └── com
|
||||
│ ├── alfresco
|
||||
│ │ ├── module
|
||||
│ │ │ └── my-all-in-one-project-share-jar
|
||||
│ │ │ └── my-all-in-one-project-share
|
||||
│ │ │ └── module.properties
|
||||
│ │ └── web-extension
|
||||
│ │ ├── messages
|
||||
│ │ │ └── my-all-in-one-project-share-jar.properties
|
||||
│ │ ├── my-all-in-one-project-share-jar-slingshot-application-context.xml
|
||||
│ │ │ └── my-all-in-one-project-share.properties
|
||||
│ │ ├── my-all-in-one-project-share-slingshot-application-context.xml
|
||||
│ │ ├── site-data
|
||||
│ │ │ └── extensions
|
||||
│ │ │ └── my-all-in-one-project-share-jar-example-widgets.xml
|
||||
│ │ │ └── my-all-in-one-project-share-example-widgets.xml
|
||||
│ │ └── site-webscripts
|
||||
│ │ ├── com
|
||||
│ │ │ └── example
|
||||
@@ -141,7 +141,7 @@ my-all-in-one-project
|
||||
│ │ └── README.md
|
||||
│ └── META-INF
|
||||
│ ├── resources
|
||||
│ │ └── my-all-in-one-project-share-jar
|
||||
│ │ └── my-all-in-one-project-share
|
||||
│ │ └── js
|
||||
│ │ └── tutorials
|
||||
│ │ └── widgets
|
||||
@@ -165,14 +165,14 @@ From a high level standpoint, we can describe the content of the project as foll
|
||||
hosting service like GitHub, SVN, CVS, etc.
|
||||
* The files stored into the root of the project are mainly related to actions and commands (running, debugging, etc.), technical configuration (`pom.xml`),
|
||||
and documentation (`README.md`).
|
||||
* `integration-tests` contains a sub-project entirely dedicated to integration tests.
|
||||
* `my-all-in-one-project-integration-tests` (typically named `<artefactId-integration-tests>`) contains a sub-project entirely dedicated to integration tests.
|
||||
* `my-all-in-one-project-platform-docker` (typically named `<artefactId-platform-docker>`) contains a sub-project dedicated to the configuration of a custom
|
||||
Docker image with the Alfresco Content Services Repository and the customization module `my-all-in-one-project-platform-jar` installed.
|
||||
* `my-all-in-one-project-platform-jar` (typically named `<artefactId-platform-jar>`) contains a sub-project entirely dedicated to the customization of the
|
||||
Docker image with the Alfresco Content Services Repository and the customization module `my-all-in-one-project-platform` installed.
|
||||
* `my-all-in-one-project-platform` (typically named `<artefactId-platform>`) contains a sub-project entirely dedicated to the customization of the
|
||||
Alfresco Content Services Repository.
|
||||
* `my-all-in-one-project-share-docker` (typically named `<artefactId-share-docker>`) contains a sub-project dedicated to the configuration of a custom
|
||||
Docker image with the Alfresco Share client and the customization module `my-all-in-one-project-share-jar` installed.
|
||||
* `my-all-in-one-project-share-jar` (typically named `<artefactId-share-jar>`) contains a sub-project entirely dedicated to the customization of the
|
||||
Docker image with the Alfresco Share client and the customization module `my-all-in-one-project-share` installed.
|
||||
* `my-all-in-one-project-share` (typically named `<artefactId-share>`) contains a sub-project entirely dedicated to the customization of the
|
||||
Alfresco Share client.
|
||||
|
||||
After this brief introduction of the All-In-One project, let’s focus on the content of the folders.
|
||||
@@ -187,9 +187,9 @@ File | Description
|
||||
`pom.xml` | This XML file contains information about the project and configuration details used by Apache Maven to build the project. You can define all the configurations, parameters, and settings in this file for projects as well as for sub-projects.
|
||||
`README.md` | File in Markdown format containing the documentation for the project.
|
||||
|
||||
## my-all-in-one-project-platform-jar
|
||||
## my-all-in-one-project-platform
|
||||
|
||||
Below is a description of the content in the `my-all-in-one-project-platform-jar` (typically named `<artefactId-platform-jar>`) sub-project. This sub-project
|
||||
Below is a description of the content in the `my-all-in-one-project-platform` (typically named `<artefactId-platform>`) sub-project. This sub-project
|
||||
contains the source code entirely dedicated to the customizing the Alfresco Content Services Repository.
|
||||
|
||||
Content | Description
|
||||
@@ -206,18 +206,18 @@ Content | Description
|
||||
|
||||
Below is a description of the content in the `my-all-in-one-project-platform-docker` (typically named `<artefactId-platform-docker>`) sub-project. This
|
||||
sub-project contains the resources required to define a custom Docker image with the Alfresco Content Services Repository and the customization module
|
||||
`my-all-in-one-project-platform-jar` installed.
|
||||
`my-all-in-one-project-platform` installed.
|
||||
|
||||
Content | Description
|
||||
--- | ---
|
||||
`pom.xml` | This XML file contains information about the project and configuration details used by Apache Maven to build the project. It adds the dependency to the `my-all-in-one-project-platform-jar` module and configures the `maven-dependency-plugin` to copy all the artifacts required in the Docker image into the folder `${project.build.directory}/extensions`.
|
||||
`pom.xml` | This XML file contains information about the project and configuration details used by Apache Maven to build the project. It adds the dependency to the `my-all-in-one-project-platform` module and configures the `maven-dependency-plugin` to copy all the artifacts required in the Docker image into the folder `${project.build.directory}/extensions`.
|
||||
`src/main/docker` | In this folder you can find everything that's needed to fully configure the custom ACS Docker image.
|
||||
`src/main/docker/Dockerfile` | This is the file that define the custom ACS Docker image. The default configuration installs all the existing JARs and AMPs under `${project.build.directory}/extensions` folder and adds custom configuration and license files.
|
||||
`src/main/docker/license` | This folder contains the licenses required for running an Enterprise project.
|
||||
|
||||
## my-all-in-one-project-share-jar
|
||||
## my-all-in-one-project-share
|
||||
|
||||
Below is a description of the content in the `my-all-in-one-project-share-jar` (typically named `<artefactId-share-jar>`) sub-project. This sub-project
|
||||
Below is a description of the content in the `my-all-in-one-project-share` (typically named `<artefactId-share>`) sub-project. This sub-project
|
||||
contains the source code entirely dedicated to the customizing the Alfresco Share client.
|
||||
|
||||
Content | Description
|
||||
@@ -235,17 +235,17 @@ Content | Description
|
||||
|
||||
Below is a description of the content in the `my-all-in-one-project-share-docker` (typically named `<artefactId-share-docker>`) sub-project. This
|
||||
sub-project contains the resources required to define a custom Docker image with the Alfresco Share Client and the customization module
|
||||
`my-all-in-one-project-share-jar` installed.
|
||||
`my-all-in-one-project-share` installed.
|
||||
|
||||
Content | Description
|
||||
--- | ---
|
||||
`pom.xml` | This XML file contains information about the project and configuration details used by Apache Maven to build the project. It adds the dependency to the `my-all-in-one-project-share-jar` module and configures the `maven-dependency-plugin` to copy all the artifacts required in the Docker image into the folder `${project.build.directory}/extensions`.
|
||||
`pom.xml` | This XML file contains information about the project and configuration details used by Apache Maven to build the project. It adds the dependency to the `my-all-in-one-project-share` module and configures the `maven-dependency-plugin` to copy all the artifacts required in the Docker image into the folder `${project.build.directory}/extensions`.
|
||||
`src/main/docker` | In this folder you can find everything that's needed to fully configure the custom Alfresco Share Docker image.
|
||||
`src/main/docker/Dockerfile` | This is the file that define the custom Alfresco Share Docker image. The default configuration installs all the existing JARs and AMPs under `${project.build.directory}/extensions` folder and adds custom configuration files.
|
||||
|
||||
## integration-tests
|
||||
## my-all-in-one-project-integration-tests
|
||||
|
||||
Below is a description of the content in the `integration-tests` sub-project. This sub-project contains all the source code and resources needed to run the integration tests.
|
||||
Below is a description of the content in the `my-all-in-one-project-integration-tests` (typically named `<artefactId-integration-tests>`) sub-project. This sub-project contains all the source code and resources needed to run the integration tests.
|
||||
|
||||
Content | Description
|
||||
--- | ---
|
||||
|
||||
Reference in New Issue
Block a user