[GitHub] [maven-dependency-plugin] slawekjaranowski merged pull request #225: [MDEP-813] Require Maven 3.2.5
slawekjaranowski merged PR #225: URL: https://github.com/apache/maven-dependency-plugin/pull/225 -- 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
[GitHub] [maven-dependency-plugin] dependabot[bot] opened a new pull request, #228: Bump plexus-archiver from 2.6.3 to 3.6.0 in /src/it/projects/setup-custom-ear-lifecycle/manager
dependabot[bot] opened a new pull request, #228: URL: https://github.com/apache/maven-dependency-plugin/pull/228 Bumps [plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) from 2.6.3 to 3.6.0. Release notes Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases";>plexus-archiver's releases. Plexus Archiver 3.6.0 requires Java 7. :rocket: New features and improvements https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/84";>#84, https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/57";>#57 - Added Archiver implementation (JarToolModularJarArchiver) that creates modular JAR files using the JDK jar tool. The implementation uses java.util.spi.ToolProvider introduced in Java 9, so if it is run on Java 7 or 8 the resulting archive will be identical to a one created by JarArchiver - the module descriptor is not going to be validated and no additional information (such as version, main class and packages) is going to be added. https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/67";>#67 - Added ability to set the module version and main class of a modular JAR file https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/83";>#83 - Added new protected method (postCreateArchive) to AbstractArchiver that is called after the archive is created successfully https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/87";>#87 - of Levan Giguashvili (https://github.com/odinn1984";>@odinn1984) Snyk eng team to fix a possible security issue. (See https://gist.github.com/grnd/eafd7dab7c4cc6197d817a07fa46b2df";>https://gist.github.com/grnd/eafd7dab7c4cc6197d817a07fa46b2df) :bug: Bug Fixes https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/73";>#73 - Symbolic links not properly encoded in ZIP archives https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/57";>#57 - ZipArchiver creates archives with inconsistent central directory entries https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/79";>#79 - JarArchiver and PlexusIoZipFileResourceCollection leak file descriptors :toolbox: Maintenance https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/77";>#77 - Fixed the way unit tests modify the timestamp of a file :package: Dependency updates https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/71";>#71, https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/72";>#72, https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/76";>#76, https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/78";>#78, https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/85";>#85, https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/86";>#86 - Updated dependencies: commons-compress to 1.16.1, plexus-utils to 3.1.0, org.tukaani:xz to 1.8 and plexus-io to 3.0.1 Plexus Archiver 3.5 requires Java 7. Now Plexus Archiver uses pure Java implementations to deal with file attributes so the useJvmChmod is no longer used and it is just ignored. Archiver#setUseJvmChmod, Archiver#isUseJvmChmod(), UnArchiver#setUseJvmChmod, UnArchiver#isUseJvmChmod(), ArchiveEntryUtils#chmod( File, int, Logger, boolean ) and ArchiveEntryUtils#chmod( File, int, Logger ) are deprecated and are subject to removal in a future version. :rocket: New features and improvements https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/51";>#51 - More specific exception for cases when there are no files to archive. Now EmptyArchiveException is thrown when you try to create empty archive. Previously the more generic ArchiverException was thrown. :bug: Bug Fixes https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/47";>#47 - Archiver follows symlinks on Windows https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/53";>#53 - AbstractZipArchiver no longer respects recompressAddedZips https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/58";>#58 - Creates corrupt JARs :package: Dependency updates https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/56";>#56 - Upgrade the minimum required Java version to 7 and Plexus IO to 3.0.0 https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/60";>#60 - Upgrade dependencies. plexus-container-default to 1.0-alpha-30, commons-compress to 1.14, org.tukaani.xz to 1.6 and com.google.code.findbugs.jsr305 to 3.0.2 Plexus Archiver 3.4.1 :rocket: New features and improvements https://github-redirect.dependabot.com/codehaus-plexus/
[GitHub] [maven-dependency-plugin] dependabot[bot] commented on pull request #224: Bump wagon-http-lightweight from 3.4.0 to 3.5.2
dependabot[bot] commented on PR #224: URL: https://github.com/apache/maven-dependency-plugin/pull/224#issuecomment-1200121640 Looks like org.apache.maven.wagon:wagon-http-lightweight is no longer a dependency, 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
[GitHub] [maven-dependency-plugin] dependabot[bot] closed pull request #224: Bump wagon-http-lightweight from 3.4.0 to 3.5.2
dependabot[bot] closed pull request #224: Bump wagon-http-lightweight from 3.4.0 to 3.5.2 URL: https://github.com/apache/maven-dependency-plugin/pull/224 -- 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
[GitHub] [maven-dependency-plugin] dependabot[bot] opened a new pull request, #229: Bump maven-dependency-tree from 3.1.0 to 3.1.1
dependabot[bot] opened a new pull request, #229: URL: https://github.com/apache/maven-dependency-plugin/pull/229 Bumps [maven-dependency-tree](https://github.com/apache/maven-dependency-tree) from 3.1.0 to 3.1.1. Release notes Sourced from https://github.com/apache/maven-dependency-tree/releases";>maven-dependency-tree's releases. v3.1.1 What's Changed MSHARED-994 - fix collect dependencies when artifact has 'war' packaging by https://github.com/belingueres";>@belingueres in https://github-redirect.dependabot.com/apache/maven-dependency-tree/pull/7";>apache/maven-dependency-tree#7 Bump maven-site-plugin from 3.9.1 to 3.10.0 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-dependency-tree/pull/8";>apache/maven-dependency-tree#8 Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.2 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-dependency-tree/pull/14";>apache/maven-dependency-tree#14 [MSHARED-1069] Upgrade Parent to 36 by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-dependency-tree/pull/20";>apache/maven-dependency-tree#20 New Contributors https://github.com/belingueres";>@belingueres made their first contribution in https://github-redirect.dependabot.com/apache/maven-dependency-tree/pull/7";>apache/maven-dependency-tree#7 https://github.com/dependabot";>@dependabot made their first contribution in https://github-redirect.dependabot.com/apache/maven-dependency-tree/pull/8";>apache/maven-dependency-tree#8 https://github.com/slawekjaranowski";>@slawekjaranowski made their first contribution in https://github-redirect.dependabot.com/apache/maven-dependency-tree/pull/20";>apache/maven-dependency-tree#20 Full Changelog: https://github.com/apache/maven-dependency-tree/compare/maven-dependency-tree-3.1.0...maven-dependency-tree-3.1.1";>https://github.com/apache/maven-dependency-tree/compare/maven-dependency-tree-3.1.0...maven-dependency-tree-3.1.1 Commits https://github.com/apache/maven-dependency-tree/commit/05bb7530c3fa8f78e9168751c814c6fc9d511de1";>05bb753 [maven-release-plugin] prepare release maven-dependency-tree-3.1.1 https://github.com/apache/maven-dependency-tree/commit/8732ab77cbcadfab55458b9f0934a2cc5a294b78";>8732ab7 Move execution of m-invoker-p to run-its profile https://github.com/apache/maven-dependency-tree/commit/7d1c702fcc00f118d02ecb03465cb2a1f364d17e";>7d1c702 [MSHARED-1069] Upgrade Parent to 36 https://github.com/apache/maven-dependency-tree/commit/74c79a5d4132e5261dd53cb79eda65fafedf61f1";>74c79a5 Add PR template https://github.com/apache/maven-dependency-tree/commit/df560858b249f5a3803aaf1b4e4cfcaa5d5634d0";>df56085 Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.2 https://github.com/apache/maven-dependency-tree/commit/dffd33c41902805ea574cb0ddff29681028e1806";>dffd33c Shared GitHub actions v2 https://github.com/apache/maven-dependency-tree/commit/7a1a12533ac6898fcb3dacbcf2466ef71d11c43a";>7a1a125 Bump maven-site-plugin from 3.9.1 to 3.10.0 https://github.com/apache/maven-dependency-tree/commit/9878b40fb3531bee47b148b1a4dc3129709a7a86";>9878b40 Drop noinstantiate, noreference https://github.com/apache/maven-dependency-tree/commit/134615e524baea40f0f0bf83a1aea8e16a5c71c8";>134615e Updated plugins https://github.com/apache/maven-dependency-tree/commit/064e63be0d21580dc6163eed037d9253cda09d03";>064e63b Added GH Shared Workflow Additional commits viewable in https://github.com/apache/maven-dependency-tree/compare/maven-dependency-tree-3.1.0...maven-dependency-tree-3.1.1";>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 - `@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
[jira] [Closed] (MDEP-813) Require Maven 3.2.5
[ https://issues.apache.org/jira/browse/MDEP-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MDEP-813. Fix Version/s: next-release Resolution: Fixed > Require Maven 3.2.5 > --- > > Key: MDEP-813 > URL: https://issues.apache.org/jira/browse/MDEP-813 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-813) Require Maven 3.2.5
[ https://issues.apache.org/jira/browse/MDEP-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573237#comment-17573237 ] Hudson commented on MDEP-813: - Build succeeded in Jenkins: Maven » Maven TLP » maven-dependency-plugin » master #27 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/master/27/ > Require Maven 3.2.5 > --- > > Key: MDEP-813 > URL: https://issues.apache.org/jira/browse/MDEP-813 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-347) Upgrade to PMD 6.48.0
Andreas Dangel created MPMD-347: --- Summary: Upgrade to PMD 6.48.0 Key: MPMD-347 URL: https://issues.apache.org/jira/browse/MPMD-347 Project: Maven PMD Plugin Issue Type: Dependency upgrade Components: CPD, PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.18.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-348) Support Java 19
Andreas Dangel created MPMD-348: --- Summary: Support Java 19 Key: MPMD-348 URL: https://issues.apache.org/jira/browse/MPMD-348 Project: Maven PMD Plugin Issue Type: New Feature Components: PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.17.0 With the next PMD version 6.44.0, Java 18 will be supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-348) Support Java 19
[ https://issues.apache.org/jira/browse/MPMD-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-348: Description: With the next PMD version 6.49.0, Java 19 is supported. (was: With the next PMD version 6.44.0, Java 18 will be supported.) > Support Java 19 > --- > > Key: MPMD-348 > URL: https://issues.apache.org/jira/browse/MPMD-348 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > > With the next PMD version 6.49.0, Java 19 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-348) Support Java 19
[ https://issues.apache.org/jira/browse/MPMD-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-348: Description: With the next PMD version 6.48.0, Java 19 is supported. (was: With the next PMD version 6.49.0, Java 19 is supported.) > Support Java 19 > --- > > Key: MPMD-348 > URL: https://issues.apache.org/jira/browse/MPMD-348 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > > With the next PMD version 6.48.0, Java 19 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-jenkins-lib] slawekjaranowski opened a new pull request, #6: Build only on linux nodes
slawekjaranowski opened a new pull request, #6: URL: https://github.com/apache/maven-jenkins-lib/pull/6 due to https://issues.apache.org/jira/browse/INFRA-23485 -- 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
[GitHub] [maven-dependency-plugin] slawekjaranowski merged pull request #226: Bump mrm-maven-plugin from 1.2.0 to 1.4.1
slawekjaranowski merged PR #226: URL: https://github.com/apache/maven-dependency-plugin/pull/226 -- 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
[GitHub] [maven-dependency-plugin] dependabot[bot] opened a new pull request, #230: Bump maven-plugins from 35 to 37
dependabot[bot] opened a new pull request, #230: URL: https://github.com/apache/maven-dependency-plugin/pull/230 Bumps [maven-plugins](https://github.com/apache/maven-parent) from 35 to 37. Release notes Sourced from https://github.com/apache/maven-parent/releases";>maven-plugins's releases. 37 What's Changed [MPOM-317] Upgrade fluido skin to 1.11.0 by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/66";>apache/maven-parent#66 Bump maven-pmd-plugin from 3.16.0 to 3.17.0 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/64";>apache/maven-parent#64 [MPOM-322] Add ASF Data Privacy by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/65";>apache/maven-parent#65 [MPOM-324] Drop Social Media Plug-ins from documentation by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/67";>apache/maven-parent#67 [MPOM-331] Upgrade Surefire to 3.0.0-M7 by https://github.com/slachiewicz";>@slachiewicz in https://github-redirect.dependabot.com/apache/maven-parent/pull/68";>apache/maven-parent#68 [MPOM-334] Upgrade fluido skin to 1.11.1 by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/70";>apache/maven-parent#70 Bump maven-toolchains-plugin from 3.0.0 to 3.1.0 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/69";>apache/maven-parent#69 Bump extra-enforcer-rules from 1.5.1 to 1.6.0 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/71";>apache/maven-parent#71 Bump apache from 26 to 27 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/72";>apache/maven-parent#72 Full Changelog: https://github.com/apache/maven-parent/compare/maven-parent-36...maven-parent-37";>https://github.com/apache/maven-parent/compare/maven-parent-36...maven-parent-37 36 What's Changed [MPOM-300] switch from GA to ASF Matomo. by https://github.com/bmarwell";>@bmarwell in https://github-redirect.dependabot.com/apache/maven-parent/pull/58";>apache/maven-parent#58 [MPOM-308] Upgrade Maven PMD Plugin from 3.15.0 to 3.16.0 by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/59";>apache/maven-parent#59 Bump taglist-maven-plugin from 2.4 to 3.0.0 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/45";>apache/maven-parent#45 Bump maven-jxr-plugin from 3.1.1 to 3.2.0 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/60";>apache/maven-parent#60 [MPOM-313] execute checkstyle in early phase of the build by https://github.com/olamy";>@olamy in https://github-redirect.dependabot.com/apache/maven-parent/pull/55";>apache/maven-parent#55 [MPOM-314] Upgrade modello-maven-plugin from 1.11 to 2.0.0 by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/61";>apache/maven-parent#61 Bump apache from 25 to 26 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/62";>apache/maven-parent#62 New Contributors https://github.com/bmarwell";>@bmarwell made their first contribution in https://github-redirect.dependabot.com/apache/maven-parent/pull/58";>apache/maven-parent#58 https://github.com/olamy";>@olamy made their first contribution in https://github-redirect.dependabot.com/apache/maven-parent/pull/55";>apache/maven-parent#55 Full Changelog: https://github.com/apache/maven-parent/compare/maven-parent-35...maven-parent-36";>https://github.com/apache/maven-parent/compare/maven-parent-35...maven-parent-36 Commits See full diff in https://github.com/apache/maven-parent/commits";>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 optio
[jira] [Created] (MDEP-814) Bump mrm-maven-plugin from 1.2.0 to 1.4.1
Slawomir Jaranowski created MDEP-814: Summary: Bump mrm-maven-plugin from 1.2.0 to 1.4.1 Key: MDEP-814 URL: https://issues.apache.org/jira/browse/MDEP-814 Project: Maven Dependency Plugin Issue Type: Dependency upgrade Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEP-814) Bump mrm-maven-plugin from 1.2.0 to 1.4.1
[ https://issues.apache.org/jira/browse/MDEP-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MDEP-814. Resolution: Fixed > Bump mrm-maven-plugin from 1.2.0 to 1.4.1 > - > > Key: MDEP-814 > URL: https://issues.apache.org/jira/browse/MDEP-814 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MDEP-815) Upgrade Parent to 37
Slawomir Jaranowski created MDEP-815: Summary: Upgrade Parent to 37 Key: MDEP-815 URL: https://issues.apache.org/jira/browse/MDEP-815 Project: Maven Dependency Plugin Issue Type: Dependency upgrade Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-dependency-plugin] slawekjaranowski closed pull request #230: Bump maven-plugins from 35 to 37
slawekjaranowski closed pull request #230: Bump maven-plugins from 35 to 37 URL: https://github.com/apache/maven-dependency-plugin/pull/230 -- 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
[GitHub] [maven-dependency-plugin] dependabot[bot] commented on pull request #230: Bump maven-plugins from 35 to 37
dependabot[bot] commented on PR #230: URL: https://github.com/apache/maven-dependency-plugin/pull/230#issuecomment-1200134776 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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] (SUREFIRE-2113) @TempDir does not correctly work
Karl Heinz Marbaise created SUREFIRE-2113:
-
Summary: @TempDir does not correctly work
Key: SUREFIRE-2113
URL: https://issues.apache.org/jira/browse/SUREFIRE-2113
Project: Maven Surefire
Issue Type: Bug
Components: JUnit 5.x support
Affects Versions: 3.0.0-M7, 2.22.2
Reporter: Karl Heinz Marbaise
Having the following test:
{code:java}
class TempDirTest {
@Test
void testTempDir(@TempDir Path tmpdir) {
System.out.println("@TempDir : " + tmpdir);
System.out.println("java.io.tmpdir : " +
System.getProperty("java.io.tmpdir"));
Path actual = tmpdir.getParent().toAbsolutePath();
Path expected = Path.of(System.getProperty("java.io.tmpdir"));
Assertions.assertEquals(expected, actual);
}
}
{code}
If I run via:
{code}
mvn -Djava.io.tmpdir=/tmp/custom clean test
{code}
within the following environment:
{code}
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /Users/khm/tools/maven
Java version: 11.0.15, vendor: Azul Systems, Inc., runtime:
/Users/khm/.sdkman/candidates/java/11.0.15-zulu/zulu-11.jdk/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "12.4", arch: "aarch64", family: "mac"
```
The given test succeeds.
If I use the following environment (changed JDK version):
{code}
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /Users/khm/tools/maven
Java version: 17.0.4, vendor: Azul Systems, Inc., runtime:
/Users/khm/.sdkman/candidates/java/17.0.4-zulu/zulu-17.jdk/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "12.4", arch: "aarch64", family: "mac"
{code}
The given test fails:
{code}
[INFO] ---
[INFO] Running org.example.TempDirTest
@TempDir :
/var/folders/wj/73qxv5hd6p573p9ytbf4kcghgn/T/junit2987236559648574880
java.io.tmpdir : /tmp/custom
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.027 s
<<< FAILURE! - in org.example.TempDirTest
[ERROR] testTempDir{Path} Time elapsed: 0.023 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: but was:
at org.example.TempDirTest.testTempDir(TempDirTest.java:18)
[INFO]
[INFO] Results:
{code}
I've checked that with different combinations:
* Maven 3.8.6
* JUnit Jupiter 5.8.2 / 5.9.0
* Maven Surefire Plugin Version:
* 2.22.2
* 3.0.0-M7
* [Platform Maven
Plugin](https://github.com/sormuras/junit-platform-maven-plugin)
I have create a full [working
example](https://github.com/khmarbaise/tempdir-annotation) which contains
appropriate named branches for the different combinations.
I've also tested the same combinations with JDK 17/11 from liberica with the
same result. Also with JDK18 the test fails.
After more checking I found out that via the standalone launcher, there is no
problem at all. (no difference between jdk versions).
{code}
java -Djava.io.tmpdir=/tmp/custom -jar
~/.m2/repository/org/junit/platform/junit-platform-console-standalone/1.9.0/junit-platform-console-standalone-1.9.0.jar
-cp classes:target/test-classes --scan-classpath
{code}
The output:
{code}
@TempDir : /tmp/custom/junit17756560401872268189
java.io.tmpdir : /tmp/custom
Thanks for using JUnit! Support its development at https://junit.org/sponsoring
╷
├─ JUnit Jupiter ✔
│ └─ TempDirTest ✔
│ └─ testTempDir(Path) ✔
├─ JUnit Vintage ✔
└─ JUnit Platform Suite ✔
Test run finished after 51 ms
[ 4 containers found ]
[ 0 containers skipped]
[ 4 containers started]
[ 0 containers aborted]
[ 4 containers successful ]
[ 0 containers failed ]
[ 1 tests found ]
[ 0 tests skipped ]
[ 1 tests started ]
[ 0 tests aborted ]
[ 1 tests successful ]
[ 0 tests failed ]
{code}
Has someone an Idea what could cause such thing?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2113) @TempDir does not correctly work
[
https://issues.apache.org/jira/browse/SUREFIRE-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated SUREFIRE-2113:
--
Description:
Having the following test:
{code:java}
class TempDirTest {
@Test
void testTempDir(@TempDir Path tmpdir) {
System.out.println("@TempDir : " + tmpdir);
System.out.println("java.io.tmpdir : " +
System.getProperty("java.io.tmpdir"));
Path actual = tmpdir.getParent().toAbsolutePath();
Path expected = Path.of(System.getProperty("java.io.tmpdir"));
Assertions.assertEquals(expected, actual);
}
}
{code}
If I run via:
{code}
mvn -Djava.io.tmpdir=/tmp/custom clean test
{code}
within the following environment:
{code}
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /Users/khm/tools/maven
Java version: 11.0.15, vendor: Azul Systems, Inc., runtime:
/Users/khm/.sdkman/candidates/java/11.0.15-zulu/zulu-11.jdk/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "12.4", arch: "aarch64", family: "mac"
{code}
The given test succeeds.
If I use the following environment (changed JDK version):
{code}
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /Users/khm/tools/maven
Java version: 17.0.4, vendor: Azul Systems, Inc., runtime:
/Users/khm/.sdkman/candidates/java/17.0.4-zulu/zulu-17.jdk/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "12.4", arch: "aarch64", family: "mac"
{code}
The given test fails:
{code}
[INFO] ---
[INFO] Running org.example.TempDirTest
@TempDir :
/var/folders/wj/73qxv5hd6p573p9ytbf4kcghgn/T/junit2987236559648574880
java.io.tmpdir : /tmp/custom
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.027 s
<<< FAILURE! - in org.example.TempDirTest
[ERROR] testTempDir{Path} Time elapsed: 0.023 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: but was:
at org.example.TempDirTest.testTempDir(TempDirTest.java:18)
[INFO]
[INFO] Results:
{code}
I've checked that with different combinations:
* Maven 3.8.6
* JUnit Jupiter 5.8.2 / 5.9.0
* Maven Surefire Plugin Version:
* 2.22.2
* 3.0.0-M7
* [Platform Maven
Plugin](https://github.com/sormuras/junit-platform-maven-plugin)
I have create a full [working
example](https://github.com/khmarbaise/tempdir-annotation) which contains
appropriate named branches for the different combinations.
I've also tested the same combinations with JDK 17/11 from liberica with the
same result. Also with JDK18 the test fails.
After more checking I found out that via the standalone launcher, there is no
problem at all. (no difference between jdk versions).
{code}
java -Djava.io.tmpdir=/tmp/custom -jar
~/.m2/repository/org/junit/platform/junit-platform-console-standalone/1.9.0/junit-platform-console-standalone-1.9.0.jar
-cp classes:target/test-classes --scan-classpath
{code}
The output:
{code}
@TempDir : /tmp/custom/junit17756560401872268189
java.io.tmpdir : /tmp/custom
Thanks for using JUnit! Support its development at https://junit.org/sponsoring
╷
├─ JUnit Jupiter ✔
│ └─ TempDirTest ✔
│ └─ testTempDir(Path) ✔
├─ JUnit Vintage ✔
└─ JUnit Platform Suite ✔
Test run finished after 51 ms
[ 4 containers found ]
[ 0 containers skipped]
[ 4 containers started]
[ 0 containers aborted]
[ 4 containers successful ]
[ 0 containers failed ]
[ 1 tests found ]
[ 0 tests skipped ]
[ 1 tests started ]
[ 0 tests aborted ]
[ 1 tests successful ]
[ 0 tests failed ]
{code}
Has someone an Idea what could cause such thing?
was:
Having the following test:
{code:java}
class TempDirTest {
@Test
void testTempDir(@TempDir Path tmpdir) {
System.out.println("@TempDir : " + tmpdir);
System.out.println("java.io.tmpdir : " +
System.getProperty("java.io.tmpdir"));
Path actual = tmpdir.getParent().toAbsolutePath();
Path expected = Path.of(System.getProperty("java.io.tmpdir"));
Assertions.assertEquals(expected, actual);
}
}
{code}
If I run via:
{code}
mvn -Djava.io.tmpdir=/tmp/custom clean test
{code}
within the following environment:
{code}
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /Users/khm/tools/maven
Java version: 11.0.15, vendor: Azul Systems, Inc., runtime:
/Users/khm/.sdkman/candidates/java/11.0.15-zulu/zulu-11.jdk/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "12.4", arch: "aarch64", family: "mac"
```
The given test succeeds.
If I use the following environment (changed JDK version):
{code}
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /Users/khm/tools/maven
Java version: 17.0.4, vendor: Azul Systems, I
[GitHub] [maven-dependency-plugin] slawekjaranowski opened a new pull request, #231: [MDEP-815] Upgrade Parent to 37
slawekjaranowski opened a new pull request, #231: URL: https://github.com/apache/maven-dependency-plugin/pull/231 cleanup override configuration 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/MDEP) 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 `[MDEP-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MDEP-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) - [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] [Closed] (MDEP-804) Allow auto-ignore of all non-test scoped dependencies used only in test scope
[ https://issues.apache.org/jira/browse/MDEP-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MDEP-804. > Allow auto-ignore of all non-test scoped dependencies used only in test scope > - > > Key: MDEP-804 > URL: https://issues.apache.org/jira/browse/MDEP-804 > Project: Maven Dependency Plugin > Issue Type: New Feature > Components: analyze >Affects Versions: 3.3.0 >Reporter: Henning Schmiedehausen >Assignee: Henning Schmiedehausen >Priority: Major > Labels: pull-request-available > Fix For: next-release > > > Pre-3.2.0, dependencies that were used only in test scope but not declared in > test scope (most likely declared in compile scope) were accepted by the > plugin and not flagged as a problem. > Starting with 3.2.0 (and the current 3.3.0), these are reported with > "Non-test scoped test only dependencies found". If the scope of the > dependencies can not be changed (there are many reasons for that in large > projects), the old behavior can be restored by adding each flagged dependency > to the "ignoredNonTestScopedDependencies" configuration option in the > respective project. > This is, especially in large projects, cumbersome and brittle. > There should be a boolean flag, "ignoreAllNonTestScoped" that, when set, > allows ignoring non-test scoped dependencies if they are used only in test > scope. This flag restores the pre-3.2.0 behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-pmd-plugin] adangel opened a new pull request, #81: [MPMD-347] - Upgrade to PMD 6.48.0
adangel opened a new pull request, #81: URL: https://github.com/apache/maven-pmd-plugin/pull/81 https://issues.apache.org/jira/browse/MPMD-347 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. - [ ] 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
[GitHub] [maven-pmd-plugin] adangel opened a new pull request, #82: [MPMD-348] - Support Java 19
adangel opened a new pull request, #82: URL: https://github.com/apache/maven-pmd-plugin/pull/82 https://issues.apache.org/jira/browse/MPMD-348 Depends on #81 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. - [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] [Assigned] (MPH-186) maven-parent to 37
[ https://issues.apache.org/jira/browse/MPH-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MPH-186: --- Assignee: Karl Heinz Marbaise > maven-parent to 37 > -- > > Key: MPH-186 > URL: https://issues.apache.org/jira/browse/MPH-186 > Project: Maven Help Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPH-186) maven-parent to 37
Karl Heinz Marbaise created MPH-186: --- Summary: maven-parent to 37 Key: MPH-186 URL: https://issues.apache.org/jira/browse/MPH-186 Project: Maven Help Plugin Issue Type: Dependency upgrade Affects Versions: 3.2.0 Reporter: Karl Heinz Marbaise Fix For: 3.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-pmd-plugin] adangel merged pull request #82: [MPMD-348] - Support Java 19
adangel merged PR #82: URL: https://github.com/apache/maven-pmd-plugin/pull/82 -- 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
[GitHub] [maven-pmd-plugin] adangel merged pull request #81: [MPMD-347] - Upgrade to PMD 6.48.0
adangel merged PR #81: URL: https://github.com/apache/maven-pmd-plugin/pull/81 -- 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] (MPMD-347) Upgrade to PMD 6.48.0
[ https://issues.apache.org/jira/browse/MPMD-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-347. --- Resolution: Fixed Fixed: https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=10d345c3588fad71df9f7e5bf505e1ece2817c74 > Upgrade to PMD 6.48.0 > - > > Key: MPMD-347 > URL: https://issues.apache.org/jira/browse/MPMD-347 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-348) Support Java 19
[ https://issues.apache.org/jira/browse/MPMD-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-348: Fix Version/s: 3.18.0 (was: 3.17.0) > Support Java 19 > --- > > Key: MPMD-348 > URL: https://issues.apache.org/jira/browse/MPMD-348 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.18.0 > > > With the next PMD version 6.48.0, Java 19 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-348) Support Java 19
[ https://issues.apache.org/jira/browse/MPMD-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-348. --- Resolution: Fixed Fixed: https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=2ecd5788286c80b12136cb7e86a6ff1795c53e23 > Support Java 19 > --- > > Key: MPMD-348 > URL: https://issues.apache.org/jira/browse/MPMD-348 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.18.0 > > > With the next PMD version 6.48.0, Java 19 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPH-187) Upgrade to JDK minimum
Karl Heinz Marbaise created MPH-187: --- Summary: Upgrade to JDK minimum Key: MPH-187 URL: https://issues.apache.org/jira/browse/MPH-187 Project: Maven Help Plugin Issue Type: Task Affects Versions: 3.2.0 Reporter: Karl Heinz Marbaise Fix For: 3.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MPH-187) Upgrade to JDK minimum
[ https://issues.apache.org/jira/browse/MPH-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MPH-187: --- Assignee: Karl Heinz Marbaise > Upgrade to JDK minimum > -- > > Key: MPH-187 > URL: https://issues.apache.org/jira/browse/MPH-187 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-help-plugin] khmarbaise opened a new pull request, #69: [MPH-186] - maven-parent to 37
khmarbaise opened a new pull request, #69: URL: https://github.com/apache/maven-help-plugin/pull/69 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/MPH) 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. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MPH-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MPH-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. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] 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) - [ ] 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-348) Support Java 19
[ https://issues.apache.org/jira/browse/MPMD-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573254#comment-17573254 ] Hudson commented on MPMD-348: - Build succeeded in Jenkins: Maven » Maven TLP » maven-pmd-plugin » master #44 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pmd-plugin/job/master/44/ > Support Java 19 > --- > > Key: MPMD-348 > URL: https://issues.apache.org/jira/browse/MPMD-348 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.18.0 > > > With the next PMD version 6.48.0, Java 19 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-347) Upgrade to PMD 6.48.0
[ https://issues.apache.org/jira/browse/MPMD-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573253#comment-17573253 ] Hudson commented on MPMD-347: - Build succeeded in Jenkins: Maven » Maven TLP » maven-pmd-plugin » master #44 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pmd-plugin/job/master/44/ > Upgrade to PMD 6.48.0 > - > > Key: MPMD-347 > URL: https://issues.apache.org/jira/browse/MPMD-347 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-help-plugin] khmarbaise commented on pull request #69: [MPH-186] - maven-parent to 37
khmarbaise commented on PR #69: URL: https://github.com/apache/maven-help-plugin/pull/69#issuecomment-1200145743 I will several cleanup afterwards. Only the first step. -- 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
[GitHub] [maven-help-plugin] asfgit merged pull request #69: [MPH-186] - maven-parent to 37
asfgit merged PR #69: URL: https://github.com/apache/maven-help-plugin/pull/69 -- 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] (MPH-186) maven-parent to 37
[ https://issues.apache.org/jira/browse/MPH-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MPH-186. --- Resolution: Done > maven-parent to 37 > -- > > Key: MPH-186 > URL: https://issues.apache.org/jira/browse/MPH-186 > Project: Maven Help Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPH-186) maven-parent to 37
[ https://issues.apache.org/jira/browse/MPH-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573255#comment-17573255 ] Karl Heinz Marbaise commented on MPH-186: - Done in [67e12728dadc962dff0a71313c5b6d094bcf2a3c|https://gitbox.apache.org/repos/asf?p=maven-help-plugin.git;a=commitdiff;h=67e12728dadc962dff0a71313c5b6d094bcf2a3c] > maven-parent to 37 > -- > > Key: MPH-186 > URL: https://issues.apache.org/jira/browse/MPH-186 > Project: Maven Help Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-help-plugin] dependabot[bot] commented on pull request #63: Bump maven-enforcer-plugin from 3.0.0-M3 to 3.1.0
dependabot[bot] commented on PR #63: URL: https://github.com/apache/maven-help-plugin/pull/63#issuecomment-1200148070 Looks like org.apache.maven.plugins:maven-enforcer-plugin 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
[GitHub] [maven-help-plugin] dependabot[bot] closed pull request #63: Bump maven-enforcer-plugin from 3.0.0-M3 to 3.1.0
dependabot[bot] closed pull request #63: Bump maven-enforcer-plugin from 3.0.0-M3 to 3.1.0 URL: https://github.com/apache/maven-help-plugin/pull/63 -- 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] (MPH-186) maven-parent to 37
[ https://issues.apache.org/jira/browse/MPH-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573258#comment-17573258 ] Hudson commented on MPH-186: Build succeeded in Jenkins: Maven » Maven TLP » maven-help-plugin » master #16 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-help-plugin/job/master/16/ > maven-parent to 37 > -- > > Key: MPH-186 > URL: https://issues.apache.org/jira/browse/MPH-186 > Project: Maven Help Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1119) Cleanup IT tests
Slawomir Jaranowski created MSHARED-1119: Summary: Cleanup IT tests Key: MSHARED-1119 URL: https://issues.apache.org/jira/browse/MSHARED-1119 Project: Maven Shared Components Issue Type: Task Components: maven-dependency-analyzer Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: maven-dependency-analyzer-3.0.0 * use Maven version form project * update dependencies in IT tests -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MPH-188) Cleanup - Pom
[ https://issues.apache.org/jira/browse/MPH-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MPH-188: --- Assignee: Karl Heinz Marbaise > Cleanup - Pom > - > > Key: MPH-188 > URL: https://issues.apache.org/jira/browse/MPH-188 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPH-188) Cleanup - Pom
Karl Heinz Marbaise created MPH-188: --- Summary: Cleanup - Pom Key: MPH-188 URL: https://issues.apache.org/jira/browse/MPH-188 Project: Maven Help Plugin Issue Type: Task Affects Versions: 3.3.0 Reporter: Karl Heinz Marbaise Fix For: 3.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-dependency-analyzer] slawekjaranowski opened a new pull request, #68: [MSHARED-1119] Cleanup IT tests
slawekjaranowski opened a new pull request, #68: URL: https://github.com/apache/maven-dependency-analyzer/pull/68 - use Maven version form project - update dependencies in IT tests --- 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/MSHARED) 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. Also be sure having selected the correct component. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Format the pull request title like `[MSHARED-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MSHARED-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) - [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] (MPH-187) Upgrade to JDK minimum
[ https://issues.apache.org/jira/browse/MPH-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573262#comment-17573262 ] Karl Heinz Marbaise commented on MPH-187: - Done in [3974cd1cc5c99143d035663a91012bf09f62f845|https://gitbox.apache.org/repos/asf?p=maven-help-plugin.git;a=commitdiff;h=3974cd1cc5c99143d035663a91012bf09f62f845] > Upgrade to JDK minimum > -- > > Key: MPH-187 > URL: https://issues.apache.org/jira/browse/MPH-187 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPH-187) Upgrade to JDK minimum
[ https://issues.apache.org/jira/browse/MPH-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MPH-187. --- Resolution: Done > Upgrade to JDK minimum > -- > > Key: MPH-187 > URL: https://issues.apache.org/jira/browse/MPH-187 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPH-187) Upgrade to JDK minimum
[ https://issues.apache.org/jira/browse/MPH-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573264#comment-17573264 ] Hudson commented on MPH-187: Build succeeded in Jenkins: Maven » Maven TLP » maven-help-plugin » master #17 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-help-plugin/job/master/17/ > Upgrade to JDK minimum > -- > > Key: MPH-187 > URL: https://issues.apache.org/jira/browse/MPH-187 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-400) add system requirements history section
[
https://issues.apache.org/jira/browse/MPLUGIN-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573265#comment-17573265
]
Slawomir Jaranowski commented on MPLUGIN-400:
-
We can add parameter to report plugin with structure (list of histories
version):
{code:xml}
plugin version
maven version
jdk version
{code}
> add system requirements history section
> ---
>
> Key: MPLUGIN-400
> URL: https://issues.apache.org/jira/browse/MPLUGIN-400
> Project: Maven Plugin Tools
> Issue Type: New Feature
> Components: Plugin Plugin
>Reporter: Herve Boutemy
>Priority: Major
>
> currently, we generate a system requirement section
> h3. System Requirements
> The following specifies the minimum requirements to run this Maven plugin:
> |Maven|3.0|
> |JDK|1.7|
> |Memory|No minimum requirement.|
> |Disk Space|No minimum requirement.|
> We also need an history of previous versions to be able to show what was the
> last version that had another JDK or Maven prerequisite.
> while at it, I think we can remove memory and disk space that we never use...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPLUGIN-400) add system requirements history section
[
https://issues.apache.org/jira/browse/MPLUGIN-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573275#comment-17573275
]
Herve Boutemy commented on MPLUGIN-400:
---
yes
another approach to limit XML boilerplate and replace with easier to read
content:
{code:xml}
((plugin version)) requires Maven ((maven version))
and JDK ((jdk version))
{code}
with some code to split the String to its 3 fields (and fail if the expected
"requires Maven" and "and JDK" text is not found)
> add system requirements history section
> ---
>
> Key: MPLUGIN-400
> URL: https://issues.apache.org/jira/browse/MPLUGIN-400
> Project: Maven Plugin Tools
> Issue Type: New Feature
> Components: Plugin Plugin
>Reporter: Herve Boutemy
>Priority: Major
>
> currently, we generate a system requirement section
> h3. System Requirements
> The following specifies the minimum requirements to run this Maven plugin:
> |Maven|3.0|
> |JDK|1.7|
> |Memory|No minimum requirement.|
> |Disk Space|No minimum requirement.|
> We also need an history of previous versions to be able to show what was the
> last version that had another JDK or Maven prerequisite.
> while at it, I think we can remove memory and disk space that we never use...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-dependency-tree] michael-o commented on a diff in pull request #10: [MSHARED-1071] Drop maven 3.0 compatibility, Maven 3.2.5, Injects
michael-o commented on code in PR #10:
URL:
https://github.com/apache/maven-dependency-tree/pull/10#discussion_r933820488
##
pom.xml:
##
@@ -55,7 +55,9 @@
-8
+ 8
Review Comment:
Indent broken
##
pom.xml:
##
@@ -69,51 +71,38 @@
org.apache.maven
maven-core
- 3.0.5
-
-
- org.codehaus.plexus
- plexus-component-annotations
- true
-
-
- org.sonatype.aether
- aether-api
- 1.13.1
- true
+ ${maven.version}
+ provided
org.eclipse.aether
aether-api
- 1.1.0
- true
+ ${resolverVersion}
+ provided
org.eclipse.aether
aether-util
- 1.1.0
-
-
- org.eclipse.aether
- aether-api
-
-
+ ${resolverVersion}
+
+
+ org.slf4j
+ slf4j-api
+ 1.7.33
Review Comment:
36?
--
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] (MPLUGIN-400) add system requirements history section
[ https://issues.apache.org/jira/browse/MPLUGIN-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573277#comment-17573277 ] Slawomir Jaranowski commented on MPLUGIN-400: - even more can be both :-) and everybody will be happy > add system requirements history section > --- > > Key: MPLUGIN-400 > URL: https://issues.apache.org/jira/browse/MPLUGIN-400 > Project: Maven Plugin Tools > Issue Type: New Feature > Components: Plugin Plugin >Reporter: Herve Boutemy >Priority: Major > > currently, we generate a system requirement section > h3. System Requirements > The following specifies the minimum requirements to run this Maven plugin: > |Maven|3.0| > |JDK|1.7| > |Memory|No minimum requirement.| > |Disk Space|No minimum requirement.| > We also need an history of previous versions to be able to show what was the > last version that had another JDK or Maven prerequisite. > while at it, I think we can remove memory and disk space that we never use... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DOXIA-667) Add and to recognized tag list
John Dimeo created DOXIA-667: Summary: Add and to recognized tag list Key: DOXIA-667 URL: https://issues.apache.org/jira/browse/DOXIA-667 Project: Maven Doxia Issue Type: Improvement Components: Module - Markdown Reporter: John Dimeo I see both `` and `` here: [maven-doxia/HtmlMarkup.java at master · apache/maven-doxia (github.com)|https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/markup/HtmlMarkup.java] is there a reason it's not part of `ALL_TAGS` here? [https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/util/HtmlTools.java#L42] I'm getting this error: [maven-doxia/Xhtml5BaseSink.java at master · apache/maven-doxia (github.com)|https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/sink/impl/Xhtml5BaseSink.java#L2206] when I try to use details/disclosure in a Markdown file. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIA-667) Add and to recognized tag list
[
https://issues.apache.org/jira/browse/DOXIA-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Dimeo updated DOXIA-667:
-
Description:
I see both {{}} and {{}} here:
[maven-doxia/HtmlMarkup.java at master · apache/maven-doxia
(github.com)|https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/markup/HtmlMarkup.java]
is there a reason it's not part of {{ALL_TAGS}} here?
[https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/util/HtmlTools.java#L42]
I'm getting this error:
[maven-doxia/Xhtml5BaseSink.java at master · apache/maven-doxia
(github.com)|https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/sink/impl/Xhtml5BaseSink.java#L2206]
when I try to use details/disclosure in a Markdown file.
was:
I see both `` and `` here:
[maven-doxia/HtmlMarkup.java at master · apache/maven-doxia
(github.com)|https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/markup/HtmlMarkup.java]
is there a reason it's not part of `ALL_TAGS` here?
[https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/util/HtmlTools.java#L42]
I'm getting this error:
[maven-doxia/Xhtml5BaseSink.java at master · apache/maven-doxia
(github.com)|https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/sink/impl/Xhtml5BaseSink.java#L2206]
when I try to use details/disclosure in a Markdown file.
> Add and to recognized tag list
> --
>
> Key: DOXIA-667
> URL: https://issues.apache.org/jira/browse/DOXIA-667
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Module - Markdown
>Reporter: John Dimeo
>Priority: Major
> Labels: easyfix
>
> I see both {{}} and {{}} here:
> [maven-doxia/HtmlMarkup.java at master · apache/maven-doxia
> (github.com)|https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/markup/HtmlMarkup.java]
> is there a reason it's not part of {{ALL_TAGS}} here?
> [https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/util/HtmlTools.java#L42]
> I'm getting this error:
> [maven-doxia/Xhtml5BaseSink.java at master · apache/maven-doxia
> (github.com)|https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/sink/impl/Xhtml5BaseSink.java#L2206]
> when I try to use details/disclosure in a Markdown file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DOXIA-667) Add and to recognized tag list
[
https://issues.apache.org/jira/browse/DOXIA-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Dimeo updated DOXIA-667:
-
Component/s: Module - Xhtml
(was: Module - Markdown)
> Add and to recognized tag list
> --
>
> Key: DOXIA-667
> URL: https://issues.apache.org/jira/browse/DOXIA-667
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Module - Xhtml
>Reporter: John Dimeo
>Priority: Major
> Labels: easyfix
>
> I see both {{}} and {{}} here:
> [maven-doxia/HtmlMarkup.java at master · apache/maven-doxia
> (github.com)|https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/markup/HtmlMarkup.java]
> is there a reason it's not part of {{ALL_TAGS}} here?
> [https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/util/HtmlTools.java#L42]
> I'm getting this error:
> [maven-doxia/Xhtml5BaseSink.java at master · apache/maven-doxia
> (github.com)|https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/sink/impl/Xhtml5BaseSink.java#L2206]
> when I try to use details/disclosure in a Markdown file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-dependency-tree] slawekjaranowski commented on a diff in pull request #10: [MSHARED-1071] Drop maven 3.0 compatibility, Maven 3.2.5, Injects
slawekjaranowski commented on code in PR #10: URL: https://github.com/apache/maven-dependency-tree/pull/10#discussion_r933847470 ## pom.xml: ## @@ -55,7 +55,9 @@ -8 + 8 Review Comment: tab 😄 -- 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
[GitHub] [maven-plugin-tools] slawekjaranowski commented on pull request #129: [MPLUGIN-408] helpmojo improvement
slawekjaranowski commented on PR #129: URL: https://github.com/apache/maven-plugin-tools/pull/129#issuecomment-1200270387 Nobody wants to look? If need more time let me know. Failed build on jenkins on branch which was removed when PR has been created ... -- 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] (MPLUGIN-408) simplification in helpmojo build
[
https://issues.apache.org/jira/browse/MPLUGIN-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573287#comment-17573287
]
ASF GitHub Bot commented on MPLUGIN-408:
slawekjaranowski commented on PR #129:
URL:
https://github.com/apache/maven-plugin-tools/pull/129#issuecomment-1200270387
Nobody wants to look?
If need more time let me know.
Failed build on jenkins on branch which was removed when PR has been created
...
> simplification in helpmojo build
>
>
> Key: MPLUGIN-408
> URL: https://issues.apache.org/jira/browse/MPLUGIN-408
> Project: Maven Plugin Tools
> Issue Type: Wish
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> h2. Current situation
> - {{plugin:helpmojo}} extends {{AbstractGeneratorMojo}}
> - {{plugin:helpmojo}} is bound to {{generate-sources}} phase
> see
> https://maven.apache.org/plugin-tools/maven-plugin-plugin/helpmojo-mojo.html
> We have 2 steps for generate a {{HelpMojo}} for a plugin:
> 1. first step in {{plugin:helpmojo}} goal
> - {{helpmojo}} *builds plugin.xml descriptor* by discovering mojos in
> project (hoping to find javadoc annotations as it was done in the past), when
> we use {{@Mojo}} annotations for goals descriptions no mojo are discovered
> because source generation happens before compilation
> - try to discover package for {{HelpMojo}}: because descriptor is empty -
> *empty package* is used for generating source for {{HelpMojo}}
> 2. next step in {{plugin:descriptor}} goal, bound to {{process-classes}}
> phase
> https://maven.apache.org/plugin-tools/maven-plugin-plugin/descriptor-mojo.html
> - once again *build plugin descriptors* by discovering mojos in project, but
> this time
> - now we can have mojo so we can calculate package name
> - empty package name of {{HelpMojo}} is rewritten in generated source code
> - using ASM, package in class of {{HelpMojo}} is changed
> - source code and compiled class are moved to correct directory
> h2. Simplification proposition
> - use {{groupId.artifactId}} as java package of {{HelpMojo}} directly in
> {{plugin:helpmojo}} when generating source code
> - cleanup/simplify code (remove the {{plugin:descriptor}} package discovery
> and move)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-plugin-tools] michael-o commented on pull request #129: [MPLUGIN-408] helpmojo improvement
michael-o commented on PR #129: URL: https://github.com/apache/maven-plugin-tools/pull/129#issuecomment-1200273612 > Nobody wants to look? If need more time let me know. > > Failed build on jenkins on branch which was removed when PR has been created ... Massive change, takes time. It is weekend also... -- 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] (MPLUGIN-408) simplification in helpmojo build
[
https://issues.apache.org/jira/browse/MPLUGIN-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573288#comment-17573288
]
ASF GitHub Bot commented on MPLUGIN-408:
michael-o commented on PR #129:
URL:
https://github.com/apache/maven-plugin-tools/pull/129#issuecomment-1200273612
> Nobody wants to look? If need more time let me know.
>
> Failed build on jenkins on branch which was removed when PR has been
created ...
Massive change, takes time. It is weekend also...
> simplification in helpmojo build
>
>
> Key: MPLUGIN-408
> URL: https://issues.apache.org/jira/browse/MPLUGIN-408
> Project: Maven Plugin Tools
> Issue Type: Wish
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> h2. Current situation
> - {{plugin:helpmojo}} extends {{AbstractGeneratorMojo}}
> - {{plugin:helpmojo}} is bound to {{generate-sources}} phase
> see
> https://maven.apache.org/plugin-tools/maven-plugin-plugin/helpmojo-mojo.html
> We have 2 steps for generate a {{HelpMojo}} for a plugin:
> 1. first step in {{plugin:helpmojo}} goal
> - {{helpmojo}} *builds plugin.xml descriptor* by discovering mojos in
> project (hoping to find javadoc annotations as it was done in the past), when
> we use {{@Mojo}} annotations for goals descriptions no mojo are discovered
> because source generation happens before compilation
> - try to discover package for {{HelpMojo}}: because descriptor is empty -
> *empty package* is used for generating source for {{HelpMojo}}
> 2. next step in {{plugin:descriptor}} goal, bound to {{process-classes}}
> phase
> https://maven.apache.org/plugin-tools/maven-plugin-plugin/descriptor-mojo.html
> - once again *build plugin descriptors* by discovering mojos in project, but
> this time
> - now we can have mojo so we can calculate package name
> - empty package name of {{HelpMojo}} is rewritten in generated source code
> - using ASM, package in class of {{HelpMojo}} is changed
> - source code and compiled class are moved to correct directory
> h2. Simplification proposition
> - use {{groupId.artifactId}} as java package of {{HelpMojo}} directly in
> {{plugin:helpmojo}} when generating source code
> - cleanup/simplify code (remove the {{plugin:descriptor}} package discovery
> and move)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MDEP-816) Incorrect discription of 'verbose' parameter
codeno created MDEP-816:
---
Summary: Incorrect discription of 'verbose' parameter
Key: MDEP-816
URL: https://issues.apache.org/jira/browse/MDEP-816
Project: Maven Dependency Plugin
Issue Type: Bug
Components: tree
Affects Versions: 3.3.0
Reporter: codeno
{code:java}
/**
* Whether to include omitted nodes in the serialized dependency tree. Notice
this feature actually uses Maven 2
* algorithm and https://maven.apache.org/shared/maven-dependency-tree/";>may give wrong
results when used
* with Maven 3.
*
* @since 2.0-alpha-6
*/{code}
Metioned issue was fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-816) Incorrect discription of 'verbose' parameter
[
https://issues.apache.org/jira/browse/MDEP-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573291#comment-17573291
]
Slawomir Jaranowski commented on MDEP-816:
--
PR are welcome.
> Incorrect discription of 'verbose' parameter
>
>
> Key: MDEP-816
> URL: https://issues.apache.org/jira/browse/MDEP-816
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: tree
>Affects Versions: 3.3.0
>Reporter: codeno
>Priority: Trivial
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> {code:java}
> /**
> * Whether to include omitted nodes in the serialized dependency tree. Notice
> this feature actually uses Maven 2
> * algorithm and href="https://maven.apache.org/shared/maven-dependency-tree/";>may give wrong
> results when used
> * with Maven 3.
> *
> * @since 2.0-alpha-6
> */{code}
> Metioned issue was fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-816) Incorrect discription of 'verbose' parameter
[
https://issues.apache.org/jira/browse/MDEP-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MDEP-816:
-
Labels: up-for-grabs (was: )
> Incorrect discription of 'verbose' parameter
>
>
> Key: MDEP-816
> URL: https://issues.apache.org/jira/browse/MDEP-816
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: tree
>Affects Versions: 3.3.0
>Reporter: codeno
>Priority: Trivial
> Labels: up-for-grabs
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> {code:java}
> /**
> * Whether to include omitted nodes in the serialized dependency tree. Notice
> this feature actually uses Maven 2
> * algorithm and href="https://maven.apache.org/shared/maven-dependency-tree/";>may give wrong
> results when used
> * with Maven 3.
> *
> * @since 2.0-alpha-6
> */{code}
> Metioned issue was fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MPLUGIN-400) add system requirements history section
[ https://issues.apache.org/jira/browse/MPLUGIN-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski reassigned MPLUGIN-400: --- Assignee: Slawomir Jaranowski > add system requirements history section > --- > > Key: MPLUGIN-400 > URL: https://issues.apache.org/jira/browse/MPLUGIN-400 > Project: Maven Plugin Tools > Issue Type: New Feature > Components: Plugin Plugin >Reporter: Herve Boutemy >Assignee: Slawomir Jaranowski >Priority: Major > > currently, we generate a system requirement section > h3. System Requirements > The following specifies the minimum requirements to run this Maven plugin: > |Maven|3.0| > |JDK|1.7| > |Memory|No minimum requirement.| > |Disk Space|No minimum requirement.| > We also need an history of previous versions to be able to show what was the > last version that had another JDK or Maven prerequisite. > while at it, I think we can remove memory and disk space that we never use... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-jxr] michael-o opened a new pull request, #64: Prepare for Doxia 2.0.0
michael-o opened a new pull request, #64: URL: https://github.com/apache/maven-jxr/pull/64 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/JXR) 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. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[JXR-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `JXR-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. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] 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) - [ ] 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] [Updated] (MPLUGIN-403) Generating site reports for plugin results in NoSuchMethodError
[ https://issues.apache.org/jira/browse/MPLUGIN-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPLUGIN-403: --- Fix Version/s: 3.7.0 > Generating site reports for plugin results in NoSuchMethodError > --- > > Key: MPLUGIN-403 > URL: https://issues.apache.org/jira/browse/MPLUGIN-403 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.6.4 > Environment: Maven 3.8.5 > JDK 8 > Windows 10 >Reporter: Brad Larrick >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0 > > > When generating the site for a maven plugin I get the following: > java.lang.NoSuchMethodError: org.apache.maven.doxia.sink.Sink.verbatim(Z)V > at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText > (AbstractMavenReportRenderer.java:448) > at > org.apache.maven.plugin.plugin.PluginReport$PluginOverviewRenderer.renderUsageSection > (PluginReport.java:694) > at > org.apache.maven.plugin.plugin.PluginReport$PluginOverviewRenderer.renderBody > (PluginReport.java:616) > at org.apache.maven.reporting.AbstractMavenReportRenderer.render > (AbstractMavenReportRenderer.java:80) > at org.apache.maven.plugin.plugin.PluginReport.executeReport > (PluginReport.java:266) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPLUGIN-403) Generating site reports for plugin results in NoSuchMethodError
[ https://issues.apache.org/jira/browse/MPLUGIN-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPLUGIN-403. -- Resolution: Fixed Implicitly fixed by MPLUGIN-395. > Generating site reports for plugin results in NoSuchMethodError > --- > > Key: MPLUGIN-403 > URL: https://issues.apache.org/jira/browse/MPLUGIN-403 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.6.4 > Environment: Maven 3.8.5 > JDK 8 > Windows 10 >Reporter: Brad Larrick >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0 > > > When generating the site for a maven plugin I get the following: > java.lang.NoSuchMethodError: org.apache.maven.doxia.sink.Sink.verbatim(Z)V > at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText > (AbstractMavenReportRenderer.java:448) > at > org.apache.maven.plugin.plugin.PluginReport$PluginOverviewRenderer.renderUsageSection > (PluginReport.java:694) > at > org.apache.maven.plugin.plugin.PluginReport$PluginOverviewRenderer.renderBody > (PluginReport.java:616) > at org.apache.maven.reporting.AbstractMavenReportRenderer.render > (AbstractMavenReportRenderer.java:80) > at org.apache.maven.plugin.plugin.PluginReport.executeReport > (PluginReport.java:266) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-release] michael-o commented on pull request #144: [MRELEASE-1094] Clean up dependencies
michael-o commented on PR #144: URL: https://github.com/apache/maven-release/pull/144#issuecomment-1200287744 @cstamas Any further objections? -- 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
[GitHub] [maven-release] asfgit closed pull request #143: [MRELEASE-1100] Upgrade Maven SCM to 2.0.0-M2
asfgit closed pull request #143: [MRELEASE-1100] Upgrade Maven SCM to 2.0.0-M2 URL: https://github.com/apache/maven-release/pull/143 -- 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] (MRELEASE-1100) Upgrade Maven SCM to 2.0.0-M2
[ https://issues.apache.org/jira/browse/MRELEASE-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MRELEASE-1100. Resolution: Fixed Fixed with [a197ada6eb54ba89037a04c9d24ee1faab82aa80|https://gitbox.apache.org/repos/asf?p=maven-release.git;a=commit;h=a197ada6eb54ba89037a04c9d24ee1faab82aa80]. > Upgrade Maven SCM to 2.0.0-M2 > - > > Key: MRELEASE-1100 > URL: https://issues.apache.org/jira/browse/MRELEASE-1100 > Project: Maven Release Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0-M7 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-release] nielsbasjes commented on pull request #104: [MRELEASE-1078] Conventional commits
nielsbasjes commented on PR #104: URL: https://github.com/apache/maven-release/pull/104#issuecomment-1200292343 Rebased against the master which now includes the needed SCM 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
[GitHub] [maven-help-plugin] slachiewicz merged pull request #61: Bump asm from 9.2 to 9.3
slachiewicz merged PR #61: URL: https://github.com/apache/maven-help-plugin/pull/61 -- 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
[GitHub] [maven-help-plugin] slachiewicz merged pull request #58: Bump asm-commons from 9.2 to 9.3
slachiewicz merged PR #58: URL: https://github.com/apache/maven-help-plugin/pull/58 -- 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] (MRELEASE-1100) Upgrade Maven SCM to 2.0.0-M2
[ https://issues.apache.org/jira/browse/MRELEASE-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573302#comment-17573302 ] Hudson commented on MRELEASE-1100: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-release » master #55 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-release/job/master/55/ > Upgrade Maven SCM to 2.0.0-M2 > - > > Key: MRELEASE-1100 > URL: https://issues.apache.org/jira/browse/MRELEASE-1100 > Project: Maven Release Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0-M7 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-help-plugin] slachiewicz commented on pull request #59: Bump plexus-utils from 3.3.0 to 3.4.2
slachiewicz commented on PR #59: URL: https://github.com/apache/maven-help-plugin/pull/59#issuecomment-1200293379 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-release] asfgit closed pull request #139: [MRELEASE-1099] allow using a shallow clone during release:perform
asfgit closed pull request #139: [MRELEASE-1099] allow using a shallow clone during release:perform URL: https://github.com/apache/maven-release/pull/139 -- 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] (MRELEASE-1099) Use shallow checkout/clone during release:perform
[
https://issues.apache.org/jira/browse/MRELEASE-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-1099.
Resolution: Fixed
Fixed with
[cc7d3b6a4c5e0ac7ceea0f7790b6248f1848d160|https://gitbox.apache.org/repos/asf?p=maven-release.git;a=commit;h=cc7d3b6a4c5e0ac7ceea0f7790b6248f1848d160].
> Use shallow checkout/clone during release:perform
> -
>
> Key: MRELEASE-1099
> URL: https://issues.apache.org/jira/browse/MRELEASE-1099
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: scm
>Affects Versions: 3.0.0-M6
>Reporter: Michael Cramer
>Assignee: Michael Osipov
>Priority: Major
> Labels: checkout, clone, git, shallow, up-for-grabs
> Fix For: 3.0.0-M7
>
>
> this is a follow-up for MRELEASE-1082.
> after using the new 3.0.0-M6 version we are still getting the warning about
> missing blame information during the sonarqube analysis performed during the
> perform step. While checking why it doesn't work I figured out that the
> previous implementation is incomplete.
> {noformat}
> [INFO] [WARNING] Missing blame information for the following files:
> {noformat}
> Two things are missing as far as i have seen:
> - the {{release-descriptor.mdo}} is incomplete
> -- missing equals implementation for {{scmShallowClone}}
> -- missing hashcode implementation for {{scmShallowClone}}
> - during perform the default of true is used for {{scmShallowClone}} because
> no parameter is available for {{scmShallowClone}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MRELEASE-1099) Use shallow checkout/clone during release:perform
[
https://issues.apache.org/jira/browse/MRELEASE-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573305#comment-17573305
]
Hudson commented on MRELEASE-1099:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-release » master #56
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-release/job/master/56/
> Use shallow checkout/clone during release:perform
> -
>
> Key: MRELEASE-1099
> URL: https://issues.apache.org/jira/browse/MRELEASE-1099
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: scm
>Affects Versions: 3.0.0-M6
>Reporter: Michael Cramer
>Assignee: Michael Osipov
>Priority: Major
> Labels: checkout, clone, git, shallow, up-for-grabs
> Fix For: 3.0.0-M7
>
>
> this is a follow-up for MRELEASE-1082.
> after using the new 3.0.0-M6 version we are still getting the warning about
> missing blame information during the sonarqube analysis performed during the
> perform step. While checking why it doesn't work I figured out that the
> previous implementation is incomplete.
> {noformat}
> [INFO] [WARNING] Missing blame information for the following files:
> {noformat}
> Two things are missing as far as i have seen:
> - the {{release-descriptor.mdo}} is incomplete
> -- missing equals implementation for {{scmShallowClone}}
> -- missing hashcode implementation for {{scmShallowClone}}
> - during perform the default of true is used for {{scmShallowClone}} because
> no parameter is available for {{scmShallowClone}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MSITE-909) Add Bootstrap Site Skin to documentation
Stephen Crocker created MSITE-909: - Summary: Add Bootstrap Site Skin to documentation Key: MSITE-909 URL: https://issues.apache.org/jira/browse/MSITE-909 Project: Maven Site Plugin Issue Type: New Feature Reporter: Stephen Crocker I have developed a new Maven Site skin based on Bootstrap 5 components and elements which can be toggled on/off allowing a variety of layouts. The areas of the community I have shared this with have suggested placing it into the available skin documentation so other projects can find it. This feature is adding that information to the relevant documentation page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-site] stevecrox opened a new pull request, #314: MSITE-909 - Added new Site skin information to documentation
stevecrox opened a new pull request, #314: URL: https://github.com/apache/maven-site/pull/314 Added new Site skin information to documentation -- 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] (MSITE-909) Add Bootstrap Site Skin to documentation
[ https://issues.apache.org/jira/browse/MSITE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573306#comment-17573306 ] ASF GitHub Bot commented on MSITE-909: -- stevecrox opened a new pull request, #314: URL: https://github.com/apache/maven-site/pull/314 Added new Site skin information to documentation > Add Bootstrap Site Skin to documentation > > > Key: MSITE-909 > URL: https://issues.apache.org/jira/browse/MSITE-909 > Project: Maven Site Plugin > Issue Type: New Feature >Reporter: Stephen Crocker >Priority: Minor > > I have developed a new Maven Site skin based on Bootstrap 5 components and > elements which can be toggled on/off allowing a variety of layouts. > The areas of the community I have shared this with have suggested placing it > into the available skin documentation so other projects can find it. > This feature is adding that information to the relevant documentation page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSITE-909) Add Bootstrap Site Skin to documentation
[ https://issues.apache.org/jira/browse/MSITE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573307#comment-17573307 ] Stephen Crocker commented on MSITE-909: --- Raised PR: https://github.com/apache/maven-site/pull/314 > Add Bootstrap Site Skin to documentation > > > Key: MSITE-909 > URL: https://issues.apache.org/jira/browse/MSITE-909 > Project: Maven Site Plugin > Issue Type: New Feature >Reporter: Stephen Crocker >Priority: Minor > > I have developed a new Maven Site skin based on Bootstrap 5 components and > elements which can be toggled on/off allowing a variety of layouts. > The areas of the community I have shared this with have suggested placing it > into the available skin documentation so other projects can find it. > This feature is adding that information to the relevant documentation page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNGSITE-488) Add Bootstrap Site Skin to documentation
[ https://issues.apache.org/jira/browse/MNGSITE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNGSITE-488: --- Issue Type: Task (was: New Feature) > Add Bootstrap Site Skin to documentation > > > Key: MNGSITE-488 > URL: https://issues.apache.org/jira/browse/MNGSITE-488 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Stephen Crocker >Priority: Minor > > I have developed a new Maven Site skin based on Bootstrap 5 components and > elements which can be toggled on/off allowing a variety of layouts. > The areas of the community I have shared this with have suggested placing it > into the available skin documentation so other projects can find it. > This feature is adding that information to the relevant documentation page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Moved] (MNGSITE-488) Add Bootstrap Site Skin to documentation
[ https://issues.apache.org/jira/browse/MNGSITE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov moved MSITE-909 to MNGSITE-488: -- Key: MNGSITE-488 (was: MSITE-909) Project: Maven Project Web Site (was: Maven Site Plugin) > Add Bootstrap Site Skin to documentation > > > Key: MNGSITE-488 > URL: https://issues.apache.org/jira/browse/MNGSITE-488 > Project: Maven Project Web Site > Issue Type: New Feature >Reporter: Stephen Crocker >Priority: Minor > > I have developed a new Maven Site skin based on Bootstrap 5 components and > elements which can be toggled on/off allowing a variety of layouts. > The areas of the community I have shared this with have suggested placing it > into the available skin documentation so other projects can find it. > This feature is adding that information to the relevant documentation page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-release] michael-o opened a new pull request, #145: Simplify PerformReleaseMojo
michael-o opened a new pull request, #145: URL: https://github.com/apache/maven-release/pull/145 @kwin @nielsbasjes Have a look whether this makes sense to you. I am not 100% certain about this. It feels awkward that this mojo does not extend from `AbstractScmReleaseMojo`, but still from `AbstractReleaseMojo` since other release mojos do so. If this isn't right a comment should be added to the code explaning why. This affects #133 and #134. -- 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
[GitHub] [maven-release] michael-o commented on pull request #145: Simplify PerformReleaseMojo
michael-o commented on PR #145: URL: https://github.com/apache/maven-release/pull/145#issuecomment-1200301826 @slavino Have a look also. -- 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] (DOXIA-667) Add and to recognized tag list
[
https://issues.apache.org/jira/browse/DOXIA-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573316#comment-17573316
]
Michael Osipov commented on DOXIA-667:
--
Indeed! Kindly review for missing tags and provide a PR. I will happily merge.
> Add and to recognized tag list
> --
>
> Key: DOXIA-667
> URL: https://issues.apache.org/jira/browse/DOXIA-667
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Module - Xhtml
>Reporter: John Dimeo
>Priority: Major
> Labels: easyfix
>
> I see both {{}} and {{}} here:
> [maven-doxia/HtmlMarkup.java at master · apache/maven-doxia
> (github.com)|https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/markup/HtmlMarkup.java]
> is there a reason it's not part of {{ALL_TAGS}} here?
> [https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/util/HtmlTools.java#L42]
> I'm getting this error:
> [maven-doxia/Xhtml5BaseSink.java at master · apache/maven-doxia
> (github.com)|https://github.com/apache/maven-doxia/blob/master/doxia-core/src/main/java/org/apache/maven/doxia/sink/impl/Xhtml5BaseSink.java#L2206]
> when I try to use details/disclosure in a Markdown file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-816) Incorrect description of 'verbose' parameter
[
https://issues.apache.org/jira/browse/MDEP-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
codeno updated MDEP-816:
Summary: Incorrect description of 'verbose' parameter (was: Incorrect
discription of 'verbose' parameter)
> Incorrect description of 'verbose' parameter
>
>
> Key: MDEP-816
> URL: https://issues.apache.org/jira/browse/MDEP-816
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: tree
>Affects Versions: 3.3.0
>Reporter: codeno
>Priority: Trivial
> Labels: up-for-grabs
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> {code:java}
> /**
> * Whether to include omitted nodes in the serialized dependency tree. Notice
> this feature actually uses Maven 2
> * algorithm and href="https://maven.apache.org/shared/maven-dependency-tree/";>may give wrong
> results when used
> * with Maven 3.
> *
> * @since 2.0-alpha-6
> */{code}
> Metioned issue was fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-816) Incorrect description of 'verbose' parameter
[
https://issues.apache.org/jira/browse/MDEP-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573337#comment-17573337
]
codeno commented on MDEP-816:
-
Just found this is duplicate.
[MDEP-809]
> Incorrect description of 'verbose' parameter
>
>
> Key: MDEP-816
> URL: https://issues.apache.org/jira/browse/MDEP-816
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: tree
>Affects Versions: 3.3.0
>Reporter: codeno
>Priority: Trivial
> Labels: up-for-grabs
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> {code:java}
> /**
> * Whether to include omitted nodes in the serialized dependency tree. Notice
> this feature actually uses Maven 2
> * algorithm and href="https://maven.apache.org/shared/maven-dependency-tree/";>may give wrong
> results when used
> * with Maven 3.
> *
> * @since 2.0-alpha-6
> */{code}
> Metioned issue was fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-mvnd] gzm55 opened a new issue, #669: runtime jdk requirement of java client (via mvnd.sh) should be aligned to JDK8
gzm55 opened a new issue, #669: URL: https://github.com/apache/maven-mvnd/issues/669 Now java client (via `mvnd.sh`) requires JDK11, different with native `mvnd` and the embedded maven 3.8.5. This makes the user surprising in some production environments. - Native `mvnd`: requires JDK8 - maven 3.8.5: requires JDK8 - `mvnd.sh`: requires JDK11 ? -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
