You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by sl...@apache.org on 2026/09/27 19:09:07 UTC
(maven-executor) branch main updated (ac70d63 -> 108ed07)
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/maven-executor.git
from ac70d63 Build against Maven 4.0.0-rc-7
new 332efd5 Bump org.apache.maven:maven-parent from 49 to 50
new f285b7a Use inputExcludes for apache-rat 0.18
new ecd3890 Pin maven-compiler-plugin to 3.15.0
new 108ed07 Shorten the compiler plugin pin comment
The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
pom.xml | 49 +++++++++++++++++++++++++++----------------------
1 file changed, 27 insertions(+), 22 deletions(-)
(maven-executor) 01/04: Bump org.apache.maven:maven-parent from 49 to 50
Posted by sl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/maven-executor.git
commit 332efd5bb3ef829607130e9fe4d109764fa53c70
Author: dependabot[bot] <49...@users.noreply.github.com>
AuthorDate: Wed Sep 23 07:26:24 2026 +0000
Bump org.apache.maven:maven-parent from 49 to 50
Bumps [org.apache.maven:maven-parent](https://github.com/apache/maven-parent) from 49 to 50.
- [Release notes](https://github.com/apache/maven-parent/releases)
- [Commits](https://github.com/apache/maven-parent/commits)
---
updated-dependencies:
- dependency-name: org.apache.maven:maven-parent
dependency-version: '50'
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <su...@github.com>
---
pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pom.xml b/pom.xml
index 755579c..5fa2065 100644
--- a/pom.xml
+++ b/pom.xml
@@ -23,7 +23,7 @@
<parent>
<groupId>org.apache.maven</groupId>
<artifactId>maven-parent</artifactId>
- <version>49</version>
+ <version>50</version>
<relativePath />
</parent>
(maven-executor) 04/04: Shorten the compiler plugin pin comment
Posted by sl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/maven-executor.git
commit 108ed071f3f3f16838323839693608c83d627674
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Sat Sep 26 00:01:03 2026 +0200
Shorten the compiler plugin pin comment
---
pom.xml | 14 ++------------
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/pom.xml b/pom.xml
index 8486394..380733d 100644
--- a/pom.xml
+++ b/pom.xml
@@ -70,18 +70,8 @@
<project.build.outputTimestamp>2026-06-12T10:14:54Z</project.build.outputTimestamp>
<testTmpDir>${project.build.directory}/tmp</testTmpDir>
- <!--
- ! Pinned below the version maven-parent 50 (apache 40) manages. 3.16.0's stricter
- ! "recompile when dependencies change" check forces docker-exe's compile-java9 to
- ! rerun inside the site plugin's forked, compile-only javadoc:aggregate build, where
- ! reactor dependencies are still plain target/classes directories. module-info there
- ! only sees maven-executor's MR-JAR module descriptor once it is packaged as a real
- ! jar (META-INF/versions/9 is a jar-format concept), so the forked compile fails with
- ! "module not found: org.apache.maven.executor". 3.15.0's weaker staleness check
- ! instead reuses the classes already compiled during the preceding `verify`, where
- ! packaging happens before docker-exe compiles and the module is visible.
- ! Remove this pin only once that forked-compile module path resolution is fixed.
- -->
+ <!-- 3.16.0 recompiles docker-exe inside the site build, where the sibling's MR-JAR module-info
+ (META-INF/versions/9) is not visible from target/classes; a clean compile fails on 3.15.0 too. -->
<version.maven-compiler-plugin>3.15.0</version.maven-compiler-plugin>
<version.maven3>3.9.16</version.maven3>
<version.maven3resolver>1.9.27</version.maven3resolver>
(maven-executor) 03/04: Pin maven-compiler-plugin to 3.15.0
Posted by sl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/maven-executor.git
commit ecd3890f4d35f80871a2083e1a6d30420ef4e92b
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Fri Sep 25 21:34:12 2026 +0200
Pin maven-compiler-plugin to 3.15.0
maven-parent 50 (via apache 40) manages 3.16.0, whose stricter
"recompile when dependencies change" check forces docker-exe's
compile-java9 to rerun inside the site plugin's forked, compile-only
javadoc:aggregate build. There, reactor dependencies are still plain
target/classes directories, and module-info can't see maven-executor's
MR-JAR module descriptor until it's packaged as a real jar (nesting
under META-INF/versions/9 is a jar-format concept) - so the forked
compile fails with "module not found: org.apache.maven.executor".
3.15.0's weaker staleness check instead reuses the classes already
compiled during the preceding verify, where packaging happens before
docker-exe compiles and the module is visible. Remove this pin only
once that forked-compile module path resolution is fixed.
---
pom.xml | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/pom.xml b/pom.xml
index 4a5d7e9..8486394 100644
--- a/pom.xml
+++ b/pom.xml
@@ -70,6 +70,19 @@
<project.build.outputTimestamp>2026-06-12T10:14:54Z</project.build.outputTimestamp>
<testTmpDir>${project.build.directory}/tmp</testTmpDir>
+ <!--
+ ! Pinned below the version maven-parent 50 (apache 40) manages. 3.16.0's stricter
+ ! "recompile when dependencies change" check forces docker-exe's compile-java9 to
+ ! rerun inside the site plugin's forked, compile-only javadoc:aggregate build, where
+ ! reactor dependencies are still plain target/classes directories. module-info there
+ ! only sees maven-executor's MR-JAR module descriptor once it is packaged as a real
+ ! jar (META-INF/versions/9 is a jar-format concept), so the forked compile fails with
+ ! "module not found: org.apache.maven.executor". 3.15.0's weaker staleness check
+ ! instead reuses the classes already compiled during the preceding `verify`, where
+ ! packaging happens before docker-exe compiles and the module is visible.
+ ! Remove this pin only once that forked-compile module path resolution is fixed.
+ -->
+ <version.maven-compiler-plugin>3.15.0</version.maven-compiler-plugin>
<version.maven3>3.9.16</version.maven3>
<version.maven3resolver>1.9.27</version.maven3resolver>
<version.maven4>4.0.0-rc-7</version.maven4>
(maven-executor) 02/04: Use inputExcludes for apache-rat 0.18
Posted by sl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/maven-executor.git
commit f285b7a1d395f86671046a7040c9b6a29a682166
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Fri Sep 25 12:37:04 2026 +0200
Use inputExcludes for apache-rat 0.18
Keep the rat configuration in pluginManagement; the check itself is
activated by the parent's java17+ profile on JDK 17+.
Signed-off-by: Sylwester Lachiewicz <sl...@apache.org>
---
pom.xml | 44 +++++++++++++++++++++++---------------------
1 file changed, 23 insertions(+), 21 deletions(-)
diff --git a/pom.xml b/pom.xml
index 5fa2065..4a5d7e9 100644
--- a/pom.xml
+++ b/pom.xml
@@ -212,6 +212,27 @@
<build>
<pluginManagement>
<plugins>
+ <plugin>
+ <groupId>org.apache.rat</groupId>
+ <artifactId>apache-rat-plugin</artifactId>
+ <configuration>
+ <inputExcludes combine.children="append">
+
+ <exclude>Jenkinsfile</exclude>
+ <exclude>.github/**</exclude>
+ <exclude>deploySite.bat</exclude>
+ <exclude>deploySite.sh</exclude>
+ <exclude>LICENCE</exclude>
+ <exclude>NOTICE</exclude>
+ <exclude>LICENCE</exclude>
+ <!--
+ ! Excluded the license files itself cause they do not have a license of themselves.
+ -->
+ <exclude>src/main/appended-resources/licenses/**</exclude>
+
+ </inputExcludes>
+ </configuration>
+ </plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
@@ -264,30 +285,11 @@
</plugin>
</plugins>
</pluginManagement>
- <plugins>
- <plugin>
- <groupId>org.apache.rat</groupId>
- <artifactId>apache-rat-plugin</artifactId>
- <configuration>
- <excludes>
- <exclude>Jenkinsfile</exclude>
- <exclude>.github/**</exclude>
- <exclude>deploySite.bat</exclude>
- <exclude>deploySite.sh</exclude>
- <exclude>LICENCE</exclude>
- <exclude>NOTICE</exclude>
- <exclude>LICENCE</exclude>
- <!--
- ! Excluded the license files itself cause they do not have a license of themselves.
- -->
- <exclude>src/main/appended-resources/licenses/**</exclude>
- </excludes>
- </configuration>
- </plugin>
- </plugins>
+ <plugins />
</build>
<profiles>
+
<profile>
<id>reporting</id>
<reporting>