Re: [PR] Bump actions/setup-java from 4.7.0 to 4.7.1 [maven-gh-actions-shared]

slawekjaranowski merged PR #159: URL: https://github.com/apache/maven-gh-actions-shared/pull/159 -- 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-

[PR] Bump org.apache.maven.shared:file-management from 3.1.0 to 3.2.0 [maven-jar-plugin]

dependabot[bot] opened a new pull request, #143: URL: https://github.com/apache/maven-jar-plugin/pull/143 Bumps [org.apache.maven.shared:file-management](https://github.com/apache/maven-file-management) from 3.1.0 to 3.2.0. Release notes Sourced from https://github.com/apache/mave

[PR] Bump org.apache.maven.shared:file-management from 3.1.0 to 3.2.0 [maven-jar-plugin]

dependabot[bot] opened a new pull request, #142: URL: https://github.com/apache/maven-jar-plugin/pull/142 Bumps [org.apache.maven.shared:file-management](https://github.com/apache/maven-file-management) from 3.1.0 to 3.2.0. Release notes Sourced from https://github.com/apache/mave

Re: [PR] Bump org.jacoco:jacoco-maven-plugin from 0.8.12 to 0.8.13 [maven-doxia-converter]

slachiewicz merged PR #93: URL: https://github.com/apache/maven-doxia-converter/pull/93 -- 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.

Re: [PR] Bump org.codehaus.plexus:plexus-java from 1.0.3 to 1.5.0 [maven-jmod-plugin]

slachiewicz commented on PR #41: URL: https://github.com/apache/maven-jmod-plugin/pull/41#issuecomment-2813779147 @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 specific c

Re: [I] Possible JLine classpath issue [maven-mvnd]

telemenar commented on issue #1125: URL: https://github.com/apache/maven-mvnd/issues/1125#issuecomment-2813736657 I figured out what is happening here, it is a quarkus breakage, it is referenced here: https://github.com/quarkusio/quarkus/pull/41260 And they say it will be resolved

Re: [PR] Bump org.apache.maven.extensions:maven-extensions from 41 to 44 [maven-build-cache-extension]

slachiewicz commented on PR #200: URL: https://github.com/apache/maven-build-cache-extension/pull/200#issuecomment-2813377239 @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 t

[jira] [Commented] (MCHECKSTYLE-431) Avoid creating unnecessary target files for pom projects

[ https://issues.apache.org/jira/browse/MCHECKSTYLE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945433#comment-17945433 ] Alexis Jehan commented on MCHECKSTYLE-431: -- That has been months, still no

[jira] [Commented] (MPMD-412) Tests are inobviously broken due to overly broad catch clauses

[ https://issues.apache.org/jira/browse/MPMD-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945408#comment-17945408 ] ASF GitHub Bot commented on MPMD-412: - elharo opened a new pull request, #190: URL: htt

[jira] [Updated] (MNG-8694) Version not augmentable during runtime in Maven 4 as it was in Maven 3

[ https://issues.apache.org/jira/browse/MNG-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nico Jahn updated MNG-8694: --- Description: In Maven 3.x the revision property could be used to - dynamically define the final version of a p

[jira] [Updated] (MNG-8694) Version not augmentable during runtime in Maven 4 as it was in Maven 3

[ https://issues.apache.org/jira/browse/MNG-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nico Jahn updated MNG-8694: --- Attachment: MNG-6894-log.txt > Version not augmentable during runtime in Maven 4 as it was in Maven 3 > --

Re: [I] Empty output for help:evaluate [maven-mvnd]

Wolf2323 commented on issue #1026: URL: https://github.com/apache/maven-mvnd/issues/1026#issuecomment-2812741429 Ok, I figured out a solution, I could fix it by adding `--non-recursive ` -- This is an automated message from the Apache Git Service. To respond to the message, please log on t

[jira] [Updated] (MNG-8694) Version not augmentable during runtime in Maven 4 as it was in Maven 3

[ https://issues.apache.org/jira/browse/MNG-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nico Jahn updated MNG-8694: --- Description: In Maven 3.x the revision property could be used to - dynamically define the final version of a p

Re: [I] Empty output for help:evaluate [maven-mvnd]

Wolf2323 commented on issue #1026: URL: https://github.com/apache/maven-mvnd/issues/1026#issuecomment-2812523049 Hey, I want to do a similar thing: ``` REVISION_VERSION="$(./mvnw --raw-streams help:evaluate -Dexpression=revision -DforceStdout -q)" ``` I already use `--raw-streams

[jira] [Updated] (MNG-8694) Version not augmentable during runtime in Maven 4 as it was in Maven 3

[ https://issues.apache.org/jira/browse/MNG-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nico Jahn updated MNG-8694: --- Attachment: revision-demo.zip > Version not augmentable during runtime in Maven 4 as it was in Maven 3 > -

[jira] [Updated] (MNG-8694) Version not augmentable during runtime in Maven 4 as it was in Maven 3

[ https://issues.apache.org/jira/browse/MNG-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nico Jahn updated MNG-8694: --- Attachment: (was: revision-demo.zip) > Version not augmentable during runtime in Maven 4 as it was in Maven

[jira] [Commented] (MNG-8659) Allow maven plugins to automatically run a Mojo without an explicit execution.

[ https://issues.apache.org/jira/browse/MNG-8659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945316#comment-17945316 ] Nico Jahn commented on MNG-8659: I highly appreciate this idea. Most of the times it feels

Re: [I] Possible JLine classpath issue [maven-mvnd]

kreake commented on issue #1125: URL: https://github.com/apache/maven-mvnd/issues/1125#issuecomment-2812279991 I can only second that. Windows 10, Graal 17, mvnd 1.0.2, maven 3.9.9, quarkus 3.10.2 Have tried it with multiple quarkus projects. None of them work. -- This is an automate

[jira] [Updated] (MNG-8694) Version not augmentable during runtime in Maven 4 as it was in Maven 3

[ https://issues.apache.org/jira/browse/MNG-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nico Jahn updated MNG-8694: --- Summary: Version not augmentable during runtime in Maven 4 as it was in Maven 3 (was: Revision property not a

[jira] [Created] (MNG-8694) Revision property not augmentable in Maven 4 as it was in Maven 3

Nico Jahn created MNG-8694: -- Summary: Revision property not augmentable in Maven 4 as it was in Maven 3 Key: MNG-8694 URL: https://issues.apache.org/jira/browse/MNG-8694 Project: Maven Issue Type: