[jira] [Commented] (MNG-6573) Use latest Maven 3.6.0 to build Maven Core and plugins with ASF CI

2019-05-06 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MNG-6573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834313#comment-16834313
 ] 

Hudson commented on MNG-6573:
-

Build failed in Jenkins: Maven TLP » maven-surefire » master #19

See https://builds.apache.org/job/maven-box/job/maven-surefire/job/master/19/

> Use latest Maven 3.6.0 to build Maven Core and plugins with ASF CI
> --
>
> Key: MNG-6573
> URL: https://issues.apache.org/jira/browse/MNG-6573
> Project: Maven
>  Issue Type: Task
>  Components: Integration Tests
>Reporter: Sylwester Lachiewicz
>Assignee: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 3.6.1
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Maven Core Integration Test passed ok for Linux and Windows for Java 7, 8, 
> 11, 12-ea, 13-ea.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (SUREFIRE-1666) printSummary=false does not completely suppress the summary on the console

2019-05-06 Thread Tibor Digana (JIRA)


 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana closed SUREFIRE-1666.
--
Resolution: Fixed

https://gitbox.apache.org/repos/asf/apache/?p=maven-surefire.git;a=commit;h=aeb346937ce5f0d98c266d955054e2f61061768b

> printSummary=false does not completely suppress the summary on the console
> --
>
> Key: SUREFIRE-1666
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1666
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M4
>
>
> Currently the plugins can suppress only
> {noformat}
> [INFO] 
> [INFO] Results:
> [INFO] 
> {noformat}
> It is incomplete feature ({{printSummary=false}}) because the *summary* is to 
> suppress the next two lines as well:
> {noformat}
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] 
> [INFO] Results:
> [INFO] 
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> [INFO] 
> {noformat}
> Errors and failures have to be printed always.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (SUREFIRE-1666) printSummary=false does not completely suppress the summary on the console

2019-05-06 Thread Tibor Digana (JIRA)


 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana updated SUREFIRE-1666:
---
Description: 
Currently the plugins can suppress only

{noformat}
[INFO] 
[INFO] Results:
[INFO] 
{noformat}

It is incomplete feature ({{printSummary=false}}) because the *summary* is to 
suppress the next two lines as well:

{noformat}
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
{noformat}

Errors and failures have to be printed always.

  was:
Currently the plugins can suppress only

{noformat}
[INFO] 
[INFO] Results:
[INFO] 
{noformat}

It is incomplete feature ({{printSummary=false}}) because the *summary* is to 
suppress the next two lines as well:

{noformat}
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
{noformat}

Errors and failures have to be printed always.


> printSummary=false does not completely suppress the summary on the console
> --
>
> Key: SUREFIRE-1666
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1666
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M4
>
>
> Currently the plugins can suppress only
> {noformat}
> [INFO] 
> [INFO] Results:
> [INFO] 
> {noformat}
> It is incomplete feature ({{printSummary=false}}) because the *summary* is to 
> suppress the next two lines as well:
> {noformat}
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] 
> [INFO] Results:
> [INFO] 
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> [INFO] 
> {noformat}
> Errors and failures have to be printed always.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SUREFIRE-1666) printSummary=false does not completely suppress the summary on the console

2019-05-06 Thread Tibor Digana (JIRA)
Tibor Digana created SUREFIRE-1666:
--

 Summary: printSummary=false does not completely suppress the 
summary on the console
 Key: SUREFIRE-1666
 URL: https://issues.apache.org/jira/browse/SUREFIRE-1666
 Project: Maven Surefire
  Issue Type: Improvement
  Components: Maven Failsafe Plugin, Maven Surefire Plugin
Reporter: Tibor Digana
Assignee: Tibor Digana
 Fix For: 3.0.0-M4


Currently the plugins can suppress only

{noformat}
[INFO] 
[INFO] Results:
[INFO] 
{noformat}

