[
https://issues.apache.org/jira/browse/SUREFIRE-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832387#comment-16832387
]
Tibor Digana commented on SUREFIRE-1623:
----------------------------------------
>> I think forking another process just for this is clumsy
You have to understand that the plugin starts forked JVM by default and you can
change it by setting {{forkCount=0}} in your configuration in POM. Running this
native command in the forked JVM is the right place because it has a prupose
and the purpose is to check the parent process (Maven) has been killed (e.g.
intended in Jenkins CI) and child JVM (fork) kills itself. Thus the file
handlers are freed on Jenkins and the next build can freely erase the workspace
and start builing a project.
> 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
>
> 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)
