[jira] [Comment Edited] (MJAVADOC-728) Dependencies not resolved for aggregate-jar

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/MJAVADOC-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17691490#comment-17691490 ] Martin Höller edited comment on MJAVADOC-728 at 11/7/23 7:09 AM: -

[jira] [Comment Edited] (MJAVADOC-728) Dependencies not resolved for aggregate-jar

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/MJAVADOC-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17691490#comment-17691490 ] Martin Höller edited comment on MJAVADOC-728 at 11/7/23 7:08 AM: -

[jira] [Comment Edited] (MJAVADOC-728) Dependencies not resolved for aggregate-jar

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/MJAVADOC-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17691490#comment-17691490 ] Martin Höller edited comment on MJAVADOC-728 at 11/7/23 7:07 AM: -

[jira] [Comment Edited] (MJAVADOC-728) Dependencies not resolved for aggregate-jar

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/MJAVADOC-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17691490#comment-17691490 ] Martin Höller edited comment on MJAVADOC-728 at 11/7/23 7:07 AM: -

[jira] [Comment Edited] (MJAVADOC-728) Dependencies not resolved for aggregate-jar

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/MJAVADOC-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17691490#comment-17691490 ] Martin Höller edited comment on MJAVADOC-728 at 11/7/23 7:07 AM: -

[jira] [Commented] (MJAVADOC-728) Dependencies not resolved for aggregate-jar

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/MJAVADOC-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783511#comment-17783511 ] Martin Höller commented on MJAVADOC-728: Still same (buggy) behavior with

[PR] Change bootstrap syntax to align with the usual one [maven-integration-testing]

2023-11-06 Thread via GitHub
gnodet opened a new pull request, #316: URL: https://github.com/apache/maven-integration-testing/pull/316 (no comment) -- 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

[jira] [Commented] (MSHARED-1327) Change output directory default in AbstractMavenReport

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MSHARED-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783407#comment-17783407 ] ASF GitHub Bot commented on MSHARED-1327: - kriegaex commented on PR #26: URL:

Re: [PR] [MSHARED-1327] Change output directory default [maven-reporting-impl]

2023-11-06 Thread via GitHub
kriegaex commented on PR #26: URL: https://github.com/apache/maven-reporting-impl/pull/26#issuecomment-1797056331 > would you keep it in the build output dir directory? What is your opinion on the clutter? My use case with AspectJ reporting is a multi-page report, for which always

[PR] Bump junitVersion from 5.10.0 to 5.10.1 [maven-doxia-sitetools]

2023-11-06 Thread via GitHub
dependabot[bot] opened a new pull request, #117: URL: https://github.com/apache/maven-doxia-sitetools/pull/117 Bumps `junitVersion` from 5.10.0 to 5.10.1. Updates `org.junit.jupiter:junit-jupiter-api` from 5.10.0 to 5.10.1 Release notes Sourced from

[PR] Bump org.junit.jupiter:junit-jupiter-api from 5.10.0 to 5.10.1 [maven-dependency-tree]

2023-11-06 Thread via GitHub
dependabot[bot] opened a new pull request, #41: URL: https://github.com/apache/maven-dependency-tree/pull/41 Bumps [org.junit.jupiter:junit-jupiter-api](https://github.com/junit-team/junit5) from 5.10.0 to 5.10.1. Release notes Sourced from

[jira] [Commented] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783397#comment-17783397 ] ASF GitHub Bot commented on MNG-7909: - cstamas commented on PR #1282: URL:

Re: [PR] [MNG-7909] Upgrade to Resolver 2.0.0-alpha-1 [maven]

2023-11-06 Thread via GitHub
cstamas commented on PR #1282: URL: https://github.com/apache/maven/pull/1282#issuecomment-1796964259 > Wasn't this one solved by #893 ? WILL be solved when merged, yes :smile: -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