It is incomplete feature ({{printSummary=false}}) because the *summary* is to 
suppress the next two lines as well:

{noformat}
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
{noformat}

Errors and failures have to be printed always.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SUREFIRE-1623) TempWmicBatchFile.bat is left in project dirs after surefire tests are run

2019-05-06 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834264#comment-16834264
 ] 

Tibor Digana commented on SUREFIRE-1623:


[~ChrisGWarp]
Pls attach the dump files if they exist as well.
See them in the directories {{target/surefire-reports}} of every module. Thx.

> 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
> Attachments: reproduce-surefire-issue master.zip
>
>
> 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)


[jira] [Commented] (SUREFIRE-1623) TempWmicBatchFile.bat is left in project dirs after surefire tests are run

2019-05-06 Thread Chris Graham (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834231#comment-16834231
 ] 

Chris Graham commented on SUREFIRE-1623:


{noformat}
[INFO]
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[DEBUG] Determined Maven Process ID 3332
[DEBUG] boot classpath:  C:\Documents and 
Settings\admin\.m2\repository\org\apache\maven\surefire\surefire-shadefire\3.0.0-M3\surefire-shadefire-3.0.0-M3.jar
  C:\Wor
kspaces\Apache\maven-surefire\surefire-booter\target\test-classes  
C:\Workspaces\Apache\maven-surefire\surefire-booter\target\classes  
C:\Workspaces\Apache\maven-sur
efire\surefire-api\target\surefire-api-3.0.0-SNAPSHOT.jar  
C:\Workspaces\Apache\maven-surefire\surefire-logger-api\target\surefire-logger-api-3.0.0-SNAPSHOT.jar
  C:\
Documents and 
Settings\admin\.m2\repository\org\apache\maven\shared\maven-shared-utils\3.1.0\maven-shared-utils-3.1.0.jar
  C:\Documents and Settings\admin\.m2\reposi
tory\org\apache\commons\commons-lang3\3.8.1\commons-lang3-3.8.1.jar  
C:\Documents and 
Settings\admin\.m2\repository\commons-io\commons-io\2.6\commons-io-2.6.jar  C:\
Documents and 
Settings\admin\.m2\repository\com\google\code\findbugs\jsr305\2.0.3\jsr305-2.0.3.jar
  C:\Documents and Settings\admin\.m2\repository\commons-codec\comm
ons-codec\1.11\commons-codec-1.11.jar  C:\Documents and 
Settings\admin\.m2\repository\org\mockito\mockito-core\2.21.0\mockito-core-2.21.0.jar
  C:\Documents and Setti
ngs\admin\.m2\repository\net\bytebuddy\byte-buddy\1.8.15\byte-buddy-1.8.15.jar  
C:\Documents and 
Settings\admin\.m2\repository\net\bytebuddy\byte-buddy-agent\1.8.15\
byte-buddy-agent-1.8.15.jar  C:\Documents and 
Settings\admin\.m2\repository\org\objenesis\objenesis\2.6\objenesis-2.6.jar  
C:\Documents and Settings\admin\.m2\reposi
tory\org\powermock\powermock-core\2.0.0-RC.1\powermock-core-2.0.0-RC.1.jar  
C:\Documents and 
Settings\admin\.m2\repository\org\powermock\powermock-reflect\2.0.0-RC.1
\powermock-reflect-2.0.0-RC.1.jar  C:\Documents and 
Settings\admin\.m2\repository\org\javassist\javassist\3.22.0-GA\javassist-3.22.0-GA.jar
  C:\Documents and Setting
s\admin\.m2\repository\org\powermock\powermock-module-junit4\2.0.0-RC.1\powermock-module-junit4-2.0.0-RC.1.jar
  C:\Documents and Settings\admin\.m2\repository\org\po
wermock\powermock-module-junit4-common\2.0.0-RC.1\powermock-module-junit4-common-2.0.0-RC.1.jar
  C:\Documents and Settings\admin\.m2\repository\org\hamcrest\hamcrest
