aboutsummaryrefslogtreecommitdiffstats
path: root/aspectjmatcher
diff options
context:
space:
mode:
authorAlexander Kriegisch <Alexander@Kriegisch.name>2021-03-11 23:13:06 +0700
committerAlexander Kriegisch <Alexander@Kriegisch.name>2021-03-11 23:22:26 +0700
commitee5274fa7e0f82f6f840346aa969f618682dfdba (patch)
tree85a6e2537ac3c9280fef3949c3d613888230a77f /aspectjmatcher
parent021ad3e375d1fe124906e25dbbeb7bf05874097b (diff)
downloadaspectj-ee5274fa7e0f82f6f840346aa969f618682dfdba.tar.gz
aspectj-ee5274fa7e0f82f6f840346aa969f618682dfdba.zip
Set maven-assembly-plugin version 3.1.1 explicitly for each POM module
Background: There are CI tests failing because the version is not taken from the parent POM, even if set in the 'pluginManagement' section. Instead, it is resolved via the Maven Super POM, e.g. 2.2-beta-5, see: https://maven.apache.org/ref/3.6.3/maven-model-builder/super-pom.html That assembly plugin version in turn requires plexus-archiver 1.0-alpha-12. The latter cannot be downloaded from Maven Central, leading to the problems seen during builds. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
Diffstat (limited to 'aspectjmatcher')
-rw-r--r--aspectjmatcher/pom.xml11
1 files changed, 8 insertions, 3 deletions
diff --git a/aspectjmatcher/pom.xml b/aspectjmatcher/pom.xml
index 296504a0e..ce975e743 100644
--- a/aspectjmatcher/pom.xml
+++ b/aspectjmatcher/pom.xml
@@ -24,12 +24,12 @@
<executions>
<execution>
<id>test-jar</id>
- <phase></phase>
+ <phase>none</phase>
</execution>
</executions>
</plugin>
-
-
+
+
<!--
<plugin>
<groupId>org.apache.maven.plugins</groupId>
@@ -57,6 +57,11 @@
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
+ <!--
+ Set version manually in order to override version from super POM, e.g. 2.2-beta-5 from
+ https://maven.apache.org/ref/3.6.3/maven-model-builder/super-pom
+ -->
+ <version>3.1.1</version>
<executions>
<execution>
<id>aspectjmatcher-assembly</id>