summaryrefslogtreecommitdiffstats
path: root/packages/docker/pom.xml
diff options
context:
space:
mode:
authorwaqas.ikram <waqas.ikram@est.tech>2021-02-10 15:55:37 +0000
committerwaqas.ikram <waqas.ikram@est.tech>2021-02-10 15:55:52 +0000
commit1f18566c5cfbf346309dec5ddf5d59c1f479467a (patch)
treeecb69a495334d9b77a9a54c7f2b556f7c056f40c /packages/docker/pom.xml
parent27649f4b7d14a3803f73752a645c70c87ca0b039 (diff)
Revert "Changing docker module packaging to JAR"
This reverts commit 40fc9d52b0ca2eaba6d1e30f846797e301dc885b. Reason for revert: it seems that docker module in SO is triggered by “docker” profile which is only triggered in so-maven-docker-* Jenkins job. Per my understanding these jobs are only used for creating docker images and I think relying on these jobs to create a docker JAR module will create unnecessary dependency. So I think option 3 is more feasible Change-Id: Ia64778afd8fe4105ee8bf1a2f45a4d5674601289 Issue-ID: SO-3473 Signed-off-by: waqas.ikram <waqas.ikram@est.tech>
Diffstat (limited to 'packages/docker/pom.xml')
-rw-r--r--packages/docker/pom.xml7
1 files changed, 1 insertions, 6 deletions
diff --git a/packages/docker/pom.xml b/packages/docker/pom.xml
index 1f26238864..abf2c8a634 100644
--- a/packages/docker/pom.xml
+++ b/packages/docker/pom.xml
@@ -9,7 +9,7 @@
<version>1.7.1-SNAPSHOT</version>
</parent>
- <packaging>jar</packaging>
+ <packaging>pom</packaging>
<artifactId>docker</artifactId>
<name>Docker Images</name>
<description>Docker Images</description>
@@ -29,11 +29,6 @@
<build>
<finalName>${project.artifactId}-${project.version}</finalName>
- <resources>
- <resource>
- <directory>src/main/docker</directory>
- </resource>
- </resources>
<plugins>
<plugin>
<groupId>org.codehaus.groovy.maven</groupId>