[GitHub] [maven-site] gnodet merged pull request #329: Change code style to refer to the one from maven-shared-resources

2022-10-13 Thread GitBox
gnodet merged PR #329: URL: https://github.com/apache/maven-site/pull/329 -- 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: issues-unsubscr...@maven.apach

[jira] [Commented] (MSHARED-1033) Add resources required for auto-formatting

2022-10-13 Thread Hudson (Jira)
[ https://issues.apache.org/jira/browse/MSHARED-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617516#comment-17617516 ] Hudson commented on MSHARED-1033: - Build succeeded in Jenkins: Maven » Maven TLP » mave

[GitHub] [maven-shared-resources] gnodet merged pull request #1: [MSHARED-1033] Add resources required for automatic formatting and import sorting

2022-10-13 Thread GitBox
gnodet merged PR #1: URL: https://github.com/apache/maven-shared-resources/pull/1 -- 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: issues-unsubscr...@mav

[jira] [Commented] (MENFORCER-427) Rule for no version ranges, version placeholders or SNAPSHOT versions

2022-10-13 Thread Hudson (Jira)
[ https://issues.apache.org/jira/browse/MENFORCER-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617514#comment-17617514 ] Hudson commented on MENFORCER-427: -- Build succeeded in Jenkins: Maven » Maven TLP » m

[GitHub] [maven-enforcer] kwin merged pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
kwin merged PR #187: URL: https://github.com/apache/maven-enforcer/pull/187 -- 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: issues-unsubscr...@maven.apa

[jira] [Resolved] (MENFORCER-427) Rule for no version ranges, version placeholders or SNAPSHOT versions

2022-10-13 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/MENFORCER-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved MENFORCER-427. --- Resolution: Fixed Fixed in https://github.com/apache/maven-enforcer/commit/3c7474

[GitHub] [maven-javadoc-plugin] dependabot[bot] closed pull request #166: Bump qdox from 2.0.1 to 2.0.2

2022-10-13 Thread GitBox
dependabot[bot] closed pull request #166: Bump qdox from 2.0.1 to 2.0.2 URL: https://github.com/apache/maven-javadoc-plugin/pull/166 -- 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 comme

[GitHub] [maven-javadoc-plugin] dependabot[bot] commented on pull request #166: Bump qdox from 2.0.1 to 2.0.2

2022-10-13 Thread GitBox
dependabot[bot] commented on PR #166: URL: https://github.com/apache/maven-javadoc-plugin/pull/166#issuecomment-1278414494 Superseded by #169. -- 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

[GitHub] [maven-javadoc-plugin] dependabot[bot] opened a new pull request, #169: Bump qdox from 2.0.1 to 2.0.3

2022-10-13 Thread GitBox
dependabot[bot] opened a new pull request, #169: URL: https://github.com/apache/maven-javadoc-plugin/pull/169 Bumps [qdox](https://github.com/paul-hammant/qdox) from 2.0.1 to 2.0.3. Commits https://github.com/paul-hammant/qdox/commit/53d77bb3855f9768bc75317f148ce09dbe34e34c";>53

[jira] [Commented] (MNG-7529) Maven resolver makes bad repository choices when resolving version ranges

2022-10-13 Thread Henning Schmiedehausen (Jira)
[ https://issues.apache.org/jira/browse/MNG-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617361#comment-17617361 ] Henning Schmiedehausen commented on MNG-7529: - you want to look at the integrat

[GitHub] [maven-shared-resources] gnodet commented on pull request #1: [MSHARED-1033] Add resources required for automatic formatting and import sorting

2022-10-13 Thread GitBox
gnodet commented on PR #1: URL: https://github.com/apache/maven-shared-resources/pull/1#issuecomment-127813 I've reworked this small commit to include the 3 files from [maven-site](https://github.com/apache/maven-site/tree/master/content/resources/developers), with an additional plain

[jira] [Commented] (MNG-7567) Maven output out of order in windows

2022-10-13 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MNG-7567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617295#comment-17617295 ] Michael Osipov commented on MNG-7567: - Moved back to Maven. > Maven output out of orde

[jira] [Moved] (MNG-7567) Maven output out of order in windows

2022-10-13 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MNG-7567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov moved MCOMPILER-508 to MNG-7567: --- Key: MNG-7567 (was: MCOMPILER-508) Affects Version/s

[jira] [Comment Edited] (MCOMPILER-508) Maven output out of order in windows

2022-10-13 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617283#comment-17617283 ] Michael Osipov edited comment on MCOMPILER-508 at 10/13/22 7:57 PM:

[jira] [Commented] (MCOMPILER-508) Maven output out of order in windows

2022-10-13 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617283#comment-17617283 ] Michael Osipov commented on MCOMPILER-508: -- Fed the output of {{javac}} to Pl

[jira] [Moved] (MCOMPILER-508) Maven output out of order in windows

2022-10-13 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov moved MNG-7565 to MCOMPILER-508: --- Component/s: (was: Logging) Key: MCOMP

[jira] [Commented] (MNG-7565) Maven output out of order in windows

2022-10-13 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MNG-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617260#comment-17617260 ] Michael Osipov commented on MNG-7565: - I can confirm this by manually runing {{javac}}

[GitHub] [maven] kwin commented on pull request #827: Allow a Maven plugin to require a Java version

2022-10-13 Thread GitBox
kwin commented on PR #827: URL: https://github.com/apache/maven/pull/827#issuecomment-1277966331 @slawekjaranowski Thanks for the proposal, sounds good, but I am not sure when to call the validator. From both places where `MavenPluginManager#checkRequiredMavenVersion` is currently called? T

[jira] [Updated] (MNG-7566) Allow a Maven plugin to require a Java version through its plugin descriptor

2022-10-13 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/MNG-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MNG-7566: - Summary: Allow a Maven plugin to require a Java version through its plugin descriptor (was: Allow

[jira] [Updated] (MNG-7564) Potential NPE in MavenMetadataSource

2022-10-13 Thread Maarten Mulders (Jira)
[ https://issues.apache.org/jira/browse/MNG-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Mulders updated MNG-7564: - Labels: up-for-grabs (was: ) > Potential NPE in MavenMetadataSource >

[jira] [Moved] (MNG-7566) Allow a maven-plugin to require a Java version

2022-10-13 Thread Slawomir Jaranowski (Jira)
[ https://issues.apache.org/jira/browse/MNG-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski moved MPLUGIN-424 to MNG-7566: -- Component/s: (was: Plugin Plugin) Key: MNG-7566

[jira] [Commented] (MPLUGIN-424) Allow a maven-plugin to require a Java version

2022-10-13 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/MPLUGIN-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617196#comment-17617196 ] Konrad Windszus commented on MPLUGIN-424: - bq. Maven version should be also in p

[jira] [Commented] (MPLUGIN-424) Allow a maven-plugin to require a Java version

2022-10-13 Thread Slawomir Jaranowski (Jira)
[ https://issues.apache.org/jira/browse/MPLUGIN-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617195#comment-17617195 ] Slawomir Jaranowski commented on MPLUGIN-424: - By the way Maven version shou

[GitHub] [maven] slawekjaranowski commented on pull request #827: Allow a Maven plugin to require a Java version

2022-10-13 Thread GitBox
slawekjaranowski commented on PR #827: URL: https://github.com/apache/maven/pull/827#issuecomment-1277912731 Proposition - create component component like `PluginDescriptorValidator` - create two implementation one for Maven version and second new for Java varsion - inject lis

[GitHub] [maven-javadoc-plugin] alzimmermsft commented on pull request #159: [MJAVADOC-722] Log javadoc warnings and errors to file

2022-10-13 Thread GitBox
alzimmermsft commented on PR #159: URL: https://github.com/apache/maven-javadoc-plugin/pull/159#issuecomment-1277886474 Hey @michael-o just following up on this 😃 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the U

[GitHub] [maven] kwin commented on a diff in pull request #827: Allow a Maven plugin to require a Java version

2022-10-13 Thread GitBox
kwin commented on code in PR #827: URL: https://github.com/apache/maven/pull/827#discussion_r994821661 ## maven-plugin-api/src/main/mdo/plugin.mdo: ## @@ -91,6 +91,12 @@ under the License. boolean true + + requiredJavaVersion +

[GitHub] [maven] kwin opened a new pull request, #827: Allow a Maven plugin to require a Java version

2022-10-13 Thread GitBox
kwin opened a new pull request, #827: URL: https://github.com/apache/maven/pull/827 Currently just a draft around https://issues.apache.org/jira/browse/MPLUGIN-424 (which needs to be moved to MNG JIRA) -- This is an automated message from the Apache Git Service. To respond to the message

[jira] [Commented] (MNG-7561) DefaultVersionRangeResolver should not try to resolve request with same upper and lower bound

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617122#comment-17617122 ] ASF GitHub Bot commented on MNG-7561: - gnodet commented on PR #823: URL: https://github

[GitHub] [maven] gnodet commented on pull request #823: [MNG-7561] never resolve version ranges with same lower and upper bound

2022-10-13 Thread GitBox
gnodet commented on PR #823: URL: https://github.com/apache/maven/pull/823#issuecomment-125716 @michael-o @cstamas I'm trying to understand how this works. If the `VersionResolver` returns a `Set` for versions when given a range, and a single version when given a soft version, where is

[jira] [Updated] (MPLUGIN-424) Allow a maven-plugin to require a Java version

2022-10-13 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/MPLUGIN-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MPLUGIN-424: Description: Currently a Maven plugin can only require a minimum Maven version via pom's

[jira] [Created] (MPLUGIN-424) Allow a maven-plugin to require a Java version

2022-10-13 Thread Konrad Windszus (Jira)
Konrad Windszus created MPLUGIN-424: --- Summary: Allow a maven-plugin to require a Java version Key: MPLUGIN-424 URL: https://issues.apache.org/jira/browse/MPLUGIN-424 Project: Maven Plugin Tools

[jira] [Commented] (MRESOLVER-7) Download dependency POMs in parallel in BF collector

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617104#comment-17617104 ] ASF GitHub Bot commented on MRESOLVER-7: caiwei-ebay2 commented on PR #178: URL:

[GitHub] [maven-resolver] caiwei-ebay2 commented on pull request #178: [MRESOLVER-7] download poms in parallel

2022-10-13 Thread GitBox
caiwei-ebay2 commented on PR #178: URL: https://github.com/apache/maven-resolver/pull/178#issuecomment-1277725713 @michael-o How's everything? Got a chance to give more comments to this PR? And may I know what's the remaining steps to get this PR merged? -- This is an automated messag

[jira] [Commented] (MPLUGIN-418) Require prerequisites to be set for maven-plugin

2022-10-13 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/MPLUGIN-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617102#comment-17617102 ] Konrad Windszus commented on MPLUGIN-418: - The failure message should add a hint

[jira] [Commented] (MPLUGIN-423) Extract plugin report into its own plugin

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MPLUGIN-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617099#comment-17617099 ] ASF GitHub Bot commented on MPLUGIN-423: kwin commented on PR #147: URL: https:

[GitHub] [maven-plugin-tools] kwin commented on pull request #147: [MPLUGIN-423] Extract plugin report into its own plugin and deprecate the previous one

2022-10-13 Thread GitBox
kwin commented on PR #147: URL: https://github.com/apache/maven-plugin-tools/pull/147#issuecomment-1277712343 Please don't let me rewrite https://github.com/apache/maven-plugin-tools/pull/139. This PR conflicts with the other. Can we wait with this effort until #139 is merged? -- This i

[GitHub] [maven-mvnd] gzm55 opened a new pull request, #711: sync entry scripts with maven 3.8.6

2022-10-13 Thread GitBox
gzm55 opened a new pull request, #711: URL: https://github.com/apache/maven-mvnd/pull/711 The main change of the upstream scripts is removing the dependency of `which` command. This improve the portability. -- This is an automated message from the Apache Git Service. To respond to the mes

[jira] [Commented] (MNG-7106) VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds

2022-10-13 Thread Hudson (Jira)
[ https://issues.apache.org/jira/browse/MNG-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617092#comment-17617092 ] Hudson commented on MNG-7106: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #

[jira] [Commented] (MNG-7106) VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds

2022-10-13 Thread Hudson (Jira)
[ https://issues.apache.org/jira/browse/MNG-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617091#comment-17617091 ] Hudson commented on MNG-7106: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.

[jira] [Commented] (MNG-7561) DefaultVersionRangeResolver should not try to resolve request with same upper and lower bound

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617080#comment-17617080 ] ASF GitHub Bot commented on MNG-7561: - gnodet commented on PR #823: URL: https://github

[GitHub] [maven] gnodet commented on pull request #823: [MNG-7561] never resolve version ranges with same lower and upper bound

2022-10-13 Thread GitBox
gnodet commented on PR #823: URL: https://github.com/apache/maven/pull/823#issuecomment-1277663290 > > IMHO this PR is wrong, as commented on issue https://issues.apache.org/jira/browse/MNG-7561?focusedCommentId=17616329&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel

[jira] [Commented] (MNG-7561) DefaultVersionRangeResolver should not try to resolve request with same upper and lower bound

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617078#comment-17617078 ] ASF GitHub Bot commented on MNG-7561: - gnodet commented on code in PR #823: URL: https:

[GitHub] [maven] gnodet commented on a diff in pull request #823: [MNG-7561] never resolve version ranges with same lower and upper bound

2022-10-13 Thread GitBox
gnodet commented on code in PR #823: URL: https://github.com/apache/maven/pull/823#discussion_r994684855 ## maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionRangeResolver.java: ## @@ -111,28 +111,36 @@ public VersionRangeResult resolveVers

[GitHub] [maven-enforcer] kwin commented on a diff in pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
kwin commented on code in PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#discussion_r994654305 ## enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BanDynamicVersions.java: ## @@ -110,7 +117,8 @@ /** * Specify the ignored dependencies.

[GitHub] [maven-enforcer] kwin commented on a diff in pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
kwin commented on code in PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#discussion_r994654016 ## enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BanDynamicVersions.java: ## @@ -99,9 +100,15 @@ private boolean allowRanges; /** - *

[jira] [Updated] (MNG-7106) VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds

2022-10-13 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/MNG-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MNG-7106: - Fix Version/s: 4.0.0-alpha-1 > VersionRange.toString() produces a string that cannot be parsed with

[jira] [Resolved] (MNG-7106) VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds

2022-10-13 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/MNG-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved MNG-7106. -- Fix Version/s: 3.9.0 4.0.0 (was: 4.0.x-candidate)

[jira] [Commented] (MNG-7106) VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617057#comment-17617057 ] ASF GitHub Bot commented on MNG-7106: - kwin merged PR #826: URL: https://github.com/apa

[GitHub] [maven] kwin merged pull request #826: [MNG-7106] Maven 3.9 Accept same lower and upper bound in version spec string

2022-10-13 Thread GitBox
kwin merged PR #826: URL: https://github.com/apache/maven/pull/826 -- 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: issues-unsubscr...@maven.apache.org

[jira] [Commented] (MNG-7106) VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617056#comment-17617056 ] ASF GitHub Bot commented on MNG-7106: - kwin merged PR #825: URL: https://github.com/apa

[GitHub] [maven] kwin merged pull request #825: [MNG-7106] Accept same lower and upper bound in version spec string

2022-10-13 Thread GitBox
kwin merged PR #825: URL: https://github.com/apache/maven/pull/825 -- 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: issues-unsubscr...@maven.apache.org

[GitHub] [maven-enforcer] michael-o commented on a diff in pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
michael-o commented on code in PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#discussion_r994636938 ## enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BanDynamicVersions.java: ## @@ -110,7 +117,8 @@ /** * Specify the ignored dependenc

[GitHub] [maven-enforcer] michael-o commented on a diff in pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
michael-o commented on code in PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#discussion_r994635932 ## enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BanDynamicVersions.java: ## @@ -99,9 +100,15 @@ private boolean allowRanges; /** -

[jira] [Commented] (MNG-7106) VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617040#comment-17617040 ] ASF GitHub Bot commented on MNG-7106: - kwin opened a new pull request, #826: URL: https

[GitHub] [maven] kwin opened a new pull request, #826: [MNG-7106] Maven 3.9 Accept same lower and upper bound in version spec string

2022-10-13 Thread GitBox
kwin opened a new pull request, #826: URL: https://github.com/apache/maven/pull/826 Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG) filed for the chan

[jira] [Commented] (MPLUGIN-423) Extract plugin report into its own plugin

2022-10-13 Thread Guillaume Nodet (Jira)
[ https://issues.apache.org/jira/browse/MPLUGIN-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617035#comment-17617035 ] Guillaume Nodet commented on MPLUGIN-423: - I've closed the old one, given the PR

[jira] [Closed] (MPLUGIN-416) Move reporting to a separate plugin

2022-10-13 Thread Guillaume Nodet (Jira)
[ https://issues.apache.org/jira/browse/MPLUGIN-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MPLUGIN-416. --- Resolution: Duplicate > Move reporting to a separate plugin > --

[GitHub] [maven-enforcer] kwin commented on a diff in pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
kwin commented on code in PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#discussion_r994614655 ## enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BanDynamicVersions.java: ## @@ -0,0 +1,375 @@ +package org.apache.maven.plugins.enforcer; + +/* + * L

[GitHub] [maven-enforcer] kwin commented on a diff in pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
kwin commented on code in PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#discussion_r994614282 ## enforcer-rules/src/site/apt/banDynamicVersions.apt.vm: ## @@ -0,0 +1,108 @@ +~~ Licensed to the Apache Software Foundation (ASF) under one +~~ or more contributor l

[GitHub] [maven-enforcer] kwin commented on a diff in pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
kwin commented on code in PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#discussion_r994613781 ## enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BanDynamicVersions.java: ## @@ -0,0 +1,375 @@ +package org.apache.maven.plugins.enforcer; + +/* + * L

[jira] [Updated] (MNG-7565) Maven output out of order in windows

2022-10-13 Thread Vyom Yadav (Jira)
[ https://issues.apache.org/jira/browse/MNG-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyom Yadav updated MNG-7565: Description: Maven output is appearing out of order in windows. This may be related to maven or may be relat

[jira] [Updated] (MPLUGIN-423) Extract plugin report into its own plugin

2022-10-13 Thread Guillaume Nodet (Jira)
[ https://issues.apache.org/jira/browse/MPLUGIN-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MPLUGIN-423: Description: As noticed by [~michael-o] and [~ cstamas], the current plugin carries too mu

[jira] [Updated] (MPLUGIN-423) Extract plugin report into its own plugin

2022-10-13 Thread Guillaume Nodet (Jira)
[ https://issues.apache.org/jira/browse/MPLUGIN-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MPLUGIN-423: Description: As noticed by [~michael-o] and [~cstamas], the current plugin carries too muc

[jira] [Updated] (MNG-7565) Maven output out of order in windows

2022-10-13 Thread Vyom Yadav (Jira)
[ https://issues.apache.org/jira/browse/MNG-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyom Yadav updated MNG-7565: Environment: Apache Maven 3.8.6 Java version: 11.0.16.1, vendor: Azul Systems, Inc. Default locale: en_IN, pl

[GitHub] [maven-enforcer] kwin commented on a diff in pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
kwin commented on code in PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#discussion_r994613535 ## enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BanDynamicVersions.java: ## @@ -0,0 +1,375 @@ +package org.apache.maven.plugins.enforcer; + +/* + * L

[jira] [Updated] (MNG-7565) Maven output out of order in windows

2022-10-13 Thread Vyom Yadav (Jira)
[ https://issues.apache.org/jira/browse/MNG-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyom Yadav updated MNG-7565: Description: Maven output is appearing out of order in windows. This may be related to maven or may be relat

[jira] [Created] (MNG-7565) Maven output out of order in windows

2022-10-13 Thread Vyom Yadav (Jira)
Vyom Yadav created MNG-7565: --- Summary: Maven output out of order in windows Key: MNG-7565 URL: https://issues.apache.org/jira/browse/MNG-7565 Project: Maven Issue Type: Bug Components: Lo

[jira] [Assigned] (MINDEXER-141) Align tests to one provider

2022-10-13 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MINDEXER-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MINDEXER-141: Assignee: Tamas Cservenak > Align tests to one provider > --

[GitHub] [maven-indexer] cstamas opened a new pull request, #252: [MINDEXER-141] Align all tests on Junit4 for now

2022-10-13 Thread GitBox
cstamas opened a new pull request, #252: URL: https://github.com/apache/maven-indexer/pull/252 As this is simplest, sisu offers InjectedTest that is Junit4 and we will see later where from here (or how to Junit5 from here). There is a LOT of old plexus/junit3 remnants that needs cleanup.

[GitHub] [maven-enforcer] michael-o commented on a diff in pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
michael-o commented on code in PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#discussion_r994577941 ## enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BanDynamicVersions.java: ## @@ -0,0 +1,375 @@ +package org.apache.maven.plugins.enforcer; + +/*

[GitHub] [maven-enforcer] kwin commented on a diff in pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
kwin commented on code in PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#discussion_r994571730 ## enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BanDynamicVersions.java: ## @@ -0,0 +1,375 @@ +package org.apache.maven.plugins.enforcer; + +/* + * L

[GitHub] [maven-enforcer] kwin commented on a diff in pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
kwin commented on code in PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#discussion_r994571477 ## enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BanDynamicVersions.java: ## @@ -0,0 +1,375 @@ +package org.apache.maven.plugins.enforcer; + +/* + * L

[jira] [Updated] (SUREFIRE-2120) Surefire report is not produced with test name when using JUnit5 and Specs2

2022-10-13 Thread Anatoly (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anatoly updated SUREFIRE-2120: -- Description: Hi, When running tests from terminal via 'mvn clean test' command, the generated sure

[jira] [Updated] (SUREFIRE-2120) Surefire report is not produced with test name when using JUnit5 and Specs2

2022-10-13 Thread Anatoly (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anatoly updated SUREFIRE-2120: -- Description: Hi, When running tests from terminal via 'mvn clean test' command, the generated sure

[jira] [Updated] (SUREFIRE-2120) Surefire report is not produced with test name when using JUnit5 and Specs2

2022-10-13 Thread Anatoly (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anatoly updated SUREFIRE-2120: -- Description: Hi, When running tests from terminal via 'mvn clean test' command, the generated sure

[jira] [Updated] (SUREFIRE-2120) Surefire report is not produced with test name when using JUnit5 and Specs2

2022-10-13 Thread Anatoly (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anatoly updated SUREFIRE-2120: -- Description: Hi, When running tests from terminal via 'mvn clean test' command, the generated sure

[jira] [Updated] (SUREFIRE-2120) Surefire report is not produced with test name when using JUnit5 and Specs2

2022-10-13 Thread Anatoly (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anatoly updated SUREFIRE-2120: -- Description: Hi, When running tests from terminal via 'mvn clean test' command, the generated sure

[jira] [Updated] (MNG-7564) Potential NPE in MavenMetadataSource

2022-10-13 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MNG-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7564: Description: In here: https://github.com/apache/maven/blob/cb54aa429d9e63bf78c4c808898fbef1cc01ff33/

[jira] [Created] (SUREFIRE-2120) Surefire report is not produced with test name when using JUnit5 and Specs2

2022-10-13 Thread Anatoly (Jira)
Anatoly created SUREFIRE-2120: - Summary: Surefire report is not produced with test name when using JUnit5 and Specs2 Key: SUREFIRE-2120 URL: https://issues.apache.org/jira/browse/SUREFIRE-2120 Project: Ma

[jira] [Created] (MNG-7564) Potential NPE in MavenMetadataSource

2022-10-13 Thread Michael Osipov (Jira)
Michael Osipov created MNG-7564: --- Summary: Potential NPE in MavenMetadataSource Key: MNG-7564 URL: https://issues.apache.org/jira/browse/MNG-7564 Project: Maven Issue Type: Bug Repo

[jira] [Commented] (MINDEXER-169) Drop Wagon legacy transport

2022-10-13 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MINDEXER-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616987#comment-17616987 ] Michael Osipov commented on MINDEXER-169: - I guess the HTTP transport is used f

[jira] [Commented] (MSITE-911) site:attach-descriptor should also attach resources

2022-10-13 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MSITE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616984#comment-17616984 ] Michael Osipov commented on MSITE-911: -- Guess what: https://github.com/michael-o/mic

[jira] [Commented] (MSHADE-426) Shade remap chokes on Multi-Release-JARs prepped to support Java 19

2022-10-13 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MSHADE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616985#comment-17616985 ] Michael Osipov commented on MSHADE-426: --- A, yet another ASM upgrade waiting...

[GitHub] [maven-enforcer] michael-o commented on pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
michael-o commented on PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#issuecomment-1277474671 > > I think it is parsed to [1.0,1.0] then of course it incurs resolution. > > This is totally unexpected because `1.0` (soft requirement) is not resolved, see also my commen

[GitHub] [maven-enforcer] michael-o commented on a diff in pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
michael-o commented on code in PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#discussion_r994532503 ## enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BanDynamicVersions.java: ## @@ -0,0 +1,375 @@ +package org.apache.maven.plugins.enforcer; + +/*

[GitHub] [maven-enforcer] gnodet commented on a diff in pull request #187: [MENFORCER-427] New rule to ban dynamic versions

2022-10-13 Thread GitBox
gnodet commented on code in PR #187: URL: https://github.com/apache/maven-enforcer/pull/187#discussion_r994513017 ## enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BanDynamicVersions.java: ## @@ -0,0 +1,375 @@ +package org.apache.maven.plugins.enforcer; + +/* + *

[jira] [Commented] (MNG-7106) VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616970#comment-17616970 ] ASF GitHub Bot commented on MNG-7106: - michael-o commented on code in PR #825: URL: htt

[GitHub] [maven] michael-o commented on a diff in pull request #825: [MNG-7106] Accept same lower and upper bound in version spec string

2022-10-13 Thread GitBox
michael-o commented on code in PR #825: URL: https://github.com/apache/maven/pull/825#discussion_r994515136 ## maven-artifact/src/main/java/org/apache/maven/artifact/versioning/VersionRange.java: ## @@ -227,9 +223,13 @@ private static Restriction parseRestriction( String spec )

[jira] [Commented] (MNG-7106) VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616969#comment-17616969 ] ASF GitHub Bot commented on MNG-7106: - kwin commented on code in PR #825: URL: https://

[GitHub] [maven] kwin commented on a diff in pull request #825: [MNG-7106] Accept same lower and upper bound in version spec string

2022-10-13 Thread GitBox
kwin commented on code in PR #825: URL: https://github.com/apache/maven/pull/825#discussion_r994514644 ## maven-artifact/src/main/java/org/apache/maven/artifact/versioning/VersionRange.java: ## @@ -227,9 +223,13 @@ private static Restriction parseRestriction( String spec )

[jira] [Commented] (MNG-7106) VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616966#comment-17616966 ] ASF GitHub Bot commented on MNG-7106: - michael-o commented on PR #825: URL: https://git

[GitHub] [maven] michael-o commented on pull request #825: [MNG-7106] Accept same lower and upper bound in version spec string

2022-10-13 Thread GitBox
michael-o commented on PR #825: URL: https://github.com/apache/maven/pull/825#issuecomment-1277448785 > > Should we backport to 3.9? > > I think so. I agree with that as well. -- This is an automated message from the Apache Git Service. To respond to the message, please log o

[jira] [Commented] (MNG-7106) VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616964#comment-17616964 ] ASF GitHub Bot commented on MNG-7106: - michael-o commented on code in PR #825: URL: htt

[GitHub] [maven] michael-o commented on a diff in pull request #825: [MNG-7106] Accept same lower and upper bound in version spec string

2022-10-13 Thread GitBox
michael-o commented on code in PR #825: URL: https://github.com/apache/maven/pull/825#discussion_r994512882 ## maven-artifact/src/main/java/org/apache/maven/artifact/versioning/VersionRange.java: ## @@ -227,9 +223,13 @@ private static Restriction parseRestriction( String spec )

[jira] [Commented] (MNG-7561) DefaultVersionRangeResolver should not try to resolve request with same upper and lower bound

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616962#comment-17616962 ] ASF GitHub Bot commented on MNG-7561: - michael-o commented on PR #823: URL: https://git

[GitHub] [maven] michael-o commented on pull request #823: [MNG-7561] never resolve version ranges with same lower and upper bound

2022-10-13 Thread GitBox
michael-o commented on PR #823: URL: https://github.com/apache/maven/pull/823#issuecomment-1277446298 > IMHO this PR is wrong, as commented on issue https://issues.apache.org/jira/browse/MNG-7561?focusedCommentId=17616329&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpane

[jira] [Commented] (MNG-7106) VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds

2022-10-13 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616960#comment-17616960 ] ASF GitHub Bot commented on MNG-7106: - kwin commented on PR #825: URL: https://github.c

[jira] [Comment Edited] (MNG-7561) DefaultVersionRangeResolver should not try to resolve request with same upper and lower bound

2022-10-13 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MNG-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616331#comment-17616331 ] Michael Osipov edited comment on MNG-7561 at 10/13/22 11:15 AM: -

[GitHub] [maven] kwin commented on pull request #825: [MNG-7106] Accept same lower and upper bound in version spec string

2022-10-13 Thread GitBox
kwin commented on PR #825: URL: https://github.com/apache/maven/pull/825#issuecomment-1277444265 > Can you also add a test which cases the new exception? There is one exception less, not one more ;-) and I added a unit test for that: https://github.com/apache/maven/pull/825/files#dif

[jira] [Updated] (MNG-7106) VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds

2022-10-13 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MNG-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7106: Fix Version/s: 3.9.0-candidate 4.0.x-candidate > VersionRange.toString() produces

  1   2   >