-core\1.3\hamcrest-core-1.3.jar  C:\Documents and 
Settings\admin\.m2\repository\org\powermock\powermock-api-mockito2\2.0.0-RC.1\powermock-api-mockito2-2.0.0-RC.1.jar
  C:\Documents and 
Settings\admin\.m2\repository\org\powermock\powermock-api-support\2.0.0-RC.1\powermock-api-support-2.0.0-RC.1.jar
  C:\Documents and Settings\admin
\.m2\repository\junit\junit\4.12\junit-4.12.jar  C:\Documents and 
Settings\admin\.m2\repository\org\hamcrest\hamcrest-library\1.3\hamcrest-library-1.3.jar
  C:\Docume
nts and 
Settings\admin\.m2\repository\org\easytesting\fest-assert\1.4\fest-assert-1.4.jar
  C:\Documents and Settings\admin\.m2\repository\org\easytesting\fest-util\1
.1.6\fest-util-1.1.6.jar
[DEBUG] boot(compact) classpath:  surefire-shadefire-3.0.0-M3.jar  test-classes 
 classes  surefire-api-3.0.0-SNAPSHOT.jar  
surefire-logger-api-3.0.0-SNAPSHOT.jar  ma
ven-shared-utils-3.1.0.jar  commons-lang3-3.8.1.jar  commons-io-2.6.jar  
jsr305-2.0.3.jar  commons-codec-1.11.jar  mockito-core-2.21.0.jar  
byte-buddy-1.8.15.jar  by
te-buddy-agent-1.8.15.jar  objenesis-2.6.jar  powermock-core-2.0.0-RC.1.jar  
powermock-reflect-2.0.0-RC.1.jar  javassist-3.22.0-GA.jar  
powermock-module-junit4-2.0.0
-RC.1.jar  powermock-module-junit4-common-2.0.0-RC.1.jar  hamcrest-core-1.3.jar 
 powermock-api-mockito2-2.0.0-RC.1.jar  powermock-api-support-2.0.0-RC.1.jar  
junit-4
.12.jar  hamcrest-library-1.3.jar  fest-assert-1.4.jar  fest-util-1.1.6.jar
[DEBUG] Forking command line: cmd.exe /X /C ""C:\Program 
Files\Java\jdk1.8.0_152\jre\..\bin\java" -server -XX:+UseG1GC -Xms128m -Xmx144m 
-XX:+TieredCompilation -XX:T
ieredStopAtLevel=1 -XX:SoftRefLRUPolicyMSPerMB=50 -Djava.awt.headless=true 
-Djdk.net.URLClassPath.disableClassPathURLCheck=true "-javaagent:C:\\Documents 
and Setting
s\\admin\\.m2\\repository\\org\\jacoco\\org.jacoco.agent\\0.8.3\\org.jacoco.agent-0.8.3-runtime.jar=destfile=C:\\Workspaces\\Apache\\maven-surefire\\surefire-booter\
\target\\jacoco.exec,append=true,includes=**/failsafe/*:**/failsafe/**/*:**/surefire/*:**/surefire/**/*,inclnolocationclasses=true,jmx=false"
 -Dnet.bytebuddy.experim
ental=true org.apache.maven.shadefire.surefire.booter.ForkedBooter 
"C:\Documents and Settings\admin\Local 
Settings\Temp\surefire8806289940760796727" 2019-05-06T22-39
-26_587-jvmRun1 surefire5561095777841642908tmp surefire_17325591220434640506tmp"
[INFO] 

[jira] [Commented] (DOXIA-538) Tag used for monospaced is not a valid html5 tag

2019-05-06 Thread Sylwester Lachiewicz (JIRA)


[ 
https://issues.apache.org/jira/browse/DOXIA-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834155#comment-16834155
 ] 

Sylwester Lachiewicz commented on DOXIA-538:


