[jira] [Created] (MSHARED-1396) Upgrade to Doxia 2.0.0-M11
Michael Osipov created MSHARED-1396: --- Summary: Upgrade to Doxia 2.0.0-M11 Key: MSHARED-1396 URL: https://issues.apache.org/jira/browse/MSHARED-1396 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-reporting-api Reporter: Michael Osipov Assignee: Michael Osipov Fix For: maven-reporting-api-4.0.0, maven-reporting-api-4.0.0-M12 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [DOXIASITETOOLS-338] Upgrade to Parent 42 [maven-doxia-sitetools]
asfgit closed pull request #153: [DOXIASITETOOLS-338] Upgrade to Parent 42 URL: https://github.com/apache/maven-doxia-sitetools/pull/153 -- 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] (DOXIASITETOOLS-338) Upgrade to Parent 42
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845236#comment-17845236 ] ASF GitHub Bot commented on DOXIASITETOOLS-338: --- asfgit closed pull request #153: [DOXIASITETOOLS-338] Upgrade to Parent 42 URL: https://github.com/apache/maven-doxia-sitetools/pull/153 > Upgrade to Parent 42 > > > Key: DOXIASITETOOLS-338 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-338 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0, 2.0.0-M19 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIASITETOOLS-338) Upgrade to Parent 42 and Maven 3.6.3
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIASITETOOLS-338. - Resolution: Fixed Fixed with [6f232441482c220e8d31c05a50161ca55c45f30d|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=6f232441482c220e8d31c05a50161ca55c45f30d]. > Upgrade to Parent 42 and Maven 3.6.3 > > > Key: DOXIASITETOOLS-338 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-338 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0, 2.0.0-M19 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-338) Upgrade to Parent 42 and Maven 3.6.3
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-338: -- Summary: Upgrade to Parent 42 and Maven 3.6.3 (was: Upgrade to Parent 42) > Upgrade to Parent 42 and Maven 3.6.3 > > > Key: DOXIASITETOOLS-338 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-338 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0, 2.0.0-M19 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-395) Build doesn't fail for invalid CPD format
Andreas Dangel created MPMD-395: --- Summary: Build doesn't fail for invalid CPD format Key: MPMD-395 URL: https://issues.apache.org/jira/browse/MPMD-395 Project: Maven PMD Plugin Issue Type: Bug Components: CPD Affects Versions: 3.22.0 Reporter: Andreas Dangel Assignee: Andreas Dangel See [https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2094371392] If an exception occurs while the CPD report is created, the exception is only logged but doesn't fail the build. This means, that build appears to be successful, although it didn't produce all expected build artifacts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1396) Upgrade to Doxia 2.0.0-M11
[ https://issues.apache.org/jira/browse/MSHARED-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1396. --- Resolution: Fixed Fixed with [7c0a727ea22e2c31731b5165bf5c794f5f4bc850|https://gitbox.apache.org/repos/asf?p=maven-reporting-api.git;a=commit;h=7c0a727ea22e2c31731b5165bf5c794f5f4bc850]. > Upgrade to Doxia 2.0.0-M11 > -- > > Key: MSHARED-1396 > URL: https://issues.apache.org/jira/browse/MSHARED-1396 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-api-4.0.0, maven-reporting-api-4.0.0-M12 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] [MPMD-395] Build doesn't fail for invalid CPD format [maven-pmd-plugin]
adangel opened a new pull request, #150: URL: https://github.com/apache/maven-pmd-plugin/pull/150 https://issues.apache.org/jira/browse/MPMD-395 Refs https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2094372771 Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MPMD) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA 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 `[MPMD-XXX] - Subject of the JIRA Ticket`, where you replace `MPMD-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA 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. - [ ] 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) - [x] 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] (MPMD-395) Build doesn't fail for invalid CPD format
[ https://issues.apache.org/jira/browse/MPMD-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845251#comment-17845251 ] ASF GitHub Bot commented on MPMD-395: - adangel opened a new pull request, #150: URL: https://github.com/apache/maven-pmd-plugin/pull/150 https://issues.apache.org/jira/browse/MPMD-395 Refs https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2094372771 Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MPMD) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA 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 `[MPMD-XXX] - Subject of the JIRA Ticket`, where you replace `MPMD-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA 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. - [ ] 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) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). > Build doesn't fail for invalid CPD format > - > > Key: MPMD-395 > URL: https://issues.apache.org/jira/browse/MPMD-395 > Project: Maven PMD Plugin > Issue Type: Bug > Components: CPD >Affects Versions: 3.22.0 >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > > See > [https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2094371392] > > If an exception occurs while the CPD report is created, the exception is only > logged but doesn't fail the build. This means, that build appears to be > successful, although it didn't produce all expected build artifacts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPMD-379] Upgrade to use PMD 7.0.0 by default [maven-pmd-plugin]
adangel commented on PR #144: URL: https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2104232352 > @adangel That merge was a pile of junk. You imported all intermediate work into master making it impossible to trace down the actual change. Don't do that again please, always squash and rebase first. Clearly a -1 for the methodology. I was not aware, that the general rule of thumb for merging PRs is "squash and rebase". If this is the common decision around the maven project, then I'd expect this to be clearly documented, e.g. on https://maven.apache.org/developers/conventions/git.html . I'm missing there an example on how to merge PRs which consist of more than one commits. E.g. it says there "commit it to a branch, fix it up, and merge the branch." instead of "commit it to a branch, fix it up and squash and rebase this branch onto master/main". To be honest, I'm not sure if it would have prevented my merge push... (because I don't think I would have read this doc before pushing). Following the discussion on https://github.com/apache/maven-fluido-skin/pull/39#issuecomment-1166243030 - which is very helpful - it seems the decision is to try to have a linear history on the master/main branch: > Simply we require linear commit on master branch - from master perspective final result is important - we needn't history of work on PR in master. This decision should be somehow officially be documented to be transparent for everyone... For me, as a casual committer, who only pushes once every blue moon and working mostly on other projects, I would suggest to - Update the PR Template on GitHub with a section "Before merging... Maven Project requires a linear history, ... squash+rebase. Either before merge or whoever merges this. See also https://maven.apache.org/developers/conventions/git.html";. I think, this would help to remember this decision. - Enforce via push/update hook to prevent merge commits pushed to master/main. GitHub has some options to enforce a linear history. I'm sure, the infra team can configure something similar on gitbox.apache.org. That would at least prevent someone like me from simply pushing a merge. Of course, it wouldn't prevent me from pushing the complete rebased history of a PR (which is also not desired)... -- 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] (MPMD-379) Upgrade to use PMD 7.0.0 by default
[ https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845253#comment-17845253 ] ASF GitHub Bot commented on MPMD-379: - adangel commented on PR #144: URL: https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2104232352 > @adangel That merge was a pile of junk. You imported all intermediate work into master making it impossible to trace down the actual change. Don't do that again please, always squash and rebase first. Clearly a -1 for the methodology. I was not aware, that the general rule of thumb for merging PRs is "squash and rebase". If this is the common decision around the maven project, then I'd expect this to be clearly documented, e.g. on https://maven.apache.org/developers/conventions/git.html . I'm missing there an example on how to merge PRs which consist of more than one commits. E.g. it says there "commit it to a branch, fix it up, and merge the branch." instead of "commit it to a branch, fix it up and squash and rebase this branch onto master/main". To be honest, I'm not sure if it would have prevented my merge push... (because I don't think I would have read this doc before pushing). Following the discussion on https://github.com/apache/maven-fluido-skin/pull/39#issuecomment-1166243030 - which is very helpful - it seems the decision is to try to have a linear history on the master/main branch: > Simply we require linear commit on master branch - from master perspective final result is important - we needn't history of work on PR in master. This decision should be somehow officially be documented to be transparent for everyone... For me, as a casual committer, who only pushes once every blue moon and working mostly on other projects, I would suggest to - Update the PR Template on GitHub with a section "Before merging... Maven Project requires a linear history, ... squash+rebase. Either before merge or whoever merges this. See also https://maven.apache.org/developers/conventions/git.html";. I think, this would help to remember this decision. - Enforce via push/update hook to prevent merge commits pushed to master/main. GitHub has some options to enforce a linear history. I'm sure, the infra team can configure something similar on gitbox.apache.org. That would at least prevent someone like me from simply pushing a merge. Of course, it wouldn't prevent me from pushing the complete rebased history of a PR (which is also not desired)... > Upgrade to use PMD 7.0.0 by default > --- > > Key: MPMD-379 > URL: https://issues.apache.org/jira/browse/MPMD-379 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.22.0 > > > Add support for the new major version of PMD. > This gives support for analyzing Java 21 code. > The upgrade from PMD 6 to PMD 7 is a major upgrade, that might impact > end-users, if they use custom rulesets (see > [https://maven.apache.org/plugins/maven-pmd-plugin/examples/usingRuleSets.html]) > or if they override the dependencies to upgrade PMD at runtime and currently > use PMD 6.x (see > [https://maven.apache.org/plugins/maven-pmd-plugin/examples/upgrading-PMD-at-runtime.html]). > > Most likely, end-users have to review their rulesets and migrate them to PMD > 7. Rules might have been renamed or replaced. See > [https://docs.pmd-code.org/latest/pmd_release_notes_pmd7.html] and > [https://docs.pmd-code.org/latest/pmd_userdocs_migrating_to_pmd7.html] . > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPMD-395] Build doesn't fail for invalid CPD format [maven-pmd-plugin]
michael-o commented on PR #150: URL: https://github.com/apache/maven-pmd-plugin/pull/150#issuecomment-2104284197 Is this the fix for https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2094371392? -- 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] (MPMD-395) Build doesn't fail for invalid CPD format
[ https://issues.apache.org/jira/browse/MPMD-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845265#comment-17845265 ] ASF GitHub Bot commented on MPMD-395: - michael-o commented on PR #150: URL: https://github.com/apache/maven-pmd-plugin/pull/150#issuecomment-2104284197 Is this the fix for https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2094371392? > Build doesn't fail for invalid CPD format > - > > Key: MPMD-395 > URL: https://issues.apache.org/jira/browse/MPMD-395 > Project: Maven PMD Plugin > Issue Type: Bug > Components: CPD >Affects Versions: 3.22.0 >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > > See > [https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2094371392] > > If an exception occurs while the CPD report is created, the exception is only > logged but doesn't fail the build. This means, that build appears to be > successful, although it didn't produce all expected build artifacts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MWRAPPER-138) Maven Wrapper script warning on CentOS 7
Tamas Cservenak created MWRAPPER-138:
Summary: Maven Wrapper script warning on CentOS 7
Key: MWRAPPER-138
URL: https://issues.apache.org/jira/browse/MWRAPPER-138
Project: Maven Wrapper
Issue Type: Bug
Components: Maven Wrapper Scripts
Affects Versions: 3.3.1
Reporter: Tamas Cservenak
Updated Maven Wrapper to 3.3.1 (using defaults, so script-only is used), and
now {{mvnw}} script emits warning on this line:
[https://github.com/apache/maven-wrapper/blob/0e0c7409f858f52353d5450975526cb249c0d21f/maven-wrapper-distribution/src/resources/only-mvnw#L86]
"cannot change local (UTF-8): No such file or directory"
It seems CentOS does not support C.utf8 only in 8 and 9, but no prior versions.
Unsure what the consequence is of this issue, nor what should be the fix, I
just created this issue to let us know about it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-379) Upgrade to use PMD 7.0.0 by default
[ https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845321#comment-17845321 ] Gary Gregory commented on MPMD-379: --- Note that GitHub helps you there with its "Squash and Merge" in one go button. Gary > Upgrade to use PMD 7.0.0 by default > --- > > Key: MPMD-379 > URL: https://issues.apache.org/jira/browse/MPMD-379 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.22.0 > > > Add support for the new major version of PMD. > This gives support for analyzing Java 21 code. > The upgrade from PMD 6 to PMD 7 is a major upgrade, that might impact > end-users, if they use custom rulesets (see > [https://maven.apache.org/plugins/maven-pmd-plugin/examples/usingRuleSets.html]) > or if they override the dependencies to upgrade PMD at runtime and currently > use PMD 6.x (see > [https://maven.apache.org/plugins/maven-pmd-plugin/examples/upgrading-PMD-at-runtime.html]). > > Most likely, end-users have to review their rulesets and migrate them to PMD > 7. Rules might have been renamed or replaced. See > [https://docs.pmd-code.org/latest/pmd_release_notes_pmd7.html] and > [https://docs.pmd-code.org/latest/pmd_userdocs_migrating_to_pmd7.html] . > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MSHARED-1393] Allow to exclude classes from verification [maven-dependency-analyzer]
garydgregory commented on PR #118: URL: https://github.com/apache/maven-dependency-analyzer/pull/118#issuecomment-2104602026 Hello @slawekjaranowski TY for the heads up. OK, I'll adapt when this trickles down. -- 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] (MSHARED-1393) Allow to exclude classes from verification - revert MSHARED-1248
[ https://issues.apache.org/jira/browse/MSHARED-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845349#comment-17845349 ] ASF GitHub Bot commented on MSHARED-1393: - garydgregory commented on PR #118: URL: https://github.com/apache/maven-dependency-analyzer/pull/118#issuecomment-2104602026 Hello @slawekjaranowski TY for the heads up. OK, I'll adapt when this trickles down. > Allow to exclude classes from verification - revert MSHARED-1248 > > > Key: MSHARED-1393 > URL: https://issues.apache.org/jira/browse/MSHARED-1393 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-dependency-analyzer >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-dependency-analyzer-1.14.0 > > > In some situation project can contains corrupted classes. > Instead of skip it with only warning like in: MSHARED-1248 we should have > possibility to skip only known corrupted classes - not all. > When we skip all - we can stop analyzing anything when asm does not support > next byte code version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (MPMD-395) Build doesn't fail for invalid CPD format
[ https://issues.apache.org/jira/browse/MPMD-395 ] Michael Osipov deleted comment on MPMD-395: - was (Author: githubbot): michael-o commented on PR #150: URL: https://github.com/apache/maven-pmd-plugin/pull/150#issuecomment-2104284197 Is this the fix for https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2094371392? > Build doesn't fail for invalid CPD format > - > > Key: MPMD-395 > URL: https://issues.apache.org/jira/browse/MPMD-395 > Project: Maven PMD Plugin > Issue Type: Bug > Components: CPD >Affects Versions: 3.22.0 >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > > See > [https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2094371392] > > If an exception occurs while the CPD report is created, the exception is only > logged but doesn't fail the build. This means, that build appears to be > successful, although it didn't produce all expected build artifacts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPMD-395] Build doesn't fail for invalid CPD format [maven-pmd-plugin]
michael-o commented on PR #150: URL: https://github.com/apache/maven-pmd-plugin/pull/150#issuecomment-2104773821 Will try to review in the next couple of days. -- 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] (MPMD-395) Build doesn't fail for invalid CPD format
[ https://issues.apache.org/jira/browse/MPMD-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845389#comment-17845389 ] ASF GitHub Bot commented on MPMD-395: - michael-o commented on PR #150: URL: https://github.com/apache/maven-pmd-plugin/pull/150#issuecomment-2104773821 Will try to review in the next couple of days. > Build doesn't fail for invalid CPD format > - > > Key: MPMD-395 > URL: https://issues.apache.org/jira/browse/MPMD-395 > Project: Maven PMD Plugin > Issue Type: Bug > Components: CPD >Affects Versions: 3.22.0 >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > > See > [https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2094371392] > > If an exception occurs while the CPD report is created, the exception is only > logged but doesn't fail the build. This means, that build appears to be > successful, although it didn't produce all expected build artifacts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump m-wrapper-p from 3.2.0 to 3.3.1 [maven-gh-actions-shared]
slawekjaranowski opened a new pull request, #101: URL: https://github.com/apache/maven-gh-actions-shared/pull/101 (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] [Created] (MSOURCES-148) The plugin should respect the --update-dependencies for final versions
Benjamin Muschko created MSOURCES-148:
-
Summary: The plugin should respect the --update-dependencies for
final versions
Key: MSOURCES-148
URL: https://issues.apache.org/jira/browse/MSOURCES-148
Project: Maven Source Plugin
Issue Type: New Feature
Reporter: Benjamin Muschko
Executing the build with the flag {{--update-dependencies}} should only update
SNAPSHOT dependencies. The plugin doesn't seem to evaluate this flag. Running
the build with the flag will update SNAPSHOT _and_ final dependencies leading
to a much longer build time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MSHARED-1395] Remove dependency on commons-io [maven-dependency-analyzer]
slawekjaranowski merged PR #120: URL: https://github.com/apache/maven-dependency-analyzer/pull/120 -- 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] (MSHARED-1395) Remove dependency on commons-io
[
https://issues.apache.org/jira/browse/MSHARED-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845434#comment-17845434
]
ASF GitHub Bot commented on MSHARED-1395:
-
slawekjaranowski merged PR #120:
URL: https://github.com/apache/maven-dependency-analyzer/pull/120
> Remove dependency on commons-io
> ---
>
> Key: MSHARED-1395
> URL: https://issues.apache.org/jira/browse/MSHARED-1395
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-dependency-analyzer
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: maven-dependency-analyzer-1.14.0
>
>
> Only one simple method is used {{IOUtils#toByteArra}} ... we can do it in
> project.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MSHARED-1395) Remove dependency on commons-io
[
https://issues.apache.org/jira/browse/MSHARED-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski closed MSHARED-1395.
Resolution: Fixed
> Remove dependency on commons-io
> ---
>
> Key: MSHARED-1395
> URL: https://issues.apache.org/jira/browse/MSHARED-1395
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-dependency-analyzer
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: maven-dependency-analyzer-1.14.0
>
>
> Only one simple method is used {{IOUtils#toByteArra}} ... we can do it in
> project.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Typos [maven-site]
elharo merged PR #524: URL: https://github.com/apache/maven-site/pull/524 -- 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] Update guide-using-toolchains.apt [maven-site]
elharo commented on code in PR #517:
URL: https://github.com/apache/maven-site/pull/517#discussion_r1597136406
##
content/apt/guides/mini/guide-using-toolchains.apt:
##
@@ -69,7 +71,7 @@ Guide to Using Toolchains
*-*--+-++
| jdk |
<<<{{{https://www.mojohaus.org/keytool/keytool-maven-plugin/}keytool-maven-plugin}}>>>
| 1.4 | MojoHaus
*-*--+-++
-| protobuf|
<<<{{{http://sergei-ivanov.github.io/maven-protoc-plugin/examples/protobuf-toolchain.html}maven-protoc-plugin}}>>>
| 0.3.2 | github
+| protobuf|
<<<{{{https://www.xolstice.org/protobuf-maven-plugin/examples/protobuf-toolchain.html}protobuf-maven-plugin}}>>>
| 0.3.2 | github
Review Comment:
does the version need to be updated here too?
--
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] Set both maven.compiler.source and maven.compiler.target to 1.8 [maven-site]
elharo merged PR #520: URL: https://github.com/apache/maven-site/pull/520 -- 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.resolver:maven-resolver-util from 1.4.1 to 1.9.20 [maven-invoker-plugin]
slawekjaranowski commented on PR #239: URL: https://github.com/apache/maven-invoker-plugin/pull/239#issuecomment-2105161822 @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.apache.maven.resolver:maven-resolver-util from 1.4.1 to 1.9.20 [maven-invoker-plugin]
dependabot[bot] closed pull request #239: Bump org.apache.maven.resolver:maven-resolver-util from 1.4.1 to 1.9.20 URL: https://github.com/apache/maven-invoker-plugin/pull/239 -- 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.resolver:maven-resolver-util from 1.4.1 to 1.9.20 [maven-invoker-plugin]
dependabot[bot] commented on PR #239: URL: https://github.com/apache/maven-invoker-plugin/pull/239#issuecomment-2105161869 OK, I won't notify you about org.apache.maven.resolver:maven-resolver-util 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] [MDEP-919] Try to fix a list-repositories for Maven 4 [maven-dependency-plugin]
slawekjaranowski commented on PR #386: URL: https://github.com/apache/maven-dependency-plugin/pull/386#issuecomment-2105232231 Maven 4:  Maven 3  @cstamas @gnodet we have difference in result of `mirroredRepositories` -- 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] (MDEP-919) Fix / investigate failed ITs with Maven4
[
https://issues.apache.org/jira/browse/MDEP-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845478#comment-17845478
]
ASF GitHub Bot commented on MDEP-919:
-
slawekjaranowski commented on PR #386:
URL:
https://github.com/apache/maven-dependency-plugin/pull/386#issuecomment-2105232231
Maven 4:
Maven 3
@cstamas @gnodet we have difference in result of `mirroredRepositories`
> Fix / investigate failed ITs with Maven4
>
>
> Key: MDEP-919
> URL: https://issues.apache.org/jira/browse/MDEP-919
> Project: Maven Dependency Plugin
> Issue Type: Task
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> We still have failed:
> {noformat}
> [ERROR] The following builds failed:
> [ERROR] * tree-multimodule/pom.xml
> [ERROR] * tree-verbose/pom.xml
> [ERROR] * list-repositories/pom.xml
> [ERROR] * tree-verbose-multimodule/pom.xml{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-923) Code cleanups
[
https://issues.apache.org/jira/browse/MDEP-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MDEP-923:
-
Description:
* remove usage of deprecated API where possible
* cleanup pom after update to 42
* exclude transitive dependencies on org.apache.maven
* add {{@project.version@}} in ITs
* Remove plexus logger from DependencySilentLog
was:
* remove usage of deprecated API where possible
* cleanup pom after update to 42
* exclude transitive dependencies on org.apache.maven
* add {{@project.version@}} in ITs
> Code cleanups
> -
>
> Key: MDEP-923
> URL: https://issues.apache.org/jira/browse/MDEP-923
> Project: Maven Dependency Plugin
> Issue Type: Task
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.7.0
>
>
> * remove usage of deprecated API where possible
> * cleanup pom after update to 42
> * exclude transitive dependencies on org.apache.maven
> * add {{@project.version@}} in ITs
> * Remove plexus logger from DependencySilentLog
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump doxiaVersion from 2.0.0-M10 to 2.0.0-M11 [maven-doxia-sitetools]
dependabot[bot] opened a new pull request, #154: URL: https://github.com/apache/maven-doxia-sitetools/pull/154 Bumps `doxiaVersion` from 2.0.0-M10 to 2.0.0-M11. Updates `org.apache.maven.doxia:doxia-sink-api` from 2.0.0-M10 to 2.0.0-M11 Commits https://github.com/apache/maven-doxia/commit/21c2e55ad4dbffe23165b0cd5da8a751af502c1b";>21c2e55 [maven-release-plugin] prepare release doxia-2.0.0-M11 https://github.com/apache/maven-doxia/commit/6051b7286f8c181bcb38ff57de623e94e84bb546";>6051b72 Explictily set Java version https://github.com/apache/maven-doxia/commit/11c6a53f9308848813fa09ce4a7d111ce2e75ee0";>11c6a53 [DOXIA-736] Upgrade to Parent 42 https://github.com/apache/maven-doxia/commit/5cfb8ee091acb9f036d003a537748cfa7ac1f8a9";>5cfb8ee Remove invalid tag https://github.com/apache/maven-doxia/commit/9c3a6564a22c11a172ad420cc6662e3007b69cff";>9c3a656 Use non-deprecated code https://github.com/apache/maven-doxia/commit/c1a38e62e99d5f100cef4d990c67ee2fcc0f8955";>c1a38e6 Fix Javadoc issue https://github.com/apache/maven-doxia/commit/b3088e760105fd86014b4a1e28fe85e424f868d9";>b3088e7 [maven-release-plugin] prepare for next development iteration See full diff in https://github.com/apache/maven-doxia/compare/doxia-2.0.0-M10...doxia-2.0.0-M11";>compare view Updates `org.apache.maven.doxia:doxia-core` from 2.0.0-M10 to 2.0.0-M11 Commits https://github.com/apache/maven-doxia/commit/21c2e55ad4dbffe23165b0cd5da8a751af502c1b";>21c2e55 [maven-release-plugin] prepare release doxia-2.0.0-M11 https://github.com/apache/maven-doxia/commit/6051b7286f8c181bcb38ff57de623e94e84bb546";>6051b72 Explictily set Java version https://github.com/apache/maven-doxia/commit/11c6a53f9308848813fa09ce4a7d111ce2e75ee0";>11c6a53 [DOXIA-736] Upgrade to Parent 42 https://github.com/apache/maven-doxia/commit/5cfb8ee091acb9f036d003a537748cfa7ac1f8a9";>5cfb8ee Remove invalid tag https://github.com/apache/maven-doxia/commit/9c3a6564a22c11a172ad420cc6662e3007b69cff";>9c3a656 Use non-deprecated code https://github.com/apache/maven-doxia/commit/c1a38e62e99d5f100cef4d990c67ee2fcc0f8955";>c1a38e6 Fix Javadoc issue https://github.com/apache/maven-doxia/commit/b3088e760105fd86014b4a1e28fe85e424f868d9";>b3088e7 [maven-release-plugin] prepare for next development iteration See full diff in https://github.com/apache/maven-doxia/compare/doxia-2.0.0-M10...doxia-2.0.0-M11";>compare view Updates `org.apache.maven.doxia:doxia-module-apt` from 2.0.0-M10 to 2.0.0-M11 Updates `org.apache.maven.doxia:doxia-module-fml` from 2.0.0-M10 to 2.0.0-M11 Updates `org.apache.maven.doxia:doxia-module-markdown` from 2.0.0-M10 to 2.0.0-M11 Updates `org.apache.maven.doxia:doxia-module-xdoc` from 2.0.0-M10 to 2.0.0-M11 Updates `org.apache.maven.doxia:doxia-module-xhtml5` from 2.0.0-M10 to 2.0.0-M11 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 - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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 resolverVersion from 1.4.1 to 1.9.20 [maven-doxia-sitetools]
dependabot[bot] opened a new pull request, #155: URL: https://github.com/apache/maven-doxia-sitetools/pull/155 Bumps `resolverVersion` from 1.4.1 to 1.9.20. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.4.1 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354578";>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas";>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483";>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas";>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484";>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20";>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12353946";>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3";>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82";>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent POM 42 (https://redirect.github.com/apache/maven-resolver/issues/484";>#484) https://github.com/apache/maven-resolver/commit/4f16d5ecd94f85e6e7d793e6b6b82f20c9afbf56";>4f16d5e [MRESOLVER-547] Just use setVersion (https://redirect.github.com/apache/maven-resolver/issues/483";>#483) https://github.com/apache/maven-resolver/commit/c1b24c699621930f4eb77721400f2f6c46930626";>c1b24c6 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-resolver/commit/c1b03574961fd2daa7a678bb3fbf9f0779afee56";>c1b0357 [maven-release-plugin] prepare release maven-resolver-1.9.19 https://github.com/apache/maven-resolver/commit/adadd42d1642f39bafedb2ddd619b044fecb12b0";>adadd42 [MRESOLVER-536] Do not belly up if FS does not support setting mtime (https://redirect.github.com/apache/maven-resolver/issues/469";>#469) https://github.com/apache/maven-resolver/commit/31df8a3dc503895172d277de56b1c4a53da0a27c";>31df8a3 [1.9.x] Update dependencies (https://redirect.github.com/apache/maven-resolver/issues/462";>#462) https://github.com/apache/maven-resolver/commit/b225076e5d5b2fe3f166a4018802ac94b7cc94f7";>b225076 [MRESOLVER-522] Improve congested file locks behaviour (https://redirect.github.com/apache/maven-resolver/issues/455";>#455) (https://redirect.github.com/apache/maven-resolver/issues/461";>#461) https://github.com/apache/maven-resolver/commit/fc969c2570041bb72c3f0141ff4957e8754f365c";>fc969c2 [1.9.x][MRESOLVER-483] Fix path concatenation logic (https://redirect.github.com/apache/maven-resolver/issues/420";>#420) https://github.com/apache/maven-resolver/commit/a3e620d6d2ab6ca58d42d264347341b31da00dde";>a3e620d Use one Maven in CI Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.4.1...maven-resolver-1.9.20";>compare view Updates `org.apache.maven.resolver:maven-resolver-impl` from 1.4.1 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-impl's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354578";>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas";>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483";>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas";>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484";>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20";>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12353946";>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3";>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82";>446009d [MRESOLVER-549][
[PR] Bump mavenVersion from 3.6.3 to 3.9.6 [maven-doxia-sitetools]
dependabot[bot] opened a new pull request, #156:
URL: https://github.com/apache/maven-doxia-sitetools/pull/156
Bumps `mavenVersion` from 3.6.3 to 3.9.6.
Updates `org.apache.maven:maven-artifact` from 3.6.3 to 3.9.6
Release notes
Sourced from https://github.com/apache/maven/releases";>org.apache.maven:maven-artifact's
releases.
3.9.6
https://maven.apache.org/docs/3.9.6/release-notes.html";>Release
Notes - Maven - Version 3.9.6
Improvement
[https://issues.apache.org/jira/browse/MNG-7939";>MNG-7939]
- Allow to exclude plugins from validation
Dependency upgrade
[https://issues.apache.org/jira/browse/MNG-7913";>MNG-7913]
- Upgrade Sisu version to 0.9.0.M2
[https://issues.apache.org/jira/browse/MNG-7934";>MNG-7934]
- Upgrade Resolver version to 1.9.18
[https://issues.apache.org/jira/browse/MNG-7942";>MNG-7942]
- Upgrade to parent POM 41
[https://issues.apache.org/jira/browse/MNG-7943";>MNG-7943]
- Upgrade default plugin bindings
3.9.5
https://maven.apache.org/docs/3.9.5/release-notes.html";>Release
Notes - Maven - Version 3.9.5
Bug
[https://issues.apache.org/jira/browse/MNG-7851";>MNG-7851]
- Error message when modelVersion is 4.0 is confusing
Improvement
[https://issues.apache.org/jira/browse/MNG-7875";>MNG-7875]
- colorize transfer messages
[https://issues.apache.org/jira/browse/MNG-7895";>MNG-7895]
- Support ${project.basedir} in file profile activation
Task
[https://issues.apache.org/jira/browse/MNG-7856";>MNG-7856]
- Maven Resolver Provider classes ctor change
[https://issues.apache.org/jira/browse/MNG-7870";>MNG-7870]
- Undeprecate wrongly deprecated repository metadata
[https://issues.apache.org/jira/browse/MNG-7872";>MNG-7872]
- Deprecate org.apache.maven.repository.internal.MavenResolverModule
[https://issues.apache.org/jira/browse/MNG-7874";>MNG-7874]
- maven-resolver-provider: introduce NAME constants.
Dependency upgrade
[https://issues.apache.org/jira/browse/MNG-7859";>MNG-7859]
- Update to Resolver 1.9.16
3.9.4
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12353369";>Release
Notes - Maven - Version 3.9.4
... (truncated)
Commits
https://github.com/apache/maven/commit/bc0240f3c744dd6b6ec2920b3cd08dcc295161ae";>bc0240f
[maven-release-plugin] prepare release maven-3.9.6
https://github.com/apache/maven/commit/e6cc6c53cb979f46e7cf97fc9bab686343500a94";>e6cc6c5
[MNG-7943] Upgrade default plugin bindings
https://github.com/apache/maven/commit/48adee3711705c65918b2c736e88093a052f30f8";>48adee3
[MNG-7934] Update to Resolver 1.9.18 (https://redirect.github.com/apache/maven/issues/1326";>#1326)
https://github.com/apache/maven/commit/da6c7e4bcac34677ad9e7d93f345d9c896866e1b";>da6c7e4
[MNG-7942] Upgrade maven-parent to 41
https://github.com/apache/maven/commit/95fa548e1db672ac7b102ff27585c82ed5ae9ed2";>95fa548
[MNG-7934] Update to Resolver 1.9.17 (https://redirect.github.com/apache/maven/issues/1321";>#1321)
https://github.com/apache/maven/commit/c54baa64b38c09c440a11285d560e47d894b2414";>c54baa6
[MNG-7939] Allow to exclude plugins from validation
https://github.com/apache/maven/commit/ecd59b7158e048a6298b8b52d44fccaba26065ad";>ecd59b7
[MNG-7913] Upgrade Sisu version (https://redirect.github.com/apache/maven/issues/1286";>#1286)
https://github.com/apache/maven/commit/53edd71c989d8f2f2b92ee0b281976772c78b927";>53edd71
Use the same branch name for ITs on Jenkins (https://redirect.github.com/apache/maven/issues/1263";>#1263)
https://github.com/apache/maven/commit/2bc44491af62fef51e17d6ad0172baff82c8d022";>2bc4449
The maven-3.9.x branch should fallback to maven-3.9.x branch of ITs
https://github.com/apache/maven/commit/6e532cd249c0413fb6885ca6dfcc67dce25f703d";>6e532cd
[maven-release-plugin] prepare for next development iteration
Additional commits viewable in https://github.com/apache/maven/compare/maven-3.6.3...maven-3.9.6";>compare
view
Updates `org.apache.maven:maven-core` from 3.6.3 to 3.9.6
Release notes
Sourced from https://github.com/apache/maven/releases";>org.apache.maven:maven-core's
releases.
3.9.6
https://maven.apache.org/docs/3.9.6/release-notes.html";>Release
Notes - Maven - Version 3.9.6
Improvement
[https://issues.apache.org/jira/browse/MNG-7939";>MNG-7939]
- Allow to exclude plugins from validation
Dependency upgrade
[https://issues.apache.org/jira/browse/MNG-7913";>MNG-7913]
- Upgrade Sisu version to 0.9.0.M2
[https://issues.apache.org/jira/browse/MNG-7934";>MNG-7934]
- Upgrade Resolver version to 1.9.18
[https://issues.apache.org/jira/browse/MNG-7942";>MNG-7942]
- Upgrade to parent POM 41
[https://issues.apache.org/jira/browse/MNG-7943";>MNG-7943]
- Upgrade default plugin bindings
3.9.5
https://maven.apache.org/docs/3.9.5/release-notes.html";>Rel
Re: [PR] Update guide-using-toolchains.apt [maven-site]
shalk commented on code in PR #517:
URL: https://github.com/apache/maven-site/pull/517#discussion_r1597333195
##
content/apt/guides/mini/guide-using-toolchains.apt:
##
@@ -69,7 +71,7 @@ Guide to Using Toolchains
*-*--+-++
| jdk |
<<<{{{https://www.mojohaus.org/keytool/keytool-maven-plugin/}keytool-maven-plugin}}>>>
| 1.4 | MojoHaus
*-*--+-++
-| protobuf|
<<<{{{http://sergei-ivanov.github.io/maven-protoc-plugin/examples/protobuf-toolchain.html}maven-protoc-plugin}}>>>
| 0.3.2 | github
+| protobuf|
<<<{{{https://www.xolstice.org/protobuf-maven-plugin/examples/protobuf-toolchain.html}protobuf-maven-plugin}}>>>
| 0.3.2 | github
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
[PR] feat: Specify wrapper version (or latest) [maven-wrapper]
reneleonhardt opened a new pull request, #138: URL: https://github.com/apache/maven-wrapper/pull/138 ### Feature In addition to the wrapped Maven distribution * `-Dmaven=3.9.6` or * `-Dmvnd=0.9.0` support specifying the wrapper version itself with * `-Dversion=3.3.1` This allows using/replacing the wrapper with a specific version, or updating it to * `-Dversion=latest` for example to retrieve (security) fixes or use new features. If a project doesn't want to commit the maven-wrapper.jar, but cache it in a GitHub Action after the automatic download: ``` mvn -N wrapper:wrapper -Dversion=latest -Dtype=script ``` ### Checklist Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MWRAPPER) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA 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. - [ ] Format the pull request title like `[MWRAPPER-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MWRAPPER-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA 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
