From 116226c102f8f8aced8b1a920e9a7d306401eb4d Mon Sep 17 00:00:00 2001
From: gjoranv <gv@yahooinc.com>
Date: Wed, 12 Jul 2023 11:40:24 +0200
Subject: Add container-test to test classpath

- Not sure if it's needed, but ensured unchanged test cp
---
 container-test/pom.xml | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

(limited to 'container-test')

diff --git a/container-test/pom.xml b/container-test/pom.xml
index a0358e79a8f..a22d0b59ace 100644
--- a/container-test/pom.xml
+++ b/container-test/pom.xml
@@ -32,12 +32,18 @@
         </exclusion>
       </exclusions>
     </dependency>
-    <!-- Excluded above, and re-declared here, to work around a presumed Maven bug which otherwise puts this
-         in provided scope when container-test is declared before, and together with, the container artifact -->
     <dependency>
+      <!-- Excluded above, and re-declared here, to work around a presumed Maven bug which otherwise puts this
+           in provided scope when container-test is declared before, and together with, the container artifact -->
       <groupId>org.bouncycastle</groupId>
       <artifactId>bcpkix-jdk18on</artifactId>
     </dependency>
+    <dependency>
+      <!-- Not sure if this is needed, added after removing it from 'container' to ensure unchanged test classpath-->
+      <groupId>com.yahoo.vespa</groupId>
+      <artifactId>vespaclient-container-plugin</artifactId>
+      <version>${project.version}</version>
+    </dependency>
 
     <!-- All dependencies that should be visible in test classpath, but not compile classpath,
          for user projects must be added in compile scope here. These dependencies are explicitly excluded
-- 
cgit v1.2.3