For XHTML5 we have: 
[https://dev.w3.org/html5/spec-author-view/the-code-element.html#the-code-element]

And it can be used also in fluido 
[https://github.com/google/code-prettify#how-do-i-specify-the-language-of-my-code]

 

> Tag  used for monospaced is not a valid html5 tag
> --
>
> Key: DOXIA-538
> URL: https://issues.apache.org/jira/browse/DOXIA-538
> Project: Maven Doxia
>  Issue Type: Bug
>  Components: Core, Module - Xdoc, Module - Xhtml
>Affects Versions: 1.6
>Reporter: Ievgen Degtiarenko
>Priority: Major
> Attachments: monospaced_for_doxia.patch
>
>
> https://maven.apache.org/doxia/references/apt-format.html
> <<>> is converted into Monospaced that is not valid tag 
> in html5
> Attached patch replaces  tag with  that is the most common tag that 
> is displayed as monospaced text in modern browsers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] [maven-release] rfscholte commented on a change in pull request #28: MRELEASE-985 Override snapshot dependencies from command line

2019-05-06 Thread GitBox
rfscholte commented on a change in pull request #28: MRELEASE-985 Override 
snapshot dependencies from command line
URL: https://github.com/apache/maven-release/pull/28#discussion_r281300548
 
 

 ##
 File path: 
maven-release-manager/src/main/java/org/apache/maven/shared/release/phase/CheckDependencySnapshotsPhase.java
 ##
 @@ -309,7 +309,8 @@ private static boolean checkArtifact( Artifact artifact, 
ReleaseDescriptor relea
 // We are only looking at dependencies external to the project - 
ignore anything found in the reactor as
 // it's version will be updated
 boolean result = artifact.isSnapshot()
-&& !artifact.getBaseVersion().equals( 
releaseDescriptor.getProjectOriginalVersion( versionlessKey ) );
+&& !artifact.getBaseVersion().equals( 
releaseDescriptor.getProjectOriginalVersion( versionlessKey ) )
+&& releaseDescriptor.getDependencyReleaseVersion( 
versionlessKey ) == null;
 
 Review comment:
   I see an issue here: users can pass a SNAPSHOT here and bypass the check. 
This should not be allowed, so let's find the proper position to do this.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[jira] [Commented] (SUREFIRE-1623) TempWmicBatchFile.bat is left in project dirs after surefire tests are run

2019-05-06 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833922#comment-16833922
 ] 

Tibor Digana commented on SUREFIRE-1623:


[~ChrisGWarp]
Thx Chris, the execution time is too long against my system (AMD Athlon 64 
3800+ II Core) but it is not what I understand by hanging. Because the build 
has finished.
Few weeks ago on our Mailing list one user said that he had significantly slow 
GC and he said that it was a problem with the system because he configured a 
swap file. I understood him that JVM used swap for perm-generation but he did 
not explain details.
Pls check your system too, {{Xmx}} and possibly use {{jconsole}}.
There is dump file(s) in the directory {{target/surefire-reports}}, pls go 
there and try to find them. Perhaps they would tell us more what's going on 
inside.


> 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
> Attachments: reproduce-surefire-issue master.zip
>
>
> 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)


[jira] [Commented] (MSKINS-137) Enable "Hamburger menu" with top-nav only

2019-05-06 Thread Josh Elser (JIRA)


[ 
https://issues.apache.org/jira/browse/MSKINS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833921#comment-16833921
 ] 

Josh Elser commented on MSKINS-137:
---

Thanks Hervé and Sylwester!

> Enable "Hamburger menu" with top-nav only
> -
>
> Key: MSKINS-137
> URL: https://issues.apache.org/jira/browse/MSKINS-137
> Project: Maven Skins
>  Issue Type: Improvement
>Reporter: Josh Elser
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: fluido-1.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Revitalizing this old PR https://github.com/apache/maven-skins/pull/4
> Still an issue for us down in HBase. Changes seem to apply and have worked in 
> local testing on the HBase site.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SUREFIRE-1654) Remove deprecated parameter 'forkMode' and use only 'forkCount'

