Re: [PR] Bump org.codehaus.plexus:plexus-component-annotations from 2.1.0 to 2.2.0 [maven]
gnodet commented on PR #2100: URL: https://github.com/apache/maven/pull/2100#issuecomment-2650678403 > -1 This dependency came up as part of [edd246c](https://github.com/apache/maven/commit/edd246c3a54b9a3808249685dca2bebafeddd4c7) But Maven master will not go "back" to this... and this dependency is in compat, just just leave it frozen So telling dependabot to ignore that dependency is what we want, right? -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [#502] - Add prefix to zip entries [maven-jlink-plugin]
YaSuenag opened a new pull request, #503: URL: https://github.com/apache/maven-jlink-plugin/pull/503 I would like to introduce `zipDirPrefix` to add prefix to zip entries. See #502 for details. Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [GitHub issue](https://github.com/apache/maven-jlink-plugin/issues) filed for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Format the pull request title like `[#] - Fixes bug in ApproximateQuantiles`, where you replace `#` with the appropriate GitHub issue. Best practice is to use the GitHub issue title in the pull request title and in the first line of the commit message. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [x] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-671) Don't require Java 21
[ https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925960#comment-17925960 ] Tamas Cservenak commented on MRESOLVER-671: --- That comment was added two years ago by me, then PMD had issues, that were fixed since then. Again. "tooling had to be updated", nothing more. > Don't require Java 21 > - > > Key: MRESOLVER-671 > URL: https://issues.apache.org/jira/browse/MRESOLVER-671 > Project: Maven Resolver > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > Apparently maven-resolver now requires Java 21 to build. It won't build even > with Java 17. This is getting inconveniently out of sync with what devs have > installed. E.g we can't even jdeprscan for Java 11 or 8 with this version. > This should be pushed back to 17 or further if possible. The bleeding edge is > too bloody. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Dump public IPs of runners [maven]
slawekjaranowski commented on code in PR #2103:
URL: https://github.com/apache/maven/pull/2103#discussion_r1950760898
##
.github/workflows/maven.yml:
##
@@ -138,6 +138,10 @@ jobs:
maven-${{ runner.os }}-full-
maven-${{ runner.os }}-
+ - name: Show IP
+shell: bash
+run: curl https://api.ipify.org
Review Comment:
and `curl --silent. ...` 😄
--
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
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [MNG-8575] Replace a list with O(N²) performance by O(N) at least during iteration. [maven]
gnodet merged PR #2092: URL: https://github.com/apache/maven/pull/2092 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (MNG-8575) Replace a list with O(N²) performance by O(N) at least during iteration.
[ https://issues.apache.org/jira/browse/MNG-8575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned MNG-8575: Assignee: Martin Desruisseaux > Replace a list with O(N²) performance by O(N) at least during iteration. > > > Key: MNG-8575 > URL: https://issues.apache.org/jira/browse/MNG-8575 > Project: Maven > Issue Type: Task >Reporter: Martin Desruisseaux >Assignee: Martin Desruisseaux >Priority: Major > > GitHub Pull Request: https://github.com/apache/maven/pull/2092 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8575) Replace a list with O(N²) performance by O(N) at least during iteration.
[ https://issues.apache.org/jira/browse/MNG-8575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8575. Resolution: Fixed > Replace a list with O(N²) performance by O(N) at least during iteration. > > > Key: MNG-8575 > URL: https://issues.apache.org/jira/browse/MNG-8575 > Project: Maven > Issue Type: Task >Reporter: Martin Desruisseaux >Assignee: Martin Desruisseaux >Priority: Major > > GitHub Pull Request: https://github.com/apache/maven/pull/2092 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Dump public IPs of runners [maven]
cstamas commented on code in PR #2103:
URL: https://github.com/apache/maven/pull/2103#discussion_r1950764518
##
.github/workflows/maven.yml:
##
@@ -138,6 +138,10 @@ jobs:
maven-${{ runner.os }}-full-
maven-${{ runner.os }}-
+ - name: Show IP
+shell: bash
+run: curl https://api.ipify.org
Review Comment:
Done
--
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
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (MNG-8575) Replace a list with O(N²) performance by O(N) at least during iteration.
[ https://issues.apache.org/jira/browse/MNG-8575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8575: - Reporter: Martin Desruisseaux (was: Guillaume Nodet) > Replace a list with O(N²) performance by O(N) at least during iteration. > > > Key: MNG-8575 > URL: https://issues.apache.org/jira/browse/MNG-8575 > Project: Maven > Issue Type: Task >Reporter: Martin Desruisseaux >Priority: Major > > GitHub Pull Request: https://github.com/apache/maven/pull/2092 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-671) Don't require Java 21
[ https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925995#comment-17925995 ] Tamas Cservenak commented on MRESOLVER-671: --- I find so many self contradicting things... who are "users" that are forced on upgrades? You? I disagree about the "high bar" as well, why you insist on living in past? Maven4 is not yet even released (GA), and when it MAY be released, we MAY have already the next Java LTS out. And you want to go backwards? In fact, I see folks like you the problem: if all users would use "latest" LTS (assume they would somehow manage to get it installed), we'd not have issues that we currently have, to support building projects on wildly different Java versions, from Java 8 to Java 21, spotless comes to my mind, just to mention one issue. Remember this? https://lists.apache.org/thread/ors31h7cbn6q777f8j9nkzp8x3p0b4nf > Don't require Java 21 > - > > Key: MRESOLVER-671 > URL: https://issues.apache.org/jira/browse/MRESOLVER-671 > Project: Maven Resolver > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > Apparently maven-resolver now requires Java 21 to build. It won't build even > with Java 17. This is getting inconveniently out of sync with what devs have > installed. E.g we can't even jdeprscan for Java 11 or 8 with this version. > This should be pushed back to 17 or further if possible. The bleeding edge is > too bloody. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-671) Don't require Java 21
[ https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925996#comment-17925996 ] Tamas Cservenak commented on MRESOLVER-671: --- For me, all this your are for comes from a bad reflex that for some reason became norm among Maven users (and it seems devs as well): "you should build the project using the Java version that project targets" (or in other words, if we build Java 8 stuff, let's use Java 8 to build it). Colloraly: if you use build a native app that supports Win95, it is expectation to have it built on Win95. > Don't require Java 21 > - > > Key: MRESOLVER-671 > URL: https://issues.apache.org/jira/browse/MRESOLVER-671 > Project: Maven Resolver > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > Apparently maven-resolver now requires Java 21 to build. It won't build even > with Java 17. This is getting inconveniently out of sync with what devs have > installed. E.g we can't even jdeprscan for Java 11 or 8 with this version. > This should be pushed back to 17 or further if possible. The bleeding edge is > too bloody. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MRESOLVER-671) Don't require Java 21
[ https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925996#comment-17925996 ] Tamas Cservenak edited comment on MRESOLVER-671 at 2/11/25 1:21 PM: For me, all this your are for comes from a bad reflex that for some reason became norm among Maven users (and it seems devs as well): "you should build the project using the Java version that project targets" (or in other words, if we build Java 8 stuff, let's use Java 8 to build it). Corollary: if you use build a native app that supports Win95, it is expectation to have it built on Win95. was (Author: cstamas): For me, all this your are for comes from a bad reflex that for some reason became norm among Maven users (and it seems devs as well): "you should build the project using the Java version that project targets" (or in other words, if we build Java 8 stuff, let's use Java 8 to build it). Colloraly: if you use build a native app that supports Win95, it is expectation to have it built on Win95. > Don't require Java 21 > - > > Key: MRESOLVER-671 > URL: https://issues.apache.org/jira/browse/MRESOLVER-671 > Project: Maven Resolver > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > Apparently maven-resolver now requires Java 21 to build. It won't build even > with Java 17. This is getting inconveniently out of sync with what devs have > installed. E.g we can't even jdeprscan for Java 11 or 8 with this version. > This should be pushed back to 17 or further if possible. The bleeding edge is > too bloody. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MCOMPILER-529] Update docs about version schema (Maven 3) [maven-compiler-plugin]
Bukama merged PR #295: URL: https://github.com/apache/maven-compiler-plugin/pull/295 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MCOMPILER-529) Improve the docs about usage 1.8 vs. 8 for source/target
[
https://issues.apache.org/jira/browse/MCOMPILER-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926047#comment-17926047
]
ASF GitHub Bot commented on MCOMPILER-529:
--
Bukama merged PR #295:
URL: https://github.com/apache/maven-compiler-plugin/pull/295
> Improve the docs about usage 1.8 vs. 8 for source/target
>
>
> Key: MCOMPILER-529
> URL: https://issues.apache.org/jira/browse/MCOMPILER-529
> Project: Maven Compiler Plugin
> Issue Type: Improvement
>Affects Versions: 3.10.1
>Reporter: Karl Heinz Marbaise
>Assignee: Matthias Bünger
>Priority: Minor
> Labels: up-for-grabs
>
> The current descriptions/docs only mentioned the usage of {{1.8}} for
> source/target. But it looks like I can use also {{8}} instead. But all the
> examples on the usage page etc. using {{1.8}}... even the error message tells
> me to do:
> {{code}}
> use -source 8 ...
> {{code}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-compiler-plugin]
Bukama merged PR #296: URL: https://github.com/apache/maven-compiler-plugin/pull/296 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926049#comment-17926049
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama merged PR #296:
URL: https://github.com/apache/maven-compiler-plugin/pull/296
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-compiler-plugin]
Bukama opened a new pull request, #300: URL: https://github.com/apache/maven-compiler-plugin/pull/300 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-deploy-plugin]
Bukama merged PR #99: URL: https://github.com/apache/maven-deploy-plugin/pull/99 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926050#comment-17926050
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #300:
URL: https://github.com/apache/maven-compiler-plugin/pull/300
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926051#comment-17926051
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama merged PR #99:
URL: https://github.com/apache/maven-deploy-plugin/pull/99
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump org.apache.maven.plugins:maven-invoker-plugin from 3.8.1 to 3.9.0 [maven-build-cache-extension]
olamy commented on PR #193: URL: https://github.com/apache/maven-build-cache-extension/pull/193#issuecomment-2650542956 @dependabot merge -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump commons-io:commons-io from 2.16.1 to 2.18.0 [maven-build-cache-extension]
olamy commented on PR #191: URL: https://github.com/apache/maven-build-cache-extension/pull/191#issuecomment-2650542592 @dependabot merge -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-8569) Deprecate and remove version ranges
[
https://issues.apache.org/jira/browse/MNG-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925962#comment-17925962
]
Guillaume Nodet commented on MNG-8569:
--
I see two things that could be done:
* have a way to configure which version is selected in a given range: Maven
currently selects the highest, but we could make it configurable so that the
lowest would be selected by default (this is different than the
{{MAVEN_VERSION_FILTER}} property which actually changes the output of the
range resolution
* change the consumer POM to not use range, but rather use the resolved version
I think ranges can be useful to express which versions of a given dependency
are supported, but I'm not really sure why this would imply to always select
the highest one.
Or maybe extend the syntax to support specifying the default version:
{{2.1[2,3)}} which would mean select version 2.1 by default,
the range being {{2,3)}}.
> Deprecate and remove version ranges
> ---
>
> Key: MNG-8569
> URL: https://issues.apache.org/jira/browse/MNG-8569
> Project: Maven
> Issue Type: Improvement
>Reporter: Elliotte Rusty Harold
>Priority: Critical
>
> To protect Maven users, we should eliminate, or at the very least warn, when
> version ranges are used in dependency elements. See
> [https://jlbp.dev/JLBP-14] for the rationale. tldr; version ranges make
> projects vulnerable to malicious changes of ownership in dependencies that
> can lead to remotely exploitable arbitrary code execution. I'd rate this
> about a 9.0 on the severity scale.
> I don't know of an attack using this vector in Java (yet) but it has
> been used multiple times in other ecosystems to steal bitcoins and
> install malware. Java has been lucky so far, but we are by no means
> immune to it.
> Since this is a compatibility breaking change, which I don't take likely but
> IMHO is worth it in this case, use a multi-step process:
> # Discourage this in the docs for version ranges, especially the POM
> reference.
> # Warn about this in the build when version ranges are encountered.
> # Formally deprecate the relevant code in the repo. (Might not be necessary.)
> # Add a switch (system property) to disable version ranges. Switch is off by
> default.
> # Turn the switch on by default.
> # Remove the switch.
> This might take a few years, so let's start now. It's also possible an active
> attack will push us to do this overnight. If we start now, maybe we'll be
> lucky enough to avoid emergency responses in the future.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926053#comment-17926053
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #100:
URL: https://github.com/apache/maven-deploy-plugin/pull/100
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNG-8567] Fix resumption to not recurse into subprojects [maven]
gnodet merged PR #2102: URL: https://github.com/apache/maven/pull/2102 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-8567) Resumption is broken
[
https://issues.apache.org/jira/browse/MNG-8567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8567.
Resolution: Fixed
> Resumption is broken
>
>
> Key: MNG-8567
> URL: https://issues.apache.org/jira/browse/MNG-8567
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-rc-3
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 4.0.0-rc-3
>
>
> The resumption data seems correct and correctly read, but the reactor
> includes all children from {{Maven 4 Implementation Modules}} whereas they
> have already run.
> First run:
> {code}
> [INFO] Maven 4 Dependency Injection
> .
> SUCCESS [ 2.494 s]
> [INFO] Maven 4 XML Implementation
> ...
> SUCCESS [ 0.795 s]
> [INFO] Maven 4 API Implementation
> ...
> SUCCESS [ 4.108 s]
> [INFO] Maven 4 JLine integration
>
> SUCCESS [ 0.216 s]
> [INFO] Maven 4 Logging
> ..
> SUCCESS [ 0.631 s]
> [INFO] Maven Model
> ..
> SUCCESS [ 1.839 s]
> [INFO] Maven Settings
> ...
> SUCCESS [ 0.289 s]
> [INFO] Maven Builder Support (deprecated)
> ... SUCCESS [
> 0.444 s]
> [INFO] Maven Settings Builder (deprecated)
> .. SUCCESS [
> 0.728 s]
> [INFO] Maven Toolchain Model
>
> SUCCESS [ 0.404 s]
> [INFO] Maven Toolchain Builder (deprecated)
> . SUCCESS [
> 1.482 s]
> [INFO] Maven Repository Metadata Model
> ..
> SUCCESS [ 0.643 s]
> [INFO] Maven Artifact
> ...
> SUCCESS [ 0.934 s]
> [INFO] Maven 3 Plugin API
> ...
> SUCCESS [ 0.638 s]
> [INFO] Maven Model Builder (deprecated)
> . SUCCESS
> [ 1.717 s]
> [INFO] Maven 4 Core
> .
> SUCCESS [ 13.836 s]
> [INFO] Maven Artifact Resolver Provider (deprecated)
> SUCCESS [ 2.424 s]
> [INFO] Maven Compat (deprecated)
>
> FAILURE [ 0.726 s]
> [INFO] Maven 4 CLI
> ..
> SKIPPED
> [INFO] Maven Embedder (deprecated)
> ..
> SKIPPED
> [INFO] Apache Maven Distribution
>
> SKIPPED
> [INFO] Maven 4 Executor
> .
> SKIPPED
> [INFO] Maven 4 Implementation Modules
> ...
> SKIPPED
> [INFO] Maven Compatibility Modules
> ..
> SKIPPED
> {code}
> Second run:
> {code:java}
> [INFO] Scanning for projects...
> [INFO] Resuming from org.apache.maven:maven-compat,
> org.apache.maven:maven-cli, org.apache.maven:maven-embedder,
> org.apache.maven:apache-maven, org.apache.maven:maven-executor,
> org.apache.maven:maven-impl-modules, org.apache.maven:maven-compat-modules
> due to the --resume / -r feature.
> [INFO]
> --
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Maven 4 Dependency Injection
> [jar]
> [INFO] Maven 4 XML Implementation
> [jar]
> [INFO] Maven 4 API Implementation
> [jar]
> [INFO] Maven 4
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-deploy-plugin]
Bukama opened a new pull request, #100: URL: https://github.com/apache/maven-deploy-plugin/pull/100 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-clean-plugin]
Bukama merged PR #93: URL: https://github.com/apache/maven-clean-plugin/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...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MNG-8577) Project POM hierarchy cleanup
Tamas Cservenak created MNG-8577: Summary: Project POM hierarchy cleanup Key: MNG-8577 URL: https://issues.apache.org/jira/browse/MNG-8577 Project: Maven Issue Type: Task Components: Bootstrap & Build Reporter: Tamas Cservenak Fix For: 4.0.0-rc-3 Recently we had a "reshuffle" of build layout (introduced impl/ and compat/ sub directories), but parents were not aligned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Show public IP of runner [maven-gh-actions-shared]
slawekjaranowski merged PR #150: URL: https://github.com/apache/maven-gh-actions-shared/pull/150 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Execute PR Automation only at closed event [maven-gh-actions-shared]
slawekjaranowski merged PR #149: URL: https://github.com/apache/maven-gh-actions-shared/pull/149 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-surefire]
Bukama commented on PR #809: URL: https://github.com/apache/maven-surefire/pull/809#issuecomment-2651435245 This should cover surefire, failsafe and surefire-report -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MNG-8577) Project POM hierarchy cleanup
[ https://issues.apache.org/jira/browse/MNG-8577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8577: - Description: Recently we had a "reshuffle" of build layout (introduced impl/ and compat/ sub directories), but parents were not aligned. Result should be to have these two (parent-child and subprojects) aligned, as here: https://gist.github.com/cstamas/247c61ee1b856c3f464f34fc8d56dfc8 https://gist.github.com/cstamas/b6eb40116141e9715f59aa9a7e0a3b9f was:Recently we had a "reshuffle" of build layout (introduced impl/ and compat/ sub directories), but parents were not aligned. > Project POM hierarchy cleanup > - > > Key: MNG-8577 > URL: https://issues.apache.org/jira/browse/MNG-8577 > Project: Maven > Issue Type: Task > Components: Bootstrap & Build >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-rc-3 > > > Recently we had a "reshuffle" of build layout (introduced impl/ and compat/ > sub directories), but parents were not aligned. > Result should be to have these two (parent-child and subprojects) aligned, as > here: > https://gist.github.com/cstamas/247c61ee1b856c3f464f34fc8d56dfc8 > https://gist.github.com/cstamas/b6eb40116141e9715f59aa9a7e0a3b9f -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925657#comment-17925657
]
Matthias Bünger edited comment on MNGSITE-529 at 2/11/25 4:56 PM:
--
||Plugin||Done?||
|---||
|clean|(/)|
|compiler|(/)|
|deploy|(/)|
|failsafe|(!))|
|install|(x)|
|resources|(x)|
|site|(x)|
|surefire|(!)|
|verifier|(x)|
|||
|ear|(x)|
|ejb|(x)|
|jar|(x)|
|rar|(x)|
|war|(x)|
|app-client/acr|(x)|
|shade|(x)|
|source|(x)|
|jlink|(x)|
|jmod|(x)|
||-|
|changelog|(x)|
|changes|(x)|
|checkstyle|(x)|
|doap|(x)|
|javadoc|(x)|
|jdeps|(x)|
|jxr|(x)|
|linkcheck|(x)|
|pmd|(x)|
|plugin-report|(x)|
|project-info-reports|(x)|
|surefire-report|(!)|
|--|--|
|antrun|(x)|
|artifact|(x)|
|archetype|(x)|
|assembly|(x)|
|dependency|(x)|
|enforcer|(x)|
|gpg|(x)|
|help|(x)|
|invoker|(x)|
|jarsigner|(x)|
|jdeprscan|(x)|
|pdf|(x)|
|plugin|(x)|
|release|(x)|
|remote-resources|(x)|
|scm|(x)|
|scm-publish|(x)|
|scripting|(x)|
|stage|(x)|
|toolchains|(x)|
|wrapper|(x)|
was (Author: JIRAUSER302100):
||Plugin||Done?||
|---||
|clean|(x)|
|compiler|(x)|
|deploy|(x)|
|failsafe|(x)|
|install|(x)|
|resources|(x)|
|site|(x)|
|surefire|(x)|
|verifier|(x)|
|||
|ear|(x)|
|ejb|(x)|
|jar|(x)|
|rar|(x)|
|war|(x)|
|app-client/acr|(x)|
|shade|(x)|
|source|(x)|
|jlink|(x)|
|jmod|(x)|
||-|
|changelog|(x)|
|changes|(x)|
|checkstyle|(x)|
|doap|(x)|
|javadoc|(x)|
|jdeps|(x)|
|jxr|(x)|
|linkcheck|(x)|
|pmd|(x)|
|plugin-report|(x)|
|project-info-reports|(x)|
|surefire-report|(x)|
|--|--|
|antrun|(x)|
|artifact|(x)|
|archetype|(x)|
|assembly|(x)|
|dependency|(x)|
|enforcer|(x)|
|gpg|(x)|
|help|(x)|
|invoker|(x)|
|jarsigner|(x)|
|jdeprscan|(x)|
|pdf|(x)|
|plugin|(x)|
|release|(x)|
|remote-resources|(x)|
|scm|(x)|
|scm-publish|(x)|
|scripting|(x)|
|stage|(x)|
|toolchains|(x)|
|wrapper|(x)|
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-surefire]
Bukama opened a new pull request, #809: URL: https://github.com/apache/maven-surefire/pull/809 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (MNG-8577) Project POM hierarchy cleanup
[ https://issues.apache.org/jira/browse/MNG-8577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-8577: Assignee: Tamas Cservenak > Project POM hierarchy cleanup > - > > Key: MNG-8577 > URL: https://issues.apache.org/jira/browse/MNG-8577 > Project: Maven > Issue Type: Task > Components: Bootstrap & Build >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-rc-3 > > > Recently we had a "reshuffle" of build layout (introduced impl/ and compat/ > sub directories), but parents were not aligned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.codehaus.plexus:plexus-component-annotations from 2.1.0 to 2.2.0 [maven]
cstamas commented on PR #2100: URL: https://github.com/apache/maven/pull/2100#issuecomment-2651461025 @dependabot ignore this dependency -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.codehaus.plexus:plexus-component-annotations from 2.1.0 to 2.2.0 [maven]
dependabot[bot] commented on PR #2100: URL: https://github.com/apache/maven/pull/2100#issuecomment-2651461226 OK, I won't notify you about org.codehaus.plexus:plexus-component-annotations again, unless you re-open this PR. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.codehaus.plexus:plexus-component-annotations from 2.1.0 to 2.2.0 [maven]
dependabot[bot] closed pull request #2100: Bump org.codehaus.plexus:plexus-component-annotations from 2.1.0 to 2.2.0 URL: https://github.com/apache/maven/pull/2100 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-8569) Deprecate and remove version ranges
[ https://issues.apache.org/jira/browse/MNG-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925957#comment-17925957 ] Elliotte Rusty Harold commented on MNG-8569: This is a long-term goal. I think model version 4.1 or later would be required before we remove it completely. We can warn against it more strenuously in earlier versions. > Deprecate and remove version ranges > --- > > Key: MNG-8569 > URL: https://issues.apache.org/jira/browse/MNG-8569 > Project: Maven > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Critical > > To protect Maven users, we should eliminate, or at the very least warn, when > version ranges are used in dependency elements. See > [https://jlbp.dev/JLBP-14] for the rationale. tldr; version ranges make > projects vulnerable to malicious changes of ownership in dependencies that > can lead to remotely exploitable arbitrary code execution. I'd rate this > about a 9.0 on the severity scale. > I don't know of an attack using this vector in Java (yet) but it has > been used multiple times in other ecosystems to steal bitcoins and > install malware. Java has been lucky so far, but we are by no means > immune to it. > Since this is a compatibility breaking change, which I don't take likely but > IMHO is worth it in this case, use a multi-step process: > # Discourage this in the docs for version ranges, especially the POM > reference. > # Warn about this in the build when version ranges are encountered. > # Formally deprecate the relevant code in the repo. (Might not be necessary.) > # Add a switch (system property) to disable version ranges. Switch is off by > default. > # Turn the switch on by default. > # Remove the switch. > This might take a few years, so let's start now. It's also possible an active > attack will push us to do this overnight. If we start now, maybe we'll be > lucky enough to avoid emergency responses in the future. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MRESOLVER-671) Don't require Java 21
[ https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925796#comment-17925796 ] Elliotte Rusty Harold edited comment on MRESOLVER-671 at 2/11/25 11:45 AM: --- I rarely use the latest OS. I rarely use the latest Java. And wrt Java that's the posture of the vast majority of organizations I've ever encountered, Meta and Google included. The devs I notice using the latest LTS JDK are individual cowboy developers. The large organizations where most developers work most of the time do not run or build with the latest LTS. I no longer have access to the current statistics Google collects about what its customers want (a broader and more accurate sample than I've seen elsewhere) but when I did the pattern was clear. The latest LTS was extremely rare. Second to latest was present but not the majority. Third latest was probably a plurality, and there was a long and thick tail of older versions. Non-LTS releases were a drop in the bucket except for JDKs before LTS was a thing (i.e. Java 1.7 and earlier) and these we saw a shocking number of. was (Author: elharo): I rarely use the latest OS. I rarely use the latest Java. And wrt Java that's the posture of the vast majority of organizations I've ever encountered, Meta and Google included. The devs I notice using the latest LTS JDK are individual cowboy developers. The large organizations where most developers work most of the time do not run or build with the latest LTS. I no longer have access to the current statistics Google collects about what its customers want (a broader and more accurate sample than I've seen elsewhere) but when I did the pattern was clear. The latest LTS was extremely rare. Second to latest was present but not the majority. Third latest was probably a plurality, and there was a long and thick tail of older versions. > Don't require Java 21 > - > > Key: MRESOLVER-671 > URL: https://issues.apache.org/jira/browse/MRESOLVER-671 > Project: Maven Resolver > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > Apparently maven-resolver now requires Java 21 to build. It won't build even > with Java 17. This is getting inconveniently out of sync with what devs have > installed. E.g we can't even jdeprscan for Java 11 or 8 with this version. > This should be pushed back to 17 or further if possible. The bleeding edge is > too bloody. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8576) Investigate modifying the Toolchain API to be session/project scoped
Guillaume Nodet created MNG-8576:
Summary: Investigate modifying the Toolchain API to be
session/project scoped
Key: MNG-8576
URL: https://issues.apache.org/jira/browse/MNG-8576
Project: Maven
Issue Type: Wish
Components: API
Affects Versions: 4.0.0-rc-3
Reporter: Guillaume Nodet
We do underuse the scopes as we tend to pass the {{Session}} in all requests to
have stateless services.
The {{ToolchainManager}} is a good example, as we do actually get the mojo
execution context to get to the project and store/retrieve the selected
{{Toolchain}} according to that.
That looks wrong and should be simplified.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNG-8558] Switch toolchain support for v4 API [maven]
gnodet merged PR #2084: URL: https://github.com/apache/maven/pull/2084 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-8558) Switch DefaultToolchainManager to Api V4
[
https://issues.apache.org/jira/browse/MNG-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8558.
Resolution: Fixed
> Switch DefaultToolchainManager to Api V4
>
>
> Key: MNG-8558
> URL: https://issues.apache.org/jira/browse/MNG-8558
> Project: Maven
> Issue Type: Task
>Affects Versions: 4.0.0-rc-2
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-rc-3
>
>
> As of 4.0.0-rc-2, {{maven-impl}} contains an implementation of
> {{org.apache.maven.api.services.ToolchainManager}} which wraps
> {{org.apache.maven.toolchain.DefaultToolchainManagerPrivate}}.
> Both components should be rewritten so that
> {{DefaultToolchainManagerPrivate}} wraps the new implementation of
> {{org.apache.maven.api.services.ToolchainManager}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump commons-io:commons-io from 2.16.1 to 2.18.0 [maven-build-cache-extension]
dependabot[bot] merged PR #191: URL: https://github.com/apache/maven-build-cache-extension/pull/191 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.maven.plugins:maven-invoker-plugin from 3.8.1 to 3.9.0 [maven-build-cache-extension]
dependabot[bot] merged PR #193: URL: https://github.com/apache/maven-build-cache-extension/pull/193 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Show public IP of runner [maven-gh-actions-shared]
slawekjaranowski opened a new pull request, #150: URL: https://github.com/apache/maven-gh-actions-shared/pull/150 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-8562) Maven4 consumer pom : remove "child" attribs from
[
https://issues.apache.org/jira/browse/MNG-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8562.
Resolution: Fixed
> Maven4 consumer pom : remove "child" attribs from
> ---
>
> Key: MNG-8562
> URL: https://issues.apache.org/jira/browse/MNG-8562
> Project: Maven
> Issue Type: Improvement
>Reporter: Lars Bruun-Hansen
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 4.0.0-rc-3
>
>
> With Maven4, I see my that in my {*}consumer POM{*}, I have:
> {code:xml}
> child.scm.developerConnection.inherit.append.path="false"
> child.scm.url.inherit.append.path="false">
> ...
>
> {code}
> These "child.scm.*" attribs should be removed in a consumer POM. They are
> irrelevant, perhaps even misleading when being a consumer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8569) Deprecate and remove version ranges
[ https://issues.apache.org/jira/browse/MNG-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925977#comment-17925977 ] Elliotte Rusty Harold commented on MNG-8569: I don't understand. If the range is closed and we're selecting the lowest version, then [2.1,3]still selects 2.1, no matter which versions have been released. What am I missing? And, yes, restricting the range to a list of compatible versions is a valid use case. Unfortunately it's very insecure so developers need to stop doing it. > Deprecate and remove version ranges > --- > > Key: MNG-8569 > URL: https://issues.apache.org/jira/browse/MNG-8569 > Project: Maven > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Critical > > To protect Maven users, we should eliminate, or at the very least warn, when > version ranges are used in dependency elements. See > [https://jlbp.dev/JLBP-14] for the rationale. tldr; version ranges make > projects vulnerable to malicious changes of ownership in dependencies that > can lead to remotely exploitable arbitrary code execution. I'd rate this > about a 9.0 on the severity scale. > I don't know of an attack using this vector in Java (yet) but it has > been used multiple times in other ecosystems to steal bitcoins and > install malware. Java has been lucky so far, but we are by no means > immune to it. > Since this is a compatibility breaking change, which I don't take likely but > IMHO is worth it in this case, use a multi-step process: > # Discourage this in the docs for version ranges, especially the POM > reference. > # Warn about this in the build when version ranges are encountered. > # Formally deprecate the relevant code in the repo. (Might not be necessary.) > # Add a switch (system property) to disable version ranges. Switch is off by > default. > # Turn the switch on by default. > # Remove the switch. > This might take a few years, so let's start now. It's also possible an active > attack will push us to do this overnight. If we start now, maybe we'll be > lucky enough to avoid emergency responses in the future. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-671) Don't require Java 21
[ https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925972#comment-17925972 ] Elliotte Rusty Harold commented on MRESOLVER-671: - Also, w.r.t the bleeding edge, I think there's an industry-wide failure to calculate and sum the cost of forcing upgrades on users. It's an externality. Hardly unique to Maven or Java. As one example, yesterday I blew an hour trying to install JDK 21 on my laptop just to build the resolver. I still don't have a working JDK 21 installed, but somehow ended up with JDK 23. No idea how that happened, but it seems to work so I stopped. Still doesn't work in IntelliJ though. Fixing that would probably cost another hour. > Don't require Java 21 > - > > Key: MRESOLVER-671 > URL: https://issues.apache.org/jira/browse/MRESOLVER-671 > Project: Maven Resolver > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > Apparently maven-resolver now requires Java 21 to build. It won't build even > with Java 17. This is getting inconveniently out of sync with what devs have > installed. E.g we can't even jdeprscan for Java 11 or 8 with this version. > This should be pushed back to 17 or further if possible. The bleeding edge is > too bloody. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8575) Replace a list with O(N²) performance by O(N) at least during iteration.
Guillaume Nodet created MNG-8575: Summary: Replace a list with O(N²) performance by O(N) at least during iteration. Key: MNG-8575 URL: https://issues.apache.org/jira/browse/MNG-8575 Project: Maven Issue Type: Task Reporter: Guillaume Nodet GitHub Pull Request: https://github.com/apache/maven/pull/2092 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8562] remove "child" attributes from [maven]
gnodet merged PR #2101: URL: https://github.com/apache/maven/pull/2101 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (MNG-8569) Deprecate and remove version ranges
[
https://issues.apache.org/jira/browse/MNG-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925969#comment-17925969
]
Guillaume Nodet edited comment on MNG-8569 at 2/11/25 12:16 PM:
{quote}If you're selecting the lowest or a default version, would this be just
the same as specifying that version explicitly?
{quote}
Yes if you're using an open range. No if the range is closed such as
{{{}[2.1,3]{}}}.
{quote}Also, the reason developers use ranges is generally to automatically
pick up the latest release, possibly within a major version, without having to
notice it's been released and change their code, so I'm not sure anyone will
really want the lowest version.
{quote}
Yes, I'm mostly focusing on restricting the range to a list of compatible
versions. I think that's a valid use case.
was (Author: gnt):
> If you're selecting the lowest or a default version, would this be just the
> same as specifying that version explicitly?
Yes if you're using an open range. No if the range is closed such as
{{[2.1,3]}}.
> Also, the reason developers use ranges is generally to automatically pick up
> the latest release, possibly within a major version, without having to notice
> it's been released and change their code, so I'm not sure anyone will really
> want the lowest version.
Yes, I'm mostly focusing on restricting the range to a list of compatible
versions. I think that's a valid use case.
> Deprecate and remove version ranges
> ---
>
> Key: MNG-8569
> URL: https://issues.apache.org/jira/browse/MNG-8569
> Project: Maven
> Issue Type: Improvement
>Reporter: Elliotte Rusty Harold
>Priority: Critical
>
> To protect Maven users, we should eliminate, or at the very least warn, when
> version ranges are used in dependency elements. See
> [https://jlbp.dev/JLBP-14] for the rationale. tldr; version ranges make
> projects vulnerable to malicious changes of ownership in dependencies that
> can lead to remotely exploitable arbitrary code execution. I'd rate this
> about a 9.0 on the severity scale.
> I don't know of an attack using this vector in Java (yet) but it has
> been used multiple times in other ecosystems to steal bitcoins and
> install malware. Java has been lucky so far, but we are by no means
> immune to it.
> Since this is a compatibility breaking change, which I don't take likely but
> IMHO is worth it in this case, use a multi-step process:
> # Discourage this in the docs for version ranges, especially the POM
> reference.
> # Warn about this in the build when version ranges are encountered.
> # Formally deprecate the relevant code in the repo. (Might not be necessary.)
> # Add a switch (system property) to disable version ranges. Switch is off by
> default.
> # Turn the switch on by default.
> # Remove the switch.
> This might take a few years, so let's start now. It's also possible an active
> attack will push us to do this overnight. If we start now, maybe we'll be
> lucky enough to avoid emergency responses in the future.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Dump public IPs of runners [maven]
slawekjaranowski commented on code in PR #2103:
URL: https://github.com/apache/maven/pull/2103#discussion_r1950740414
##
.github/workflows/maven.yml:
##
@@ -209,6 +212,9 @@ jobs:
maven-${{ runner.os }}-its
maven-${{ runner.os }}-
+ - name: Show IP
+run: curl https://api.ipify.org
Review Comment:
add `shell: bash` especially for windows ...
--
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
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (MRESOLVER-671) Don't require Java 21
[ https://issues.apache.org/jira/browse/MRESOLVER-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925986#comment-17925986 ] Michael Osipov commented on MRESOLVER-671: -- I fully agree with [~elharo] regarding the unnecessary high bar. > Don't require Java 21 > - > > Key: MRESOLVER-671 > URL: https://issues.apache.org/jira/browse/MRESOLVER-671 > Project: Maven Resolver > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > Apparently maven-resolver now requires Java 21 to build. It won't build even > with Java 17. This is getting inconveniently out of sync with what devs have > installed. E.g we can't even jdeprscan for Java 11 or 8 with this version. > This should be pushed back to 17 or further if possible. The bleeding edge is > too bloody. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925657#comment-17925657
]
Matthias Bünger edited comment on MNGSITE-529 at 2/11/25 6:32 PM:
--
||Plugin||Done?||
|---||
|clean|(/)|
|compiler|(/)|
|deploy|(/)|
|failsafe|(!)|
|install|(!)|
|resources|(!)|
|site|(!)|
|surefire|(!)|
|verifier|(!)|
|||
|ear|(!)|
|ejb|(!)|
|jar|(!)|
|rar|(!)|
|war|(!)|
|app-client/acr|(!)|
|shade|(!)|
|source|(!)|
|jlink|(!)|
|jmod|(!)|
||-|
|changelog|(x)|
|changes|(x)|
|checkstyle|(x)|
|doap|(x)|
|javadoc|(x)|
|jdeps|(x)|
|jxr|(x)|
|linkcheck|(x)|
|pmd|(x)|
|plugin-report|(x)|
|project-info-reports|(x)|
|surefire-report|(!)|
|--|--|
|antrun|(x)|
|artifact|(x)|
|archetype|(x)|
|assembly|(x)|
|dependency|(x)|
|enforcer|(x)|
|gpg|(x)|
|help|(x)|
|invoker|(x)|
|jarsigner|(x)|
|jdeprscan|(x)|
|pdf|(x)|
|plugin|(x)|
|release|(x)|
|remote-resources|(x)|
|scm|(x)|
|scm-publish|(x)|
|scripting|(x)|
|stage|(x)|
|toolchains|(x)|
|wrapper|(x)|
was (Author: JIRAUSER302100):
||Plugin||Done?||
|---||
|clean|(/)|
|compiler|(/)|
|deploy|(/)|
|failsafe|(!)|
|install|(!)|
|resources|(!)|
|site|(!)|
|surefire|(!)|
|verifier|(!)|
|||
|ear|(!)|
|ejb|(!)|
|jar|(x)|
|rar|(x)|
|war|(x)|
|app-client/acr|(x)|
|shade|(x)|
|source|(x)|
|jlink|(x)|
|jmod|(x)|
||-|
|changelog|(x)|
|changes|(x)|
|checkstyle|(x)|
|doap|(x)|
|javadoc|(x)|
|jdeps|(x)|
|jxr|(x)|
|linkcheck|(x)|
|pmd|(x)|
|plugin-report|(x)|
|project-info-reports|(x)|
|surefire-report|(!)|
|--|--|
|antrun|(x)|
|artifact|(x)|
|archetype|(x)|
|assembly|(x)|
|dependency|(x)|
|enforcer|(x)|
|gpg|(x)|
|help|(x)|
|invoker|(x)|
|jarsigner|(x)|
|jdeprscan|(x)|
|pdf|(x)|
|plugin|(x)|
|release|(x)|
|remote-resources|(x)|
|scm|(x)|
|scm-publish|(x)|
|scripting|(x)|
|stage|(x)|
|toolchains|(x)|
|wrapper|(x)|
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926124#comment-17926124
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #167:
URL: https://github.com/apache/maven-checkstyle-plugin/pull/167
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-checkstyle-plugin]
Bukama opened a new pull request, #167: URL: https://github.com/apache/maven-checkstyle-plugin/pull/167 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926125#comment-17926125
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #35:
URL: https://github.com/apache/maven-doap-plugin/pull/35
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-javadoc-plugin]
Bukama opened a new pull request, #360: URL: https://github.com/apache/maven-javadoc-plugin/pull/360 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926126#comment-17926126
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #360:
URL: https://github.com/apache/maven-javadoc-plugin/pull/360
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-jdeps-plugin]
Bukama opened a new pull request, #21: URL: https://github.com/apache/maven-jdeps-plugin/pull/21 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926127#comment-17926127
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #21:
URL: https://github.com/apache/maven-jdeps-plugin/pull/21
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926132#comment-17926132
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #182:
URL: https://github.com/apache/maven-pmd-plugin/pull/182
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-enforcer]
Bukama opened a new pull request, #351: URL: https://github.com/apache/maven-enforcer/pull/351 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.codehaus.plexus:plexus-component-annotations from 2.1.0 to 2.2.0 [maven]
slachiewicz commented on PR #2100: URL: https://github.com/apache/maven/pull/2100#issuecomment-2651830134 Not sure what's wrong with this version. As we finały marked more classes as deprecated and internally now if someone opens code or tries to recompile it - it's more visible. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926143#comment-17926143
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #351:
URL: https://github.com/apache/maven-enforcer/pull/351
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926144#comment-17926144
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #129:
URL: https://github.com/apache/maven-gpg-plugin/pull/129
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-gpg-plugin]
Bukama opened a new pull request, #129: URL: https://github.com/apache/maven-gpg-plugin/pull/129 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926145#comment-17926145
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #128:
URL: https://github.com/apache/maven-help-plugin/pull/128
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-help-plugin]
Bukama opened a new pull request, #128: URL: https://github.com/apache/maven-help-plugin/pull/128 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-invoker-plugin]
Bukama opened a new pull request, #279: URL: https://github.com/apache/maven-invoker-plugin/pull/279 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926146#comment-17926146
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #279:
URL: https://github.com/apache/maven-invoker-plugin/pull/279
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-jxr]
Bukama opened a new pull request, #134: URL: https://github.com/apache/maven-jxr/pull/134 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926130#comment-17926130
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #134:
URL: https://github.com/apache/maven-jxr/pull/134
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-linkcheck-plugin]
Bukama opened a new pull request, #6: URL: https://github.com/apache/maven-linkcheck-plugin/pull/6 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926131#comment-17926131
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #6:
URL: https://github.com/apache/maven-linkcheck-plugin/pull/6
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-pmd-plugin]
Bukama opened a new pull request, #182: URL: https://github.com/apache/maven-pmd-plugin/pull/182 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Use JUnit version from parent [maven-compiler-plugin]
slawekjaranowski merged PR #299: URL: https://github.com/apache/maven-compiler-plugin/pull/299 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-plugin-tools]
Bukama opened a new pull request, #352: URL: https://github.com/apache/maven-plugin-tools/pull/352 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.junit.jupiter:junit-jupiter-params from 5.10.2 to 5.11.4 [maven-compiler-plugin]
dependabot[bot] commented on PR #284: URL: https://github.com/apache/maven-compiler-plugin/pull/284#issuecomment-2651767957 Looks like org.junit.jupiter:junit-jupiter-params is up-to-date now, so this is no longer needed. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.junit.jupiter:junit-jupiter-api from 5.10.2 to 5.11.4 [maven-compiler-plugin]
dependabot[bot] commented on PR #291: URL: https://github.com/apache/maven-compiler-plugin/pull/291#issuecomment-2651767489 Looks like org.junit.jupiter:junit-jupiter-api is up-to-date now, so this is no longer needed. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926133#comment-17926133
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #352:
URL: https://github.com/apache/maven-plugin-tools/pull/352
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925657#comment-17925657
]
Matthias Bünger edited comment on MNGSITE-529 at 2/11/25 6:55 PM:
--
||Plugin||Done?||
|---||
|clean|(/)|
|compiler|(/)|
|deploy|(/)|
|failsafe|(!)|
|install|(!)|
|resources|(!)|
|site|(!)|
|surefire|(!)|
|verifier|(!)|
|||
|ear|(!)|
|ejb|(!)|
|jar|(!)|
|rar|(!)|
|war|(!)|
|app-client/acr|(!)|
|shade|(!)|
|source|(!)|
|jlink|(!)|
|jmod|(!)|
||-|
|changelog|(!)|
|changes|(!)|
|checkstyle|(!)|
|doap|(!)|
|javadoc|(!)|
|jdeps|(!)|
|jxr|(!)|
|linkcheck|(!)|
|pmd|(!)|
|plugin-report|(!)|
|project-info-reports|(x)|
|surefire-report|(!)|
|--|--|
|antrun|(x)|
|artifact|(x)|
|archetype|(x)|
|assembly|(x)|
|dependency|(x)|
|enforcer|(x)|
|gpg|(x)|
|help|(x)|
|invoker|(x)|
|jarsigner|(x)|
|jdeprscan|(x)|
|pdf|(x)|
|plugin|(x)|
|release|(x)|
|remote-resources|(x)|
|scm|(x)|
|scm-publish|(x)|
|scripting|(x)|
|stage|(x)|
|toolchains|(x)|
|wrapper|(x)|
was (Author: JIRAUSER302100):
||Plugin||Done?||
|---||
|clean|(/)|
|compiler|(/)|
|deploy|(/)|
|failsafe|(!)|
|install|(!)|
|resources|(!)|
|site|(!)|
|surefire|(!)|
|verifier|(!)|
|||
|ear|(!)|
|ejb|(!)|
|jar|(!)|
|rar|(!)|
|war|(!)|
|app-client/acr|(!)|
|shade|(!)|
|source|(!)|
|jlink|(!)|
|jmod|(!)|
||-|
|changelog|(x)|
|changes|(x)|
|checkstyle|(x)|
|doap|(x)|
|javadoc|(x)|
|jdeps|(x)|
|jxr|(x)|
|linkcheck|(x)|
|pmd|(x)|
|plugin-report|(x)|
|project-info-reports|(x)|
|surefire-report|(!)|
|--|--|
|antrun|(x)|
|artifact|(x)|
|archetype|(x)|
|assembly|(x)|
|dependency|(x)|
|enforcer|(x)|
|gpg|(x)|
|help|(x)|
|invoker|(x)|
|jarsigner|(x)|
|jdeprscan|(x)|
|pdf|(x)|
|plugin|(x)|
|release|(x)|
|remote-resources|(x)|
|scm|(x)|
|scm-publish|(x)|
|scripting|(x)|
|stage|(x)|
|toolchains|(x)|
|wrapper|(x)|
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump org.junit.jupiter:junit-jupiter-api from 5.10.2 to 5.11.4 [maven-compiler-plugin]
dependabot[bot] closed pull request #291: Bump org.junit.jupiter:junit-jupiter-api from 5.10.2 to 5.11.4 URL: https://github.com/apache/maven-compiler-plugin/pull/291 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.junit.jupiter:junit-jupiter-params from 5.10.2 to 5.11.4 [maven-compiler-plugin]
dependabot[bot] closed pull request #284: Bump org.junit.jupiter:junit-jupiter-params from 5.10.2 to 5.11.4 URL: https://github.com/apache/maven-compiler-plugin/pull/284 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-jarsigner-plugin]
Bukama opened a new pull request, #46: URL: https://github.com/apache/maven-jarsigner-plugin/pull/46 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926147#comment-17926147
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #46:
URL: https://github.com/apache/maven-jarsigner-plugin/pull/46
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-jdeprscan-plugin]
Bukama opened a new pull request, #33: URL: https://github.com/apache/maven-jdeprscan-plugin/pull/33 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump org.codehaus.plexus:plexus-java from 1.3.0 to 1.4.0 [maven-surefire]
dependabot[bot] opened a new pull request, #810: URL: https://github.com/apache/maven-surefire/pull/810 Bumps [org.codehaus.plexus:plexus-java](https://github.com/codehaus-plexus/plexus-languages) from 1.3.0 to 1.4.0. Release notes Sourced from https://github.com/codehaus-plexus/plexus-languages/releases";>org.codehaus.plexus:plexus-java's releases. 1.4.0 🚀 New features and improvements Bump org.ow2.asm:asm from 9.7 to 9.7.1 - JDK 24 support (https://redirect.github.com/codehaus-plexus/plexus-languages/pull/194";>#194) https://github.com/jorsol";>@jorsol 📦 Dependency updates Bump org.codehaus.plexus:plexus from 19 to 20 (https://redirect.github.com/codehaus-plexus/plexus-languages/pull/203";>#203) @https://github.com/apps/dependabot";>dependabot[bot] Bump org.assertj:assertj-core from 3.27.2 to 3.27.3 (https://redirect.github.com/codehaus-plexus/plexus-languages/pull/201";>#201) @https://github.com/apps/dependabot";>dependabot[bot] Bump org.assertj:assertj-core from 3.27.1 to 3.27.2 (https://redirect.github.com/codehaus-plexus/plexus-languages/pull/200";>#200) @https://github.com/apps/dependabot";>dependabot[bot] Bump org.assertj:assertj-core from 3.27.0 to 3.27.1 (https://redirect.github.com/codehaus-plexus/plexus-languages/pull/199";>#199) @https://github.com/apps/dependabot";>dependabot[bot] Bump org.assertj:assertj-core from 3.26.3 to 3.27.0 (https://redirect.github.com/codehaus-plexus/plexus-languages/pull/198";>#198) @https://github.com/apps/dependabot";>dependabot[bot] Bump com.thoughtworks.qdox:qdox from 2.1.0 to 2.2.0 (https://redirect.github.com/codehaus-plexus/plexus-languages/pull/197";>#197) @https://github.com/apps/dependabot";>dependabot[bot] Bump org.ow2.asm:asm from 9.7 to 9.7.1 - JDK 24 support (https://redirect.github.com/codehaus-plexus/plexus-languages/pull/194";>#194) https://github.com/jorsol";>@jorsol 👻 Maintenance Disable deploy job on GitHub (https://redirect.github.com/codehaus-plexus/plexus-languages/pull/202";>#202) https://github.com/slawekjaranowski";>@slawekjaranowski Added CI for JDK 24-ea (https://redirect.github.com/codehaus-plexus/plexus-languages/pull/196";>#196) https://github.com/slachiewicz";>@slachiewicz Commits https://github.com/codehaus-plexus/plexus-languages/commit/04fc2d11f6e3b78981fc3e62d64aef37c6d299a9";>04fc2d1 [maven-release-plugin] prepare release plexus-languages-1.4.0 https://github.com/codehaus-plexus/plexus-languages/commit/452c8f157f29c2bdfe1d19dbe8c0c07aa641d559";>452c8f1 Bump org.codehaus.plexus:plexus from 19 to 20 (https://redirect.github.com/codehaus-plexus/plexus-languages/issues/203";>#203) https://github.com/codehaus-plexus/plexus-languages/commit/77283f38d7319e1bb9b52b65eca96c4e45e13137";>77283f3 Disable deploy job on GitHub https://github.com/codehaus-plexus/plexus-languages/commit/1e651ae701f69dc1bb3b481d763e7983f1db392f";>1e651ae Bump org.assertj:assertj-core from 3.27.2 to 3.27.3 https://github.com/codehaus-plexus/plexus-languages/commit/fe8e3677a3c64f1b83b9ce48a18ac2a3e0599f80";>fe8e367 Bump org.assertj:assertj-core from 3.27.1 to 3.27.2 https://github.com/codehaus-plexus/plexus-languages/commit/e50bd0871ccbff67b0b340c160e79499bc30025c";>e50bd08 Bump org.assertj:assertj-core from 3.27.0 to 3.27.1 https://github.com/codehaus-plexus/plexus-languages/commit/859c03fdedae3e53d39cf1a0d3bfced43c6b083d";>859c03f Bump org.assertj:assertj-core from 3.26.3 to 3.27.0 https://github.com/codehaus-plexus/plexus-languages/commit/390c51316c67c0616ab94d13b00bee2082936d28";>390c513 Bump com.thoughtworks.qdox:qdox from 2.1.0 to 2.2.0 https://github.com/codehaus-plexus/plexus-languages/commit/9767a26fa43353a686897b189ba0f7c3fc0dc907";>9767a26 Added sample helloworld compiled with Java 23 and 24 https://github.com/codehaus-plexus/plexus-languages/commit/1978ee7754065815fda640a0e188983cacd08278";>1978ee7 Bump org.ow2.asm:asm from 9.7 to 9.7.1 - JDK 24 support Additional commits viewable in https://github.com/codehaus-plexus/plexus-languages/compare/plexus-languages-1.3.0...plexus-languages-1.4.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR
Re: [PR] [MNG-8577] Project POM hierarchy [maven]
cstamas merged PR #2104: URL: https://github.com/apache/maven/pull/2104 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-8577) Project POM hierarchy cleanup
[ https://issues.apache.org/jira/browse/MNG-8577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-8577. Resolution: Fixed > Project POM hierarchy cleanup > - > > Key: MNG-8577 > URL: https://issues.apache.org/jira/browse/MNG-8577 > Project: Maven > Issue Type: Task > Components: Bootstrap & Build >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-rc-3 > > > Recently we had a "reshuffle" of build layout (introduced impl/ and compat/ > sub directories), but parents were not aligned. > Result should be to have these two (parent-child and subprojects) aligned, as > here: > https://gist.github.com/cstamas/247c61ee1b856c3f464f34fc8d56dfc8 > https://gist.github.com/cstamas/b6eb40116141e9715f59aa9a7e0a3b9f -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-scm]
Bukama opened a new pull request, #234: URL: https://github.com/apache/maven-scm/pull/234 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-scm-publish-plugin]
Bukama opened a new pull request, #52: URL: https://github.com/apache/maven-scm-publish-plugin/pull/52 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-529) Correct label of plugin-info.html to "Plugin Documentation" in our plugins' site.xml
[
https://issues.apache.org/jira/browse/MNGSITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926151#comment-17926151
]
ASF GitHub Bot commented on MNGSITE-529:
Bukama opened a new pull request, #234:
URL: https://github.com/apache/maven-scm/pull/234
(no comment)
> Correct label of plugin-info.html to "Plugin Documentation" in our plugins'
> site.xml
>
>
> Key: MNGSITE-529
> URL: https://issues.apache.org/jira/browse/MNGSITE-529
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Matthias Bünger
>Priority: Major
>
> This is an umbrella ticket.
> As complained in MPLUGIN-492, all of our {{site.xml}} use the label "Goals"
> for {{plugin-info.html}} which is wrong because this report contains more
> than the goal listing, it also contain requirements, history, etc.
> We should align it everywhere to the original label: "Plugin Documentation"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-scripting-plugin]
Bukama opened a new pull request, #33: URL: https://github.com/apache/maven-scripting-plugin/pull/33 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Upgrade to Maven 4.0.0-rc-2 [maven-install-plugin]
slawekjaranowski opened a new pull request, #114: URL: https://github.com/apache/maven-install-plugin/pull/114 (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 unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Upgrade to Maven 4.0.0-rc-2 [maven-install-plugin]
gnodet commented on code in PR #114: URL: https://github.com/apache/maven-install-plugin/pull/114#discussion_r1951580306 ## .github/workflows/maven-verify.yml: ## @@ -26,6 +26,5 @@ jobs: name: Verify uses: apache/maven-gh-actions-shared/.github/workflows/maven-verify.yml@v4 with: - ff-maven: "4.0.0-beta-5" # Maven version for fail-fast-build - maven-matrix: '[ "4.0.0-beta-5" ]' - jdk-matrix: '[ "17", "21" ]' + maven4-build: true Review Comment: What's the effect of this flag ? -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Upgrade to Maven 4.0.0-rc-2 [maven-install-plugin]
slawekjaranowski commented on code in PR #114: URL: https://github.com/apache/maven-install-plugin/pull/114#discussion_r1951590659 ## .github/workflows/maven-verify.yml: ## @@ -26,6 +26,5 @@ jobs: name: Verify uses: apache/maven-gh-actions-shared/.github/workflows/maven-verify.yml@v4 with: - ff-maven: "4.0.0-beta-5" # Maven version for fail-fast-build - maven-matrix: '[ "4.0.0-beta-5" ]' - jdk-matrix: '[ "17", "21" ]' + maven4-build: true Review Comment: https://github.com/apache/maven-gh-actions-shared?tab=readme-ov-file#build-with-maven-4-only -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNGSITE-529] Rename "Goals" to "Plugin Documentation" [maven-plugin-tools]
slawekjaranowski commented on PR #352: URL: https://github.com/apache/maven-plugin-tools/pull/352#issuecomment-2652081137 3.x branch -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
