[jira] [Commented] (MSITE-971) Site generation not resolving git.commit.time

[ https://issues.apache.org/jira/browse/MSITE-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747835#comment-17747835 ] Michael Osipov commented on MSITE-971: -- [~larrick], for the time being I recommend us

[jira] [Assigned] (MSITE-971) Site generation not resolving git.commit.time

[ https://issues.apache.org/jira/browse/MSITE-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MSITE-971: Assignee: (was: Michael Osipov) > Site generation not resolving git.commit.time > -

[jira] [Created] (MWRAPPER-113) Error and warning output goes to standard output and intermingles with Maven output

Ingo Karkat created MWRAPPER-113: Summary: Error and warning output goes to standard output and intermingles with Maven output Key: MWRAPPER-113 URL: https://issues.apache.org/jira/browse/MWRAPPER-113

[jira] [Updated] (MWRAPPER-112) Detection of JAVA_HOME fails due to bad quoting

[ https://issues.apache.org/jira/browse/MWRAPPER-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ingo Karkat updated MWRAPPER-112: - Affects Version/s: next-release > Detection of JAVA_HOME fails due to bad quoting > ---

[jira] [Created] (MRESOLVER-390) Modify classpath creation out of resolved graph

Tamas Cservenak created MRESOLVER-390: - Summary: Modify classpath creation out of resolved graph Key: MRESOLVER-390 URL: https://issues.apache.org/jira/browse/MRESOLVER-390 Project: Maven Resolver

[jira] [Created] (MRESOLVER-391) Scope mediation improvements

Tamas Cservenak created MRESOLVER-391: - Summary: Scope mediation improvements Key: MRESOLVER-391 URL: https://issues.apache.org/jira/browse/MRESOLVER-391 Project: Maven Resolver Issue Typ

[jira] [Commented] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747883#comment-17747883 ] Tamas Cservenak commented on MNG-7852: -- Aside of the "unexpected" (which is known issu

[GitHub] [maven-wrapper] inkarkat opened a new pull request, #106: [MWRAPPER-113] Some mvnw error and warning output goes to standard output

inkarkat opened a new pull request, #106: URL: https://github.com/apache/maven-wrapper/pull/106 Errors and warnings from the wrapper should go to standard error, so that those are also shown to the user when the regular Maven output is suppressed, redirected into a file, or captured by a sc

[jira] [Commented] (MWRAPPER-113) Error and warning output goes to standard output and intermingles with Maven output

[ https://issues.apache.org/jira/browse/MWRAPPER-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747886#comment-17747886 ] ASF GitHub Bot commented on MWRAPPER-113: - inkarkat opened a new pull request,

[jira] [Commented] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747888#comment-17747888 ] Vladimir Sitnikov commented on MNG-7852: {quote}all the rest of issues were closed

[jira] [Updated] (MWRAPPER-113) Error and warning output goes to standard output and intermingles with Maven output

[ https://issues.apache.org/jira/browse/MWRAPPER-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ingo Karkat updated MWRAPPER-113: - Flags: Patch Description: Errors and warnings from the wrapper should go to standard

[jira] [Updated] (MWRAPPER-112) Detection of JAVA_HOME fails due to bad quoting

[ https://issues.apache.org/jira/browse/MWRAPPER-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ingo Karkat updated MWRAPPER-112: - Flags: Patch Labels: pull-request-available (was: ) > Detection of JAVA_HOME fails due to

[jira] [Commented] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747891#comment-17747891 ] Vladimir Sitnikov commented on MNG-7852: {quote}Am really unsure what you want to s

[jira] [Comment Edited] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747891#comment-17747891 ] Vladimir Sitnikov edited comment on MNG-7852 at 7/27/23 10:03 AM: ---

[jira] [Created] (MNG-7853) Support Gradle Module Metadata

Vladimir Sitnikov created MNG-7853: -- Summary: Support Gradle Module Metadata Key: MNG-7853 URL: https://issues.apache.org/jira/browse/MNG-7853 Project: Maven Issue Type: Improvement

[jira] [Commented] (MNG-5652) "supplies"/"provides"/"proffers" concept proposal

[ https://issues.apache.org/jira/browse/MNG-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748076#comment-17748076 ] Vladimir Sitnikov commented on MNG-5652: Version ranges often create complexity iss

[jira] [Commented] (MNG-7853) Support Gradle Module Metadata

[ https://issues.apache.org/jira/browse/MNG-7853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748077#comment-17748077 ] Vladimir Sitnikov commented on MNG-7853: Module Metadata covers "capabilities" case

[jira] [Commented] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748087#comment-17748087 ] Tamas Cservenak commented on MNG-7852: -- Maven provides solution to all your enlisted p

[jira] [Commented] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748094#comment-17748094 ] Tamas Cservenak commented on MNG-7852: -- And just FTR: you mention "no such method" wit

[jira] [Comment Edited] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748094#comment-17748094 ] Tamas Cservenak edited comment on MNG-7852 at 7/27/23 11:19 AM: -

[jira] [Comment Edited] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748094#comment-17748094 ] Tamas Cservenak edited comment on MNG-7852 at 7/27/23 11:19 AM: -

[jira] [Created] (MNG-7854) Imported entries that are ignored should be emitted as warning

Tamas Cservenak created MNG-7854: Summary: Imported entries that are ignored should be emitted as warning Key: MNG-7854 URL: https://issues.apache.org/jira/browse/MNG-7854 Project: Maven Iss

[jira] [Commented] (MNG-7854) Imported entries that are ignored should be emitted as warning

[ https://issues.apache.org/jira/browse/MNG-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748112#comment-17748112 ] ASF GitHub Bot commented on MNG-7854: - cstamas opened a new pull request, #1211: URL: h

[jira] [Commented] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748113#comment-17748113 ] Tamas Cservenak commented on MNG-7852: -- For protobuf issue, here is a reproducer, a PR

[jira] [Created] (MNG-7855) Dependencies wrongly put on class-path rather than module-path

Martin Desruisseaux created MNG-7855: Summary: Dependencies wrongly put on class-path rather than module-path Key: MNG-7855 URL: https://issues.apache.org/jira/browse/MNG-7855 Project: Maven

[jira] [Commented] (MJLINK-64) Add-options double quoting

[ https://issues.apache.org/jira/browse/MJLINK-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748174#comment-17748174 ] ASF GitHub Bot commented on MJLINK-64: -- bmarwell merged PR #166: URL: https://github.

[jira] [Resolved] (MJLINK-64) Add-options double quoting

[ https://issues.apache.org/jira/browse/MJLINK-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Marwell resolved MJLINK-64. Fix Version/s: 3.2.0 Resolution: Fixed > Add-options double quoting > ---

[jira] [Commented] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748173#comment-17748173 ] Vladimir Sitnikov commented on MNG-7852: {quote}This "real life example" is totally

[GitHub] [maven] kun-lu20 commented on pull request #1207: [MNG-7848] Add s390x pipeline to Jenkins CI

kun-lu20 commented on PR #1207: URL: https://github.com/apache/maven/pull/1207#issuecomment-1653722464 Hi @slachiewicz , Could you please help to merge this PR and set up a nightly build s390x pipeline on Jenkins CI? Thank you so much! -- This is an automated message from th

[jira] [Commented] (MNG-7848) Add s390x pipeline to Jenkins CI

[ https://issues.apache.org/jira/browse/MNG-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748178#comment-17748178 ] ASF GitHub Bot commented on MNG-7848: - kun-lu20 commented on PR #1207: URL: https://git

[jira] [Commented] (MRESOLVER-390) Modify classpath creation out of resolved graph

[ https://issues.apache.org/jira/browse/MRESOLVER-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748186#comment-17748186 ] ASF GitHub Bot commented on MRESOLVER-390: -- cstamas opened a new pull request

[jira] [Commented] (SUREFIRE-2097) More configuration for surefire JPMS

[ https://issues.apache.org/jira/browse/SUREFIRE-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748204#comment-17748204 ] Martin Desruisseaux commented on SUREFIRE-2097: --- This issue seems relate

[GitHub] [maven] cstamas opened a new pull request, #1212: EXPERIMENT

cstamas opened a new pull request, #1212: URL: https://github.com/apache/maven/pull/1212 Applies MRESOLVER-390 changes, and removes all sprinkled artifact ordering, delegates fully to Resolver. If you do `mvn -X package` you can see for example that enforcer plugin classpath is built

[jira] [Commented] (MNG-6357) Dependency order should be nearest first

[ https://issues.apache.org/jira/browse/MNG-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748214#comment-17748214 ] Tamas Cservenak commented on MNG-6357: -- Related experiment https://github.com/apache/m

[jira] [Commented] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748217#comment-17748217 ] Vladimir Sitnikov commented on MNG-7852: One more case (5): * I'm the author of my

[jira] [Comment Edited] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748217#comment-17748217 ] Vladimir Sitnikov edited comment on MNG-7852 at 7/27/23 3:46 PM:

[jira] [Commented] (MSOURCES-121) Check for duplicated addition of the same file

[ https://issues.apache.org/jira/browse/MSOURCES-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748237#comment-17748237 ] Matt Nelson commented on MSOURCES-121: -- This change appears to introduce a failure

[jira] [Comment Edited] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748217#comment-17748217 ] Vladimir Sitnikov edited comment on MNG-7852 at 7/27/23 4:02 PM:

[GitHub] [maven] slawekjaranowski commented on pull request #1211: [MNG-7854] Warn if imported depMgt is ignored as it already exists

slawekjaranowski commented on PR #1211: URL: https://github.com/apache/maven/pull/1211#issuecomment-1653927227 What will be if I define version of some library directly in depMng and next it will be also declared in imported depMng? I would like to override in project one of dependenc

[jira] [Commented] (MNG-7854) Imported entries that are ignored should be emitted as warning

[ https://issues.apache.org/jira/browse/MNG-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748244#comment-17748244 ] ASF GitHub Bot commented on MNG-7854: - slawekjaranowski commented on PR #1211: URL: htt

[jira] [Commented] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748243#comment-17748243 ] Lenny Primak commented on MNG-7852: --- Hi, I understand your points, and they are indeed v

[GitHub] [maven] cstamas commented on pull request #1211: [MNG-7854] Warn if imported depMgt is ignored as it already exists

cstamas commented on PR #1211: URL: https://github.com/apache/maven/pull/1211#issuecomment-1653953382 This pr just adds logging, no logic change. For your question: order matters, so first depMgt wins over subsequent ones, subsequent dupes are simply ignored. -- This is an automate

[jira] [Commented] (MNG-7854) Imported entries that are ignored should be emitted as warning

[ https://issues.apache.org/jira/browse/MNG-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748249#comment-17748249 ] ASF GitHub Bot commented on MNG-7854: - cstamas commented on PR #1211: URL: https://gith

[GitHub] [maven-jlink-plugin] bmarwell merged pull request #167: [MJLINK-72] remove commons-lang3

bmarwell merged PR #167: URL: https://github.com/apache/maven-jlink-plugin/pull/167 -- 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...@m

[jira] [Commented] (MJLINK-72) Remove common-lang3

[ https://issues.apache.org/jira/browse/MJLINK-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748269#comment-17748269 ] ASF GitHub Bot commented on MJLINK-72: -- bmarwell merged PR #167: URL: https://github.

[jira] [Resolved] (MJLINK-72) Remove common-lang3

[ https://issues.apache.org/jira/browse/MJLINK-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Marwell resolved MJLINK-72. Resolution: Fixed > Remove common-lang3 > --- > > Key: MJLIN

[jira] [Created] (MJLINK-73) Add fork mode

Benjamin Marwell created MJLINK-73: -- Summary: Add fork mode Key: MJLINK-73 URL: https://issues.apache.org/jira/browse/MJLINK-73 Project: Maven JLink Plugin Issue Type: New Feature

[jira] [Commented] (MJLINK-67) Point issues link in pom to issue list instead of release list

[ https://issues.apache.org/jira/browse/MJLINK-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748272#comment-17748272 ] Benjamin Marwell commented on MJLINK-67: Hi [~elharo], I believe this is fixed in

[jira] [Commented] (MJLINK-68) url in url field instead of description field in pom.xml

[ https://issues.apache.org/jira/browse/MJLINK-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748274#comment-17748274 ] Benjamin Marwell commented on MJLINK-68: [~elharo] it is not the URL to this proje

[GitHub] [maven] elharo commented on a diff in pull request #1203: Fix codestyle in model code snippets

elharo commented on code in PR #1203: URL: https://github.com/apache/maven/pull/1203#discussion_r1276627756 ## api/maven-api-model/src/main/mdo/maven.mdo: ## @@ -2503,27 +2501,23 @@ /** * Reset the {@code executionMap} field to {@code null} */ -public void f

[jira] [Resolved] (MJLINK-68) url in url field instead of description field in pom.xml

[ https://issues.apache.org/jira/browse/MJLINK-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MJLINK-68. - Resolution: Invalid I'm not sure there should be any URL here then — where does th

[jira] [Closed] (MJLINK-68) url in url field instead of description field in pom.xml

[ https://issues.apache.org/jira/browse/MJLINK-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold closed MJLINK-68. --- > url in url field instead of description field in pom.xml > -

[jira] [Commented] (MJLINK-68) url in url field instead of description field in pom.xml

[ https://issues.apache.org/jira/browse/MJLINK-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748282#comment-17748282 ] Benjamin Marwell commented on MJLINK-68: We could just mention the JEPs by name:

[jira] [Updated] (MJLINK-67) Point issues link in pom to issue list instead of release list

[ https://issues.apache.org/jira/browse/MJLINK-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MJLINK-67: Priority: Minor (was: Major) > Point issues link in pom to issue list instead of re

[jira] [Resolved] (MJLINK-67) Point issues link in pom to issue list instead of release list

[ https://issues.apache.org/jira/browse/MJLINK-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MJLINK-67. - Resolution: Fixed Looks fixed. > Point issues link in pom to issue list instead

[jira] [Updated] (MJLINK-67) Point issues link in pom to issue list instead of release list

[ https://issues.apache.org/jira/browse/MJLINK-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MJLINK-67: Issue Type: Bug (was: Improvement) > Point issues link in pom to issue list instead

[jira] [Closed] (MJLINK-67) Point issues link in pom to issue list instead of release list

[ https://issues.apache.org/jira/browse/MJLINK-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold closed MJLINK-67. --- > Point issues link in pom to issue list instead of release list > ---

[jira] [Commented] (MJLINK-68) url in url field instead of description field in pom.xml

[ https://issues.apache.org/jira/browse/MJLINK-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748287#comment-17748287 ] Elliotte Rusty Harold commented on MJLINK-68: - That would be fine, IMHO > url

[jira] [Closed] (MSHARED-1294) Upgrade Parent to 40

[ https://issues.apache.org/jira/browse/MSHARED-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MSHARED-1294. Resolution: Fixed > Upgrade Parent to 40 > > >

[jira] [Commented] (MSHARED-1294) Upgrade Parent to 40

[ https://issues.apache.org/jira/browse/MSHARED-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748292#comment-17748292 ] ASF GitHub Bot commented on MSHARED-1294: - slawekjaranowski merged PR #40: URL:

[jira] [Commented] (MNG-7852) Use all the versions for dependency resolution rather than "nearest first" or "declared first"

[ https://issues.apache.org/jira/browse/MNG-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748323#comment-17748323 ] Vladimir Sitnikov commented on MNG-7852: Well, one of the workable algorithms is de

[jira] [Commented] (MNG-7848) Add s390x pipeline to Jenkins CI

[ https://issues.apache.org/jira/browse/MNG-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748331#comment-17748331 ] ASF GitHub Bot commented on MNG-7848: - olamy commented on PR #1207: URL: https://github

[jira] [Closed] (MSHARED-1293) Refresh download page

[ https://issues.apache.org/jira/browse/MSHARED-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MSHARED-1293. Resolution: Fixed > Refresh download page > - > >

[jira] [Commented] (MSHARED-1293) Refresh download page

[ https://issues.apache.org/jira/browse/MSHARED-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748337#comment-17748337 ] ASF GitHub Bot commented on MSHARED-1293: - slawekjaranowski merged PR #41: URL:

[jira] [Commented] (MJAR-275) outputTimestamp not applied to module-info; breaks reproducible builds

[ https://issues.apache.org/jira/browse/MJAR-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748433#comment-17748433 ] Herve Boutemy commented on MJAR-275: done https://bugs.openjdk.org/browse/JDK-8258117,

[jira] [Comment Edited] (MJAR-275) outputTimestamp not applied to module-info; breaks reproducible builds

[ https://issues.apache.org/jira/browse/MJAR-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748433#comment-17748433 ] Herve Boutemy edited comment on MJAR-275 at 7/28/23 6:36 AM: - d