[jira] [Comment Edited] (SUREFIRE-1650) Running multiple xml using suiteXmlFiles resulting in 0 test count

[ https://issues.apache.org/jira/browse/SUREFIRE-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957510#comment-16957510 ] Mark Han edited comment on SUREFIRE-1650 at 10/23/19 3:03 AM: --

[jira] [Commented] (SUREFIRE-1650) Running multiple xml using suiteXmlFiles resulting in 0 test count

[ https://issues.apache.org/jira/browse/SUREFIRE-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957510#comment-16957510 ] Mark Han commented on SUREFIRE-1650: Wow, has this been reproduced? I think I have

[GitHub] [maven-surefire] dejan2609 commented on issue #233: [SUREFIRE-1494] default provider for JUnit4 integration tests is changed (from 'surefire-junit4' to 'surefire-junit47')

dejan2609 commented on issue #233: [SUREFIRE-1494] default provider for JUnit4 integration tests is changed (from 'surefire-junit4' to 'surefire-junit47') URL: https://github.com/apache/maven-surefire/pull/233#issuecomment-545220293 Gotcha @Tibor17

[jira] [Commented] (WAGON-568) Fail to deploy on Sonatype OSS since maven 3.5.4

[ https://issues.apache.org/jira/browse/WAGON-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957369#comment-16957369 ] Stephane Landelle commented on WAGON-568: - I won't be able to investigate until ne

[jira] [Commented] (MNG-6759) [REGRESSION] Maven fails to use section from dependency when resolving transitive dependencies in some cases

[ https://issues.apache.org/jira/browse/MNG-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957314#comment-16957314 ] Robert Scholte commented on MNG-6759: - I see what you mean. Relocations aren't used tha

[GitHub] [maven-wagon] michael-o commented on issue #57: WAGON-567: support retry on server side errors

michael-o commented on issue #57: WAGON-567: support retry on server side errors URL: https://github.com/apache/maven-wagon/pull/57#issuecomment-545111098 @ColinHebert OK, I guess I need to discuss with other HttpComponents devs whether we should really split client and servers errors. `Ba

[GitHub] [maven-wagon] ColinHebert edited a comment on issue #57: WAGON-567: support retry on server side errors

ColinHebert edited a comment on issue #57: WAGON-567: support retry on server side errors URL: https://github.com/apache/maven-wagon/pull/57#issuecomment-545081565 > Do you think that using the ServiceUnavailableRetryStrategy is really the wrong way to go? I think it's "good enough"

[GitHub] [maven-wagon] ColinHebert commented on issue #57: WAGON-567: support retry on server side errors

ColinHebert commented on issue #57: WAGON-567: support retry on server side errors URL: https://github.com/apache/maven-wagon/pull/57#issuecomment-545081565 > Do you think that using the ServiceUnavailableRetryStrategy is really the wrong way to go? I think it's "good enough" to beg

[jira] [Commented] (WAGON-566) Fix for MSITE-738

[ https://issues.apache.org/jira/browse/WAGON-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957240#comment-16957240 ] Michael Osipov commented on WAGON-566: -- [~olegk], I need your expertise here. I have

[GitHub] [maven-wagon] michael-o commented on issue #57: WAGON-567: support retry on server side errors

michael-o commented on issue #57: WAGON-567: support retry on server side errors URL: https://github.com/apache/maven-wagon/pull/57#issuecomment-545076457 I will inquire why 429 is not included in the default config. * Alright, shall do so * I haven't even considered both Backoff i

[GitHub] [maven-wagon] ColinHebert edited a comment on issue #57: WAGON-567: support retry on server side errors

ColinHebert edited a comment on issue #57: WAGON-567: support retry on server side errors URL: https://github.com/apache/maven-wagon/pull/57#issuecomment-545071044 Makes sense for `DefaultServiceUnavailableRetryStrategy`, I'm actually surprised 429 was not handled out of the box. Re

[GitHub] [maven-wagon] ColinHebert edited a comment on issue #57: WAGON-567: support retry on server side errors

ColinHebert edited a comment on issue #57: WAGON-567: support retry on server side errors URL: https://github.com/apache/maven-wagon/pull/57#issuecomment-545071044 Makes sense for `DefaultServiceUnavailableRetryStrategy`, I'm actually surprised 429 was not handled out of the box. Re

[GitHub] [maven-wagon] ColinHebert commented on issue #57: WAGON-567: support retry on server side errors

ColinHebert commented on issue #57: WAGON-567: support retry on server side errors URL: https://github.com/apache/maven-wagon/pull/57#issuecomment-545071044 Makes sense for `DefaultServiceUnavailableRetryStrategy`, I'm actually surprised 429 was not handled out of the box. Regarding

[GitHub] [maven-wagon] eveardown commented on issue #55: Wagon-566

eveardown commented on issue #55: Wagon-566 URL: https://github.com/apache/maven-wagon/pull/55#issuecomment-545057532 I'll take a loOK. On Tue, 22 Oct 2019, 17:35 Michael Osipov, wrote: > I am considering merging this finally, but the modified class will likely > change due

[GitHub] [maven-wagon] michael-o commented on issue #55: Wagon-566

michael-o commented on issue #55: Wagon-566 URL: https://github.com/apache/maven-wagon/pull/55#issuecomment-545048503 I am considering merging this finally, but the modified class will likely change due to WAGON-569. This is

[jira] [Moved] (WAGON-569) Inconsistent encoding behavior for repository urls with spaces

[ https://issues.apache.org/jira/browse/WAGON-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov moved MDEPLOY-261 to WAGON-569: -- Component/s: (was: deploy:deploy) wagon

[jira] [Closed] (WAGON-491) Add ability to set certificate via byte[] and not only via file

[ https://issues.apache.org/jira/browse/WAGON-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-491. Fix Version/s: (was: waiting-for-feedback) Resolution: Won't Fix No feedback received. >

[jira] [Closed] (WAGON-286) Configurable SCM comment prefix

[ https://issues.apache.org/jira/browse/WAGON-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-286. Fix Version/s: (was: waiting-for-feedback) Resolution: Incomplete No feedback received.

[jira] [Closed] (WAGON-542) New wagon-zip provider

[ https://issues.apache.org/jira/browse/WAGON-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-542. Fix Version/s: (was: waiting-for-feedback) Resolution: Won't Fix No feedback received. >

[jira] [Comment Edited] (MNG-6759) [REGRESSION] Maven fails to use section from dependency when resolving transitive dependencies in some cases

[ https://issues.apache.org/jira/browse/MNG-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957178#comment-16957178 ] Stig Rohde Døssing edited comment on MNG-6759 at 10/22/19 3:47 PM: --

[jira] [Commented] (MNG-6759) [REGRESSION] Maven fails to use section from dependency when resolving transitive dependencies in some cases

[ https://issues.apache.org/jira/browse/MNG-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957178#comment-16957178 ] Stig Rohde Døssing commented on MNG-6759: - [~rfscholte] Thanks for taking a look at

[GitHub] [maven-integration-testing] srdo commented on issue #50: [MNG-6759] - Add test demonstrating the issue where the wrong reposit…

srdo commented on issue #50: [MNG-6759] - Add test demonstrating the issue where the wrong reposit… URL: https://github.com/apache/maven-integration-testing/pull/50#issuecomment-545023598 Thanks for letting me know about the suite. Addressed your comments.

[jira] [Closed] (WAGON-565) Do not skip retry on SSLException by default

[ https://issues.apache.org/jira/browse/WAGON-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-565. Fix Version/s: (was: waiting-for-feedback) Resolution: Not A Problem This has been fixed

[GitHub] [maven-surefire] Col-E opened a new pull request #249: Surefire-1701: Fix @DisplayName breaking reruns

Col-E opened a new pull request #249: Surefire-1701: Fix @DisplayName breaking reruns URL: https://github.com/apache/maven-surefire/pull/249 As discussed in [Surefire-1584](https://github.com/apache/maven-surefire/pull/245#issuecomment-543702810) there was a bug where `@DisplayName` would

[GitHub] [maven-wagon] michael-o edited a comment on issue #57: WAGON-567: support retry on server side errors

michael-o edited a comment on issue #57: WAGON-567: support retry on server side errors URL: https://github.com/apache/maven-wagon/pull/57#issuecomment-544947921 @ColinHebert I really much like your proposal. As soon as this goes in I will deprecate and mark the current backoff mechanism f

[GitHub] [maven-wagon] michael-o commented on issue #57: WAGON-567: support retry on server side errors

michael-o commented on issue #57: WAGON-567: support retry on server side errors URL: https://github.com/apache/maven-wagon/pull/57#issuecomment-544947921 @ColinHebert I really much like your proposal. As soon as this goes in I will deprecate and mark the current backoff mechanism for remov

[jira] [Created] (MNG-6791) document hard and soft requirements

Elliotte Rusty Harold created MNG-6791: -- Summary: document hard and soft requirements Key: MNG-6791 URL: https://issues.apache.org/jira/browse/MNG-6791 Project: Maven Issue Type: Improve

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

quiram commented on issue #245: Surefire-1584: Add option to rerun failing tests for JUnit5 URL: https://github.com/apache/maven-surefire/pull/245#issuecomment-544898214 > This is actually a **one character** fix 🤦‍♂ > > [JUnitPlatformProvider - Line 195](https://github.com/apache/

[jira] [Closed] (SUREFIRE-1702) [JDK 11 Alpine Linux] JAR content is not flushed completely down to drive "Error: Invalid or corrupt jarfile target/surefire/surefirebooter13749914711390838584.jar"

[ https://issues.apache.org/jira/browse/SUREFIRE-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1702. -- Assignee: Tibor Digana Resolution: Fixed https://gitbox.apache.org/repos/asf?p=maven-s

[jira] [Created] (SUREFIRE-1702) [JDK 11 Alpine Linux] JAR content is not flushed completely down to drive "Error: Invalid or corrupt jarfile target/surefire/surefirebooter13749914711390838584.jar"

Tibor Digana created SUREFIRE-1702: -- Summary: [JDK 11 Alpine Linux] JAR content is not flushed completely down to drive "Error: Invalid or corrupt jarfile target/surefire/surefirebooter13749914711390838584.jar" Key: SUREFIRE-170