[GitHub] [maven-surefire] slawekjaranowski commented on pull request #500: [SUREFIRE-2024] Replace testng-junit5 by testng-engine

slawekjaranowski commented on pull request #500: URL: https://github.com/apache/maven-surefire/pull/500#issuecomment-1081403804 @Tibor17 Ok, I removed additional test, and use only existing. I think that exclusions in most of time it is workaround for problem in target project.

[GitHub] [maven-invoker-plugin] dependabot[bot] opened a new pull request #109: Bump mockito-core from 4.3.1 to 4.4.0

dependabot[bot] opened a new pull request #109: URL: https://github.com/apache/maven-invoker-plugin/pull/109 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.3.1 to 4.4.0. Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-core's releas

[GitHub] [maven] laeubi commented on pull request #695: [MNG-7432] Dependencies from profile not picked up via -P

laeubi commented on pull request #695: URL: https://github.com/apache/maven/pull/695#issuecomment-1081326893 @michael-o just wondering inf we can proceed here? If its fine for 3.8.x I'll prepare PRs for 2.9.x and 4.x as well ... I also wonder if it would be suitable to release a 3.8.6 vers

[GitHub] [maven-surefire] mpkorstanje commented on pull request #503: [SUREFIRE-1710] skipAfterFailureCount in JUnit5 provider

mpkorstanje commented on pull request #503: URL: https://github.com/apache/maven-surefire/pull/503#issuecomment-1081322666 I believe the JUnit team uses community engagement as a measure of importance and interest. Now it seems the conversation never moved on after the brainstorming.