[jira] [Commented] (MNGSITE-527) broken link to settings-1.3.0.xsd

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNGSITE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783396#comment-17783396 ] ASF GitHub Bot commented on MNGSITE-527: gnodet commented on PR #464: URL:

Re: [PR] MNGSITE-527 broken link to settings-1.3.0.xsd [maven-site]

2023-11-06 Thread via GitHub
gnodet commented on PR #464: URL: https://github.com/apache/maven-site/pull/464#issuecomment-1796960251 I'm slightly worried about publishing unstable XSDs. This may cause problem is the next 4.0.0 alpha/beta/milestone release does actually change it. Users may have the schema cached by

[jira] [Commented] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783392#comment-17783392 ] ASF GitHub Bot commented on MNG-7909: - gnodet commented on PR #1282: URL:

Re: [PR] [MNG-7909] Upgrade to Resolver 2.0.0-alpha-1 [maven]

2023-11-06 Thread via GitHub
gnodet commented on PR #1282: URL: https://github.com/apache/maven/pull/1282#issuecomment-1796850539 > * we know about MavenITmng5669ReadPomsOnce, there is issue in model builder when using MT collector (and resolver 2.0.0 makes BF default that is MT) Wasn't this one solved by #893 ?

[jira] [Commented] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783391#comment-17783391 ] ASF GitHub Bot commented on MNG-7909: - cstamas commented on PR #1282: URL:

Re: [PR] MNGSITE-527 broken link to settings-1.3.0.xsd [maven-site]

2023-11-06 Thread via GitHub
gnodet commented on PR #464: URL: https://github.com/apache/maven-site/pull/464#issuecomment-1796832812 The `plugin-[version].xsd` schemas are currently not published, so don't bother with those. -- This is an automated message from the Apache Git Service. To respond to the message,

Re: [PR] [MNG-7909] Upgrade to Resolver 2.0.0-alpha-1 [maven]

2023-11-06 Thread via GitHub
cstamas commented on PR #1282: URL: https://github.com/apache/maven/pull/1282#issuecomment-1796837365 On Java 11 IT failures are: ``` Error: Failures: Error:

[jira] [Commented] (MNGSITE-527) broken link to settings-1.3.0.xsd

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNGSITE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783390#comment-17783390 ] ASF GitHub Bot commented on MNGSITE-527: gnodet commented on PR #464: URL:

[PR] Bump org.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.0 [maven-dependency-plugin]

2023-11-06 Thread via GitHub
dependabot[bot] opened a new pull request, #348: URL: https://github.com/apache/maven-dependency-plugin/pull/348 Bumps [org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) from 4.8.0 to 4.9.0. Release notes Sourced from

[jira] [Commented] (MNGSITE-527) broken link to settings-1.3.0.xsd

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNGSITE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783386#comment-17783386 ] ASF GitHub Bot commented on MNGSITE-527: gnodet commented on PR #464: URL:

Re: [PR] MNGSITE-527 broken link to settings-1.3.0.xsd [maven-site]

2023-11-06 Thread via GitHub
gnodet commented on PR #464: URL: https://github.com/apache/maven-site/pull/464#issuecomment-1796639967 The two missing XSDs should now be available by building maven master branch. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

[jira] [Updated] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1

2023-11-06 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7909: - Fix Version/s: 4.0.0-alpha-9 (was: 4.0.x-candidate) > Upgrade to Resolver

[jira] [Assigned] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1

2023-11-06 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-7909: Assignee: Tamas Cservenak > Upgrade to Resolver 2.0.0-alpha-1 >

[jira] [Updated] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1

