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/08/24 21:57:52 UTC
(maven-executor) branch main updated (4c38900 -> dad2243)
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 4c38900 Build against Maven 4.0.0-rc-6
new 2f15d4f Remove unused groovy-jsr223 dependency management entry
new dad2243 Add Surefire fork timeout so a hung fork fails with a thread dump
The 2 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 | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
(maven-executor) 01/02: Remove unused groovy-jsr223 dependency management entry
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 2f15d4ff5d3719c9338e8521567b9547fa99b6a9
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Mon Aug 24 15:46:07 2026 +0200
Remove unused groovy-jsr223 dependency management entry
Added in 0e864b3 for the maven-batch-executor module's javax.script
interpolation, which 991f66f then removed. Nothing declares the
dependency now, so Dependabot keeps proposing bumps that cannot be
evaluated against any classpath. If the batch module returns under #1,
reinstate the entry alongside the module that uses it.
---
pom.xml | 7 -------
1 file changed, 7 deletions(-)
diff --git a/pom.xml b/pom.xml
index b99677d..49b4b56 100644
--- a/pom.xml
+++ b/pom.xml
@@ -187,13 +187,6 @@
<version>${version.slf4j}</version>
</dependency>
- <!-- javax.script -->
- <dependency>
- <groupId>org.apache.groovy</groupId>
- <artifactId>groovy-jsr223</artifactId>
- <version>5.0.7</version>
- </dependency>
-
<!-- test dependencies -->
<dependency>
<groupId>org.mockito</groupId>
(maven-executor) 02/02: Add Surefire fork timeout so a hung fork fails with a thread dump
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 dad2243b93758b17c29a01cddb541376fb09dbb8
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Mon Aug 24 16:38:28 2026 +0200
Add Surefire fork timeout so a hung fork fails with a thread dump
Tests fork real Maven builds and have wedged three times in CI, producing no
output until the fail-fast-build job hit its 15-minute limit and was killed,
which leaves nothing to diagnose. On timeout Surefire's shutdown hook writes a
full thread dump to target/surefire-reports/*.dump before killing the fork.
600 seconds sits about five times above a healthy run of the module and well
inside the job limit.
---
pom.xml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/pom.xml b/pom.xml
index 49b4b56..a123061 100644
--- a/pom.xml
+++ b/pom.xml
@@ -244,6 +244,12 @@
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<useModulePath>false</useModulePath>
+ <!--
+ ! Tests fork real Maven builds, so a wedged fork otherwise produces no output at all
+ ! until the CI job itself is killed. The fail-fast-build job allows 15 minutes; a
+ ! healthy run of the whole module takes well under two.
+ -->
+ <forkedProcessTimeoutInSeconds>600</forkedProcessTimeoutInSeconds>
</configuration>
</plugin>
</plugins>