[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #502: [SUREFIRE-1432] trimStackTrace = false by default

Tibor17 edited a comment on pull request #502: URL: https://github.com/apache/maven-surefire/pull/502#issuecomment-1081315961 @slawekjaranowski I have cleaned up the [release backlog](https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20fixVersion%20%3D%203.0.0-M6

[GitHub] [maven-surefire] Tibor17 commented on pull request #502: [SUREFIRE-1432] trimStackTrace = false by default

Tibor17 commented on pull request #502: URL: https://github.com/apache/maven-surefire/pull/502#issuecomment-1081315961 @slawekjaranowski I have cleaned up the [release backlog](https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20fixVersion%20%3D%203.0.0-M6%20ORDE

[GitHub] [maven-surefire] Tibor17 commented on pull request #500: [SUREFIRE-2024] Replace testng-junit5 by testng-engine

Tibor17 commented on pull request #500: URL: https://github.com/apache/maven-surefire/pull/500#issuecomment-1081314829 @slawekjaranowski If we are so close to cut a new release, we should push this change and we can continue with the discussion and refactoring or joining the POMs in one

[jira] [Closed] (SUREFIRE-1560) Rework SUREFIRE-1535. Use only FORKTESTSET and split SurefireProvider to two interfaces - currently has two responsibilities

[ https://issues.apache.org/jira/browse/SUREFIRE-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1560. -- Resolution: Duplicate > Rework SUREFIRE-1535. Use only FORKTESTSET and split SurefireProvide

[jira] [Updated] (SUREFIRE-1560) Rework SUREFIRE-1535. Use only FORKTESTSET and split SurefireProvider to two interfaces - currently has two responsibilities

[ https://issues.apache.org/jira/browse/SUREFIRE-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1560: --- Fix Version/s: (was: 3.0) > Rework SUREFIRE-1535. Use only FORKTESTSET and split Suref

[jira] [Commented] (SUREFIRE-2048) Reworking the hack in SUREFIRE-1535. Fork should received command declaring Java type of the test.

[ https://issues.apache.org/jira/browse/SUREFIRE-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513755#comment-17513755 ] Tibor Digana commented on SUREFIRE-2048: See the original PR https://github.co

[jira] [Updated] (SUREFIRE-1814) Listener System.out.printf is written as multiple lines

[ https://issues.apache.org/jira/browse/SUREFIRE-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1814: --- Priority: Minor (was: Major) > Listener System.out.printf is written as multiple lines >

[jira] [Updated] (SUREFIRE-1709) Fire events when Provider execution is started and finished

[ https://issues.apache.org/jira/browse/SUREFIRE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1709: --- Description: Currently the XML reporter creates the report for a normal run. Then the same

[jira] [Updated] (SUREFIRE-1709) Fire events when Provider execution is started and finished

[ https://issues.apache.org/jira/browse/SUREFIRE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1709: --- Description: Currently the XML reporter creates the report for a normal run. Then the same

[jira] [Updated] (SUREFIRE-1709) Fire events when Provider execution is started and finished

[ https://issues.apache.org/jira/browse/SUREFIRE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1709: --- Description: Currently the XML reporter creates the report for a normal run. Then the same

[jira] [Updated] (SUREFIRE-1709) Fire events when Provider execution is started and finished

[ https://issues.apache.org/jira/browse/SUREFIRE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1709: --- Description: Currently the XML reporter creates the report for a normal run. Then the same

[jira] [Updated] (SUREFIRE-1709) Fire events when Provider execution is started and finished

[ https://issues.apache.org/jira/browse/SUREFIRE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1709: --- Summary: Fire events when Provider execution is started and finished (was: re-run should

[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #502: [SUREFIRE-1432] trimStackTrace = false by default

Tibor17 edited a comment on pull request #502: URL: https://github.com/apache/maven-surefire/pull/502#issuecomment-1081284797 @slawekjaranowski I think I took over the description by some user. Now we use `SmartStackTraceParser` everywhere except the JUnit3 provider. Currently, the l

[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #502: [SUREFIRE-1432] trimStackTrace = false by default

Tibor17 edited a comment on pull request #502: URL: https://github.com/apache/maven-surefire/pull/502#issuecomment-1081284797 @slawekjaranowski I think I took over the description by some user. Now we use `SmartStackTraceParser` everywhere except the JUnit3 provider. Currently the lo

[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #502: [SUREFIRE-1432] trimStackTrace = false by default

Tibor17 edited a comment on pull request #502: URL: https://github.com/apache/maven-surefire/pull/502#issuecomment-1081284797 @slawekjaranowski I think I took over the description by some user. IMHO, the user could not find the business logic. Now we use `SmartStackTraceParser` every

[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #502: [SUREFIRE-1432] trimStackTrace = false by default

Tibor17 edited a comment on pull request #502: URL: https://github.com/apache/maven-surefire/pull/502#issuecomment-1081284797 @slawekjaranowski I think I took over the description by some user. IMHO, the user could not find the business logic. Now we use `SmartStackTraceParser` every

[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #502: [SUREFIRE-1432] trimStackTrace = false by default

Tibor17 edited a comment on pull request #502: URL: https://github.com/apache/maven-surefire/pull/502#issuecomment-1081284797 @slawekjaranowski IMHO, he could not find the business logic. We use `SmartStackTraceParser` everywhere except the JUnit3 provider. Currently the logic is l

[GitHub] [maven-surefire] Tibor17 commented on pull request #502: [SUREFIRE-1432] trimStackTrace = false by default

Tibor17 commented on pull request #502: URL: https://github.com/apache/maven-surefire/pull/502#issuecomment-1081284797 @slawekjaranowski IMHO, he could not find the business logic. We use `SmartStackTraceParser` everywhere except the JUnit3 provider. Currently the logic is located

[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #503: [SUREFIRE-1710] skipAfterFailureCount in JUnit5 provider

Tibor17 edited a comment on pull request #503: URL: https://github.com/apache/maven-surefire/pull/503#issuecomment-1081266257 Yes, it would be worth to have the fix of [JUnit5 issue](https://github.com/junit-team/junit5/issues/1880) I reported. Unfortunately, the JUnit5 team does not car

[jira] [Updated] (SUREFIRE-1929) forkedProcessTimeoutInSeconds is controlled by the plugin process and the sub-process ends gracefully. The forked process should be able to timeout itself if the Maste

[ https://issues.apache.org/jira/browse/SUREFIRE-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1929: --- Fix Version/s: 3.0.0-M7 (was: 3.0.0-M6) > forkedProcessTimeoutInSec

[jira] [Updated] (SUREFIRE-1929) forkedProcessTimeoutInSeconds is controlled by the plugin process and the sub-process ends gracefully. The forked process should be able to timeout itself if the Maste

[ https://issues.apache.org/jira/browse/SUREFIRE-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1929: --- Priority: Minor (was: Major) > forkedProcessTimeoutInSeconds is controlled by the plugin

[jira] [Updated] (SUREFIRE-1814) Listener System.out.printf is written as multiple lines

[ https://issues.apache.org/jira/browse/SUREFIRE-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1814: --- Fix Version/s: 3.0.0-M7 (was: 3.0.0-M6) > Listener System.out.print

[jira] [Commented] (SUREFIRE-1814) Listener System.out.printf is written as multiple lines

[ https://issues.apache.org/jira/browse/SUREFIRE-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513735#comment-17513735 ] Tibor Digana commented on SUREFIRE-1814: Yes, it is really reproducible proble

[jira] [Updated] (SUREFIRE-2050) Remove deprecated subclasses of ConcurrentRunListener after SUREFIRE-1661, SUREFIRE-1795, SUREFIRE-1643

[ https://issues.apache.org/jira/browse/SUREFIRE-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-2050: --- Summary: Remove deprecated subclasses of ConcurrentRunListener after SUREFIRE-1661, SUREFI

[jira] [Updated] (SUREFIRE-2050) Remove deprecated subclasses of ConcurrentRunListener after SUREFIRE-1661, SUREFIRE-1795, SUREFIRE-1643

[ https://issues.apache.org/jira/browse/SUREFIRE-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-2050: --- Description: After the issues SUREFIRE-1661, SUREFIRE-1795, SUREFIRE-1643 are resolved and

[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #503: [SUREFIRE-1710] skipAfterFailureCount in JUnit5 provider

Tibor17 edited a comment on pull request #503: URL: https://github.com/apache/maven-surefire/pull/503#issuecomment-1081266257 Yes, it would be worth to have the fix in [JUnit5 issue](https://github.com/junit-team/junit5/issues/1880) I reported. Unfortunately, the JUnit5 team does not car

[GitHub] [maven-surefire] Tibor17 commented on pull request #503: [SUREFIRE-1710] skipAfterFailureCount in JUnit5 provider

Tibor17 commented on pull request #503: URL: https://github.com/apache/maven-surefire/pull/503#issuecomment-1081266257 Yes, it would be worth to have the a fix in [JUnit5 issue](https://github.com/junit-team/junit5/issues/1880) I reported. Unfortunately, the JUnit5 team does not care :-)

[jira] [Created] (SUREFIRE-2050) Remove deprecated subinterfaces of ConcurrentRunListener after SUREFIRE-1661, SUREFIRE-1795, SUREFIRE-1643

Tibor Digana created SUREFIRE-2050: -- Summary: Remove deprecated subinterfaces of ConcurrentRunListener after SUREFIRE-1661, SUREFIRE-1795, SUREFIRE-1643 Key: SUREFIRE-2050 URL: https://issues.apache.org/jira/brow

[GitHub] [maven-surefire] mpkorstanje commented on pull request #503: [SUREFIRE-1710] skipAfterFailureCount in JUnit5 provider

mpkorstanje commented on pull request #503: URL: https://github.com/apache/maven-surefire/pull/503#issuecomment-1081234664 Overall I think it would be more effective to first resolve https://github.com/junit-team/junit5/issues/1880 before trying to make it work in surefire. -- This is a

[GitHub] [maven-surefire] mpkorstanje edited a comment on pull request #503: [SUREFIRE-1710] skipAfterFailureCount in JUnit5 provider

mpkorstanje edited a comment on pull request #503: URL: https://github.com/apache/maven-surefire/pull/503#issuecomment-1081230185 Cheers. I don't mind taking a look but at a glance this will only work with JUnit Jupiter rather then every TestEngine on the JUnit Platform. The current implem

[GitHub] [maven-surefire] mpkorstanje commented on pull request #503: [SUREFIRE-1710] skipAfterFailureCount in JUnit5 provider

mpkorstanje commented on pull request #503: URL: https://github.com/apache/maven-surefire/pull/503#issuecomment-1081230185 Cheers. I don't mind taking a look but at a glance this will only work with JUnit Jupiter rather then every TestEngine on the JUnit Platform. It won't work for e

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

[ https://issues.apache.org/jira/browse/SUREFIRE-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1710: --- Fix Version/s: 3.0.0-M7 (was: 3.0.0-M6) > skipAfterFailureCount in

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

[ https://issues.apache.org/jira/browse/SUREFIRE-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1710: -- Assignee: Tibor Digana > skipAfterFailureCount in JUnit5 provider > ---

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

[ https://issues.apache.org/jira/browse/SUREFIRE-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1708: --- Fix Version/s: (was: 3.0.0-M6) > skipAfterFailureCount should be coherent across multi

[jira] [Updated] (SUREFIRE-1743) Allow custom listeners to request stop

[ https://issues.apache.org/jira/browse/SUREFIRE-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1743: --- Fix Version/s: (was: 3.0.0-M6) > Allow custom listeners to request stop >

[GitHub] [maven-surefire] Tibor17 commented on pull request #503: [SUREFIRE-1710] skipAfterFailureCount in JUnit5 provider

Tibor17 commented on pull request #503: URL: https://github.com/apache/maven-surefire/pull/503#issuecomment-1081219150 The class `FailFastJUnit5IT` should be renamed... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

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

[ https://issues.apache.org/jira/browse/SUREFIRE-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513684#comment-17513684 ] Tibor Digana commented on SUREFIRE-1710: This is the link with a PR https://gi

[jira] [Commented] (SUREFIRE-1743) Allow custom listeners to request stop

[ https://issues.apache.org/jira/browse/SUREFIRE-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513683#comment-17513683 ] Tibor Digana commented on SUREFIRE-1743: This is the link with a PR https://gi

[jira] [Updated] (SUREFIRE-1743) Allow custom listeners to request stop

[ https://issues.apache.org/jira/browse/SUREFIRE-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1743: --- External issue URL: https://github.com/apache/maven-surefire/pull/503 > Allow custom liste

[GitHub] [maven-surefire] Tibor17 commented on pull request #503: [SUREFIRE-1710] skipAfterFailureCount in JUnit5 provider

Tibor17 commented on pull request #503: URL: https://github.com/apache/maven-surefire/pull/503#issuecomment-1081215746 @andyrokit @mpkorstanje This is the implementation for https://issues.apache.org/jira/browse/SUREFIRE-1743 and https://issues.apache.org/jira/browse/SUREFIRE-1710 bu

[GitHub] [maven-surefire] Tibor17 opened a new pull request #503: [SUREFIRE-1710] skipAfterFailureCount in JUnit5 provider

Tibor17 opened a new pull request #503: URL: https://github.com/apache/maven-surefire/pull/503 This is my old change from my shelf. Providing it open. The ITs are broken and the impl should be fixed. Implements (skipAfterFailure)[https://maven.apache.org/surefire/maven-surefire-plugin/e

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

[ https://issues.apache.org/jira/browse/SUREFIRE-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513669#comment-17513669 ] Tibor Digana commented on SUREFIRE-1710: [~andyRokit] [~mpkorstanje] I have a

[jira] [Commented] (SUREFIRE-1743) Allow custom listeners to request stop

[ https://issues.apache.org/jira/browse/SUREFIRE-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513668#comment-17513668 ] Tibor Digana commented on SUREFIRE-1743: [~andyRokit] [~mpkorstanje] I have a

[jira] [Updated] (SUREFIRE-1170) skiptTests=true is used by maven-surefire-plugin as well as of maven-failsafe-plugin

[ https://issues.apache.org/jira/browse/SUREFIRE-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1170: --- Fix Version/s: 3.0 (was: 3.0.0-M6) > skiptTests=true is used by mav

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

[ https://issues.apache.org/jira/browse/SUREFIRE-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1654: --- Fix Version/s: 3.0 (was: 3.0.0-M6) > Remove deprecated parameter 'f

[jira] [Updated] (SUREFIRE-1130) Remove TODO and deprecated code in surefire 3.0

[ https://issues.apache.org/jira/browse/SUREFIRE-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1130: --- Fix Version/s: 3.0 (was: 3.0.0-M6) > Remove TODO and deprecated cod

[jira] [Assigned] (SUREFIRE-1130) Remove TODO and deprecated code in surefire 3.0

[ https://issues.apache.org/jira/browse/SUREFIRE-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1130: -- Assignee: (was: Tibor Digana) > Remove TODO and deprecated code in surefire 3.0

[jira] [Commented] (MSHARED-1049) Skipping LinkageError null, please report an issue to Maven dev team

[ https://issues.apache.org/jira/browse/MSHARED-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513637#comment-17513637 ] Philipp Ottlinger commented on MSHARED-1049: [~michael-o] thanks for the hi

[jira] [Commented] (MNG-828) log all mojo parameters and their populated values in debug mode

[ https://issues.apache.org/jira/browse/MNG-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513529#comment-17513529 ] Hudson commented on MNG-828: Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-7276 #5

[jira] [Commented] (MSHARED-1049) Skipping LinkageError null, please report an issue to Maven dev team

[ https://issues.apache.org/jira/browse/MSHARED-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513491#comment-17513491 ] Michael Osipov commented on MSHARED-1049: - There is a similar error already rep

[jira] [Moved] (MSHARED-1049) Skipping LinkageError null, please report an issue to Maven dev team

[ https://issues.apache.org/jira/browse/MSHARED-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov moved MNG-7442 to MSHARED-1049: -- Key: MSHARED-1049 (was: MNG-7442) Affects Version/

[jira] [Closed] (MNGSITE-483) https://maven.apache.org/POM/4.0.0 not accessible

[ https://issues.apache.org/jira/browse/MNGSITE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNGSITE-483. -- Resolution: Invalid >From an XML compliance perspective, this XML is invalid. The URI of >noN

[jira] [Commented] (MNGSITE-483) https://maven.apache.org/POM/4.0.0 not accessible

[ https://issues.apache.org/jira/browse/MNGSITE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513466#comment-17513466 ] Michael Pantel commented on MNGSITE-483: Take the Eclipse Platform poms. Example

[jira] [Commented] (MJAVADOC-475) Replace parameter additionalparam with additionalOptions

[ https://issues.apache.org/jira/browse/MJAVADOC-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513453#comment-17513453 ] Hudson commented on MJAVADOC-475: - Build succeeded in Jenkins: Maven » Maven TLP » mave

[GitHub] [maven-javadoc-plugin] slachiewicz merged pull request #124: (doc) Update plugin' configuration parameter (MJAVADOC-475)

slachiewicz merged pull request #124: URL: https://github.com/apache/maven-javadoc-plugin/pull/124 -- 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. To unsubscribe, e-mail:

[GitHub] [maven-resolver] caiwei-ebay edited a comment on pull request #158: MRESOLVER-247: Introduce skipper to avoid unnecessary dependency reso…

caiwei-ebay edited a comment on pull request #158: URL: https://github.com/apache/maven-resolver/pull/158#issuecomment-1079874235 @michael-o @cstamas @jebeaudet @ibabiankou As @cstamas pointed out, there is a slight but measurable performance downgrade with the BFS approach. mvn

[jira] [Commented] (MNGSITE-483) https://maven.apache.org/POM/4.0.0 not accessible

[ https://issues.apache.org/jira/browse/MNGSITE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513418#comment-17513418 ] Michael Osipov commented on MNGSITE-483: Which POMs exactly? > https://maven.ap

[GitHub] [maven-javadoc-plugin] pzygielo opened a new pull request #124: (doc) Update plugin' configuration parameter (MJAVADOC-475)

pzygielo opened a new pull request #124: URL: https://github.com/apache/maven-javadoc-plugin/pull/124 @slachiewicz - thanks for checking - #123 Seems that maven 3.2.5, that https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-javadoc-plugin/job/master/5/execution/node/195

[jira] [Commented] (MRESOLVER-216) [ERROR] Malformed \uxxxx encoding.

[ https://issues.apache.org/jira/browse/MRESOLVER-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513382#comment-17513382 ] Issa Gorissen commented on MRESOLVER-216: - Hello [~michael-o] , is this suppos

[jira] [Commented] (SUREFIRE-1969) Support for Java 17 LTS

[ https://issues.apache.org/jira/browse/SUREFIRE-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513370#comment-17513370 ] Casper Roubos commented on SUREFIRE-1969: - Sorry for the late reply. I can ret

[jira] [Commented] (MJAVADOC-475) Replace parameter additionalparam with additionalOptions

[ https://issues.apache.org/jira/browse/MJAVADOC-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513351#comment-17513351 ] Hudson commented on MJAVADOC-475: - Build failed in Jenkins: Maven » Maven TLP » maven-j

[GitHub] [maven-resolver] caiwei-ebay commented on pull request #158: MRESOLVER-247: Introduce skipper to avoid unnecessary dependency reso…

caiwei-ebay commented on pull request #158: URL: https://github.com/apache/maven-resolver/pull/158#issuecomment-1080603190 @michael-o @cstamas @jebeaudet Created a sample project to demonstrate the maven resolver slowness when comes to resolve duplicate dependencies (same GAV) with diff

[GitHub] [maven-javadoc-plugin] slachiewicz merged pull request #123: (doc) Update plugin' configuration parameter (MJAVADOC-475)

slachiewicz merged pull request #123: URL: https://github.com/apache/maven-javadoc-plugin/pull/123 -- 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. To unsubscribe, e-mail:

[jira] [Commented] (SUREFIRE-2043) Test groups not working for testng in combination with JUnit5

[ https://issues.apache.org/jira/browse/SUREFIRE-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513305#comment-17513305 ] Pavel Rybnicek commented on SUREFIRE-2043: -- Yes, it does work with testng-eng

[GitHub] [maven-surefire] Tibor17 commented on a change in pull request #499: Remove TestListResolver#optionallyWildcardFilter

Tibor17 commented on a change in pull request #499: URL: https://github.com/apache/maven-surefire/pull/499#discussion_r836228298 ## File path: surefire-providers/surefire-junit4/src/main/java/org/apache/maven/surefire/junit4/JUnit4Provider.java ## @@ -432,7 +430,6 @@ private s

[GitHub] [maven-javadoc-plugin] pzygielo commented on pull request #123: (doc) Update plugin' configuration parameter (MJAVADOC-475)

pzygielo commented on pull request #123: URL: https://github.com/apache/maven-javadoc-plugin/pull/123#issuecomment-1080407878 May I ask for review, please? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abov

[GitHub] [maven-javadoc-plugin] pzygielo commented on pull request #123: (doc) Update plugin' configuration parameter (MJAVADOC-475)

pzygielo commented on pull request #123: URL: https://github.com/apache/maven-javadoc-plugin/pull/123#issuecomment-1080404311 GH failures: - windows/8/zulu: ```Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not transfer artifact org.apache.maven.shared:m

[GitHub] [maven-surefire] Tibor17 commented on a change in pull request #499: Remove TestListResolver#optionallyWildcardFilter

Tibor17 commented on a change in pull request #499: URL: https://github.com/apache/maven-surefire/pull/499#discussion_r836219035 ## File path: surefire-api/src/test/java/org/apache/maven/surefire/api/testset/TestListResolverTest.java ## @@ -401,19 +406,6 @@ public void testInc

[GitHub] [maven-javadoc-plugin] pzygielo opened a new pull request #123: (doc) Update plugin' configuration parameter (MJAVADOC-475)

pzygielo opened a new pull request #123: URL: https://github.com/apache/maven-javadoc-plugin/pull/123 [MJAVADOC-475](https://issues.apache.org/jira/browse/MJAVADOC-475?focusedCommentId=16516951&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16516951): >

[jira] [Created] (MNGSITE-483) https://maven.apache.org/POM/4.0.0 not accessible

Michael Pantel created MNGSITE-483: -- Summary: https://maven.apache.org/POM/4.0.0 not accessible Key: MNGSITE-483 URL: https://issues.apache.org/jira/browse/MNGSITE-483 Project: Maven Project Web Site

[jira] [Commented] (MWRAPPER-61) let mvnw call mvn directly, without maven-wrapper.jar

[ https://issues.apache.org/jira/browse/MWRAPPER-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513198#comment-17513198 ] ASF GitHub Bot commented on MWRAPPER-61: gzm55 commented on pull request #33: UR

[GitHub] [maven-wrapper] gzm55 commented on pull request #33: [MWRAPPER-61] Try to skip maven-wrapper.jar, call mvn directly from mvnw.

gzm55 commented on pull request #33: URL: https://github.com/apache/maven-wrapper/pull/33#issuecomment-1080281803 @slawekjaranowski can we allow [shellcheck action](https://github.com/marketplace/actions/shellcheck)? -- This is an automated message from the Apache Git Service. To respond