2019-05-06 Thread JIRA


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833767#comment-16833767
 ] 

Dejan Stojadinović commented on SUREFIRE-1654:
--

FYI: [~tibor17] this one (almost) slipped through the cracks, but I did not 
forget about it.

> Remove deprecated parameter 'forkMode' and use only 'forkCount'
> ---
>
> Key: SUREFIRE-1654
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1654
> Project: Maven Surefire
>  Issue Type: Dependency upgrade
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin, process 
> forking
>Reporter: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M6
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SUREFIRE-1494) Make Provider surefire-junit47 default provider and deprecate surefire-junit4 Provider

2019-05-06 Thread JIRA


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833768#comment-16833768
 ] 

Dejan Stojadinović commented on SUREFIRE-1494:
--

FYI: [~tibor17] this one (almost) slipped through the cracks, but I did not 
forget about it.

> Make Provider surefire-junit47 default provider and deprecate surefire-junit4 
> Provider
> --
>
> Key: SUREFIRE-1494
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1494
> Project: Maven Surefire
>  Issue Type: New Feature
>Reporter: Tibor Digana
>Priority: Major
> Fix For: 3.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (SUREFIRE-1623) TempWmicBatchFile.bat is left in project dirs after surefire tests are run

2019-05-06 Thread Chris Graham (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833760#comment-16833760
 ] 

Chris Graham edited comment on SUREFIRE-1623 at 5/6/19 12:30 PM:
-

{noformat}
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] testapp - Root 1.0-SNAPSHOT  SUCCESS [  6.001 s]
[INFO] testapp - Application .. SUCCESS [03:03 min]
[INFO] testapp - Unit Tests ... SUCCESS [01:32 min]
[INFO] testapp - Integration Tests 1.0-SNAPSHOT ... SUCCESS [05:02 min]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 09:52 min
[INFO] Finished at: 2019-05-06T22:00:02+10:00
[INFO] 

C:\Workspaces\Apache\reproduce-surefire-issue master>dir *.bat /s
 Volume in drive C has no label.
 Volume Serial Number is 9817-F333

 Directory of C:\Workspaces\Apache\reproduce-surefire-issue 
master\integration-tests

05/06/2019  10:00 PM 0 TempWmicBatchFile.bat
   1 File(s)  0 bytes

 Directory of C:\Workspaces\Apache\reproduce-surefire-issue master\unit-tests

05/06/2019  09:54 PM 0 TempWmicBatchFile.bat
   1 File(s)  0 bytes

 Total Files Listed:
   2 File(s)  0 bytes
   0 Dir(s) 597,237,760 bytes free

C:\Workspaces\Apache\reproduce-surefire-issue master>mvn --version
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
2018-06-18T04:33:14+10:00)
Maven home: C:\apache-maven-3.5.4\bin\..
Java version: 1.8.0_152, vendor: Oracle Corporation, runtime: C:\Program 
Files\Java\jdk1.8.0_152\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"

C:\Workspaces\Apache\reproduce-surefire-issue master>{noformat}
As you can see, I get the same results.

I still get a hang whilst building surefire itself.

I have had a lot of issues installing Java 8 on this VM, The first version that 
was able to be installed was 1.8.0_40, then I installed all of these versions 
1.8.0_45, 74, 101, 111, 131, 141, 151 and finally 1.8.0_152. I am unable to 
installed 161 or higher.


