Details
-
Task
-
Resolution: Won't Do
-
L3 - Default
-
None
-
None
Description
AT:
- custom engine plugin artifacts are deployed to nexus in the `Deploy` step of the master build
Notes:
As there are no direct maven depencies the plugins are not part of the reactor ofthe deploy build. However there are modules that depend on their availability (e.g. the upgrade-optimize-data test module):
+ mvn deploy -Dskip.fe.build -DskipTests -Dskip.docker -pl distro -am -s settings.xml -B --fail-at-end -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn
Picked up JAVA_TOOL_OPTIONS: -XX:+UnlockExperimentalVMOptions
-XX:+UseCGroupMemoryLimitForHeap
-XX:MaxRAMFraction=4
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 9 modules...
[INFO] Installing Nexus Staging features:
[INFO] ... total of 9 executions of maven-deploy-plugin replaced with nexus-staging-maven-plugin
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] parent [pom]
[INFO] client [pom]
[INFO] util [pom]
[INFO] optimize-commons [jar]
[INFO] plugin [jar]
[INFO] optimize-backend [jar]
[INFO] optimize-reimport-preparation [jar]
[INFO] upgrade-optimize [jar]
[INFO] camunda-optimize [pom]