[jira] [Updated] (MDEP-663) Analyze failed: Unsupported class file major version 57 (Java 13)

2019-11-03 Thread Sudhesh RAJAN SHARMA (Jira)
[ https://issues.apache.org/jira/browse/MDEP-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudhesh RAJAN SHARMA updated MDEP-663: -- Description: Class file of major version 57 (Java 13) is not yet supported by Maven

[jira] [Created] (MDEP-663) Analyze failed: Unsupported class file major version 57 (Java 13)

2019-11-03 Thread Sudhesh RAJAN SHARMA (Jira)
Sudhesh RAJAN SHARMA created MDEP-663: - Summary: Analyze failed: Unsupported class file major version 57 (Java 13) Key: MDEP-663 URL: https://issues.apache.org/jira/browse/MDEP-663 Project: Maven

[GitHub] [maven-surefire] Tibor17 edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549214210 @Col-E You should be facing strange behavior with the report. It's not strange but the

[GitHub] [maven-surefire] Tibor17 commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549215289 The answer is in the history of the Adapter class. I don't say it was better in previous version, nothing but

[GitHub] [maven-surefire] Col-E commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Col-E commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549215015 ```java public class AppTest { @Test public void pass() { } @Test

[GitHub] [maven-surefire] Tibor17 edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549214210 @Col-E You should be facing strange behavior with the report. It's not strange but the

[GitHub] [maven-surefire] Tibor17 edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549214210 @Col-E You should be facing strange behavior with the report. It's not strange but the

[GitHub] [maven-surefire] Tibor17 commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549214210 @Col-E You should be facing strange behavior with the report. It's not strange but the implementation we

[jira] [Assigned] (SUREFIRE-1708) skipAfterFailureCount should be coherent across multiple fork JVMs

2019-11-03 Thread Tibor Digana (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1708: -- Assignee: Tibor Digana > skipAfterFailureCount should be coherent across multiple

[GitHub] [maven-surefire] Tibor17 edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549208624 ok, let's change the methodology. Although the provider is able to run parameterized test, run `mvn

[GitHub] [maven-surefire] Tibor17 commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549208624 ok, let's change the methodology. Although the provider is able to run parameterized test, run `mvn test`

[GitHub] [maven-surefire] Col-E edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Col-E edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549207446 Reporting still uses the method `toClassMethodName`. So as of right now the reporting format should be the

[GitHub] [maven-surefire] Col-E edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Col-E edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549207446 Reporting still uses the method `toClassMethodName`. So as of right now the reporting format should be the

[GitHub] [maven-surefire] Col-E commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Col-E commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549207446 Well, reporting still uses the method `toClassMethodName`. So as of right now reporting format should be the same

[GitHub] [maven-surefire] Col-E edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Col-E edited a comment on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549207446 Reporting still uses the method `toClassMethodName`. So as of right now reporting format should be the

[GitHub] [maven-surefire] Tibor17 commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549204514 Yes, this was my plan but we have to run the unit tests and Platform ITs because i am not sure if they would

[GitHub] [maven-surefire] Col-E commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Col-E commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549204098 > Can you then prepare a PR with the legacy name on the top of this commit? For clarification, are you

[GitHub] [maven-surefire] Tibor17 commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 commented on issue #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549200081 @Col-E I will implement [skipAfterFailureCount in JUnit5

[jira] [Updated] (SUREFIRE-1710) skipAfterFailureCount in JUnit5 provider

2019-11-03 Thread Tibor Digana (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1710: --- Summary: skipAfterFailureCount in JUnit5 provider (was: skip after failure count in

[jira] [Closed] (SUREFIRE-1711) Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread Tibor Digana (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1711. -- Resolution: Fixed

[jira] [Closed] (DOXIATOOLS-63) Upgrade project dependencies

2019-11-03 Thread Sylwester Lachiewicz (Jira)
[ https://issues.apache.org/jira/browse/DOXIATOOLS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed DOXIATOOLS-63. -- Resolution: Fixed > Upgrade project dependencies >

[jira] [Assigned] (DOXIATOOLS-63) Upgrade project dependencies

2019-11-03 Thread Sylwester Lachiewicz (Jira)
[ https://issues.apache.org/jira/browse/DOXIATOOLS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned DOXIATOOLS-63: -- Assignee: Sylwester Lachiewicz > Upgrade project dependencies >

[GitHub] [maven-surefire] Tibor17 merged pull request #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 merged pull request #252: [SUREFIRE-1711] Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252 This is an automated message from the Apache Git Service. To

[jira] [Created] (SUREFIRE-1711) Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread Tibor Digana (Jira)
Tibor Digana created SUREFIRE-1711: -- Summary: Support @ParameterizedTest for JUnit 5 test reruns Key: SUREFIRE-1711 URL: https://issues.apache.org/jira/browse/SUREFIRE-1711 Project: Maven Surefire

[GitHub] [maven-surefire] Tibor17 edited a comment on issue #252: Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 edited a comment on issue #252: Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549190583 ok, that's also good alternative. I will merge this with master. Can you then prepare a PR with the legacy

[GitHub] [maven-surefire] Tibor17 edited a comment on issue #252: Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 edited a comment on issue #252: Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549190583 ok, that's also good alternative. I will merge this with master. Can you then prepare a PR with the legacy

[GitHub] [maven-surefire] Tibor17 commented on issue #252: Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 commented on issue #252: Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549190583 ok, that's also good alternative. I will merge this with master. Can you then prepare a PR with the legacy name on

[GitHub] [maven-surefire] Tibor17 edited a comment on issue #252: Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 edited a comment on issue #252: Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549190583 ok, that's also good alternative. I will merge this with master. Can you then prepare a PR with the legacy

[GitHub] [maven-surefire] Col-E commented on issue #252: Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Col-E commented on issue #252: Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549189214 >And i want to ask you about the value of legacy name. Would it return something like human readable description that is unique

[GitHub] [maven-surefire] Col-E edited a comment on issue #252: Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Col-E edited a comment on issue #252: Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549189214 >And i want to ask you about the value of legacy name. Would it return something like human readable description that is

[GitHub] [maven-surefire] Tibor17 edited a comment on issue #252: Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 edited a comment on issue #252: Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549188605 LGTM, I am waiting for the build result. And i want to ask you about the value of legacy name. Would it return

[GitHub] [maven-surefire] Tibor17 edited a comment on issue #252: Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 edited a comment on issue #252: Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549188605 LGTM, I am waiting for the build result. And i want to ask you about the value of legacy name. Would it return

[GitHub] [maven-surefire] Tibor17 commented on issue #252: Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Tibor17 commented on issue #252: Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252#issuecomment-549188605 LGTM, I am waiting for the build result. And i want to ask you about the value of legacy name. Would it return something

[GitHub] [maven-surefire] Col-E commented on issue #245: Surefire-1584: Add option to rerun failing tests for JUnit5

2019-11-03 Thread GitBox
Col-E commented on issue #245: Surefire-1584: Add option to rerun failing tests for JUnit5 URL: https://github.com/apache/maven-surefire/pull/245#issuecomment-549187334 @Tibor17 @Seijan I'd like to take discussion over `@ParameterizedTest` over to a new PR that specifically deals

[GitHub] [maven-surefire] Col-E opened a new pull request #252: Support @ParameterizedTest for JUnit 5 test reruns

2019-11-03 Thread GitBox
Col-E opened a new pull request #252: Support @ParameterizedTest for JUnit 5 test reruns URL: https://github.com/apache/maven-surefire/pull/252 This change fixes the issue discussed in #245 where `@ParameterizedTest` were not supported by the JUnitPlatformProvider. The fix is

[GitHub] [maven-surefire] Tibor17 opened a new pull request #251: roadmap chart

2019-11-03 Thread GitBox
Tibor17 opened a new pull request #251: roadmap chart URL: https://github.com/apache/maven-surefire/pull/251 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[jira] [Closed] (SUREFIRE-1516) Should surefire specialize test runner when test isolation (i.e., fork) is needed?

2019-11-03 Thread Tibor Digana (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1516. -- Resolution: Won't Fix Explained in

[jira] [Assigned] (SUREFIRE-1516) Should surefire specialize test runner when test isolation (i.e., fork) is needed?

2019-11-03 Thread Tibor Digana (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1516: -- Assignee: Tibor Digana > Should surefire specialize test runner when test

[jira] [Updated] (SUREFIRE-1516) Should surefire specialize test runner when test isolation (i.e., fork) is needed?

2019-11-03 Thread Tibor Digana (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1516: --- Fix Version/s: (was: 3.0.0-M6) (was: 3.0.0-M5)

[GitHub] [maven-invoker-plugin] slawekjaranowski opened a new pull request #7: [MINVOKER-251] Allow options parallelThreads depends on available cores

2019-11-03 Thread GitBox
slawekjaranowski opened a new pull request #7: [MINVOKER-251] Allow options parallelThreads depends on available cores URL: https://github.com/apache/maven-invoker-plugin/pull/7 This is an automated message from the Apache

[jira] [Commented] (MNG-6771) Fix license issues on binary distribution

2019-11-03 Thread Herve Boutemy (Jira)
[ https://issues.apache.org/jira/browse/MNG-6771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16965725#comment-16965725 ] Herve Boutemy commented on MNG-6771: [~eolivelli]what is the problem with Plexus Cipher and

[jira] [Created] (MINVOKER-251) Allow options parallelThreads depends on available cores

2019-11-03 Thread Slawomir Jaranowski (Jira)
Slawomir Jaranowski created MINVOKER-251: Summary: Allow options parallelThreads depends on available cores Key: MINVOKER-251 URL: https://issues.apache.org/jira/browse/MINVOKER-251 Project:

[jira] [Closed] (MSOURCES-122) ITs fail due to unexpected EOL characters when building release sources from the ZIP

2019-11-03 Thread Herve Boutemy (Jira)
[ https://issues.apache.org/jira/browse/MSOURCES-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MSOURCES-122. -- Assignee: Herve Boutemy Resolution: Fixed fixed in

[GitHub] [maven-surefire] jon-bell opened a new pull request #250: Maven2surefire jvm communication

2019-11-03 Thread GitBox
jon-bell opened a new pull request #250: Maven2surefire jvm communication URL: https://github.com/apache/maven-surefire/pull/250 Contributions for PR #240 This is an automated message from the Apache Git Service. To respond

[GitHub] [maven-surefire] jon-bell edited a comment on issue #240: [SUREFIRE-1658] TCP/IP Channel for forked Surefire JVM. Extensions API and SPI. Polymorphism for remote and local process communicati

2019-11-03 Thread GitBox
jon-bell edited a comment on issue #240: [SUREFIRE-1658] TCP/IP Channel for forked Surefire JVM. Extensions API and SPI. Polymorphism for remote and local process communication. URL: https://github.com/apache/maven-surefire/pull/240#issuecomment-549141618 I think that I'm ready for some

[GitHub] [maven-surefire] jon-bell commented on issue #240: [SUREFIRE-1658] TCP/IP Channel for forked Surefire JVM. Extensions API and SPI. Polymorphism for remote and local process communication.

2019-11-03 Thread GitBox
jon-bell commented on issue #240: [SUREFIRE-1658] TCP/IP Channel for forked Surefire JVM. Extensions API and SPI. Polymorphism for remote and local process communication. URL: https://github.com/apache/maven-surefire/pull/240#issuecomment-549141618 I think that I'm ready for some

[jira] [Created] (SUREFIRE-1710) skip after failure count in JUnit5

2019-11-03 Thread Tibor Digana (Jira)
Tibor Digana created SUREFIRE-1710: -- Summary: skip after failure count in JUnit5 Key: SUREFIRE-1710 URL: https://issues.apache.org/jira/browse/SUREFIRE-1710 Project: Maven Surefire Issue

[jira] [Commented] (MSOURCES-122) ITs fail due to unexpected EOL characters when building release sources from the ZIP

2019-11-03 Thread Hudson (Jira)
[ https://issues.apache.org/jira/browse/MSOURCES-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16965668#comment-16965668 ] Hudson commented on MSOURCES-122: - Build succeeded in Jenkins: Maven TLP » maven-source-plugin » master

[jira] [Created] (SUREFIRE-1709) re-run should fire events when it is started and finished

2019-11-03 Thread Tibor Digana (Jira)
Tibor Digana created SUREFIRE-1709: -- Summary: re-run should fire events when it is started and finished Key: SUREFIRE-1709 URL: https://issues.apache.org/jira/browse/SUREFIRE-1709 Project: Maven

[jira] [Created] (SUREFIRE-1708) skipAfterFailureCount should be coherent across multiple fork JVMs

2019-11-03 Thread Tibor Digana (Jira)
Tibor Digana created SUREFIRE-1708: -- Summary: skipAfterFailureCount should be coherent across multiple fork JVMs Key: SUREFIRE-1708 URL: https://issues.apache.org/jira/browse/SUREFIRE-1708 Project:

[jira] [Updated] (MSOURCES-122) ITs fail due to unexpected EOL characters when building release sources from the ZIP

2019-11-03 Thread Herve Boutemy (Jira)
[ https://issues.apache.org/jira/browse/MSOURCES-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSOURCES-122: --- Fix Version/s: 3.2.1 > ITs fail due to unexpected EOL characters when building release

[jira] [Commented] (MJAVADOC-628) add javadoc.io link pattern when option is set to true

2019-11-03 Thread Max (Jira)
[ https://issues.apache.org/jira/browse/MJAVADOC-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16965666#comment-16965666 ] Max commented on MJAVADOC-628: -- Raised PR: [https://github.com/apache/maven-javadoc-plugin/pull/34] > add

[GitHub] [maven-javadoc-plugin] maxcellent opened a new pull request #34: MJAVADOC-628 add javadoc.io link pattern when option is …

2019-11-03 Thread GitBox
maxcellent opened a new pull request #34: MJAVADOC-628 add javadoc.io link pattern when option is … URL: https://github.com/apache/maven-javadoc-plugin/pull/34 …set to true Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make

[jira] [Updated] (DOXIATOOLS-63) Upgrade project dependencies

2019-11-03 Thread Sylwester Lachiewicz (Jira)
[ https://issues.apache.org/jira/browse/DOXIATOOLS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated DOXIATOOLS-63: --- Description: Upgrade project dependencies to latest versions supported on

[jira] [Updated] (DOXIATOOLS-63) Upgrade project dependencies

2019-11-03 Thread Sylwester Lachiewicz (Jira)
[ https://issues.apache.org/jira/browse/DOXIATOOLS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated DOXIATOOLS-63: --- Description: Upgrade project dependencies to latest versions supported on

[jira] [Updated] (DOXIATOOLS-63) Upgrade project dependencies

2019-11-03 Thread Sylwester Lachiewicz (Jira)
[ https://issues.apache.org/jira/browse/DOXIATOOLS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated DOXIATOOLS-63: --- Summary: Upgrade project dependencies (was: Upgrade to JUnit 4.12) >

[jira] [Updated] (MSOURCES-122) ITs fail due to unexpected EOL characters when building release sources from the ZIP

2019-11-03 Thread Tibor Digana (Jira)
[ https://issues.apache.org/jira/browse/MSOURCES-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated MSOURCES-122: -- Description: If you make the release vote, you use the source release ZIP built by Linux and

[jira] [Updated] (MSOURCES-122) ITs fail due to unexpected EOL characters when building release sources from the ZIP

2019-11-03 Thread Tibor Digana (Jira)
[ https://issues.apache.org/jira/browse/MSOURCES-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated MSOURCES-122: -- Description: If you make the release vote, you use the source release ZIP built by Linux and

[jira] [Updated] (MSOURCES-122) ITs fail due to unexpected EOL characters when building release sources from the ZIP

2019-11-03 Thread Tibor Digana (Jira)
[ https://issues.apache.org/jira/browse/MSOURCES-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated MSOURCES-122: -- Attachment: maven-source-plugin-3.2.0.tgz > ITs fail due to unexpected EOL characters when

[jira] [Created] (MSOURCES-122) ITs fail due to unexpected EOL characters when building release sources from the ZIP

2019-11-03 Thread Tibor Digana (Jira)
Tibor Digana created MSOURCES-122: - Summary: ITs fail due to unexpected EOL characters when building release sources from the ZIP Key: MSOURCES-122 URL: https://issues.apache.org/jira/browse/MSOURCES-122

[GitHub] [maven-surefire] Tibor17 commented on issue #231: Failsafe: Killing self fork JVM. PING timeout elapsed.

2019-11-03 Thread GitBox
Tibor17 commented on issue #231: Failsafe: Killing self fork JVM. PING timeout elapsed. URL: https://github.com/apache/maven-surefire/pull/231#issuecomment-549123747 @shark-horse I used the first commit and not the second, see https://issues.apache.org/jira/browse/SUREFIRE-1707 We

[GitHub] [maven-surefire] Tibor17 closed pull request #231: Failsafe: Killing self fork JVM. PING timeout elapsed.

2019-11-03 Thread GitBox
Tibor17 closed pull request #231: Failsafe: Killing self fork JVM. PING timeout elapsed. URL: https://github.com/apache/maven-surefire/pull/231 This is an automated message from the Apache Git Service. To respond to the

[jira] [Closed] (SUREFIRE-1707) Forked JVM is killed when GC paused the tests for over 30 seconds

2019-11-03 Thread Tibor Digana (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1707. -- Resolution: Fixed

[jira] [Created] (MINVOKER-250) streamLogsOnFailures - parameter/option

2019-11-03 Thread Slawomir Jaranowski (Jira)
Slawomir Jaranowski created MINVOKER-250: Summary: streamLogsOnFailures - parameter/option Key: MINVOKER-250 URL: https://issues.apache.org/jira/browse/MINVOKER-250 Project: Maven Invoker

[jira] [Closed] (MJAR-263) Reproducible Builds: make entries in output jar files reproducible (order + timestamp)

2019-11-03 Thread Herve Boutemy (Jira)
[ https://issues.apache.org/jira/browse/MJAR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MJAR-263. -- Assignee: Herve Boutemy Resolution: Fixed done in

[jira] [Commented] (MJAVADOC-628) add javadoc.io link pattern when option is set to true

2019-11-03 Thread Max (Jira)
[ https://issues.apache.org/jira/browse/MJAVADOC-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16965607#comment-16965607 ] Max commented on MJAVADOC-628: -- creating JIRA as suggested by Enrico Olivelli in the email. > add

[jira] [Updated] (MJAVADOC-628) add javadoc.io link pattern when option is set to true

2019-11-03 Thread Max (Jira)
[ https://issues.apache.org/jira/browse/MJAVADOC-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max updated MJAVADOC-628: - Description: For example, google gson ([https://github.com/google/gson]) has pointed their javadoc to 

[jira] [Updated] (MJAVADOC-628) add javadoc.io link pattern when option is set to true

2019-11-03 Thread Max (Jira)
[ https://issues.apache.org/jira/browse/MJAVADOC-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max updated MJAVADOC-628: - Description: For example, google gson ([https://github.com/google/gson]) has pointed their javadoc to 

[jira] [Created] (MJAVADOC-628) add javadoc.io link pattern when option is set to true

2019-11-03 Thread Max (Jira)
Max created MJAVADOC-628: Summary: add javadoc.io link pattern when option is set to true Key: MJAVADOC-628 URL: https://issues.apache.org/jira/browse/MJAVADOC-628 Project: Maven Javadoc Plugin