was (Author: chrisgwarp):
{{INFO] 
}}
{{ [INFO] Reactor Summary:}}
{{ [INFO]}}
{{ [INFO] testapp - Root 1.0-SNAPSHOT  SUCCESS [ 6.001 
s]}}
{{ [INFO] testapp - Application .. SUCCESS [03:03 
min]}}
{{ [INFO] testapp - Unit Tests ... SUCCESS [01:32 
min]}}
{{ [INFO] testapp - Integration Tests 1.0-SNAPSHOT ... SUCCESS [05:02 
min]}}
{{ [INFO] 
}}
{{ [INFO] BUILD SUCCESS}}
{{ [INFO] 
}}
{{ [INFO] Total time: 09:52 min}}
{{ [INFO] Finished at: 2019-05-06T22:00:02+10:00}}
{{ [INFO] 
}}{{C:\Workspaces\Apache\reproduce-surefire-issue
 master>dir *.bat /s}}
{{ Volume in drive C has no label.}}
{{ Volume Serial Number is 9817-F333}}{{Directory of 
C:\Workspaces\Apache\reproduce-surefire-issue 
master\integration-tests}}{{05/06/2019 10:00 PM 0 TempWmicBatchFile.bat}}
{{ 1 File(s) 0 bytes}}{{Directory of 
C:\Workspaces\Apache\reproduce-surefire-issue master\unit-tests}}{{05/06/2019 
09:54 PM 0 TempWmicBatchFile.bat}}
{{ 1 File(s) 0 bytes}}{{Total Files Listed:}}
{{ 2 File(s) 0 bytes}}
{{ 0 Dir(s) 597,237,760 bytes 
free}}{{C:\Workspaces\Apache\reproduce-surefire-issue master>mvn --version}}
{{ Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
2018-06-18T04:33:14+10:00)}}
{{ Maven home: C:\apache-maven-3.5.4\bin\..}}
{{ Java version: 1.8.0_152, vendor: Oracle Corporation, runtime: C:\Program 
Files\Java\jdk1.8.0_152\jre}}
{{ Default locale: en_US, platform encoding: Cp1252}}
{{ OS name: "windows xp", version: "5.1", arch: "x86", family: 
"windows"}}{{C:\Workspaces\Apache\reproduce-surefire-issue master>}}

As you can see, I get the same results.

I still get a hang whilst building surefire itself.

I have had a lot of issues installing Java 8 on this VM, The first version that 
was able to be installed was 1.8.0_40, then I installed all of these versions 
1.8.0_45, 74, 101, 111, 131, 141, 151 and finally 1.8.0_152. I am unable to 
installed 161 or higher.

> TempWmicBatchFile.bat is left in project dirs after surefire tests are run
> --
>
> 

[jira] [Comment Edited] (SUREFIRE-1623) TempWmicBatchFile.bat is left in project dirs after surefire tests are run

2019-05-06 Thread Chris Graham (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833760#comment-16833760
 ] 

Chris Graham edited comment on SUREFIRE-1623 at 5/6/19 12:28 PM:
-

{{INFO] 
}}
{{ [INFO] Reactor Summary:}}
{{ [INFO]}}
{{ [INFO] testapp - Root 1.0-SNAPSHOT  SUCCESS [ 6.001 
s]}}
{{ [INFO] testapp - Application .. SUCCESS [03:03 
min]}}
{{ [INFO] testapp - Unit Tests ... SUCCESS [01:32 
min]}}
{{ [INFO] testapp - Integration Tests 1.0-SNAPSHOT ... SUCCESS [05:02 
min]}}
{{ [INFO] 
}}
{{ [INFO] BUILD SUCCESS}}
{{ [INFO] 
}}
{{ [INFO] Total time: 09:52 min}}
{{ [INFO] Finished at: 2019-05-06T22:00:02+10:00}}
{{ [INFO] 
}}{{C:\Workspaces\Apache\reproduce-surefire-issue
 master>dir *.bat /s}}
{{ Volume in drive C has no label.}}
{{ Volume Serial Number is 9817-F333}}{{Directory of 
C:\Workspaces\Apache\reproduce-surefire-issue 
master\integration-tests}}{{05/06/2019 10:00 PM 0 TempWmicBatchFile.bat}}
{{ 1 File(s) 0 bytes}}{{Directory of 
C:\Workspaces\Apache\reproduce-surefire-issue master\unit-tests}}{{05/06/2019 
09:54 PM 0 TempWmicBatchFile.bat}}
{{ 1 File(s) 0 bytes}}{{Total Files Listed:}}
{{ 2 File(s) 0 bytes}}
{{ 0 Dir(s) 597,237,760 bytes 
free}}{{C:\Workspaces\Apache\reproduce-surefire-issue master>mvn --version}}
{{ Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
2018-06-18T04:33:14+10:00)}}
{{ Maven home: C:\apache-maven-3.5.4\bin\..}}
{{ Java version: 1.8.0_152, vendor: Oracle Corporation, runtime: C:\Program 
Files\Java\jdk1.8.0_152\jre}}
{{ Default locale: en_US, platform encoding: Cp1252}}
{{ OS name: "windows xp", version: "5.1", arch: "x86", family: 
"windows"}}{{C:\Workspaces\Apache\reproduce-surefire-issue master>}}

