Fix plugin related issues 05/141505/2
authorFiete Ostkamp <Fiete.Ostkamp@telekom.de>
Wed, 9 Jul 2025 08:59:19 +0000 (10:59 +0200)
committerFiete Ostkamp <Fiete.Ostkamp@telekom.de>
Wed, 9 Jul 2025 09:17:32 +0000 (11:17 +0200)
- update groovy-maven-plugin (2.0 -> 2.1.1) to fix warning that
  appears in Java 11+. In the future we should switch to the
  gmavenplus plugin
- exclude csar files from being eligible for filtering by the
  maven-resources-plugin in the asdc-controller module.
  This fixes an IndexOutputBounds exception that otherwise occurs
- bind the maven-dependency-plugin:unpack execution to the prepare-package
  phase to only execute it when the Docker images are build

Issue-ID: SO-4201
Change-Id: I339661406a4bce06e59ff5589977688c9d41f459
Signed-off-by: Fiete Ostkamp <Fiete.Ostkamp@telekom.de>
asdc-controller/pom.xml
pom.xml

index 262f578..6bc09b4 100644 (file)
             </lifecycleMappingMetadata>
           </configuration>
         </plugin>
+        <plugin>
+          <groupId>org.apache.maven.plugins</groupId>
+          <artifactId>maven-resources-plugin</artifactId>
+          <configuration>
+            <nonFilteredFileExtensions>
+              <nonFilteredFileExtension>csar</nonFilteredFileExtension>
+            </nonFilteredFileExtensions>
+          </configuration>
+        </plugin>
       </plugins>
     </pluginManagement>
     <plugins>
diff --git a/pom.xml b/pom.xml
index f51fd3a..6b89104 100644 (file)
--- a/pom.xml
+++ b/pom.xml
       <plugin>
         <groupId>org.codehaus.gmaven</groupId>
         <artifactId>groovy-maven-plugin</artifactId>
-        <version>2.0</version>
+        <version>2.1.1</version>
         <executions>
           <!-- set absolute base path from super pom -->
           <execution>
           <executions>
             <execution>
               <id>extract-docker-file</id>
+              <phase>prepare-package</phase>
               <goals>
                 <goal>unpack</goal>
               </goals>