maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <>
Subject [jira] [Commented] (SUREFIRE-1623) TempWmicBatchFile.bat is left in project dirs after surefire tests are run
Date Fri, 03 May 2019 12:46:00 GMT


Tibor Digana commented on SUREFIRE-1623:

No, I wasn't able to reproduce this issue completely. The plugin does not hang.
I only say that I reproduced the existence of {{TempWmicBatchFile.bat}}.
Here is the project attached when I used it on Windows XP x64 in 2018.
Pls check it out with the same project. What happens then?

mvn -V
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1g; support was removed
in 8.0
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T20:41:47+02:00)
Maven home: e:\Projects\apache-maven-3.6.0\bin\..
Java version: 1.8.0, vendor: Oracle Corporation, runtime: e:\Program Files\Java\jdk1.8.0\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp", version: "5.2", arch: "amd64", family: "windows"

java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)

> TempWmicBatchFile.bat is left in project dirs after surefire tests are run
> --------------------------------------------------------------------------
>                 Key: SUREFIRE-1623
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 3.0.0-M3
>            Reporter: Chris Graham
>            Assignee: Tibor Digana
>            Priority: Blocker
>         Attachments: reproduce-surefire-issue
> When the WMIC command it run to obtain the process start time, the current implementation
leaves behind a batch file, TempWmicBatchFile.bat, which is zero bytes long.
> This file needs to be removed post execution.
> Leaving it behind will interfere with the release plugin as a scm status call will fail
with files needing to be added. Simply ignoring the file is a very sloppy approach.

This message was sent by Atlassian JIRA

View raw message