2023-11-06 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7909: - Description: Post alpha-8 a release of Resolver 2.0.0-alpha-1 (depending on other work, like

[jira] [Updated] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1

2023-11-06 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7909: - Summary: Upgrade to Resolver 2.0.0-alpha-1 (was: Upgrade to Resolver 2.0.0) > Upgrade to Resolver

[jira] [Commented] (MSHARED-1327) Change output directory default in AbstractMavenReport

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MSHARED-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783382#comment-17783382 ] ASF GitHub Bot commented on MSHARED-1327: - michael-o commented on PR #26: URL:

Re: [PR] [MSHARED-1327] Change output directory default [maven-reporting-impl]

2023-11-06 Thread via GitHub
michael-o commented on PR #26: URL: https://github.com/apache/maven-reporting-impl/pull/26#issuecomment-1796462318 @kriegaex I have rebased this PR. Here is the output when there is no subdir: ``` D:\Entwicklung\Projekte\maven-reporting-impl [patch-1 ≡ +2 ~0 -0 !]> ls

[jira] [Closed] (MSHARED-1326) Improve (documentation on) MavenReport interface/AbstractMavenReport class

2023-11-06 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MSHARED-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1326. --- Resolution: Fixed Fixed with

[jira] [Commented] (MSHARED-1326) Improve (documentation on) MavenReport interface/AbstractMavenReport class

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MSHARED-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783373#comment-17783373 ] ASF GitHub Bot commented on MSHARED-1326: - asfgit closed pull request #25: [MSHARED-1326]

Re: [PR] [MSHARED-1326] Improve (documentation on) AbstractMavenReport class [maven-reporting-impl]

2023-11-06 Thread via GitHub
asfgit closed pull request #25: [MSHARED-1326] Improve (documentation on) AbstractMavenReport class URL: https://github.com/apache/maven-reporting-impl/pull/25 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

[jira] [Commented] (MSHARED-1326) Improve (documentation on) MavenReport interface/AbstractMavenReport class

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MSHARED-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783371#comment-17783371 ] ASF GitHub Bot commented on MSHARED-1326: - asfgit closed pull request #19: [MSHARED-1326]

Re: [PR] [MSHARED-1326] Improve (documentation on) MavenReport interface [maven-reporting-api]

2023-11-06 Thread via GitHub
asfgit closed pull request #19: [MSHARED-1326] Improve (documentation on) MavenReport interface URL: https://github.com/apache/maven-reporting-api/pull/19 -- 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

[jira] [Commented] (MRESOLVER-426) Move some HTTP configuration properties from transport-http

2023-11-06 Thread Slawomir Jaranowski (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783364#comment-17783364 ] Slawomir Jaranowski commented on MRESOLVER-426: --- We should consider to easy use common

Re: [PR] Use 4.0.99 as as intermediate model to keep 4.1.0 for the Maven 4.x model [maven]

2023-11-06 Thread via GitHub
cstamas commented on code in PR #1297: URL: https://github.com/apache/maven/pull/1297#discussion_r1383907491 ## api/maven-api-model/src/main/mdo/maven.mdo: ## @@ -387,7 +388,7 @@ - 4.0.0/4.1.0 + 4.0.0/4.0.99 Review Comment: Sadly,

Re: [PR] Use 4.0.99 as as intermediate model to keep 4.1.0 for the Maven 4.x model [maven]

2023-11-06 Thread via GitHub
kwin commented on code in PR #1297: URL: https://github.com/apache/maven/pull/1297#discussion_r1383904826 ## api/maven-api-model/src/main/mdo/maven.mdo: ## @@ -387,7 +388,7 @@ - 4.0.0/4.1.0 + 4.0.0/4.0.99 Review Comment: Ah,

[PR] Bump org.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.0 [maven-archiver]

2023-11-06 Thread via GitHub
dependabot[bot] opened a new pull request, #44: URL: https://github.com/apache/maven-archiver/pull/44 Bumps [org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) from 4.8.0 to 4.9.0. Release notes Sourced from

[PR] Bump org.junit:junit-bom from 5.10.0 to 5.10.1 [maven-archiver]

2023-11-06 Thread via GitHub
dependabot[bot] opened a new pull request, #43: URL: https://github.com/apache/maven-archiver/pull/43 Bumps [org.junit:junit-bom](https://github.com/junit-team/junit5) from 5.10.0 to 5.10.1. Release notes Sourced from

Re: [PR] Use 4.0.99 as as intermediate model to keep 4.1.0 for the Maven 4.x model [maven]

2023-11-06 Thread via GitHub
gnodet commented on code in PR #1297: URL: https://github.com/apache/maven/pull/1297#discussion_r1383873531 ## api/maven-api-model/src/main/mdo/maven.mdo: ## @@ -387,7 +388,7 @@ - 4.0.0/4.1.0 + 4.0.0/4.0.99 Review Comment: This is

Re: [PR] Use 4.0.99 as as intermediate model to keep 4.1.0 for the Maven 4.x model [maven]

2023-11-06 Thread via GitHub
kwin commented on code in PR #1297: URL: https://github.com/apache/maven/pull/1297#discussion_r1383859037 ## api/maven-api-model/src/main/mdo/maven.mdo: ## @@ -387,7 +388,7 @@ - 4.0.0/4.1.0 + 4.0.0/4.0.99 Review Comment: @gnodet

Re: [PR] Bump org.junit:junit-bom from 5.9.3 to 5.10.0 [maven-surefire]

2023-11-06 Thread via GitHub
dependabot[bot] closed pull request #679: Bump org.junit:junit-bom from 5.9.3 to 5.10.0 URL: https://github.com/apache/maven-surefire/pull/679 -- 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

Re: [PR] Bump org.junit:junit-bom from 5.9.3 to 5.10.0 [maven-surefire]

2023-11-06 Thread via GitHub
dependabot[bot] commented on PR #679: URL: https://github.com/apache/maven-surefire/pull/679#issuecomment-1796041223 Superseded by #685. -- 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

[PR] Bump org.junit:junit-bom from 5.9.3 to 5.10.1 [maven-surefire]

2023-11-06 Thread via GitHub
dependabot[bot] opened a new pull request, #685: URL: https://github.com/apache/maven-surefire/pull/685 Bumps [org.junit:junit-bom](https://github.com/junit-team/junit5) from 5.9.3 to 5.10.1. Release notes Sourced from

Re: [PR] Use 4.0.99 as as intermediate model to keep 4.1.0 for the Maven 4.x model [maven]

2023-11-06 Thread via GitHub
gnodet merged PR #1297: URL: https://github.com/apache/maven/pull/1297 -- 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] [Updated] (MANTRUN-239) Update parent pom to 40

2023-11-06 Thread Sylwester Lachiewicz (Jira)
[ https://issues.apache.org/jira/browse/MANTRUN-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MANTRUN-239: - Summary: Update parent pom to 40 (was: Update parent pom to 39) > Update

[jira] [Commented] (MANTRUN-239) Update parent pom to 39

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MANTRUN-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783339#comment-17783339 ] ASF GitHub Bot commented on MANTRUN-239: slachiewicz merged PR #88: URL:

Re: [PR] [MANTRUN-239] Upgrade parent pom to 40 [maven-antrun-plugin]

2023-11-06 Thread via GitHub
slachiewicz merged PR #88: URL: https://github.com/apache/maven-antrun-plugin/pull/88 -- 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] (MANTRUN-241) Update junit to 5.10.1

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MANTRUN-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783335#comment-17783335 ] ASF GitHub Bot commented on MANTRUN-241: slachiewicz merged PR #89: URL:

[jira] [Closed] (MANTRUN-241) Update junit to 5.10.1

2023-11-06 Thread Sylwester Lachiewicz (Jira)
[ https://issues.apache.org/jira/browse/MANTRUN-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MANTRUN-241. Assignee: Sylwester Lachiewicz Resolution: Fixed > Update junit to 5.10.1 >

Re: [PR] [MANTRUN-241] Bump org.junit.jupiter:junit-jupiter-engine to 5.10.1 [maven-antrun-plugin]

2023-11-06 Thread via GitHub
slachiewicz merged PR #89: URL: https://github.com/apache/maven-antrun-plugin/pull/89 -- 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:

Re: [PR] Bump xmlunit-matchers from 2.9.0 to 2.9.1 [maven-antrun-plugin]

2023-11-06 Thread via GitHub
elharo merged PR #83: URL: https://github.com/apache/maven-antrun-plugin/pull/83 -- 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:

Re: [PR] Bump xmlunit-core from 2.9.0 to 2.9.1 [maven-antrun-plugin]

2023-11-06 Thread via GitHub
elharo merged PR #84: URL: https://github.com/apache/maven-antrun-plugin/pull/84 -- 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:

Re: [PR] Bump xmlunit-matchers from 2.9.0 to 2.9.1 [maven-antrun-plugin]

2023-11-06 Thread via GitHub
slachiewicz commented on PR #83: URL: https://github.com/apache/maven-antrun-plugin/pull/83#issuecomment-1795800107 @dependabot rebase -- 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

[jira] [Commented] (MANTRUN-241) Update junit to 5.10.1

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MANTRUN-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783321#comment-17783321 ] ASF GitHub Bot commented on MANTRUN-241: slachiewicz opened a new pull request, #89: URL:

Re: [PR] Bump xmlunit-core from 2.9.0 to 2.9.1 [maven-antrun-plugin]

2023-11-06 Thread via GitHub
slachiewicz commented on PR #84: URL: https://github.com/apache/maven-antrun-plugin/pull/84#issuecomment-1795798951 @dependabot rebase -- 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

[jira] [Commented] (MANTRUN-239) Update parent pom to 39

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MANTRUN-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783320#comment-17783320 ] ASF GitHub Bot commented on MANTRUN-239: slachiewicz opened a new pull request, #88: URL:

[jira] [Created] (MANTRUN-241) Update junit to 5.10.1

2023-11-06 Thread Sylwester Lachiewicz (Jira)
Sylwester Lachiewicz created MANTRUN-241: Summary: Update junit to 5.10.1 Key: MANTRUN-241 URL: https://issues.apache.org/jira/browse/MANTRUN-241 Project: Maven Antrun Plugin Issue

[jira] [Commented] (MRESOLVER-428) Handle differently the "memoized HTTP 404" cached responses

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/MRESOLVER-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783301#comment-17783301 ] Christoph Läubrich commented on MRESOLVER-428: -- I just wanted to add a real use case

Re: [PR] Bump org.junit.jupiter:junit-jupiter-engine from 5.9.1 to 5.10.0 [maven-antrun-plugin]

2023-11-06 Thread via GitHub
dependabot[bot] commented on PR #86: URL: https://github.com/apache/maven-antrun-plugin/pull/86#issuecomment-1795613407 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor

Re: [PR] Bump org.junit.jupiter:junit-jupiter-engine from 5.9.1 to 5.10.0 [maven-antrun-plugin]

2023-11-06 Thread via GitHub
slachiewicz closed pull request #86: Bump org.junit.jupiter:junit-jupiter-engine from 5.9.1 to 5.10.0 URL: https://github.com/apache/maven-antrun-plugin/pull/86 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

[jira] [Commented] (MRESOLVER-428) Handle differently the "memoized HTTP 404" cached responses

2023-11-06 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783298#comment-17783298 ] Tamas Cservenak commented on MRESOLVER-428: --- I would leave out the "not yet synced to

[jira] [Commented] (MRESOLVER-428) Handle differently the "memoized HTTP 404" cached responses

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/MRESOLVER-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783293#comment-17783293 ] Christoph Läubrich commented on MRESOLVER-428: -- Would be great if such a 404 is simply

[jira] [Created] (MRESOLVER-428) Handle differently the "memoized HTTP 404" cached responses

2023-11-06 Thread Tamas Cservenak (Jira)
Tamas Cservenak created MRESOLVER-428: - Summary: Handle differently the "memoized HTTP 404" cached responses Key: MRESOLVER-428 URL: https://issues.apache.org/jira/browse/MRESOLVER-428 Project:

[jira] [Created] (MRESOLVER-427) Expose configuration for inhibiting Expect-Continue handshake

2023-11-06 Thread Tamas Cservenak (Jira)
Tamas Cservenak created MRESOLVER-427: - Summary: Expose configuration for inhibiting Expect-Continue handshake Key: MRESOLVER-427 URL: https://issues.apache.org/jira/browse/MRESOLVER-427 Project:

[jira] [Created] (MRESOLVER-426) Move some HTTP configuration properties from transport-http

2023-11-06 Thread Tamas Cservenak (Jira)
Tamas Cservenak created MRESOLVER-426: - Summary: Move some HTTP configuration properties from transport-http Key: MRESOLVER-426 URL: https://issues.apache.org/jira/browse/MRESOLVER-426 Project:

Re: [PR] Change build pom naming from xxx-build.pom to xxx-build-pom.xml [maven]

2023-11-06 Thread via GitHub
gnodet commented on PR #1298: URL: https://github.com/apache/maven/pull/1298#issuecomment-1795431208 > > > This does not look wrong. What is the motivation behind this? > > > > > > The problem seems to be that sonatype oss release validation fail staging repositories deployed

[PR] Bump org.junit:junit-bom from 5.10.0 to 5.10.1 [maven-enforcer]

2023-11-06 Thread via GitHub
dependabot[bot] opened a new pull request, #296: URL: https://github.com/apache/maven-enforcer/pull/296 Bumps [org.junit:junit-bom](https://github.com/junit-team/junit5) from 5.10.0 to 5.10.1. Release notes Sourced from

[jira] [Updated] (SCM-1014) Enable scm changelog on files for svnexe provider

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/SCM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Quoß updated SCM-1014: -- Description: When using the maven scm changelog command in our custom maven release manager phases

[jira] [Updated] (SCM-1014) Enable scm changelog on files for svnexe provider

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/SCM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Quoß updated SCM-1014: -- Affects Version/s: 2.0.1 > Enable scm changelog on files for svnexe provider >

[jira] [Updated] (SCM-1014) Enable scm changelog on files for svnexe provider

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/SCM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Quoß updated SCM-1014: -- Component/s: maven-scm-provider-svn > Enable scm changelog on files for svnexe provider >

[jira] [Updated] (SCM-1014) Enable scm changelog on files for svnexe provider

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/SCM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Quoß updated SCM-1014: -- Priority: Minor (was: Major) > Enable scm changelog on files for svnexe provider >

[jira] [Updated] (SCM-1014) Enable scm changelog on files for svnexe provider

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/SCM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Quoß updated SCM-1014: -- Description: When using the maven scm changelog command in our custom maven release manager phases

[jira] [Updated] (SCM-1014) Enable scm changelog on files for svnexe provider

2023-11-06 Thread Jira
[ https://issues.apache.org/jira/browse/SCM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Quoß updated SCM-1014: -- Description: When using the maven scm changelog command in our custom maven release manager phases

[jira] [Created] (SCM-1014) Enable scm changelog on files for svnexe provider

2023-11-06 Thread Jira
Clemens Quoß created SCM-1014: - Summary: Enable scm changelog on files for svnexe provider Key: SCM-1014 URL: https://issues.apache.org/jira/browse/SCM-1014 Project: Maven SCM Issue Type:

[jira] [Updated] (MSITE-988) Documentation

2023-11-06 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MSITE-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSITE-988: - Fix Version/s: 4.0.0-M12 > Documentation > - > > Key: MSITE-988 >

[jira] [Assigned] (MSITE-988) Documentation

2023-11-06 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MSITE-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MSITE-988: Assignee: Michael Osipov > Documentation > - > > Key:

Re: [PR] Bump org.junit.jupiter:junit-jupiter-engine from 5.9.1 to 5.10.0 [maven-antrun-plugin]

2023-11-06 Thread via GitHub
dependabot[bot] commented on PR #86: URL: https://github.com/apache/maven-antrun-plugin/pull/86#issuecomment-1794860869 A newer version of org.junit.jupiter:junit-jupiter-engine exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a

[PR] Bump org.junit:junit-bom from 5.10.0 to 5.10.1 [maven-plugin-tools]

2023-11-06 Thread via GitHub
dependabot[bot] opened a new pull request, #238: URL: https://github.com/apache/maven-plugin-tools/pull/238 Bumps [org.junit:junit-bom](https://github.com/junit-team/junit5) from 5.10.0 to 5.10.1. Release notes Sourced from

[PR] Bump org.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.0 [maven-plugin-tools]

2023-11-06 Thread via GitHub
dependabot[bot] opened a new pull request, #237: URL: https://github.com/apache/maven-plugin-tools/pull/237 Bumps [org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) from 4.8.0 to 4.9.0. Release notes Sourced from

Re: [PR] Use 4.0.0-alpha-8 instead of SNAPSHOT [maven-integration-testing]

2023-11-06 Thread via GitHub
gnodet merged PR #315: URL: https://github.com/apache/maven-integration-testing/pull/315 -- 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:

Re: [PR] Use 4.0.0-alpha-8 instead of SNAPSHOT [maven-integration-testing]

2023-11-06 Thread via GitHub
gnodet commented on code in PR #315: URL: https://github.com/apache/maven-integration-testing/pull/315#discussion_r1383274777 ## core-it-suite/src/test/resources-filtered/bootstrap.txt: ## @@ -18,6 +18,8 @@ org.apache.commons:commons-text:1.10.0

Re: [PR] Use 4.0.0-alpha-8 instead of SNAPSHOT [maven-integration-testing]

2023-11-06 Thread via GitHub
gnodet commented on code in PR #315: URL: https://github.com/apache/maven-integration-testing/pull/315#discussion_r1383274777 ## core-it-suite/src/test/resources-filtered/bootstrap.txt: ## @@ -18,6 +18,8 @@ org.apache.commons:commons-text:1.10.0

Re: [PR] Use 4.0.0-alpha-8 instead of SNAPSHOT [maven-integration-testing]

2023-11-06 Thread via GitHub
slawekjaranowski commented on code in PR #315: URL: https://github.com/apache/maven-integration-testing/pull/315#discussion_r1383269705 ## core-it-suite/src/test/resources-filtered/bootstrap.txt: ## @@ -18,6 +18,8 @@ org.apache.commons:commons-text:1.10.0

[jira] [Created] (MSITE-988) Documentation

2023-11-06 Thread Ernst Reissner (Jira)
Ernst Reissner created MSITE-988: Summary: Documentation Key: MSITE-988 URL: https://issues.apache.org/jira/browse/MSITE-988 Project: Maven Site Plugin Issue Type: Bug Components:

[jira] [Commented] (MNG-5695) inconsistent custom Guice scope bindings

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783204#comment-17783204 ] ASF GitHub Bot commented on MNG-5695: - cstamas commented on code in PR #236: URL:

Re: [PR] [MNG-5695] document Maven 3.2.5+ scoped components usage [maven-plugin-tools]

2023-11-06 Thread via GitHub
cstamas commented on code in PR #236: URL: https://github.com/apache/maven-plugin-tools/pull/236#discussion_r1383237666 ## maven-plugin-tools-annotations/src/site/apt/index.apt: ## @@ -94,27 +94,42 @@ public class MyMojo hint = "..." ) private MyComponent

[PR] Bump junitVersion from 5.10.0 to 5.10.1 [maven-doxia]

2023-11-06 Thread via GitHub
dependabot[bot] opened a new pull request, #178: URL: https://github.com/apache/maven-doxia/pull/178 Bumps `junitVersion` from 5.10.0 to 5.10.1. Updates `org.junit.jupiter:junit-jupiter-api` from 5.10.0 to 5.10.1 Release notes Sourced from

Re: [PR] Use 4.0.0-alpha-8 instead of SNAPSHOT [maven-integration-testing]

2023-11-06 Thread via GitHub
gnodet commented on PR #315: URL: https://github.com/apache/maven-integration-testing/pull/315#issuecomment-1794672092 > Should we also add to core-it-suite/src/test/resources-filtered/bootstrap.txt? Good point. It should actually fail. I think the reason it does not is because

[jira] [Created] (MASSEMBLY-1002) Assembly fails to include directories when they are symbolic links

2023-11-06 Thread Jimisola Laursen (Jira)
Jimisola Laursen created MASSEMBLY-1002: --- Summary: Assembly fails to include directories when they are symbolic links Key: MASSEMBLY-1002 URL: https://issues.apache.org/jira/browse/MASSEMBLY-1002

[jira] [Updated] (MSHARED-1326) Improve (documentation on) MavenReport interface/AbstractMavenReport class

2023-11-06 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/MSHARED-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1326: Description: Based on a

Re: [PR] Change build pom naming from xxx-build.pom to xxx-build-pom.xml [maven]

2023-11-06 Thread via GitHub
michael-o commented on PR #1298: URL: https://github.com/apache/maven/pull/1298#issuecomment-1794431344 > > This does not look wrong. What is the motivation behind this? > > The problem seems to be that sonatype oss release validation fail staging repositories deployed with Maven 4.

[PR] Use 4.0.0-alpha-8 instead of SNAPSHOT [maven-integration-testing]

2023-11-06 Thread via GitHub
gnodet opened a new pull request, #315: URL: https://github.com/apache/maven-integration-testing/pull/315 (no comment) -- 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

Re: [PR] Change build pom naming from xxx-build.pom to xxx-build-pom.xml [maven]

2023-11-06 Thread via GitHub
gnodet commented on PR #1298: URL: https://github.com/apache/maven/pull/1298#issuecomment-1794423566 > This does not look wrong. What is the motivation behind this? The problem seems to be that sonatype oss release validation fail staging repositories deployed with Maven 4. The issue

[jira] [Commented] (MRESOLVER-423) Remove the 3.x banner from Resolver site

2023-11-06 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MRESOLVER-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783154#comment-17783154 ] ASF GitHub Bot commented on MRESOLVER-423: -- olamy commented on PR #354: URL:

[PR] Bump org.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.0 [maven-ear-plugin]

2023-11-06 Thread via GitHub
dependabot[bot] opened a new pull request, #98: URL: https://github.com/apache/maven-ear-plugin/pull/98 Bumps [org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) from 4.8.0 to 4.9.0. Release notes Sourced from

Re: [PR] [MRESOLVER-423] Legacy promotion is no stay here [maven-resolver]

2023-11-06 Thread via GitHub
olamy commented on PR #354: URL: https://github.com/apache/maven-resolver/pull/354#issuecomment-1794418256 Looking at this page https://maven.apache.org/docs/history.html, we are still supporting 3.8.x -- This is an automated message from the Apache Git Service. To respond to the

Re: [PR] [test] Added Unit tests for AssemblyFileUtils, FileLocation, and Mess… [maven-assembly-plugin]

2023-11-06 Thread via GitHub
slawekjaranowski commented on PR #161: URL: https://github.com/apache/maven-assembly-plugin/pull/161#issuecomment-1794333899 @Kaushikdhola please check build output the same should be when you build project locally  -- This is an automated message from the Apache Git Service. To

Re: [PR] Change build pom naming from xxx-build.pom to xxx-build-pom.xml [maven]

2023-11-06 Thread via GitHub
michael-o commented on PR #1298: URL: https://github.com/apache/maven/pull/1298#issuecomment-1794331534 This does not look wrong. What is the motivation behind this? How will the attached artifact looked like if then main POM is still `foo.pom`? -- This is an automated message from the

  1   2   >