[jira] [Commented] (SUREFIRE-1264) Some tests can be lost when running in parallel with parameterized tests

[ https://issues.apache.org/jira/browse/SUREFIRE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004097#comment-16004097 ] Rik Smith commented on SUREFIRE-1264: - [~tibor17] With our test suite i find it di

[jira] [Updated] (MNG-5378) Use maven-shared-utils in Maven core to replace plexus-utils

[ https://issues.apache.org/jira/browse/MNG-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-5378: --- Issue Type: Task (was: Bug) > Use maven-shared-utils in Maven core to replace plexus-utils > --

[jira] [Updated] (MNG-5378) Use maven-shared-utils in Maven core to replace plexus-utils

[ https://issues.apache.org/jira/browse/MNG-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-5378: --- Description: see http://maven.apache.org/shared/maven-shared-utils/ for the rationale > Use maven-share

[jira] [Commented] (MNG-5378) Use m-s-u in Maven core

[ https://issues.apache.org/jira/browse/MNG-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003913#comment-16003913 ] Hervé Boutemy commented on MNG-5378: yes, I'll change the issue title for more clarity :

[jira] [Updated] (MNG-5378) Use maven-shared-utils in Maven core to replace plexus-utils

[ https://issues.apache.org/jira/browse/MNG-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-5378: --- Summary: Use maven-shared-utils in Maven core to replace plexus-utils (was: Use maven-shared-utils in M

[jira] [Updated] (MNG-5378) Use maven-shared-utils in Maven core

[ https://issues.apache.org/jira/browse/MNG-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-5378: --- Summary: Use maven-shared-utils in Maven core (was: Use m-s-u in Maven core) > Use maven-shared-utils

[jira] [Commented] (MNG-6218) Jansi 1.13 does not recognize MinGW bash

[ https://issues.apache.org/jira/browse/MNG-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003910#comment-16003910 ] Hervé Boutemy commented on MNG-6218: yes, [~DannyNullZwo], please confirm: at my day wor

[jira] [Comment Edited] (MNG-6218) Jansi 1.13 does not recognize MinGW bash

[ https://issues.apache.org/jira/browse/MNG-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1554#comment-1554 ] Hervé Boutemy edited comment on MNG-6218 at 5/10/17 2:03 AM: - I

[jira] [Created] (MNG-6230) Separate plugin dependencies and execution declarations

Peter Cummuskey created MNG-6230: Summary: Separate plugin dependencies and execution declarations Key: MNG-6230 URL: https://issues.apache.org/jira/browse/MNG-6230 Project: Maven Issue Type:

[jira] [Commented] (MNG-5378) Use m-s-u in Maven core

[ https://issues.apache.org/jira/browse/MNG-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003696#comment-16003696 ] Peter Cummuskey commented on MNG-5378: -- Would I be correct in guessing that "m-s-u" sta

[jira] [Closed] (MNG-6229) Write out optionality in Core IT Plugins for collection and resolution

[ https://issues.apache.org/jira/browse/MNG-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6229. --- Resolution: Fixed Fixed with [4714fad90b14cbf625c183625edfbb1929782155|https://git-wip-us.apache.org/re

[jira] [Created] (MNG-6229) Write out optionality in Core IT Plugins for collection and resolution

Michael Osipov created MNG-6229: --- Summary: Write out optionality in Core IT Plugins for collection and resolution Key: MNG-6229 URL: https://issues.apache.org/jira/browse/MNG-6229 Project: Maven

[jira] [Closed] (MNG-6186) switch to improved HawtJNI

[ https://issues.apache.org/jira/browse/MNG-6186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MNG-6186. -- Resolution: Fixed Assignee: Hervé Boutemy Fix Version/s: (was: 3.5.1-candidate)

[jira] [Closed] (MNG-6205) Non-ascii chars in name element are displayed as question marks in Win CLI output (regression)

[ https://issues.apache.org/jira/browse/MNG-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MNG-6205. -- Resolution: Fixed Assignee: Hervé Boutemy JAnsi upgraded to 1.16, which does a better job at detecti

[jira] [Closed] (MNG-6223) mvn -f outputs invalid error when specifying POM directory

[ https://issues.apache.org/jira/browse/MNG-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MNG-6223. -- Resolution: Fixed Assignee: Hervé Boutemy fixed both on Windows and Unix IT in http://git-wip-us.ap

[jira] [Created] (MNG-6228) Optionality not displayed in dependency tree when run in debug mode

Michael Osipov created MNG-6228: --- Summary: Optionality not displayed in dependency tree when run in debug mode Key: MNG-6228 URL: https://issues.apache.org/jira/browse/MNG-6228 Project: Maven

[jira] [Commented] (MNG-6223) mvn -f outputs invalid error when specifying POM directory

[ https://issues.apache.org/jira/browse/MNG-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003362#comment-16003362 ] Hudson commented on MNG-6223: - SUCCESS: Integrated in Jenkins build maven-3.x #1648 (See [https

[jira] [Commented] (MNG-6205) Non-ascii chars in name element are displayed as question marks in Win CLI output (regression)

[ https://issues.apache.org/jira/browse/MNG-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003363#comment-16003363 ] Hudson commented on MNG-6205: - SUCCESS: Integrated in Jenkins build maven-3.x #1648 (See [https

[jira] [Commented] (MNG-6186) switch to improved HawtJNI

[ https://issues.apache.org/jira/browse/MNG-6186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003364#comment-16003364 ] Hudson commented on MNG-6186: - SUCCESS: Integrated in Jenkins build maven-3.x #1648 (See [https

[jira] [Comment Edited] (MNG-6221) Maven cannot build with Java 1.8.0_131

[ https://issues.apache.org/jira/browse/MNG-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003318#comment-16003318 ] Michael Osipov edited comment on MNG-6221 at 5/9/17 7:06 PM: - Lo

[jira] [Commented] (MNG-6221) Maven cannot build with Java 1.8.0_131

[ https://issues.apache.org/jira/browse/MNG-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003318#comment-16003318 ] Michael Osipov commented on MNG-6221: - Looking for to the example, I'd take a look. > M

[jira] [Assigned] (MNG-5935) Optional true getting lost in managed dependencies when transitive

[ https://issues.apache.org/jira/browse/MNG-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MNG-5935: --- Assignee: Michael Osipov > Optional true getting lost in managed dependencies when transitive >

[jira] [Commented] (SCM-724) pushChanges not working with maven-scm-provider-jazz

[ https://issues.apache.org/jira/browse/SCM-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002645#comment-16002645 ] Iñaki Ibarrola Atxa commented on SCM-724: - I am also experiencing this problem. In ou

[jira] [Comment Edited] (SCM-724) pushChanges not working with maven-scm-provider-jazz

[ https://issues.apache.org/jira/browse/SCM-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002645#comment-16002645 ] Iñaki Ibarrola Atxa edited comment on SCM-724 at 5/9/17 1:09 PM: --

[jira] [Commented] (SUREFIRE-1370) Build failed in Jenkins with error :The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ https://issues.apache.org/jira/browse/SUREFIRE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002557#comment-16002557 ] Tibor Digana commented on SUREFIRE-1370: Try to find the file {{hs_err*.log}} i

[jira] [Commented] (SUREFIRE-1370) Build failed in Jenkins with error :The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ https://issues.apache.org/jira/browse/SUREFIRE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002555#comment-16002555 ] Tibor Digana commented on SUREFIRE-1370: [~vijayblp] Have you seen {{OutOfMemor

[jira] [Commented] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002439#comment-16002439 ] Olivier Peyrusse commented on SUREFIRE-1302: Seems good to me. Since you le

[jira] [Updated] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1302: --- I plan to send PING from Maven process every second. This would be better synchronization. The

[jira] [Updated] (SUREFIRE-1370) Build failed in Jenkins with error :The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ https://issues.apache.org/jira/browse/SUREFIRE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated SUREFIRE-1370: Attachment: NewfailureLogs.txt New failure Logs > Build failed in Jenkins with error :The forked VM term

[jira] [Commented] (SUREFIRE-1370) Build failed in Jenkins with error :The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ https://issues.apache.org/jira/browse/SUREFIRE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002313#comment-16002313 ] Vijay commented on SUREFIRE-1370: - These are new logs generated with option -verbose:gc

[jira] [Commented] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002287#comment-16002287 ] Olivier Peyrusse commented on SUREFIRE-1302: Yes, why not. It is not easy t

[jira] [Updated] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1302: --- Are you open for testing SNAPSHOT version in several days? {quote} I though you meant that in

[jira] [Commented] (SUREFIRE-1370) Build failed in Jenkins with error :The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ https://issues.apache.org/jira/browse/SUREFIRE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002224#comment-16002224 ] Tibor Digana commented on SUREFIRE-1370: [~vijayblp] In this case the JVM crash

[jira] [Commented] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002216#comment-16002216 ] Olivier Peyrusse commented on SUREFIRE-1302: Hello [~tibor17], I will sure

[jira] [Updated] (SUREFIRE-1370) Build failed in Jenkins with error :The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ https://issues.apache.org/jira/browse/SUREFIRE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated SUREFIRE-1370: Attachment: 2017-05-09T08-08-44_247-jvmRun1.dumpstream Generated with option -verbose:gc > Build failed

[jira] [Commented] (SUREFIRE-1370) Build failed in Jenkins with error :The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ https://issues.apache.org/jira/browse/SUREFIRE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002194#comment-16002194 ] Vijay commented on SUREFIRE-1370: - Please find attached logs generated with -verbose:gc