[
https://issues.apache.org/jira/browse/SUREFIRE-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829897#comment-16829897
]
Chris Graham commented on SUREFIRE-1623:
----------------------------------------
I'm glad that you've been able to replicate it. It's pretty clear that it is
only from Surefire; yet you still seem resistant to the idea.
If you wanted to be 100% paranoid, then check if the file exists before the
exec call, record the fact, then delete it if it did not exist prior to the
call, and exists afterwards.
Personally, I think forking another process just for this is clumsy, but I have
not read in detail the underlying justification either (so there may be good
justification for it).
> TempWmicBatchFile.bat is left in project dirs after surefire tests are run
> --------------------------------------------------------------------------
>
> Key: SUREFIRE-1623
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1623
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 3.0.0-M3
> Reporter: Chris Graham
> Assignee: Tibor Digana
> Priority: Blocker
> Fix For: 3.0.0-M4
>
>
> WINDOWS ONLY:
> 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
(v7.6.3#76005)