As you can see, I get the same results.

I still get a hang whilst building surefire itself.

I have had a lot of issues installing Java 8 on this VM, The first version that 
was able to be installed was 1.8.0_40, then I installed all of these versions 
1.8.0_45, 74, 101, 111, 131, 141, 151 and finally 1.8.0_152. I am unable to 
installed 161 or higher.


was (Author: chrisgwarp):
{{[INFO] 

[INFO] Reactor Summary:
[INFO]
[INFO] testapp - Root 1.0-SNAPSHOT  SUCCESS [  6.001 s]
[INFO] testapp - Application .. SUCCESS [03:03 min]
[INFO] testapp - Unit Tests ... SUCCESS [01:32 min]
[INFO] testapp - Integration Tests 1.0-SNAPSHOT ... SUCCESS [05:02 min]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 09:52 min
[INFO] Finished at: 2019-05-06T22:00:02+10:00
[INFO] 

C:\Workspaces\Apache\reproduce-surefire-issue master>dir *.bat /s
 Volume in drive C has no label.
 Volume Serial Number is 9817-F333

 Directory of C:\Workspaces\Apache\reproduce-surefire-issue 
master\integration-tests

05/06/2019  10:00 PM 0 TempWmicBatchFile.bat
   1 File(s)  0 bytes

 Directory of C:\Workspaces\Apache\reproduce-surefire-issue master\unit-tests

05/06/2019  09:54 PM 0 TempWmicBatchFile.bat
   1 File(s)  0 bytes

 Total Files Listed:
   2 File(s)  0 bytes
   0 Dir(s) 597,237,760 bytes free

C:\Workspaces\Apache\reproduce-surefire-issue master>mvn --version
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
2018-06-18T04:33:14+10:00)
Maven home: C:\apache-maven-3.5.4\bin\..
Java version: 1.8.0_152, vendor: Oracle Corporation, runtime: C:\Program 
Files\Java\jdk1.8.0_152\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"

C:\Workspaces\Apache\reproduce-surefire-issue master>}}

As you can see, I get the same results.

I still get a hang whilst building surefire itself. 

I have had a lot of issues installing Java 8 on this VM, The first version that 
was able to be installed was 1.8.0_40, then I installed all of these versions 
1.8.0_45, 74, 101, 111, 131, 141, 151 and finally 1.8.0_152. I am unable to 
installed 161 or higher.


> TempWmicBatchFile.bat is left in project dirs after surefire tests are run
> --
>
> Key: 

[jira] [Commented] (SUREFIRE-1623) TempWmicBatchFile.bat is left in project dirs after surefire tests are run

2019-05-06 Thread Chris Graham (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833760#comment-16833760
 ] 

Chris Graham commented on SUREFIRE-1623:


