[ 
https://issues.apache.org/jira/browse/WHISKER-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18069522#comment-18069522
 ] 

ASF subversion and git services commented on WHISKER-31:
--------------------------------------------------------

Commit 7ede1d71711195a7c849b4b053f20896f2a3d99e in creadur-whisker's branch 
refs/heads/dependabot/maven/log4j2.version-2.25.4 from Philipp Ottlinger
[ https://gitbox.apache.org/repos/asf?p=creadur-whisker.git;h=7ede1d7 ]

Revert "WHISKER-31: Try out if new version fixes the build problem"

Problem remains with new version.

This reverts commit efdf4feba12c3126417e61a29c85316387335282.


> GitHubAction-build failures on Windows and JDK<v21 after migrating to log4j
> ---------------------------------------------------------------------------
>
>                 Key: WHISKER-31
>                 URL: https://issues.apache.org/jira/browse/WHISKER-31
>             Project: Apache Whisker
>          Issue Type: Bug
>    Affects Versions: 0.2
>            Reporter: Philipp Ottlinger
>            Priority: Critical
>
> After migrating to log4j2 via WHISKER-18 we experience build failures on 
> Windows and JDKs:
> * 8
> * 11
> * 17
> but the build goes through on Windows-JDK21 and all Ubuntu-builds in the same 
> matrix build.
> Example:
> https://github.com/apache/creadur-whisker/actions/runs/14948277443/job/41994451722
> It seems as if the maven-invoker-tests are not working.
> h2. Call for help
> Could anyone with a Windows machine verify the situation by just building 
> locally and adding the build output of a failing integration test to this 
> task?
> Thanks



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to