{{[INFO] 

[INFO] Reactor Summary:
[INFO]
[INFO] testapp - Root 1.0-SNAPSHOT  SUCCESS [  6.001 s]
[INFO] testapp - Application .. SUCCESS [03:03 min]
[INFO] testapp - Unit Tests ... SUCCESS [01:32 min]
[INFO] testapp - Integration Tests 1.0-SNAPSHOT ... SUCCESS [05:02 min]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 09:52 min
[INFO] Finished at: 2019-05-06T22:00:02+10:00
[INFO] 

C:\Workspaces\Apache\reproduce-surefire-issue master>dir *.bat /s
 Volume in drive C has no label.
 Volume Serial Number is 9817-F333

 Directory of C:\Workspaces\Apache\reproduce-surefire-issue 
master\integration-tests

05/06/2019  10:00 PM 0 TempWmicBatchFile.bat
   1 File(s)  0 bytes

 Directory of C:\Workspaces\Apache\reproduce-surefire-issue master\unit-tests

05/06/2019  09:54 PM 0 TempWmicBatchFile.bat
   1 File(s)  0 bytes

 Total Files Listed:
   2 File(s)  0 bytes
   0 Dir(s) 597,237,760 bytes free

C:\Workspaces\Apache\reproduce-surefire-issue master>mvn --version
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
2018-06-18T04:33:14+10:00)
Maven home: C:\apache-maven-3.5.4\bin\..
Java version: 1.8.0_152, vendor: Oracle Corporation, runtime: C:\Program 
Files\Java\jdk1.8.0_152\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"

C:\Workspaces\Apache\reproduce-surefire-issue master>}}

As you can see, I get the same results.

I still get a hang whilst building surefire itself. 

I have had a lot of issues installing Java 8 on this VM, The first version that 
was able to be installed was 1.8.0_40, then I installed all of these versions 
1.8.0_45, 74, 101, 111, 131, 141, 151 and finally 1.8.0_152. I am unable to 
installed 161 or higher.


> 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
> Attachments: reproduce-surefire-issue master.zip
>
>
> 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)


[jira] [Comment Edited] (SUREFIRE-1623) TempWmicBatchFile.bat is left in project dirs after surefire tests are run

2019-05-06 Thread Chris Graham (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833348#comment-16833348
 ] 

Chris Graham edited comment on SUREFIRE-1623 at 5/6/19 7:09 AM:


My intent in the above, perhaps would have been clearer if instead of 
'paranoid', I wrote 'to program defensively', ie, only remove the file if the 
file was present before the execution.
I have lots of issues getting 1.8 installed in this VM, so I've had to go back 
to 1.8.0_40 and then install newer versions after that (an initial install of 
1.8.0_181 or 191 did not work).
Simply running 'mvn clean install' on surefire itself produces the WMIC files 
left behind, and the next build fails on a rat check. So I have to skip tests 
whilst building surefire itself. When I run the build with tests enabled, it 
hangs on the first JUnit test in the surefire-booter module, with a call to 
WMIC.exe (two of them have been spawned).
I will try to get to a point where I can build surefire under 32 bit XP and 
then see if I can drill down deeper into the code to see what is triggering the 
issue.



was (Author: chrisgwarp):
My intent in the above, perhaps would have been clearer if instead of 
'paranoid', I wrote 'to program defensively', ie, only remove the file if the 
file was present before the execution.
I have lots of issues getting 1.8 installed in this VM, so I've had to go back 
to 1.8.0_40 and then install newer versions after that (an initial install of 
1.8.0_181 or 191 did not work).
Simply running 'mvn clean install' on surefire itself produces the WMIC files 
left behind, and the next build fails on a rat check. So I have to skip tests 
whilst building surefire itself.
I will try to get to a point where I can build surefire under 32 bit XP and 
then see if I can drill down deeper into the code to see what is triggering the 
issue.


> 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
> Attachments: reproduce-surefire-issue master.zip
>
>
> 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)