[PR] Bump org.apache.maven.resolver:maven-resolver-connector-basic from 1.6.3 to 2.0.0 [maven-verifier]
dependabot[bot] opened a new pull request, #93: URL: https://github.com/apache/maven-verifier/pull/93 Bumps [org.apache.maven.resolver:maven-resolver-connector-basic](https://github.com/apache/maven-resolver) from 1.6.3 to 2.0.0. Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-connector-basic's releases. 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721";>Release Notes - Maven Resolver - Version 2.0.0 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/be148b8952b18f6c1e5245f66b554440676fb6dc";>be148b8 [maven-release-plugin] prepare release maven-resolver-2.0.0 https://github.com/apache/maven-resolver/commit/19a3c52c905dbb9686948e6f8ce73db404defdd8";>19a3c52 Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/525";>#525) https://github.com/apache/maven-resolver/commit/eb170c3a17919449fc1dc182b30daacc11dffefa";>eb170c3 [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/909330cc277f501e9e3aea80f8d5af2832d87e91";>909330c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/522";>#522) https://github.com/apache/maven-resolver/commit/2c76efa494f868de72f7fe47fc88bed0023cab0b";>2c76efa [MRESOLVER-575] Bump org.redisson:redisson from 3.31.0 to 3.32.0 (https://redirect.github.com/apache/maven-resolver/issues/519";>#519) https://github.com/apache/maven-resolver/commit/a65450f2a4509fe289c10b2a7cf6a7f76ff500c2";>a65450f [MRESOLVER-571] Fix usage of '-noimport' directive on exports https://github.com/apache/maven-resolver/commit/d4bd9917a1eb7f76bad89fa35969b76deb4e89d9";>d4bd991 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/d0edd7942f7af7732bccf6a7e68d0321906c6379";>d0edd79 [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/8266e6c320a7cf4deed3deb253ff4fd506d1d8f2";>8266e6c [MRESOLVER-27] Turn resolver api, spi and utils into Java 9 modules (https://redirect.github.com/apache/maven-resolver/issues/516";>#516) https://github.com/apache/maven-resolver/commit/2393568ca1722f15dbb0133d745a36dd6d583342";>2393568 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.6.3...maven-resolver-2.0.0";>compare view Most Recent Ignore Conditions Applied to This Pull Request | Dependency Name | Ignore Conditions | | --- | --- | | org.apache.maven.resolver:maven-resolver-connector-basic | [>= 1.9.a, < 1.10] | [](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 reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log
[jira] [Commented] (MNG-8173) -Dpackaging= is ignored when using mvn deploy:deploy-file
[
https://issues.apache.org/jira/browse/MNG-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863668#comment-17863668
]
Lars Schmertmann commented on MNG-8173:
---
Using "deploy:*3.0.0-M2*:deploy-file" as mentioned in MDEPLOY-311 works with
3.9.8.
"deploy:*3.0.0*:deploy-file" is broken.
> -Dpackaging= is ignored when using mvn deploy:deploy-file
> -
>
> Key: MNG-8173
> URL: https://issues.apache.org/jira/browse/MNG-8173
> Project: Maven
> Issue Type: Bug
> Components: Command Line, Deployment
>Affects Versions: 3.9.6, 3.9.7, 3.9.8
> Environment: Archlinux
>Reporter: Lars Schmertmann
>Priority: Major
>
> We have a project where we deploy the following files:
> {code}
> ausweisapp-2.2.0.aar
> ausweisapp-2.2.0.aar.asc
> ausweisapp-2.2.0.pom
> ausweisapp-2.2.0.pom.asc
> ausweisapp-2.2.0-sources.jar
> ausweisapp-2.2.0-sources.jar.asc
> {code}
> We are using the following commands:
> {code}
> /usr/bin/mvn deploy:deploy-file -Dfile=ausweisapp-2.2.0.aar
> -DpomFile=ausweisapp-2.2.0.pom -Dsources=ausweisapp-2.2.0-sources.jar
> -DrepositoryId=nexus
> -Durl=https://s01.oss.sonatype.org/service/local/staging/deploy/maven2
> --settings settings.xml
> /usr/bin/mvn deploy:deploy-file -Dfile=ausweisapp-2.2.0.aar.asc
> -Dpackaging=aar.asc -Dclassifier= -DpomFile=ausweisapp-2.2.0.pom
> -DrepositoryId=nexus
> -Durl=https://s01.oss.sonatype.org/service/local/staging/deploy/maven2
> --settings settings.xml
> /usr/bin/mvn deploy:deploy-file -Dfile=ausweisapp-2.2.0.pom.asc
> -Dpackaging=pom.asc -Dclassifier= -DpomFile=ausweisapp-2.2.0.pom
> -DrepositoryId=nexus
> -Durl=https://s01.oss.sonatype.org/service/local/staging/deploy/maven2
> --settings settings.xml
> /usr/bin/mvn deploy:deploy-file -Dfile=ausweisapp-2.2.0-sources.jar.asc
> -Dpackaging=jar.asc -Dclassifier=sources -DpomFile=ausweisapp-2.2.0.pom
> -DrepositoryId=nexus
> -Durl=https://s01.oss.sonatype.org/service/local/staging/deploy/maven2
> --settings settings.xml
> {code}
> With 3.8.7 everythings works fine. But at least with 3.9.6 - 3.9.8
> `-Dpackaging=` is ignored.
> This leads to the following renames during deployment and the signature check
> fails:
> {code}
> ausweisapp-2.2.0.aar.asc -> ausweisapp-2.2.0.asc
> ausweisapp-2.2.0.pom.asc -> ausweisapp-2.2.0.asc
> ausweisapp-2.2.0-sources.jar.asc -> ausweisapp-2.2.0-sources.asc
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump resolverVersion from 1.9.20 to 1.9.21 [maven-resolver-ant-tasks]
dependabot[bot] opened a new pull request, #41: URL: https://github.com/apache/maven-resolver-ant-tasks/pull/41 Bumps `resolverVersion` from 1.9.20 to 1.9.21. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.9.20 to 1.9.21 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 1.9.21 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354622";>Release Notes - Maven Resolver - Version 1.9.21 What's Changed [Build] Unify bnd-maven-plugin and maven-jar-plugin invocations by https://github.com/HannesWell";>@HannesWell in https://redirect.github.com/apache/maven-resolver/pull/509";>apache/maven-resolver#509 [Build] Define all MANIFEST.MF entries through the bnd-maven-plugin by https://github.com/HannesWell";>@HannesWell in https://redirect.github.com/apache/maven-resolver/pull/518";>apache/maven-resolver#518 [1.9.x] [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata by https://github.com/HannesWell";>@HannesWell in https://redirect.github.com/apache/maven-resolver/pull/505";>apache/maven-resolver#505 [1.9.x] [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal by https://github.com/HannesWell";>@HannesWell in https://redirect.github.com/apache/maven-resolver/pull/510";>apache/maven-resolver#510 [1.9.x] [MRESOLVER-571] Import o.e.aether packages with the exact same version by https://github.com/HannesWell";>@HannesWell in https://redirect.github.com/apache/maven-resolver/pull/507";>apache/maven-resolver#507 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f3adea9e6315787af930140de5ebea37754c79f1";>f3adea9 [maven-release-plugin] prepare release maven-resolver-1.9.21 https://github.com/apache/maven-resolver/commit/665516073ff613b6e38e08a69d58b2c4ed92d3cd";>6655160 [1.9.x] Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/524";>#524) https://github.com/apache/maven-resolver/commit/c7639bc0a663b3209d4d9bd068aaf74ceee1bfd4";>c7639bc [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/99ddef87e5c06c73e0e0b0c1983436466c3f4780";>99ddef8 [MRESOLVER-576] Make Resolver 1.x site land in LATEST-1.x https://github.com/apache/maven-resolver/commit/ca35d0c39e62c02e3b49cf4b74e68a4324e0b7eb";>ca35d0c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/523";>#523) https://github.com/apache/maven-resolver/commit/62887800d400416d5ebedef8351dda76dc1b6163";>6288780 [MRESOLVER-575] Bump org.redisson:redisson to 3.32.0 https://github.com/apache/maven-resolver/commit/f14ed822655c26d6a76ff4d513190b4035e38693";>f14ed82 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/5b8f47a5a96ffb8e7ea8152b18eadc8356bd8c87";>5b8f47a [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/e33cd9495972ffbdf286df6cb942d25dbb36ddd3";>e33cd94 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata https://github.com/apache/maven-resolver/commit/52b4db37064afad4987f6c25c8b3d2c60fec28d4";>52b4db3 [Build] Define all MANIFEST.MF entries through the bnd-maven-plugin Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.20...maven-resolver-1.9.21";>compare view Updates `org.apache.maven.resolver:maven-resolver-util` from 1.9.20 to 1.9.21 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-util's releases. 1.9.21 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354622";>Release Notes - Maven Resolver - Version 1.9.21 What's Changed [Build] Unify bnd-maven-plugin and maven-jar-plugin invocations by https://github.com/HannesWell";>@HannesWell in https://redirect.github.com/apache/maven-resolver/pull/509";>apache/maven-resolver#509 [Build] Define all MANIFEST.MF entries through the bnd-maven-plugin by https://github.com/HannesWell";>@HannesWell in https://redirect.github.com/apache/maven-resolver/pull/518";>apache/maven-resolver#518 [1.9.x] [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata by https://github.com/HannesWell";>@HannesWell in https://redirect.github.com/apache/maven-resolver/pull/505";>apache/maven-resolver#505 [1.9.x] [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal by https://github.com/HannesWell";>@HannesWell in https://redirect.github.com/apache/maven-resolver/pull/510";>apache/maven-resolver#510 [1.9.x] [MRESOLVER-571] Import o.e.aether packages with the exact same ve
[PR] Bump org.apache.maven.resolver:maven-resolver-api from 2.0.0-alpha-11 to 2.0.0 [maven-install-plugin]
dependabot[bot] opened a new pull request, #74: URL: https://github.com/apache/maven-install-plugin/pull/74 Bumps [org.apache.maven.resolver:maven-resolver-api](https://github.com/apache/maven-resolver) from 2.0.0-alpha-11 to 2.0.0. Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721";>Release Notes - Maven Resolver - Version 2.0.0 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/be148b8952b18f6c1e5245f66b554440676fb6dc";>be148b8 [maven-release-plugin] prepare release maven-resolver-2.0.0 https://github.com/apache/maven-resolver/commit/19a3c52c905dbb9686948e6f8ce73db404defdd8";>19a3c52 Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/525";>#525) https://github.com/apache/maven-resolver/commit/eb170c3a17919449fc1dc182b30daacc11dffefa";>eb170c3 [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/909330cc277f501e9e3aea80f8d5af2832d87e91";>909330c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/522";>#522) https://github.com/apache/maven-resolver/commit/2c76efa494f868de72f7fe47fc88bed0023cab0b";>2c76efa [MRESOLVER-575] Bump org.redisson:redisson from 3.31.0 to 3.32.0 (https://redirect.github.com/apache/maven-resolver/issues/519";>#519) https://github.com/apache/maven-resolver/commit/a65450f2a4509fe289c10b2a7cf6a7f76ff500c2";>a65450f [MRESOLVER-571] Fix usage of '-noimport' directive on exports https://github.com/apache/maven-resolver/commit/d4bd9917a1eb7f76bad89fa35969b76deb4e89d9";>d4bd991 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/d0edd7942f7af7732bccf6a7e68d0321906c6379";>d0edd79 [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/8266e6c320a7cf4deed3deb253ff4fd506d1d8f2";>8266e6c [MRESOLVER-27] Turn resolver api, spi and utils into Java 9 modules (https://redirect.github.com/apache/maven-resolver/issues/516";>#516) https://github.com/apache/maven-resolver/commit/2393568ca1722f15dbb0133d745a36dd6d583342";>2393568 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-2.0.0-alpha-11...maven-resolver-2.0.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump resolverVersion from 1.9.18 to 2.0.0 [maven-artifact-plugin]
dependabot[bot] opened a new pull request, #49: URL: https://github.com/apache/maven-artifact-plugin/pull/49 Bumps `resolverVersion` from 1.9.18 to 2.0.0. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.9.18 to 2.0.0 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721";>Release Notes - Maven Resolver - Version 2.0.0 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/be148b8952b18f6c1e5245f66b554440676fb6dc";>be148b8 [maven-release-plugin] prepare release maven-resolver-2.0.0 https://github.com/apache/maven-resolver/commit/19a3c52c905dbb9686948e6f8ce73db404defdd8";>19a3c52 Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/525";>#525) https://github.com/apache/maven-resolver/commit/eb170c3a17919449fc1dc182b30daacc11dffefa";>eb170c3 [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/909330cc277f501e9e3aea80f8d5af2832d87e91";>909330c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/522";>#522) https://github.com/apache/maven-resolver/commit/2c76efa494f868de72f7fe47fc88bed0023cab0b";>2c76efa [MRESOLVER-575] Bump org.redisson:redisson from 3.31.0 to 3.32.0 (https://redirect.github.com/apache/maven-resolver/issues/519";>#519) https://github.com/apache/maven-resolver/commit/a65450f2a4509fe289c10b2a7cf6a7f76ff500c2";>a65450f [MRESOLVER-571] Fix usage of '-noimport' directive on exports https://github.com/apache/maven-resolver/commit/d4bd9917a1eb7f76bad89fa35969b76deb4e89d9";>d4bd991 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/d0edd7942f7af7732bccf6a7e68d0321906c6379";>d0edd79 [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/8266e6c320a7cf4deed3deb253ff4fd506d1d8f2";>8266e6c [MRESOLVER-27] Turn resolver api, spi and utils into Java 9 modules (https://redirect.github.com/apache/maven-resolver/issues/516";>#516) https://github.com/apache/maven-resolver/commit/2393568ca1722f15dbb0133d745a36dd6d583342";>2393568 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.18...maven-resolver-2.0.0";>compare view Updates `org.apache.maven.resolver:maven-resolver-util` from 1.9.18 to 2.0.0 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-util's releases. 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721";>Release Notes - Maven Resolver - Version 2.0.0 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/be148b8952b18f6c1e5245f66b554440676fb6dc";>be148b8 [maven-release-plugin] prepare release maven-resolver-2.0.0 https://github.com/apache/maven-resolver/commit/19a3c52c905dbb9686948e6f8ce73db404defdd8";>19a3c52 Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/525";>#525) https://github.com/apache/maven-resolver/commit/eb170c3a17919449fc1dc182b30daacc11dffefa";>eb170c3 [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/909330cc277f501e9e3aea80f8d5af2832d87e91";>909330c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/522";>#522) https://github.com/apache/maven-resolver/commit/2c76efa494f868de72f7fe47fc88bed0023cab0b";>2c76efa [MRESOLVER-575] Bump org.redisson:redisson from 3.31.0 to 3.32.0 (https://redirect.github.com/apache/maven-resolver/issues/519";>#519) https://github.com/apache/maven-resolver/commit/a65450f2a4509fe289c10b2a7cf6a7f76ff500c2";>a65450f [MRESOLVER-571] Fix usage of '-noimport' directive on exports https://github.com/apache/maven-resolver/commit/d4bd9917a1eb7f76bad89fa35969b76deb4e89d9";>d4bd991 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/d0edd7942f7af7732bccf6a7e68d0321906c6379";>d0edd79 [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/8266e6c320a7cf4deed3deb253ff4fd506d1d8f2";>8266e6c [MRESOLVER-27] Turn resolver api, spi and utils into Java 9 modules (https://redirect.github.com/apache/maven-resolver/issues/516";>#516) https://github.com/apache/maven-resolver/commit/2393568ca1722f15dbb0133d745a36dd6d583342";>2393568 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata Additional commits viewable in
[PR] Bump resolver.version from 1.9.20 to 2.0.0 [maven-indexer]
dependabot[bot] opened a new pull request, #375: URL: https://github.com/apache/maven-indexer/pull/375 Bumps `resolver.version` from 1.9.20 to 2.0.0. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.9.20 to 2.0.0 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721";>Release Notes - Maven Resolver - Version 2.0.0 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/be148b8952b18f6c1e5245f66b554440676fb6dc";>be148b8 [maven-release-plugin] prepare release maven-resolver-2.0.0 https://github.com/apache/maven-resolver/commit/19a3c52c905dbb9686948e6f8ce73db404defdd8";>19a3c52 Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/525";>#525) https://github.com/apache/maven-resolver/commit/eb170c3a17919449fc1dc182b30daacc11dffefa";>eb170c3 [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/909330cc277f501e9e3aea80f8d5af2832d87e91";>909330c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/522";>#522) https://github.com/apache/maven-resolver/commit/2c76efa494f868de72f7fe47fc88bed0023cab0b";>2c76efa [MRESOLVER-575] Bump org.redisson:redisson from 3.31.0 to 3.32.0 (https://redirect.github.com/apache/maven-resolver/issues/519";>#519) https://github.com/apache/maven-resolver/commit/a65450f2a4509fe289c10b2a7cf6a7f76ff500c2";>a65450f [MRESOLVER-571] Fix usage of '-noimport' directive on exports https://github.com/apache/maven-resolver/commit/d4bd9917a1eb7f76bad89fa35969b76deb4e89d9";>d4bd991 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/d0edd7942f7af7732bccf6a7e68d0321906c6379";>d0edd79 [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/8266e6c320a7cf4deed3deb253ff4fd506d1d8f2";>8266e6c [MRESOLVER-27] Turn resolver api, spi and utils into Java 9 modules (https://redirect.github.com/apache/maven-resolver/issues/516";>#516) https://github.com/apache/maven-resolver/commit/2393568ca1722f15dbb0133d745a36dd6d583342";>2393568 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.20...maven-resolver-2.0.0";>compare view Updates `org.apache.maven.resolver:maven-resolver-util` from 1.9.20 to 2.0.0 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-util's releases. 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721";>Release Notes - Maven Resolver - Version 2.0.0 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/be148b8952b18f6c1e5245f66b554440676fb6dc";>be148b8 [maven-release-plugin] prepare release maven-resolver-2.0.0 https://github.com/apache/maven-resolver/commit/19a3c52c905dbb9686948e6f8ce73db404defdd8";>19a3c52 Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/525";>#525) https://github.com/apache/maven-resolver/commit/eb170c3a17919449fc1dc182b30daacc11dffefa";>eb170c3 [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/909330cc277f501e9e3aea80f8d5af2832d87e91";>909330c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/522";>#522) https://github.com/apache/maven-resolver/commit/2c76efa494f868de72f7fe47fc88bed0023cab0b";>2c76efa [MRESOLVER-575] Bump org.redisson:redisson from 3.31.0 to 3.32.0 (https://redirect.github.com/apache/maven-resolver/issues/519";>#519) https://github.com/apache/maven-resolver/commit/a65450f2a4509fe289c10b2a7cf6a7f76ff500c2";>a65450f [MRESOLVER-571] Fix usage of '-noimport' directive on exports https://github.com/apache/maven-resolver/commit/d4bd9917a1eb7f76bad89fa35969b76deb4e89d9";>d4bd991 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/d0edd7942f7af7732bccf6a7e68d0321906c6379";>d0edd79 [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/8266e6c320a7cf4deed3deb253ff4fd506d1d8f2";>8266e6c [MRESOLVER-27] Turn resolver api, spi and utils into Java 9 modules (https://redirect.github.com/apache/maven-resolver/issues/516";>#516) https://github.com/apache/maven-resolver/commit/2393568ca1722f15dbb0133d745a36dd6d583342";>2393568 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata Additional commits viewable in https
[PR] Bump org.xmlunit:xmlunit-matchers from 2.9.1 to 2.10.0 [maven-archetype]
dependabot[bot] opened a new pull request, #200: URL: https://github.com/apache/maven-archetype/pull/200 Bumps [org.xmlunit:xmlunit-matchers](https://github.com/xmlunit/xmlunit) from 2.9.1 to 2.10.0. Release notes Sourced from https://github.com/xmlunit/xmlunit/releases";>org.xmlunit:xmlunit-matchers's releases. XMLUnit for Java 2.10.0 add a new ElementSelectors.byNameAndAllAttributes variant that filters attributes before deciding whether elements can be compared. Inspired by Issue https://redirect.github.com/xmlunit/xmlunit/issues/259";>#259 By default the TransformerFactorys created will now try to disable extension functions. If you need extension functions for your transformations you may want to pass in your own instance of TransformerFactory and TransformerFactoryConfigurer may help with that. Inspired by Issue https://redirect.github.com/xmlunit/xmlunit/issues/264";>#264 JAXPXPathEngine will now try to disable the execution of extension functions by default but uses XPathFactory#setProperty which is not available prior to Java 18. You may want to enable secure processing on an XPathFactory instance you pass to JAXPXPathEngine instead - and XPathFactoryConfigurer may help with that. Changelog Sourced from https://github.com/xmlunit/xmlunit/blob/main/RELEASE_NOTES.md";>org.xmlunit:xmlunit-matchers's changelog. XMLUnit for Java 2.10.0 - /Released 2024-04-28/ add a new ElementSelectors.byNameAndAllAttributes variant that filters attributes before deciding whether elements can be compared. Inspired by Issue https://redirect.github.com/xmlunit/xmlunit/issues/259";>#259 By default the TransformerFactorys created will now try to disable extension functions. If you need extension functions for your transformations you may want to pass in your own instance of TransformerFactory and TransformerFactoryConfigurer may help with that. Inspired by Issue https://redirect.github.com/xmlunit/xmlunit/issues/264";>#264 This is tracked as https://github.com/xmlunit/xmlunit/security/advisories/GHSA-chfm-68vv-pvw5";>CVE-2024-31573. JAXPXPathEngine will now try to disable the execution of extension functions by default but uses XPathFactory#setProperty which is not available prior to Java 18. You may want to enable secure processing on an XPathFactory instance you pass to JAXPXPathEngine instead - and XPathFactoryConfigurer may help with that. Commits https://github.com/xmlunit/xmlunit/commit/33a5d6a28712878fc1355802571aab074d2145c1";>33a5d6a fix release number https://github.com/xmlunit/xmlunit/commit/eceec4ab6f1edce3138e32a12bf3d2e1755ba73b";>eceec4a javadocs https://github.com/xmlunit/xmlunit/commit/75828fdc6952da5d8e4ae3ef509d15cfb8f2b728";>75828fd Create SECURITY.md https://github.com/xmlunit/xmlunit/commit/dcaafe9174e69d18c9bcf27b9a40862f3bab360a";>dcaafe9 record extension function changes https://github.com/xmlunit/xmlunit/commit/611f6beb4dbce136d4ef608239695b07d7bd7006";>611f6be try to disable extension functions for XPaths https://github.com/xmlunit/xmlunit/commit/b81d48b71dfd2868bdfc30a3e17ff973f32bc15b";>b81d48b disable XSLT extension functions by default, add more configurers https://github.com/xmlunit/xmlunit/commit/ba149098c97c9c845a0877c905d6b9d84e6568d0";>ba14909 XMLUnit 1.x is no longer maintained https://github.com/xmlunit/xmlunit/commit/cd6731e34ab7f6dbe0c7cf6b22c85af16ac3ff8e";>cd6731e this is going to be a feature release, not a bugfix release https://github.com/xmlunit/xmlunit/commit/c47d390d36d81708b9f3ebb196a6c7391198d6c1";>c47d390 record last changes https://github.com/xmlunit/xmlunit/commit/514191511f2ade5078a4fea02e37d0d281368e78";>5141915 add byNameAndAllAttributes that uses an attrbute filter Additional commits viewable in https://github.com/xmlunit/xmlunit/compare/v2.9.1...v2.10.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@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 - `@depen
[PR] Bump org.apache.maven.shared:maven-script-interpreter from 1.2 to 1.6 [maven-archetype]
dependabot[bot] opened a new pull request, #199: URL: https://github.com/apache/maven-archetype/pull/199 Bumps [org.apache.maven.shared:maven-script-interpreter](https://github.com/apache/maven-script-interpreter) from 1.2 to 1.6. Release notes Sourced from https://github.com/apache/maven-script-interpreter/releases";>org.apache.maven.shared:maven-script-interpreter's releases. 1.6 https://issues.apache.org/jira/browse/MSHARED-1386";>[MSHARED-1386] - Manage context ClassLoader for current thread (https://redirect.github.com/apache/maven-script-interpreter/pull/121";>#121) https://github.com/slawekjaranowski";>@slawekjaranowski 📦 Dependency updates https://issues.apache.org/jira/browse/MSHARED-1385";>[MSHARED-1385] - Bump org.apache.groovy:groovy from 4.0.20 to 4.0.21 (https://redirect.github.com/apache/maven-script-interpreter/pull/119";>#119) https://github.com/dependabot";>@dependabot https://issues.apache.org/jira/browse/MSHARED-1383";>[MSHARED-1383] - Bump org.apache.maven.shared:maven-shared-components from 41 to 42 (https://redirect.github.com/apache/maven-script-interpreter/pull/120";>#120) https://github.com/dependabot";>@dependabot https://issues.apache.org/jira/browse/MSHARED-1384";>[MSHARED-1384] - Bump commons-io:commons-io from 2.16.0 to 2.16.1 (https://redirect.github.com/apache/maven-script-interpreter/pull/118";>#118) https://github.com/dependabot";>@dependabot 1.5 🚀 New features and improvements https://issues.apache.org/jira/browse/MSHARED-1368";>[MSHARED-1368] - Synchronize interpreter execution (https://redirect.github.com/apache/maven-script-interpreter/pull/115";>#115) https://github.com/slawekjaranowski";>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-1359";>[MSHARED-1359] - Use child first classloader in BeanShellScriptInterpreter (https://redirect.github.com/apache/maven-script-interpreter/pull/114";>#114) https://github.com/slawekjaranowski";>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-1359";>[MSHARED-1359] - Optimize classloader in BeanShellScriptInterpreter (https://redirect.github.com/apache/maven-script-interpreter/pull/112";>#112) https://github.com/slawekjaranowski";>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-1359";>[MSHARED-1359] - Allow reuse the same classloader for multiple script executions (https://redirect.github.com/apache/maven-script-interpreter/pull/109";>#109) https://github.com/slawekjaranowski";>@slawekjaranowski 📦 Dependency updates https://issues.apache.org/jira/browse/MSHARED-1370";>[MSHARED-1370] - Bump commons-io:commons-io from 2.11.0 to 2.16.0 (https://redirect.github.com/apache/maven-script-interpreter/pull/113";>#113) https://github.com/dependabot";>@dependabot Bump org.apache.groovy:groovy from 4.0.18 to 4.0.20 (https://redirect.github.com/apache/maven-script-interpreter/pull/108";>#108) https://github.com/dependabot";>@dependabot Bump apache/maven-gh-actions-shared from 3 to 4 (https://redirect.github.com/apache/maven-script-interpreter/pull/107";>#107) https://github.com/dependabot";>@dependabot Bump org.junit:junit-bom from 5.10.1 to 5.10.2 (https://redirect.github.com/apache/maven-script-interpreter/pull/105";>#105) https://github.com/dependabot";>@dependabot Bump org.apache.groovy:groovy from 4.0.17 to 4.0.18 (https://redirect.github.com/apache/maven-script-interpreter/pull/104";>#104) https://github.com/dependabot";>@dependabot Bump org.apache.groovy:groovy from 4.0.6 to 4.0.17 (https://redirect.github.com/apache/maven-script-interpreter/pull/102";>#102) https://github.com/dependabot";>@dependabot https://issues.apache.org/jira/browse/MSHARED-1350";>[MSHARED-1350] - Upgrade parent POM to version 41 (https://redirect.github.com/apache/maven-script-interpreter/pull/103";>#103) https://github.com/slachiewicz";>@slachiewicz Bump org.junit:junit-bom from 5.10.0 to 5.10.1 (https://redirect.github.com/apache/maven-script-interpreter/pull/99";>#99) https://github.com/dependabot";>@dependabot Bump org.junit:junit-bom from 5.9.2 to 5.10.0 (https://redirect.github.com/apache/maven-script-interpreter/pull/98";>#98) https://github.com/dependabot";>@dependabot Bump junit-bom from 5.9.1 to 5.9.2 (https://redirect.github.com/apache/maven-script-interpreter/pull/90";>#90) https://github.com/dependabot";>@dependabot Bump apache/maven-gh-actions-shared from 2 to 3 (https://redirect.github.com/apache/maven-script-interpreter/pull/93";>#93) https://github.com/dependabot";>@dependabot 👻 Maintenance https://issues.apache.org/jira/browse/MSHARED-1378";>[MSHARED-1378] - Cleanup of test code (https://redirect.github.com/apache/maven-script-interpreter/pull/117";>#117) https://github.com/slawekjaranowski";>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-1371";>[MSHARED-1371] - Refresh download page (htt
[PR] Bump com.ibm.icu:icu4j from 74.2 to 75.1 [maven-archetype]
dependabot[bot] opened a new pull request, #201: URL: https://github.com/apache/maven-archetype/pull/201 Bumps [com.ibm.icu:icu4j](https://github.com/unicode-org/icu) from 74.2 to 75.1. Release notes Sourced from https://github.com/unicode-org/icu/releases";>com.ibm.icu:icu4j's releases. ICU 75.1 Unicode® ICU 75 updates to https://cldr.unicode.org/index/downloads/cldr-45";>CLDR 45 (https://blog.unicode.org/2024/04/unicode-cldr-v45-beta-available-for.html";>beta blog) locale data with new locales and various additions and corrections. C++ code now requires C++17 and is being made more robust. The CLDR MessageFormat 2.0 specification is now in https://github.com/unicode-org/message-format-wg?tab=readme-ov-file#messageformat-2-technical-preview";>technology preview, together with a corresponding update of the ICU4J (Java) tech preview and a new ICU4C (C++) tech preview. For details, please see https://icu.unicode.org/download/75";>https://icu.unicode.org/download/75. ICU 75 RC We are pleased to announce the release candidate for Unicode® ICU 75. It updates to https://cldr.unicode.org/index/downloads/cldr-45";>CLDR 45 (https://blog.unicode.org/2024/03/unicode-cldr-v45-alpha-available-for.html";>alpha blog) locale data with new locales and various additions and corrections. C++ code now requires C++17 and is being made more robust. The CLDR MessageFormat 2.0 specification is now in https://github.com/unicode-org/message-format-wg?tab=readme-ov-file#messageformat-2-technical-preview";>technology preview, together with a corresponding update of the ICU4J (Java) tech preview and a new ICU4C (C++) tech preview. For details, please see https://icu.unicode.org/download/75";>https://icu.unicode.org/download/75. Please test this release candidate on your platforms and report bugs and regressions by Monday, 2024-apr-15, via the https://icu.unicode.org/contacts";>icu-support mailing list, and/or please https://icu.unicode.org/bugs";>find/submit error reports. Please do not use this release candidate in production. The preliminary API reference documents are published on https://unicode-org.github.io/icu-docs/";>unicode-org.github.io/icu-docs/ – follow the “Dev” links there. Commits See full diff in https://github.com/unicode-org/icu/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 options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump maven.resolver.version from 2.0.0-alpha-11 to 2.0.0 [maven-mvnd]
dependabot[bot] opened a new pull request, #1051: URL: https://github.com/apache/maven-mvnd/pull/1051 Bumps `maven.resolver.version` from 2.0.0-alpha-11 to 2.0.0. Updates `org.apache.maven.resolver:maven-resolver-api` from 2.0.0-alpha-11 to 2.0.0 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721";>Release Notes - Maven Resolver - Version 2.0.0 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/be148b8952b18f6c1e5245f66b554440676fb6dc";>be148b8 [maven-release-plugin] prepare release maven-resolver-2.0.0 https://github.com/apache/maven-resolver/commit/19a3c52c905dbb9686948e6f8ce73db404defdd8";>19a3c52 Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/525";>#525) https://github.com/apache/maven-resolver/commit/eb170c3a17919449fc1dc182b30daacc11dffefa";>eb170c3 [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/909330cc277f501e9e3aea80f8d5af2832d87e91";>909330c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/522";>#522) https://github.com/apache/maven-resolver/commit/2c76efa494f868de72f7fe47fc88bed0023cab0b";>2c76efa [MRESOLVER-575] Bump org.redisson:redisson from 3.31.0 to 3.32.0 (https://redirect.github.com/apache/maven-resolver/issues/519";>#519) https://github.com/apache/maven-resolver/commit/a65450f2a4509fe289c10b2a7cf6a7f76ff500c2";>a65450f [MRESOLVER-571] Fix usage of '-noimport' directive on exports https://github.com/apache/maven-resolver/commit/d4bd9917a1eb7f76bad89fa35969b76deb4e89d9";>d4bd991 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/d0edd7942f7af7732bccf6a7e68d0321906c6379";>d0edd79 [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/8266e6c320a7cf4deed3deb253ff4fd506d1d8f2";>8266e6c [MRESOLVER-27] Turn resolver api, spi and utils into Java 9 modules (https://redirect.github.com/apache/maven-resolver/issues/516";>#516) https://github.com/apache/maven-resolver/commit/2393568ca1722f15dbb0133d745a36dd6d583342";>2393568 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-2.0.0-alpha-11...maven-resolver-2.0.0";>compare view Updates `org.apache.maven.resolver:maven-resolver-impl` from 2.0.0-alpha-11 to 2.0.0 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-impl's releases. 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721";>Release Notes - Maven Resolver - Version 2.0.0 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/be148b8952b18f6c1e5245f66b554440676fb6dc";>be148b8 [maven-release-plugin] prepare release maven-resolver-2.0.0 https://github.com/apache/maven-resolver/commit/19a3c52c905dbb9686948e6f8ce73db404defdd8";>19a3c52 Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/525";>#525) https://github.com/apache/maven-resolver/commit/eb170c3a17919449fc1dc182b30daacc11dffefa";>eb170c3 [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/909330cc277f501e9e3aea80f8d5af2832d87e91";>909330c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/522";>#522) https://github.com/apache/maven-resolver/commit/2c76efa494f868de72f7fe47fc88bed0023cab0b";>2c76efa [MRESOLVER-575] Bump org.redisson:redisson from 3.31.0 to 3.32.0 (https://redirect.github.com/apache/maven-resolver/issues/519";>#519) https://github.com/apache/maven-resolver/commit/a65450f2a4509fe289c10b2a7cf6a7f76ff500c2";>a65450f [MRESOLVER-571] Fix usage of '-noimport' directive on exports https://github.com/apache/maven-resolver/commit/d4bd9917a1eb7f76bad89fa35969b76deb4e89d9";>d4bd991 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/d0edd7942f7af7732bccf6a7e68d0321906c6379";>d0edd79 [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/8266e6c320a7cf4deed3deb253ff4fd506d1d8f2";>8266e6c [MRESOLVER-27] Turn resolver api, spi and utils into Java 9 modules (https://redirect.github.com/apache/maven-resolver/issues/516";>#516) https://github.com/apache/maven-resolver/commit/2393568ca1722f15dbb0133d745a36dd6d583342";>2393568 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata
Re: [PR] Bump resolverVersion from 1.9.18 to 1.9.20 [maven-gpg-plugin]
dependabot[bot] commented on PR #101: URL: https://github.com/apache/maven-gpg-plugin/pull/101#issuecomment-2212976694 Superseded by #106. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump resolverVersion from 1.9.18 to 1.9.20 [maven-gpg-plugin]
dependabot[bot] closed pull request #101: Bump resolverVersion from 1.9.18 to 1.9.20 URL: https://github.com/apache/maven-gpg-plugin/pull/101 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump resolverVersion from 1.9.18 to 2.0.0 [maven-gpg-plugin]
dependabot[bot] opened a new pull request, #106: URL: https://github.com/apache/maven-gpg-plugin/pull/106 Bumps `resolverVersion` from 1.9.18 to 2.0.0. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.9.18 to 2.0.0 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721";>Release Notes - Maven Resolver - Version 2.0.0 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/be148b8952b18f6c1e5245f66b554440676fb6dc";>be148b8 [maven-release-plugin] prepare release maven-resolver-2.0.0 https://github.com/apache/maven-resolver/commit/19a3c52c905dbb9686948e6f8ce73db404defdd8";>19a3c52 Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/525";>#525) https://github.com/apache/maven-resolver/commit/eb170c3a17919449fc1dc182b30daacc11dffefa";>eb170c3 [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/909330cc277f501e9e3aea80f8d5af2832d87e91";>909330c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/522";>#522) https://github.com/apache/maven-resolver/commit/2c76efa494f868de72f7fe47fc88bed0023cab0b";>2c76efa [MRESOLVER-575] Bump org.redisson:redisson from 3.31.0 to 3.32.0 (https://redirect.github.com/apache/maven-resolver/issues/519";>#519) https://github.com/apache/maven-resolver/commit/a65450f2a4509fe289c10b2a7cf6a7f76ff500c2";>a65450f [MRESOLVER-571] Fix usage of '-noimport' directive on exports https://github.com/apache/maven-resolver/commit/d4bd9917a1eb7f76bad89fa35969b76deb4e89d9";>d4bd991 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/d0edd7942f7af7732bccf6a7e68d0321906c6379";>d0edd79 [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/8266e6c320a7cf4deed3deb253ff4fd506d1d8f2";>8266e6c [MRESOLVER-27] Turn resolver api, spi and utils into Java 9 modules (https://redirect.github.com/apache/maven-resolver/issues/516";>#516) https://github.com/apache/maven-resolver/commit/2393568ca1722f15dbb0133d745a36dd6d583342";>2393568 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.18...maven-resolver-2.0.0";>compare view Updates `org.apache.maven.resolver:maven-resolver-util` from 1.9.18 to 2.0.0 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-util's releases. 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721";>Release Notes - Maven Resolver - Version 2.0.0 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/be148b8952b18f6c1e5245f66b554440676fb6dc";>be148b8 [maven-release-plugin] prepare release maven-resolver-2.0.0 https://github.com/apache/maven-resolver/commit/19a3c52c905dbb9686948e6f8ce73db404defdd8";>19a3c52 Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/525";>#525) https://github.com/apache/maven-resolver/commit/eb170c3a17919449fc1dc182b30daacc11dffefa";>eb170c3 [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/909330cc277f501e9e3aea80f8d5af2832d87e91";>909330c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/522";>#522) https://github.com/apache/maven-resolver/commit/2c76efa494f868de72f7fe47fc88bed0023cab0b";>2c76efa [MRESOLVER-575] Bump org.redisson:redisson from 3.31.0 to 3.32.0 (https://redirect.github.com/apache/maven-resolver/issues/519";>#519) https://github.com/apache/maven-resolver/commit/a65450f2a4509fe289c10b2a7cf6a7f76ff500c2";>a65450f [MRESOLVER-571] Fix usage of '-noimport' directive on exports https://github.com/apache/maven-resolver/commit/d4bd9917a1eb7f76bad89fa35969b76deb4e89d9";>d4bd991 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/d0edd7942f7af7732bccf6a7e68d0321906c6379";>d0edd79 [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/8266e6c320a7cf4deed3deb253ff4fd506d1d8f2";>8266e6c [MRESOLVER-27] Turn resolver api, spi and utils into Java 9 modules (https://redirect.github.com/apache/maven-resolver/issues/516";>#516) https://github.com/apache/maven-resolver/commit/2393568ca1722f15dbb0133d745a36dd6d583342";>2393568 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata Additional commits viewable in htt
[PR] Bump org.apache.maven.resolver:maven-resolver-api from 1.9.20 to 2.0.0 [maven-wrapper]
dependabot[bot] opened a new pull request, #148: URL: https://github.com/apache/maven-wrapper/pull/148 Bumps [org.apache.maven.resolver:maven-resolver-api](https://github.com/apache/maven-resolver) from 1.9.20 to 2.0.0. Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721";>Release Notes - Maven Resolver - Version 2.0.0 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/be148b8952b18f6c1e5245f66b554440676fb6dc";>be148b8 [maven-release-plugin] prepare release maven-resolver-2.0.0 https://github.com/apache/maven-resolver/commit/19a3c52c905dbb9686948e6f8ce73db404defdd8";>19a3c52 Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/525";>#525) https://github.com/apache/maven-resolver/commit/eb170c3a17919449fc1dc182b30daacc11dffefa";>eb170c3 [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/909330cc277f501e9e3aea80f8d5af2832d87e91";>909330c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/522";>#522) https://github.com/apache/maven-resolver/commit/2c76efa494f868de72f7fe47fc88bed0023cab0b";>2c76efa [MRESOLVER-575] Bump org.redisson:redisson from 3.31.0 to 3.32.0 (https://redirect.github.com/apache/maven-resolver/issues/519";>#519) https://github.com/apache/maven-resolver/commit/a65450f2a4509fe289c10b2a7cf6a7f76ff500c2";>a65450f [MRESOLVER-571] Fix usage of '-noimport' directive on exports https://github.com/apache/maven-resolver/commit/d4bd9917a1eb7f76bad89fa35969b76deb4e89d9";>d4bd991 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/d0edd7942f7af7732bccf6a7e68d0321906c6379";>d0edd79 [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/8266e6c320a7cf4deed3deb253ff4fd506d1d8f2";>8266e6c [MRESOLVER-27] Turn resolver api, spi and utils into Java 9 modules (https://redirect.github.com/apache/maven-resolver/issues/516";>#516) https://github.com/apache/maven-resolver/commit/2393568ca1722f15dbb0133d745a36dd6d583342";>2393568 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.20...maven-resolver-2.0.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump resolverVersion from 2.0.0-alpha-11 to 2.0.0 [maven]
dependabot[bot] opened a new pull request, #1600: URL: https://github.com/apache/maven/pull/1600 Bumps `resolverVersion` from 2.0.0-alpha-11 to 2.0.0. Updates `org.apache.maven.resolver:maven-resolver-api` from 2.0.0-alpha-11 to 2.0.0 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721";>Release Notes - Maven Resolver - Version 2.0.0 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/be148b8952b18f6c1e5245f66b554440676fb6dc";>be148b8 [maven-release-plugin] prepare release maven-resolver-2.0.0 https://github.com/apache/maven-resolver/commit/19a3c52c905dbb9686948e6f8ce73db404defdd8";>19a3c52 Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/525";>#525) https://github.com/apache/maven-resolver/commit/eb170c3a17919449fc1dc182b30daacc11dffefa";>eb170c3 [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/909330cc277f501e9e3aea80f8d5af2832d87e91";>909330c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/522";>#522) https://github.com/apache/maven-resolver/commit/2c76efa494f868de72f7fe47fc88bed0023cab0b";>2c76efa [MRESOLVER-575] Bump org.redisson:redisson from 3.31.0 to 3.32.0 (https://redirect.github.com/apache/maven-resolver/issues/519";>#519) https://github.com/apache/maven-resolver/commit/a65450f2a4509fe289c10b2a7cf6a7f76ff500c2";>a65450f [MRESOLVER-571] Fix usage of '-noimport' directive on exports https://github.com/apache/maven-resolver/commit/d4bd9917a1eb7f76bad89fa35969b76deb4e89d9";>d4bd991 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/d0edd7942f7af7732bccf6a7e68d0321906c6379";>d0edd79 [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/8266e6c320a7cf4deed3deb253ff4fd506d1d8f2";>8266e6c [MRESOLVER-27] Turn resolver api, spi and utils into Java 9 modules (https://redirect.github.com/apache/maven-resolver/issues/516";>#516) https://github.com/apache/maven-resolver/commit/2393568ca1722f15dbb0133d745a36dd6d583342";>2393568 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-2.0.0-alpha-11...maven-resolver-2.0.0";>compare view Updates `org.apache.maven.resolver:maven-resolver-spi` from 2.0.0-alpha-11 to 2.0.0 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-spi's releases. 2.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721";>Release Notes - Maven Resolver - Version 2.0.0 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/be148b8952b18f6c1e5245f66b554440676fb6dc";>be148b8 [maven-release-plugin] prepare release maven-resolver-2.0.0 https://github.com/apache/maven-resolver/commit/19a3c52c905dbb9686948e6f8ce73db404defdd8";>19a3c52 Tame bnd plugin warnings (https://redirect.github.com/apache/maven-resolver/issues/525";>#525) https://github.com/apache/maven-resolver/commit/eb170c3a17919449fc1dc182b30daacc11dffefa";>eb170c3 [MRESOLVER-577] Update to Maven 3.9.8 https://github.com/apache/maven-resolver/commit/909330cc277f501e9e3aea80f8d5af2832d87e91";>909330c [MRESOLVER-574] Use standard cookie spec (https://redirect.github.com/apache/maven-resolver/issues/522";>#522) https://github.com/apache/maven-resolver/commit/2c76efa494f868de72f7fe47fc88bed0023cab0b";>2c76efa [MRESOLVER-575] Bump org.redisson:redisson from 3.31.0 to 3.32.0 (https://redirect.github.com/apache/maven-resolver/issues/519";>#519) https://github.com/apache/maven-resolver/commit/a65450f2a4509fe289c10b2a7cf6a7f76ff500c2";>a65450f [MRESOLVER-571] Fix usage of '-noimport' directive on exports https://github.com/apache/maven-resolver/commit/d4bd9917a1eb7f76bad89fa35969b76deb4e89d9";>d4bd991 [MRESOLVER-571] Import o.e.aether packages with the exact same version https://github.com/apache/maven-resolver/commit/d0edd7942f7af7732bccf6a7e68d0321906c6379";>d0edd79 [MRESOLVER-572] Export internal packages in OSGi metadata as x-internal https://github.com/apache/maven-resolver/commit/8266e6c320a7cf4deed3deb253ff4fd506d1d8f2";>8266e6c [MRESOLVER-27] Turn resolver api, spi and utils into Java 9 modules (https://redirect.github.com/apache/maven-resolver/issues/516";>#516) https://github.com/apache/maven-resolver/commit/2393568ca1722f15dbb0133d745a36dd6d583342";>2393568 [MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata Additional
[jira] [Commented] (MJARSIGNER-76) Print names of processed files
[
https://issues.apache.org/jira/browse/MJARSIGNER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863636#comment-17863636
]
Elliotte Rusty Harold commented on MJARSIGNER-76:
-
"which cases are you thinking of where this output is not useful? " Essentially
all of them. If I use this plugin I want it to sign the files. I don't want to
read through pages of logs and do, well I don't even know what I would do with
this output. It's noise. How many times do you think this plugin runs every
day? What percentage of those do you think anyone will look at these messages
and do something because of them?
> Print names of processed files
> --
>
> Key: MJARSIGNER-76
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-76
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Marcono1234
>Priority: Minor
>
> h2. Problem
> Currently the plugin just prints the number of processed artifacts once it is
> done, for example:
> {quote}
> 2 archive(s) processed
> {quote}
> This has these disadvantages:
> - It is not immediately obvious if the intended file has been signed (e.g.
> when using wildcards)
> - If the number is higher than expected, it is not obvious which additional
> files were signed redundantly
> In both cases it is necessary to manually inspect the artifacts of the
> project and check if they have been signed (or use {{jarsigner}} to verify
> them).
> h2. Improvement
> By default the plugin should print the file names of the signed artifacts.
> This information is already available in {{AbstractJarsignerMojo#execute}},
> but currently only {{archives.size()}} is logged.
> - Ideally each file should be logged in a separate line to be easier to read.
> - The relative file path (and not only the file name) should be logged.
> Otherwise there might be confusion if the same file exists in multiple
> directories, e.g. if it is copied by another plugin during the build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8155) Reword "This project has been banned from the build due to previous failures."
[ https://issues.apache.org/jira/browse/MNG-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863635#comment-17863635 ] ASF GitHub Bot commented on MNG-8155: - elharo merged PR #1599: URL: https://github.com/apache/maven/pull/1599 > Reword "This project has been banned from the build due to previous failures." > -- > > Key: MNG-8155 > URL: https://issues.apache.org/jira/browse/MNG-8155 > Project: Maven > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Saw this error message. This confused me and I did not initially know what it > meant. In fact, I guessed wrong. > [INFO] Skipping presto-prism-plugin > [INFO] This project has been banned from the build due to previous failures. > I suggest rephrasing along the lines of "Module name was not built because > the module module-name it depends on failed to build." -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8155] Improve not built error message [maven]
elharo merged PR #1599: URL: https://github.com/apache/maven/pull/1599 -- 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-391) Log what developers care about and not what they don't
[ https://issues.apache.org/jira/browse/MPMD-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863634#comment-17863634 ] ASF GitHub Bot commented on MPMD-391: - michael-o commented on PR #156: URL: https://github.com/apache/maven-pmd-plugin/pull/156#issuecomment-2212595450 Note: Some issues mentioned in the JIRA ticket are out of control of this plugin therefore there are out of scope here. > Log what developers care about and not what they don't > -- > > Key: MPMD-391 > URL: https://issues.apache.org/jira/browse/MPMD-391 > Project: Maven PMD Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Assignee: Michael Osipov >Priority: Major > Fix For: 3.24.0 > > > Here's output from a recent PMD plugin run that failed: > [INFO] >>> maven-pmd-plugin:3.21.2:check (default-cli) > :pmd @ commons-io >>> > [INFO] > [INFO] --- maven-pmd-plugin:3.21.2:pmd (pmd) @ commons-io --- > [INFO] PMD version: 6.55.0 > [INFO] Rendering content with > org.apache.maven.skins:maven-default-skin:jar:1.3 skin. > [INFO] > [INFO] <<< maven-pmd-plugin:3.21.2:check (default-cli) < :pmd @ commons-io <<< > [INFO] > [INFO] > [INFO] --- maven-pmd-plugin:3.21.2:check (default-cli) @ commons-io --- > [INFO] PMD version: 6.55.0 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 05:22 min > [INFO] Finished at: 2024-01-14T14:11:30Z > [INFO] > > Error: Failed to execute goal > org.apache.maven.plugins:maven-pmd-plugin:3.21.2:check (default-cli) on > project commons-io: You have 1 PMD violation. For more details see: > /home/runner/work/commons-io/commons-io/target/pmd.xml -> [Help 1] > Error: > Error: To see the full stack trace of the errors, re-run Maven with the -e > switch. > Error: Re-run Maven using the -X switch to enable full debug logging. > Error: > Error: For more information about the errors and possible solutions, please > read the following articles: > Error: [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > Error: Process completed with exit code 1. > Things I don't care about that are printed: > * PMD version > * Doxia skin > * Blank lines > * Total time > * Timestamp when it finished > * Generic information about Mojo failures > * Exit code from Mojo > The one thing I care about: > * The actual error that caused the failure > Everything in the first list can be hidden in some random log file no one > will ever look at. Everything in the second list should be front and center. > Instead Maven gets this exactly backwards, -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPMD-391] Log what developers care about and not what they don't [maven-pmd-plugin]
michael-o commented on PR #156: URL: https://github.com/apache/maven-pmd-plugin/pull/156#issuecomment-2212595450 Note: Some issues mentioned in the JIRA ticket are out of control of this plugin therefore there are out of scope here. -- 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-400) Upgrade to PMD 7.3.0
[ https://issues.apache.org/jira/browse/MPMD-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPMD-400. --- Resolution: Fixed Fixed with [7a3b2c2d516678f3e5ed6ec0c0c9f6298c5b9977|https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=7a3b2c2d516678f3e5ed6ec0c0c9f6298c5b9977]. > Upgrade to PMD 7.3.0 > > > Key: MPMD-400 > URL: https://issues.apache.org/jira/browse/MPMD-400 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.24.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-400) Upgrade to PMD 7.3.0
[ https://issues.apache.org/jira/browse/MPMD-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863633#comment-17863633 ] ASF GitHub Bot commented on MPMD-400: - michael-o merged PR #157: URL: https://github.com/apache/maven-pmd-plugin/pull/157 > Upgrade to PMD 7.3.0 > > > Key: MPMD-400 > URL: https://issues.apache.org/jira/browse/MPMD-400 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.24.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-400) Upgrade to PMD 7.3.0
[ https://issues.apache.org/jira/browse/MPMD-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863632#comment-17863632 ] ASF GitHub Bot commented on MPMD-400: - michael-o closed pull request #157: [MPMD-400] Upgrade to PMD 7.3.0 URL: https://github.com/apache/maven-pmd-plugin/pull/157 > Upgrade to PMD 7.3.0 > > > Key: MPMD-400 > URL: https://issues.apache.org/jira/browse/MPMD-400 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.24.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPMD-400] Upgrade to PMD 7.3.0 [maven-pmd-plugin]
michael-o merged PR #157: URL: https://github.com/apache/maven-pmd-plugin/pull/157 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MPMD-400] Upgrade to PMD 7.3.0 [maven-pmd-plugin]
michael-o closed pull request #157: [MPMD-400] Upgrade to PMD 7.3.0 URL: https://github.com/apache/maven-pmd-plugin/pull/157 -- 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-383) PMD should fail when there is a processing error
[
https://issues.apache.org/jira/browse/MPMD-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863630#comment-17863630
]
Michael Osipov commented on MPMD-383:
-
I consider the issue as invalid because you ran the `pmd` goal which is a
reporting goal. I do not expect a reporting goal to fail here. You should
verify this again with a check goal.
> PMD should fail when there is a processing error
>
>
> Key: MPMD-383
> URL: https://issues.apache.org/jira/browse/MPMD-383
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Components: PMD
>Affects Versions: 3.21.0
>Reporter: Thomas Nikolay
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: image-2023-07-28-13-34-28-717.png
>
>
> We had the case that PMD can't process some processing error but the build
> does not fail.
>
> {noformat}
> [2023-07-28T10:59:44.102Z] [INFO] --- maven-pmd-plugin:3.20.0:pmd (pmd) @
> mod-config-client-cst ---
> [2023-07-28T10:59:44.692Z] [INFO] PMD version: 6.53.0
> [2023-07-28T10:59:45.672Z] [WARNING] Removed misconfigured rule:
> GK-SAP-ApacheLoggerDeniedRule cause: missing value
> [2023-07-28T10:59:45.672Z] [WARNING] There are 3 PMD processing errors:
> [2023-07-28T10:59:45.672Z] [WARNING]
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/cst/client/AppInfoProviderImpl_CST_Test.java:
> PMDException: Error while processing
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/cst/client/AppInfoProviderImpl_CST_Test.java
> [2023-07-28T10:59:45.948Z]
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST_Test.java:
> PMDException: Error while processing
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST_Test.java
> [2023-07-28T10:59:45.948Z]
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/main/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST.java:
> PMDException: Error while processing
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/main/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST.java
> [2023-07-28T10:59:45.948Z] [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [2023-07-28T10:59:46.210Z] [INFO]
> [2023-07-28T10:59:46.210Z] [INFO] <<< maven-pmd-plugin:3.20.0:check
> (pmd-check) < :pmd @ mod-config-client-cst <<<
> {noformat}
>
> My expectation would be that the build failed when there a processing errors.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-400) Upgrade to PMD 7.3.0
[ https://issues.apache.org/jira/browse/MPMD-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863628#comment-17863628 ] ASF GitHub Bot commented on MPMD-400: - michael-o opened a new pull request, #157: URL: https://github.com/apache/maven-pmd-plugin/pull/157 This closes #157 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/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. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] 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. - [ ] 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). > Upgrade to PMD 7.3.0 > > > Key: MPMD-400 > URL: https://issues.apache.org/jira/browse/MPMD-400 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.24.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] [MPMD-400] Upgrade to PMD 7.3.0 [maven-pmd-plugin]
michael-o opened a new pull request, #157: URL: https://github.com/apache/maven-pmd-plugin/pull/157 This closes #157 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/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. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] 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. - [ ] 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] [Created] (MPMD-400) Upgrade to PMD 7.3.0
Michael Osipov created MPMD-400: --- Summary: Upgrade to PMD 7.3.0 Key: MPMD-400 URL: https://issues.apache.org/jira/browse/MPMD-400 Project: Maven PMD Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.24.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-391) Log what developers care about and not what they don't
[ https://issues.apache.org/jira/browse/MPMD-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863627#comment-17863627 ] ASF GitHub Bot commented on MPMD-391: - michael-o opened a new pull request, #156: URL: https://github.com/apache/maven-pmd-plugin/pull/156 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/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. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] 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. - [ ] 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). > Log what developers care about and not what they don't > -- > > Key: MPMD-391 > URL: https://issues.apache.org/jira/browse/MPMD-391 > Project: Maven PMD Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Assignee: Michael Osipov >Priority: Major > Fix For: 3.23.1 > > > Here's output from a recent PMD plugin run that failed: > [INFO] >>> maven-pmd-plugin:3.21.2:check (default-cli) > :pmd @ commons-io >>> > [INFO] > [INFO] --- maven-pmd-plugin:3.21.2:pmd (pmd) @ commons-io --- > [INFO] PMD version: 6.55.0 > [INFO] Rendering content with > org.apache.maven.skins:maven-default-skin:jar:1.3 skin. > [INFO] > [INFO] <<< maven-pmd-plugin:3.21.2:check (default-cli) < :pmd @ commons-io <<< > [INFO] > [INFO] > [INFO] --- maven-pmd-plugin:3.21.2:check (default-cli) @ commons-io --- > [INFO] PMD version: 6.55.0 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 05:22 min > [INFO] Finished at: 2024-01-14T14:11:30Z > [INFO] > > Error: Failed to execute goal > org.apache.maven.plugins:maven-pmd-plugin:3.21.2:check (default-cli) on > project commons-io: You have 1 PMD violation. For more details see: > /home/runner/work/commons-io/commons-io/target/pmd.xml -> [Help 1] > Error: > Error: To see the full stack trace of the errors, re-run Maven with the -e > switch. > Error: Re-run Maven using the -X switch to enable full debug logging. > Error: > Error: For more information about the errors and possible solutions, please > read the following articles: > Error: [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > Error: Process completed with exit code 1. > Things I don't care about that are printed: > * PMD version > * Doxia skin > * Blank lines > * Total time > * Timestamp when it finished > * Generic information about Mojo failures > * Exit code from Mojo > The one thing I care about: > * The actual error that caused the failure > Everything in the first list can be hidden in some random log file no one > will ever look at. Everything in the second list should be front and center. > Instead Maven gets this exactly backwards, -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] [MPMD-391] Log what developers care about and not what they don't [maven-pmd-plugin]
michael-o opened a new pull request, #156: URL: https://github.com/apache/maven-pmd-plugin/pull/156 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/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. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] 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. - [ ] 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-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863624#comment-17863624
]
ASF GitHub Bot commented on MPMD-399:
-
michael-o merged PR #154:
URL: https://github.com/apache/maven-pmd-plugin/pull/154
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.23.1
>
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} directory
> and therefore no {{target/classes}} or {{target/test-classes}} directories
> are generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPMD-399.
---
Resolution: Fixed
Fixed with
[2a72cc86d5f25625059a2e7428038cb1841ac612|https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=2a72cc86d5f25625059a2e7428038cb1841ac612].
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.23.1
>
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} directory
> and therefore no {{target/classes}} or {{target/test-classes}} directories
> are generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-391) Log what developers care about and not what they don't
[ https://issues.apache.org/jira/browse/MPMD-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPMD-391: Fix Version/s: 3.23.1 > Log what developers care about and not what they don't > -- > > Key: MPMD-391 > URL: https://issues.apache.org/jira/browse/MPMD-391 > Project: Maven PMD Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Assignee: Michael Osipov >Priority: Major > Fix For: 3.23.1 > > > Here's output from a recent PMD plugin run that failed: > [INFO] >>> maven-pmd-plugin:3.21.2:check (default-cli) > :pmd @ commons-io >>> > [INFO] > [INFO] --- maven-pmd-plugin:3.21.2:pmd (pmd) @ commons-io --- > [INFO] PMD version: 6.55.0 > [INFO] Rendering content with > org.apache.maven.skins:maven-default-skin:jar:1.3 skin. > [INFO] > [INFO] <<< maven-pmd-plugin:3.21.2:check (default-cli) < :pmd @ commons-io <<< > [INFO] > [INFO] > [INFO] --- maven-pmd-plugin:3.21.2:check (default-cli) @ commons-io --- > [INFO] PMD version: 6.55.0 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 05:22 min > [INFO] Finished at: 2024-01-14T14:11:30Z > [INFO] > > Error: Failed to execute goal > org.apache.maven.plugins:maven-pmd-plugin:3.21.2:check (default-cli) on > project commons-io: You have 1 PMD violation. For more details see: > /home/runner/work/commons-io/commons-io/target/pmd.xml -> [Help 1] > Error: > Error: To see the full stack trace of the errors, re-run Maven with the -e > switch. > Error: Re-run Maven using the -X switch to enable full debug logging. > Error: > Error: For more information about the errors and possible solutions, please > read the following articles: > Error: [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > Error: Process completed with exit code 1. > Things I don't care about that are printed: > * PMD version > * Doxia skin > * Blank lines > * Total time > * Timestamp when it finished > * Generic information about Mojo failures > * Exit code from Mojo > The one thing I care about: > * The actual error that caused the failure > Everything in the first list can be hidden in some random log file no one > will ever look at. Everything in the second list should be front and center. > Instead Maven gets this exactly backwards, -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MPMD-391) Log what developers care about and not what they don't
[ https://issues.apache.org/jira/browse/MPMD-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPMD-391: --- Assignee: Michael Osipov > Log what developers care about and not what they don't > -- > > Key: MPMD-391 > URL: https://issues.apache.org/jira/browse/MPMD-391 > Project: Maven PMD Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Assignee: Michael Osipov >Priority: Major > > Here's output from a recent PMD plugin run that failed: > [INFO] >>> maven-pmd-plugin:3.21.2:check (default-cli) > :pmd @ commons-io >>> > [INFO] > [INFO] --- maven-pmd-plugin:3.21.2:pmd (pmd) @ commons-io --- > [INFO] PMD version: 6.55.0 > [INFO] Rendering content with > org.apache.maven.skins:maven-default-skin:jar:1.3 skin. > [INFO] > [INFO] <<< maven-pmd-plugin:3.21.2:check (default-cli) < :pmd @ commons-io <<< > [INFO] > [INFO] > [INFO] --- maven-pmd-plugin:3.21.2:check (default-cli) @ commons-io --- > [INFO] PMD version: 6.55.0 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 05:22 min > [INFO] Finished at: 2024-01-14T14:11:30Z > [INFO] > > Error: Failed to execute goal > org.apache.maven.plugins:maven-pmd-plugin:3.21.2:check (default-cli) on > project commons-io: You have 1 PMD violation. For more details see: > /home/runner/work/commons-io/commons-io/target/pmd.xml -> [Help 1] > Error: > Error: To see the full stack trace of the errors, re-run Maven with the -e > switch. > Error: Re-run Maven using the -X switch to enable full debug logging. > Error: > Error: For more information about the errors and possible solutions, please > read the following articles: > Error: [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > Error: Process completed with exit code 1. > Things I don't care about that are printed: > * PMD version > * Doxia skin > * Blank lines > * Total time > * Timestamp when it finished > * Generic information about Mojo failures > * Exit code from Mojo > The one thing I care about: > * The actual error that caused the failure > Everything in the first list can be hidden in some random log file no one > will ever look at. Everything in the second list should be front and center. > Instead Maven gets this exactly backwards, -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863623#comment-17863623
]
ASF GitHub Bot commented on MPMD-399:
-
michael-o closed pull request #154: [MPMD-399] Incorrect warning: The project X
does not seem to be compi…
URL: https://github.com/apache/maven-pmd-plugin/pull/154
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.23.1
>
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} directory
> and therefore no {{target/classes}} or {{target/test-classes}} directories
> are generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MPMD-399] Incorrect warning: The project X does not seem to be compi… [maven-pmd-plugin]
michael-o merged PR #154: URL: https://github.com/apache/maven-pmd-plugin/pull/154 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MPMD-399] Incorrect warning: The project X does not seem to be compi… [maven-pmd-plugin]
michael-o closed pull request #154: [MPMD-399] Incorrect warning: The project X does not seem to be compi… URL: https://github.com/apache/maven-pmd-plugin/pull/154 -- 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-273) Dependency jar with rules fails only with SNAPSHOT version
[
https://issues.apache.org/jira/browse/MPMD-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPMD-273.
---
Resolution: Incomplete
No reaction eversince.
> Dependency jar with rules fails only with SNAPSHOT version
> --
>
> Key: MPMD-273
> URL: https://issues.apache.org/jira/browse/MPMD-273
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.10.0
> Environment: Jenkins scripted build job calls Maven running on RHEL 7
> Linux build agents controlled by Jenkins 2.73. Java 8.
>Reporter: Lee Meador
>Priority: Major
>
> One build job creates a coding-standards jar containing PMD rulesets and I
> have run that build with and without SNAPSHOT for version 0.0.2. If I go to
> my Nexus GUI and search, I see the 0.0.2 version and about 8 SNAPSHOT
> versions with different dates and times. 0.0.2 is in the releases repo and
> 0.0.2-SNAPSHOT(s) are in the snapshots repo.
> I have settings.xml set to point to our the public Nexus 3 repository which
> proxies to Maven Central and several other repos both open source and
> internal to our company. The releases repo is included in public. The
> snapshot repo is not included in public, this proxy repo.
> This is the mirrorOf tag in settings.xml.
> {{ !nexus-snapshots,*}}
> For another build job, I have a tag in the pom pointing to our
> snapshot repo with snapshot enabled and releases NOT enabled. This tag is
> there to give it an id that works with the mirroring:
> {{ nexus-snapshots}}
> Other snapshot versions of things needed when compiling the code are found by
> maven.
> I configure the maven pmd plugin thusly:
> {quote}{{}}
> {{ org.apache.maven.plugins}}
> {{ maven-pmd-plugin}}
> {{ }}
> {{ }}
> {{ }}
> {{ check}}
> {{ }}
> {{ }}
> {{ }}
> {{ }}
> {{ utf-8}}
> {{ 100}}
> {{ 1.8}}
> {{ 3}}
> {{ true}}
> {{ }}
> {{ pmd-config2.xml}}
> {{ }}
> {{ }}
> {{ }}
> {{ }}
> {{ com.aa.crewtech.tools}}
> {{ coding-standards}}
> {{ ${coding-standards.version}}}
> {{ }}
> {{ }}
> {{ }}{quote}
> If I run my build and the property coding-standards.version has the value
> 0.0.2 everything works.
> If coding-standards.version has the value 0.0.2-SNAPSHOT it fails with this
> error:
> _ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd (pmd) on project
> SqlTool: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd failed: Plugin
> org.apache.maven.plugins:maven-pmd-plugin:3.10.0 or one of its dependencies
> could not be resolved: Could not find artifact
> com.my.company:coding-standards:jar:0.0.2-SNAPSHOT in nexus
> ([https://nexusread.mycompany.com/repository/public/|https://nexusread.aa.com/repository/OT-public/])
> -> [Help 1]_
> All these builds actually run in my Jenkins with all the code under source
> control and its all repeatable. SNAPSHOT version for the ruleset jar fails.
> Non-SNAPSHOT version works.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPMD-399:
Description:
PMD plugin is reporting the following warnings on in a multi-maven project:
"The project X does not seem to be compiled. PMD results might be inaccurate."
This is caused by the fact that not all modules have a
* {{src/main/java}} or
* {{src/test/java}} directory
and therefore no {{target/classes}} or {{target/test-classes}} directories are
generated.
The affected code that causes the problem can be found here:
[https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
h3. Reproduction example
* Create a maven multi-module project
* Leave {{src/main/java}} of one module empty
* Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
-DskipTests}}
→ (x) Warning is reported
h3. Possible fixes
* Make it possible to ignore this warning
* Do not warn when at least {{target/classes}} or {{target/test-classes}} is
present
was:
PMD plugin is reporting the following warnings on in a multi-maven project:
"The project X does not seem to be compiled. PMD results might be inaccurate."
This is caused by the fact that not all modules have a
* {{src/main/java}} or
* {{src/test/java}} folder
and therefore no {{target/classes}} or {{target/test-classes}} folders are
generated.
The affected code that causes the problem can be found here:
[https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
h3. Reproduction example
* Create a maven multi-module project
* Leave {{src/main/java}} of one module empty
* Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
-DskipTests}}
→ (x) Warning is reported
h3. Possible fixes
* Make it possible to ignore this warning
* Do not warn when at least {{target/classes}} or {{target/test-classes}} is
present
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.23.1
>
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} directory
> and therefore no {{target/classes}} or {{target/test-classes}} directories
> are generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPMD-399:
Fix Version/s: 3.23.1
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.23.1
>
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} folder
> and therefore no {{target/classes}} or {{target/test-classes}} folders are
> generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MPMD-399:
---
Assignee: Michael Osipov
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Assignee: Michael Osipov
>Priority: Major
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} folder
> and therefore no {{target/classes}} or {{target/test-classes}} folders are
> generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump org.codehaus.mojo:animal-sniffer-maven-plugin from 1.23 to 1.24 [maven-pmd-plugin]
michael-o merged PR #155: URL: https://github.com/apache/maven-pmd-plugin/pull/155 -- 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] (MJARSIGNER-76) Print names of processed files
[
https://issues.apache.org/jira/browse/MJARSIGNER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863618#comment-17863618
]
ASF GitHub Bot commented on MJARSIGNER-76:
--
Marcono1234 commented on PR #20:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/20#issuecomment-2212519982
@elharo, regarding your comment here and also your [comment on
JIRA](https://issues.apache.org/jira/browse/MJARSIGNER-76?focusedCommentId=17863556&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17863556):
> This is yet more unactionable log junk for builds that already have far
too much of it.
I don't really agree that it is "unactionable" (nor that is "junk"). As
mentioned in the issue description on JIRA, the current output does not make it
clear which files the plugin actually signed. Or what do you mean by
"unactionable"? Technically all INFO messages from Maven and plugins are
unactionable because they just inform you what Maven or the plugins are doing,
without prompting you to change anything (unlike WARNING or ERROR).
And sure, it would be great if Maven printed nearly nothing to the console
and everything just worked. But in the cases where something does not work, or
even where the build is successful but the result in unexpected, such output
can be useful for troubleshooting.
And you can customize Maven logging to only log WARNING and above.
Or which cases are you thinking of where this output is not useful? Builds
with dozens of signed files? I would just like to know why you are so strongly
opposed to this.
As suggested by @lasselindqvist above, would it be acceptable to log this at
DEBUG level?
> Print names of processed files
> --
>
> Key: MJARSIGNER-76
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-76
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Marcono1234
>Priority: Minor
>
> h2. Problem
> Currently the plugin just prints the number of processed artifacts once it is
> done, for example:
> {quote}
> 2 archive(s) processed
> {quote}
> This has these disadvantages:
> - It is not immediately obvious if the intended file has been signed (e.g.
> when using wildcards)
> - If the number is higher than expected, it is not obvious which additional
> files were signed redundantly
> In both cases it is necessary to manually inspect the artifacts of the
> project and check if they have been signed (or use {{jarsigner}} to verify
> them).
> h2. Improvement
> By default the plugin should print the file names of the signed artifacts.
> This information is already available in {{AbstractJarsignerMojo#execute}},
> but currently only {{archives.size()}} is logged.
> - Ideally each file should be logged in a separate line to be easier to read.
> - The relative file path (and not only the file name) should be logged.
> Otherwise there might be confusion if the same file exists in multiple
> directories, e.g. if it is copied by another plugin during the build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MJARSIGNER-76] Print names of processed files [maven-jarsigner-plugin]
Marcono1234 commented on PR #20: URL: https://github.com/apache/maven-jarsigner-plugin/pull/20#issuecomment-2212519982 @elharo, regarding your comment here and also your [comment on JIRA](https://issues.apache.org/jira/browse/MJARSIGNER-76?focusedCommentId=17863556&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17863556): > This is yet more unactionable log junk for builds that already have far too much of it. I don't really agree that it is "unactionable" (nor that is "junk"). As mentioned in the issue description on JIRA, the current output does not make it clear which files the plugin actually signed. Or what do you mean by "unactionable"? Technically all INFO messages from Maven and plugins are unactionable because they just inform you what Maven or the plugins are doing, without prompting you to change anything (unlike WARNING or ERROR). And sure, it would be great if Maven printed nearly nothing to the console and everything just worked. But in the cases where something does not work, or even where the build is successful but the result in unexpected, such output can be useful for troubleshooting. And you can customize Maven logging to only log WARNING and above. Or which cases are you thinking of where this output is not useful? Builds with dozens of signed files? I would just like to know why you are so strongly opposed to this. As suggested by @lasselindqvist above, would it be acceptable to log this at DEBUG level? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (SUREFIRE-2250) Surefire Test Report Schema properties element is not consistent with the code
[
https://issues.apache.org/jira/browse/SUREFIRE-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863599#comment-17863599
]
Michael Osipov edited comment on SUREFIRE-2250 at 7/7/24 5:25 PM:
--
Fixed with
[561b4ca356e6fae53f0f16f4862fdd22305852fb|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=561b4ca356e6fae53f0f16f4862fdd22305852fb].
was (Author: michael-o):
Fixed with
[d1777028eb011834dd109f7c17b2766d683a150d|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=d1777028eb011834dd109f7c17b2766d683a150d].
> Surefire Test Report Schema properties element is not consistent with the code
> --
>
> Key: SUREFIRE-2250
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2250
> Project: Maven Surefire
> Issue Type: Bug
> Components: xml generation
>Affects Versions: 3.3.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.3.1
>
>
> surefire-test-report.xsd defines:
> {code:xml}
>
> {code}
> but the Java code says:
> {code}
> private static void showProperties(XMLWriter xmlWriter, Map String> systemProperties) throws IOException {
> xmlWriter.startElement("properties");
> for (final Entry entry : systemProperties.entrySet())
> {
> final String key = entry.getKey();
> String value = entry.getValue();
> if (value == null) {
> value = "null";
> }
> xmlWriter.startElement("property");
> xmlWriter.addAttribute("name", key);
> xmlWriter.addAttribute("value", extraEscapeAttribute(value));
> xmlWriter.endElement();
> }
> xmlWriter.endElement();
> }
> {code}
> and is called only once in
> {{org.apache.maven.plugin.surefire.report.StatelessXmlReporter.testSetCompleted(WrappedReportEntry,
> TestSetStats)}}. This makes the schema definition wrong. Let's fix this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (SUREFIRE-1360) Ability to disable properties for successfully passed tests
[ https://issues.apache.org/jira/browse/SUREFIRE-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863598#comment-17863598 ] Michael Osipov edited comment on SUREFIRE-1360 at 7/7/24 5:24 PM: -- Fixed with [6aaea8a6dfed1f8f5b803dc202fefa5a47f14bb7|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=6aaea8a6dfed1f8f5b803dc202fefa5a47f14bb7]. was (Author: michael-o): Fixed with [9fcae73f9431cc49eae8ae367014ffd113cef618|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=9fcae73f9431cc49eae8ae367014ffd113cef618]. > Ability to disable properties for successfully passed tests > --- > > Key: SUREFIRE-1360 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1360 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin, Maven Surefire Plugin, xml > generation >Reporter: Jaromir Hamala >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.3.1 > > > I'd like to have an option to disable dumping (all?) properties into XML > reports. > Reasoning: > The same properties are repeated in 10,000's of XML test reports. > In many cases this is unnecessary. It's painful when a test environment has > I/O throttling - think of AWS with I/O burst credits. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SUREFIRE-2250) Surefire Test Report Schema properties element is not consistent with the code
[
https://issues.apache.org/jira/browse/SUREFIRE-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863603#comment-17863603
]
ASF GitHub Bot commented on SUREFIRE-2250:
--
asfgit merged PR #758:
URL: https://github.com/apache/maven-surefire/pull/758
> Surefire Test Report Schema properties element is not consistent with the code
> --
>
> Key: SUREFIRE-2250
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2250
> Project: Maven Surefire
> Issue Type: Bug
> Components: xml generation
>Affects Versions: 3.3.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.3.1
>
>
> surefire-test-report.xsd defines:
> {code:xml}
>
> {code}
> but the Java code says:
> {code}
> private static void showProperties(XMLWriter xmlWriter, Map String> systemProperties) throws IOException {
> xmlWriter.startElement("properties");
> for (final Entry entry : systemProperties.entrySet())
> {
> final String key = entry.getKey();
> String value = entry.getValue();
> if (value == null) {
> value = "null";
> }
> xmlWriter.startElement("property");
> xmlWriter.addAttribute("name", key);
> xmlWriter.addAttribute("value", extraEscapeAttribute(value));
> xmlWriter.endElement();
> }
> xmlWriter.endElement();
> }
> {code}
> and is called only once in
> {{org.apache.maven.plugin.surefire.report.StatelessXmlReporter.testSetCompleted(WrappedReportEntry,
> TestSetStats)}}. This makes the schema definition wrong. Let's fix this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SUREFIRE-2250) Surefire Test Report Schema properties element is not consistent with the code
[
https://issues.apache.org/jira/browse/SUREFIRE-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863602#comment-17863602
]
ASF GitHub Bot commented on SUREFIRE-2250:
--
asfgit merged PR #758:
URL: https://github.com/apache/maven-surefire/pull/758
> Surefire Test Report Schema properties element is not consistent with the code
> --
>
> Key: SUREFIRE-2250
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2250
> Project: Maven Surefire
> Issue Type: Bug
> Components: xml generation
>Affects Versions: 3.3.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.3.1
>
>
> surefire-test-report.xsd defines:
> {code:xml}
>
> {code}
> but the Java code says:
> {code}
> private static void showProperties(XMLWriter xmlWriter, Map String> systemProperties) throws IOException {
> xmlWriter.startElement("properties");
> for (final Entry entry : systemProperties.entrySet())
> {
> final String key = entry.getKey();
> String value = entry.getValue();
> if (value == null) {
> value = "null";
> }
> xmlWriter.startElement("property");
> xmlWriter.addAttribute("name", key);
> xmlWriter.addAttribute("value", extraEscapeAttribute(value));
> xmlWriter.endElement();
> }
> xmlWriter.endElement();
> }
> {code}
> and is called only once in
> {{org.apache.maven.plugin.surefire.report.StatelessXmlReporter.testSetCompleted(WrappedReportEntry,
> TestSetStats)}}. This makes the schema definition wrong. Let's fix this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [SUREFIRE-2250] Surefire Test Report Schema properties element is not consistent with the code [maven-surefire]
asfgit merged PR #758: URL: https://github.com/apache/maven-surefire/pull/758 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SUREFIRE-2250] Surefire Test Report Schema properties element is not consistent with the code [maven-surefire]
asfgit merged PR #758: URL: https://github.com/apache/maven-surefire/pull/758 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SUREFIRE-1360] Ability to disable properties for successfully passed tests [maven-surefire]
asfgit closed pull request #755: [SUREFIRE-1360] Ability to disable properties for successfully passed tests URL: https://github.com/apache/maven-surefire/pull/755 -- 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] (SUREFIRE-1360) Ability to disable properties for successfully passed tests
[ https://issues.apache.org/jira/browse/SUREFIRE-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SUREFIRE-1360. Resolution: Fixed Fixed with [9fcae73f9431cc49eae8ae367014ffd113cef618|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=9fcae73f9431cc49eae8ae367014ffd113cef618]. > Ability to disable properties for successfully passed tests > --- > > Key: SUREFIRE-1360 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1360 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin, Maven Surefire Plugin, xml > generation >Reporter: Jaromir Hamala >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.3.1 > > > I'd like to have an option to disable dumping (all?) properties into XML > reports. > Reasoning: > The same properties are repeated in 10,000's of XML test reports. > In many cases this is unnecessary. It's painful when a test environment has > I/O throttling - think of AWS with I/O burst credits. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SUREFIRE-2250) Surefire Test Report Schema properties element is not consistent with the code
[
https://issues.apache.org/jira/browse/SUREFIRE-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-2250.
Resolution: Fixed
Fixed with
[d1777028eb011834dd109f7c17b2766d683a150d|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=d1777028eb011834dd109f7c17b2766d683a150d].
> Surefire Test Report Schema properties element is not consistent with the code
> --
>
> Key: SUREFIRE-2250
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2250
> Project: Maven Surefire
> Issue Type: Bug
> Components: xml generation
>Affects Versions: 3.3.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.3.1
>
>
> surefire-test-report.xsd defines:
> {code:xml}
>
> {code}
> but the Java code says:
> {code}
> private static void showProperties(XMLWriter xmlWriter, Map String> systemProperties) throws IOException {
> xmlWriter.startElement("properties");
> for (final Entry entry : systemProperties.entrySet())
> {
> final String key = entry.getKey();
> String value = entry.getValue();
> if (value == null) {
> value = "null";
> }
> xmlWriter.startElement("property");
> xmlWriter.addAttribute("name", key);
> xmlWriter.addAttribute("value", extraEscapeAttribute(value));
> xmlWriter.endElement();
> }
> xmlWriter.endElement();
> }
> {code}
> and is called only once in
> {{org.apache.maven.plugin.surefire.report.StatelessXmlReporter.testSetCompleted(WrappedReportEntry,
> TestSetStats)}}. This makes the schema definition wrong. Let's fix this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SUREFIRE-2105) Failsafe report size increased with version upgrade from 2.17 to 2.22.2
[ https://issues.apache.org/jira/browse/SUREFIRE-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SUREFIRE-2105. Resolution: Fixed I believe that this is now addressed with SUREFIRE-1360. > Failsafe report size increased with version upgrade from 2.17 to 2.22.2 > --- > > Key: SUREFIRE-2105 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2105 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.22.2, 3.0.0-M5, 3.0.0-M6 >Reporter: parita jivani >Assignee: Michael Osipov >Priority: Major > Fix For: 3.3.1 > > > Java test project we were using surefire/failsafe version 2.17 and upgraded > it to 2.22.2. > After upgrade failsafe report size has increased from approx. 7-8KB to > 180-200KB. > Properties, "java.class.path" and "surefire.test.class.path" are having large > class path values. If we can get property configuration option like mask > bigger properties values of configuration to unable or disable according to > requirement would really help to resolve size issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPLUGIN-436) Deprecate implementation configuration in plugin descriptor
[ https://issues.apache.org/jira/browse/MPLUGIN-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPLUGIN-436: --- Description: Goal is to align with MPLUGIN-435. Likely should be done for 4.x rather than 3.x. was: Goal is to align with https://issues.apache.org/jira/browse/MPLUGIN-435. Likely should be done for 4.x rather than 3.x. > Deprecate implementation configuration in plugin descriptor > --- > > Key: MPLUGIN-436 > URL: https://issues.apache.org/jira/browse/MPLUGIN-436 > Project: Maven Plugin Tools > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Minor > > Goal is to align with MPLUGIN-435. > Likely should be done for 4.x rather than 3.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] 4 upgrade to java 18 [maven-jlink-plugin]
michab66 commented on PR #208: URL: https://github.com/apache/maven-jlink-plugin/pull/208#issuecomment-2212497566 Accident. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] 4 upgrade to java 18 [maven-jlink-plugin]
michab66 closed pull request #208: 4 upgrade to java 18 URL: https://github.com/apache/maven-jlink-plugin/pull/208 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] 4 upgrade to java 18 [maven-jlink-plugin]
michab66 opened a new pull request, #208: URL: https://github.com/apache/maven-jlink-plugin/pull/208 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/MJLINK) 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 `[MJLINK-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MJLINK-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] (MSITE-1012) Clean up notion that sites aren't deployed to repositories
[
https://issues.apache.org/jira/browse/MSITE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863584#comment-17863584
]
ASF GitHub Bot commented on MSITE-1012:
---
michael-o opened a new pull request, #195:
URL: https://github.com/apache/maven-site-plugin/pull/195
This closes #195
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/MSITE) 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 `[MSITE-XXX] - Fixes bug in
ApproximateQuantiles`,
where you replace `MSITE-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).
> Clean up notion that sites aren't deployed to repositories
> --
>
> Key: MSITE-1012
> URL: https://issues.apache.org/jira/browse/MSITE-1012
> Project: Maven Site Plugin
> Issue Type: Task
> Components: inheritance, multi module, site:deploy
>Affects Versions: 4.0.0-M15
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-M16
>
>
> As is seems with MSITE-1010 people assume that since we use the term "site
> repository" it behaves like a Maven repository in terms of structure. It does
> **not**. Let's get rid of that term and use "site" or "site deployment" only.
> No implications. With this, the parameter {{stagingRepositoryId}} in
> {{SiteStageDeployMojo}} will be ranamed to {{stagingSiteId}} to clean up
> confusion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MSITE-1012] Clean up notion that sites aren't deployed to repositories [maven-site-plugin]
michael-o opened a new pull request, #195: URL: https://github.com/apache/maven-site-plugin/pull/195 This closes #195 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/MSITE) 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 `[MSITE-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MSITE-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] (MSITE-1012) Clean up notion that sites aren't deployed to repositories
[
https://issues.apache.org/jira/browse/MSITE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-1012:
--
Issue Type: Task (was: Improvement)
> Clean up notion that sites aren't deployed to repositories
> --
>
> Key: MSITE-1012
> URL: https://issues.apache.org/jira/browse/MSITE-1012
> Project: Maven Site Plugin
> Issue Type: Task
> Components: inheritance, multi module, site:deploy
>Affects Versions: 4.0.0-M15
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-M16
>
>
> As is seems with MSITE-1010 people assume that since we use the term "site
> repository" it behaves like a Maven repository in terms of structure. It does
> **not**. Let's get rid of that term and use "site" or "site deployment" only.
> No implications. With this, the parameter {{stagingRepositoryId}} in
> {{SiteStageDeployMojo}} will be ranamed to {{stagingSiteId}} to clean up
> confusion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSITE-1012) Clean up notion that sites aren't deployed to repositories
[
https://issues.apache.org/jira/browse/MSITE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-1012:
--
Description: As is seems with MSITE-1010 people assume that since we use
the term "site repository" it behaves like a Maven repository in terms of
structure. It does **not**. Let's get rid of that term and use "site" or "site
deployment" only. No implications. With this, the parameter
{{stagingRepositoryId}} in {{SiteStageDeployMojo}} will be ranamed to
{{stagingSiteId}} to clean up confusion. (was: As is seems with MSITE-1010
people assume that since we use the term "site repository" it behaves like a
Maven repository in terms of structure. It does **not**. Let's get rid of that
term and use "site" or "site deployment" only. No implications.
With this the parameter {{stagingRepositoryId}} in {{SiteStageDeployMojo}} will
be ranamed to {{stagingSiteId}} to clean up confusion.)
> Clean up notion that sites aren't deployed to repositories
> --
>
> Key: MSITE-1012
> URL: https://issues.apache.org/jira/browse/MSITE-1012
> Project: Maven Site Plugin
> Issue Type: Improvement
> Components: inheritance, multi module, site:deploy
>Affects Versions: 4.0.0-M15
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-M16
>
>
> As is seems with MSITE-1010 people assume that since we use the term "site
> repository" it behaves like a Maven repository in terms of structure. It does
> **not**. Let's get rid of that term and use "site" or "site deployment" only.
> No implications. With this, the parameter {{stagingRepositoryId}} in
> {{SiteStageDeployMojo}} will be ranamed to {{stagingSiteId}} to clean up
> confusion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSITE-1012) Clean up notion that sites aren't deployed to repositories
[
https://issues.apache.org/jira/browse/MSITE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-1012:
--
Description:
As is seems with MSITE-1010 people assume that since we use the term "site
repository" it behaves like a Maven repository in terms of structure. It does
**not**. Let's get rid of that term and use "site" or "site deployment" only.
No implications.
With this the parameter {{stagingRepositoryId}} in {{SiteStageDeployMojo}} will
be ranamed to {{stagingSiteId}} to clean up confusion.
was:As is seems with MSITE-1010 people assume that since we use the term
"site repository" it behaves like a Maven repository in terms of structure. It
does **not**. Let's get rid of that term and use "site" or "site deployment"
only. No implications.
> Clean up notion that sites aren't deployed to repositories
> --
>
> Key: MSITE-1012
> URL: https://issues.apache.org/jira/browse/MSITE-1012
> Project: Maven Site Plugin
> Issue Type: Improvement
> Components: inheritance, multi module, site:deploy
>Affects Versions: 4.0.0-M15
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-M16
>
>
> As is seems with MSITE-1010 people assume that since we use the term "site
> repository" it behaves like a Maven repository in terms of structure. It does
> **not**. Let's get rid of that term and use "site" or "site deployment" only.
> No implications.
> With this the parameter {{stagingRepositoryId}} in {{SiteStageDeployMojo}}
> will be ranamed to {{stagingSiteId}} to clean up confusion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MSITE-1012) Clean up notion that sites aren't deployed to repositories
Michael Osipov created MSITE-1012: - Summary: Clean up notion that sites aren't deployed to repositories Key: MSITE-1012 URL: https://issues.apache.org/jira/browse/MSITE-1012 Project: Maven Site Plugin Issue Type: Improvement Components: inheritance, multi module, site:deploy Affects Versions: 4.0.0-M15 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 4.0.0-M16, 4.0.0 As is seems with MSITE-1010 people assume that since we use the term "site repository" it behaves like a Maven repository in terms of structure. It does **not**. Let's get rid of that term and use "site" or "site deployment" only. No implications. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.apache.maven:maven-parent from 41 to 42 [maven-dist-tool]
slachiewicz commented on PR #54: URL: https://github.com/apache/maven-dist-tool/pull/54#issuecomment-2212457406 @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
Re: [PR] Bump org.easymock:easymock from 5.2.0 to 5.3.0 [maven-archetype]
slachiewicz merged PR #197: URL: https://github.com/apache/maven-archetype/pull/197 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7771) Don't use ArtifactResolutionException#getMessage() w/o knowing whether there are other exceptions or not
[
https://issues.apache.org/jira/browse/MNG-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863573#comment-17863573
]
Michael Osipov commented on MNG-7771:
-
Correct, [~cstamas] nailed it mostly. The information has to be in the
exception and Maven has to expose it correct. Neither is. Even if the issue is
not in Maven per sé, the issue is visible from Maven from a user's PoV.
> Don't use ArtifactResolutionException#getMessage() w/o knowing whether there
> are other exceptions or not
>
>
> Key: MNG-7771
> URL: https://issues.apache.org/jira/browse/MNG-7771
> Project: Maven
> Issue Type: Sub-task
>Affects Versions: 3.8.8, 3.9.1, 4.0.0-alpha-5
>Reporter: Michael Osipov
>Priority: Major
> Fix For: 3.9.x-candidate, 4.0.x-candidate, 4.0.0
>
>
> {{ArtifactResolutionException#getMessage()}} only considers the message from
> the first cause, completely ignoring other causes. So it is order-dependent
> and can be misleading. Create an expeception-agnotic message and all
> submessages shall be retrieved through API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump org.codehaus.mojo:animal-sniffer-maven-plugin from 1.23 to 1.24 [maven-surefire]
slachiewicz merged PR #757: URL: https://github.com/apache/maven-surefire/pull/757 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.codehaus.plexus:plexus-testing from 1.3.0 to 1.4.0 [maven-doxia]
slachiewicz merged PR #217: URL: https://github.com/apache/maven-doxia/pull/217 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.junit:junit-bom from 5.10.2 to 5.10.3 [maven-doxia]
slachiewicz merged PR #216: URL: https://github.com/apache/maven-doxia/pull/216 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-8155) Reword "This project has been banned from the build due to previous failures."
[ https://issues.apache.org/jira/browse/MNG-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863563#comment-17863563 ] ASF GitHub Bot commented on MNG-8155: - elharo opened a new pull request, #1599: URL: https://github.com/apache/maven/pull/1599 Part of MNG-8155 > Reword "This project has been banned from the build due to previous failures." > -- > > Key: MNG-8155 > URL: https://issues.apache.org/jira/browse/MNG-8155 > Project: Maven > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Saw this error message. This confused me and I did not initially know what it > meant. In fact, I guessed wrong. > [INFO] Skipping presto-prism-plugin > [INFO] This project has been banned from the build due to previous failures. > I suggest rephrasing along the lines of "Module name was not built because > the module module-name it depends on failed to build." -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8155) Reword "This project has been banned from the build due to previous failures."
[ https://issues.apache.org/jira/browse/MNG-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MNG-8155: --- Description: Saw this error message. This confused me and I did not initially know what it meant. In fact, I guessed wrong. [INFO] Skipping presto-prism-plugin [INFO] This project has been banned from the build due to previous failures. I suggest rephrasing along the lines of "Module name was not built because the module module-name it depends on failed to build." was: Saw this error message. This confused me and I did not initially know what it meant. In fact, I guessed wrong. [INFO] Skipping presto-prism-plugin [INFO] This project has been banned from the build due to previous failures. I suggest rephrasing along the lines of "Module name was not build because the module module-name it depends on failed to build." > Reword "This project has been banned from the build due to previous failures." > -- > > Key: MNG-8155 > URL: https://issues.apache.org/jira/browse/MNG-8155 > Project: Maven > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Saw this error message. This confused me and I did not initially know what it > meant. In fact, I guessed wrong. > [INFO] Skipping presto-prism-plugin > [INFO] This project has been banned from the build due to previous failures. > I suggest rephrasing along the lines of "Module name was not built because > the module module-name it depends on failed to build." -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSITE-1010) site-deployment for POM projects does not create project directories in site repository
[
https://issues.apache.org/jira/browse/MSITE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863562#comment-17863562
]
ASF GitHub Bot commented on MSITE-1010:
---
Bukama commented on PR #194:
URL:
https://github.com/apache/maven-site-plugin/pull/194#issuecomment-2212434485
Thanks for the review. Requested changes done.
> site-deployment for POM projects does not create project directories in site
> repository
> ---
>
> Key: MSITE-1010
> URL: https://issues.apache.org/jira/browse/MSITE-1010
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:deploy
>Affects Versions: 3.12.0, 4.0.0-M14
> Environment: Nexus, since at least Maven 3.6.3 (not tested with 3.9.7
> or 4.0.0-beta)
>Reporter: Matthias Bünger
>Priority: Minor
> Attachments: pom.xml, webdav.txt
>
>
> I noticed the following issue while updating the plugins in our teams
> META-POM and could backtrack it at least until 3.12 but might be an even
> older issue. Havn't checked 4.0.0-M15 but from the releases notes I doubt it
> is fixed.
> When you do "site-deploy" for a single module or multi module project the
> site files (.html, css-folders, etc.) are stored in the site-repository (we
> have current Nexus version) within a subfolder with the name of the project,
> e.g
> {code}
> / (root of site-repository)
> /- project-A
>/css
>report.html
> /- project-B
>/css
>report.html
> /project-C
> {code}
> If you do the same for a "POM" project (e.g. a META-POM or BOM) the site
> files are all stored at root level (instead of creating a project folder) and
> ofc overwriting the ones from other POM-projects:
> {code}
> / (root of site-repository)
> /css
> /project-A
> /project-B
> /project-C
> report.html
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MSITE-1010] Add documentation how site repository inheritance [maven-site-plugin]
Bukama commented on PR #194: URL: https://github.com/apache/maven-site-plugin/pull/194#issuecomment-2212434485 Thanks for the review. Requested changes done. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MJARSIGNER-76) Print names of processed files
[
https://issues.apache.org/jira/browse/MJARSIGNER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863558#comment-17863558
]
ASF GitHub Bot commented on MJARSIGNER-76:
--
elharo commented on PR #20:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/20#issuecomment-2212413163
No, I am saying close the PR and don't do this. It's not a feature we need
or want. It makes Maven worse.
> Print names of processed files
> --
>
> Key: MJARSIGNER-76
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-76
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Marcono1234
>Priority: Minor
>
> h2. Problem
> Currently the plugin just prints the number of processed artifacts once it is
> done, for example:
> {quote}
> 2 archive(s) processed
> {quote}
> This has these disadvantages:
> - It is not immediately obvious if the intended file has been signed (e.g.
> when using wildcards)
> - If the number is higher than expected, it is not obvious which additional
> files were signed redundantly
> In both cases it is necessary to manually inspect the artifacts of the
> project and check if they have been signed (or use {{jarsigner}} to verify
> them).
> h2. Improvement
> By default the plugin should print the file names of the signed artifacts.
> This information is already available in {{AbstractJarsignerMojo#execute}},
> but currently only {{archives.size()}} is logged.
> - Ideally each file should be logged in a separate line to be easier to read.
> - The relative file path (and not only the file name) should be logged.
> Otherwise there might be confusion if the same file exists in multiple
> directories, e.g. if it is copied by another plugin during the build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MJARSIGNER-76] Print names of processed files [maven-jarsigner-plugin]
elharo commented on PR #20: URL: https://github.com/apache/maven-jarsigner-plugin/pull/20#issuecomment-2212413163 No, I am saying close the PR and don't do this. It's not a feature we need or want. It makes Maven worse. -- 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] (MJARSIGNER-76) Print names of processed files
[
https://issues.apache.org/jira/browse/MJARSIGNER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863557#comment-17863557
]
ASF GitHub Bot commented on MJARSIGNER-76:
--
lasselindqvist commented on PR #20:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/20#issuecomment-2212412394
> -10. Maven is too verbose already. I want less output, not more. This is
yet more unactionable log junk.
What changes are you requesting? Changing the log leve to debug?
> Print names of processed files
> --
>
> Key: MJARSIGNER-76
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-76
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Marcono1234
>Priority: Minor
>
> h2. Problem
> Currently the plugin just prints the number of processed artifacts once it is
> done, for example:
> {quote}
> 2 archive(s) processed
> {quote}
> This has these disadvantages:
> - It is not immediately obvious if the intended file has been signed (e.g.
> when using wildcards)
> - If the number is higher than expected, it is not obvious which additional
> files were signed redundantly
> In both cases it is necessary to manually inspect the artifacts of the
> project and check if they have been signed (or use {{jarsigner}} to verify
> them).
> h2. Improvement
> By default the plugin should print the file names of the signed artifacts.
> This information is already available in {{AbstractJarsignerMojo#execute}},
> but currently only {{archives.size()}} is logged.
> - Ideally each file should be logged in a separate line to be easier to read.
> - The relative file path (and not only the file name) should be logged.
> Otherwise there might be confusion if the same file exists in multiple
> directories, e.g. if it is copied by another plugin during the build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MJARSIGNER-76] Print names of processed files [maven-jarsigner-plugin]
lasselindqvist commented on PR #20: URL: https://github.com/apache/maven-jarsigner-plugin/pull/20#issuecomment-2212412394 > -10. Maven is too verbose already. I want less output, not more. This is yet more unactionable log junk. What changes are you requesting? Changing the log leve to debug? -- 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] [Resolved] (MJARSIGNER-76) Print names of processed files
[
https://issues.apache.org/jira/browse/MJARSIGNER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MJARSIGNER-76.
-
Resolution: Won't Do
We need less logs, not more. This is yet more unactionable log junk for builds
that already have far too much of it.
> Print names of processed files
> --
>
> Key: MJARSIGNER-76
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-76
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Marcono1234
>Priority: Minor
>
> h2. Problem
> Currently the plugin just prints the number of processed artifacts once it is
> done, for example:
> {quote}
> 2 archive(s) processed
> {quote}
> This has these disadvantages:
> - It is not immediately obvious if the intended file has been signed (e.g.
> when using wildcards)
> - If the number is higher than expected, it is not obvious which additional
> files were signed redundantly
> In both cases it is necessary to manually inspect the artifacts of the
> project and check if they have been signed (or use {{jarsigner}} to verify
> them).
> h2. Improvement
> By default the plugin should print the file names of the signed artifacts.
> This information is already available in {{AbstractJarsignerMojo#execute}},
> but currently only {{archives.size()}} is logged.
> - Ideally each file should be logged in a separate line to be easier to read.
> - The relative file path (and not only the file name) should be logged.
> Otherwise there might be confusion if the same file exists in multiple
> directories, e.g. if it is copied by another plugin during the build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7771) Don't use ArtifactResolutionException#getMessage() w/o knowing whether there are other exceptions or not
[
https://issues.apache.org/jira/browse/MNG-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863554#comment-17863554
]
Tamas Cservenak commented on MNG-7771:
--
So this is more about "consuming" and formatting console output for user when
this exception is thrown.
> Don't use ArtifactResolutionException#getMessage() w/o knowing whether there
> are other exceptions or not
>
>
> Key: MNG-7771
> URL: https://issues.apache.org/jira/browse/MNG-7771
> Project: Maven
> Issue Type: Sub-task
>Affects Versions: 3.8.8, 3.9.1, 4.0.0-alpha-5
>Reporter: Michael Osipov
>Priority: Major
> Fix For: 3.9.x-candidate, 4.0.x-candidate, 4.0.0
>
>
> {{ArtifactResolutionException#getMessage()}} only considers the message from
> the first cause, completely ignoring other causes. So it is order-dependent
> and can be misleading. Create an expeception-agnotic message and all
> submessages shall be retrieved through API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7771) Don't use ArtifactResolutionException#getMessage() w/o knowing whether there are other exceptions or not
[
https://issues.apache.org/jira/browse/MNG-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863553#comment-17863553
]
Tamas Cservenak commented on MNG-7771:
--
The exception carries multiple important information, and this really about
formatting understandable, meaningful, but at the same time complete error
message on console (to user) in case it is being thrown.
> Don't use ArtifactResolutionException#getMessage() w/o knowing whether there
> are other exceptions or not
>
>
> Key: MNG-7771
> URL: https://issues.apache.org/jira/browse/MNG-7771
> Project: Maven
> Issue Type: Sub-task
>Affects Versions: 3.8.8, 3.9.1, 4.0.0-alpha-5
>Reporter: Michael Osipov
>Priority: Major
> Fix For: 3.9.x-candidate, 4.0.x-candidate, 4.0.0
>
>
> {{ArtifactResolutionException#getMessage()}} only considers the message from
> the first cause, completely ignoring other causes. So it is order-dependent
> and can be misleading. Create an expeception-agnotic message and all
> submessages shall be retrieved through API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7771) Don't use ArtifactResolutionException#getMessage() w/o knowing whether there are other exceptions or not
[
https://issues.apache.org/jira/browse/MNG-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863551#comment-17863551
]
Guillaume Nodet commented on MNG-7771:
--
[~michael-o] That was my understanding too. But then, shouldn't we move the
issue to maven-resolver ?
I don't really understand what you expect from Maven.
> Don't use ArtifactResolutionException#getMessage() w/o knowing whether there
> are other exceptions or not
>
>
> Key: MNG-7771
> URL: https://issues.apache.org/jira/browse/MNG-7771
> Project: Maven
> Issue Type: Sub-task
>Affects Versions: 3.8.8, 3.9.1, 4.0.0-alpha-5
>Reporter: Michael Osipov
>Priority: Major
> Fix For: 3.9.x-candidate, 4.0.x-candidate, 4.0.0
>
>
> {{ArtifactResolutionException#getMessage()}} only considers the message from
> the first cause, completely ignoring other causes. So it is order-dependent
> and can be misleading. Create an expeception-agnotic message and all
> submessages shall be retrieved through API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-8177) Warning "'dependencyManagement.dependencies.dependency.systemPath' for com.sun:tools:jar refers to a non-existing file C:\Temp\jdk-11.0.23\..\lib\tools.jar"
Wolfgang Knauf created MNG-8177:
---
Summary: Warning
"'dependencyManagement.dependencies.dependency.systemPath' for
com.sun:tools:jar refers to a non-existing file
C:\Temp\jdk-11.0.23\..\lib\tools.jar"
Key: MNG-8177
URL: https://issues.apache.org/jira/browse/MNG-8177
Project: Maven
Issue Type: Bug
Components: Core
Affects Versions: 3.9.8
Environment: Java 11
Reporter: Wolfgang Knauf
This warning pops up first with Maven 3.9.8, previous versions up to 3.89.7 did
not report it:
{{[WARNING] 1 problem was encountered while building the effective model for
org.jboss:jboss-dmr:jar:1.3.0.Final}}
When using the "-X" switch, I see this additional message:
{{[WARNING] 'dependencyManagement.dependencies.dependency.systemPath' for
com.sun:tools:jar refers to a non-existing file
C:\Temp\jdk-11.0.23\..\lib\tools.jar. Please verify that you run Maven using a
JDK and not just a JRE. @ org.jboss:jboss-dmr:1.3.0.Final}}
I run it with JDK 11, but downloaded the zip file only. There is no
"tools.jar", which was removed as part of Java 9.
To reproduce: create a project from this archetype:
{{mvn archetype:generate -DarchetypeCatalog=local -DgroupId=com.acme
-DartifactId=example-subsystem -Dversion=1.0-SNAPSHOT
-Dmodule=org.test.subsystem -Dpackage=com.acme.example
-DarchetypeGroupId=org.wildfly.archetype
-DarchetypeArtifactId=wildfly-subsystem -DarchetypeVersion=32.0.0.Final
-DinteractiveMode=false}}
Then run this command to see the warning:
{{mvn dependency:tree -X}}
Actually, I don't know why jboss-dmr:1.3.0 is tested, as the project should
reference jboss-dmr:1.7.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSITE-1010) site-deployment for POM projects does not create project directories in site repository
[
https://issues.apache.org/jira/browse/MSITE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863550#comment-17863550
]
ASF GitHub Bot commented on MSITE-1010:
---
michael-o commented on code in PR #194:
URL: https://github.com/apache/maven-site-plugin/pull/194#discussion_r1667658214
##
src/site/apt/examples/inheritancesiterepository.apt:
##
@@ -0,0 +1,77 @@
+ --
+ Inheritance Site Repository
Review Comment:
Use hyphens in the file name
##
src/site/apt/examples/inheritancesiterepository.apt:
##
@@ -0,0 +1,77 @@
+ --
+ Inheritance Site Repository
+ --
+Matthias Bünger
+ --
+ 2024-07-07
+ --
+
+ ~~ Licensed to the Apache Software Foundation (ASF) under one
+ ~~ or more contributor license agreements. See the NOTICE file
+ ~~ distributed with this work for additional information
+ ~~ regarding copyright ownership. The ASF licenses this file
+ ~~ to you under the Apache License, Version 2.0 (the
+ ~~ "License"); you may not use this file except in compliance
+ ~~ with the License. You may obtain a copy of the License at
+ ~~
+ ~~ http://www.apache.org/licenses/LICENSE-2.0
+ ~~
+ ~~ Unless required by applicable law or agreed to in writing,
+ ~~ software distributed under the License is distributed on an
+ ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ ~~ KIND, either express or implied. See the License for the
+ ~~ specific language governing permissions and limitations
+ ~~ under the License.
+
+ ~~ NOTE: For help with the syntax of this file, see:
+ ~~ http://maven.apache.org/doxia/references/apt-format.html
+
+
+Inheritance of the site repository
+
+ Inside your <<>> you can not only configure the
<<>> for the releases and snapshots
+ of your project, but also where to deploy your site pages when using the
<<<{{{../deploy-mojo.html}site:deploy}}>>>
+ goal. The following configuration would deploy the project's site to a local
folder called <<>>.
Review Comment:
directory, not folder
##
src/site/apt/examples/inheritancesiterepository.apt:
##
@@ -0,0 +1,77 @@
+ --
+ Inheritance Site Repository
+ --
+Matthias Bünger
+ --
+ 2024-07-07
+ --
+
+ ~~ Licensed to the Apache Software Foundation (ASF) under one
+ ~~ or more contributor license agreements. See the NOTICE file
+ ~~ distributed with this work for additional information
+ ~~ regarding copyright ownership. The ASF licenses this file
+ ~~ to you under the Apache License, Version 2.0 (the
+ ~~ "License"); you may not use this file except in compliance
+ ~~ with the License. You may obtain a copy of the License at
+ ~~
+ ~~ http://www.apache.org/licenses/LICENSE-2.0
+ ~~
+ ~~ Unless required by applicable law or agreed to in writing,
+ ~~ software distributed under the License is distributed on an
+ ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ ~~ KIND, either express or implied. See the License for the
+ ~~ specific language governing permissions and limitations
+ ~~ under the License.
+
+ ~~ NOTE: For help with the syntax of this file, see:
+ ~~ http://maven.apache.org/doxia/references/apt-format.html
+
+
+Inheritance of the site repository
+
+ Inside your <<>> you can not only configure the
<<>> for the releases and snapshots
+ of your project, but also where to deploy your site pages when using the
<<<{{{../deploy-mojo.html}site:deploy}}>>>
+ goal. The following configuration would deploy the project's site to a local
folder called <<>>.
+
++-+
+
+
+ localFileRepository
+ file:C:\temp\temprepo\
+
+
++-+
+
+ The content of this site-repository would look similar to the following
after your your deployment.
+
++-+
+/ (root of site-repository - here C:\temp\temprepo\)
+ /css
+report.html
++-+
+
+ You see that all files are placed inside the site-repository and that no
subfolder with their name is created.
+ That's a small, but important difference in comparison how the regular
<<>> of the build lifecycle works,
Review Comment:
Note: deploy and site-deploy only share names. That's it.
##
src/site/apt/examples/inheritancesiterepository.apt:
##
@@ -0,0 +1,77 @@
+ --
+ Inheritance Site Repository
+ --
+Matthias Bünger
+ --
+ 2024-07-07
+ --
+
+ ~~ Licensed to the Apache Software Foundation (ASF) under one
+ ~~ or more contributor license agreements. See the NOTICE file
+ ~~ distributed with this work for additional information
+ ~~ regarding copyright ownership. The ASF licenses this file
+ ~~ to you under the Apache License, Version 2.0 (the
+ ~~ "License"); you may not use this file except in compliance
+ ~~ with the License. You may obtain a copy of the License at
+ ~~
+ ~~ http://www.apache.org/licenses/LICENSE-2.0
+ ~~
+ ~~ Unless required by applicable law or agreed to in writing,
+ ~~ software distributed under the License is distribute
Re: [PR] [MSITE-1010] Add documentation how site repository inheritance [maven-site-plugin]
michael-o commented on code in PR #194:
URL: https://github.com/apache/maven-site-plugin/pull/194#discussion_r1667658214
##
src/site/apt/examples/inheritancesiterepository.apt:
##
@@ -0,0 +1,77 @@
+ --
+ Inheritance Site Repository
Review Comment:
Use hyphens in the file name
##
src/site/apt/examples/inheritancesiterepository.apt:
##
@@ -0,0 +1,77 @@
+ --
+ Inheritance Site Repository
+ --
+Matthias Bünger
+ --
+ 2024-07-07
+ --
+
+ ~~ Licensed to the Apache Software Foundation (ASF) under one
+ ~~ or more contributor license agreements. See the NOTICE file
+ ~~ distributed with this work for additional information
+ ~~ regarding copyright ownership. The ASF licenses this file
+ ~~ to you under the Apache License, Version 2.0 (the
+ ~~ "License"); you may not use this file except in compliance
+ ~~ with the License. You may obtain a copy of the License at
+ ~~
+ ~~ http://www.apache.org/licenses/LICENSE-2.0
+ ~~
+ ~~ Unless required by applicable law or agreed to in writing,
+ ~~ software distributed under the License is distributed on an
+ ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ ~~ KIND, either express or implied. See the License for the
+ ~~ specific language governing permissions and limitations
+ ~~ under the License.
+
+ ~~ NOTE: For help with the syntax of this file, see:
+ ~~ http://maven.apache.org/doxia/references/apt-format.html
+
+
+Inheritance of the site repository
+
+ Inside your <<>> you can not only configure the
<<>> for the releases and snapshots
+ of your project, but also where to deploy your site pages when using the
<<<{{{../deploy-mojo.html}site:deploy}}>>>
+ goal. The following configuration would deploy the project's site to a local
folder called <<>>.
Review Comment:
directory, not folder
##
src/site/apt/examples/inheritancesiterepository.apt:
##
@@ -0,0 +1,77 @@
+ --
+ Inheritance Site Repository
+ --
+Matthias Bünger
+ --
+ 2024-07-07
+ --
+
+ ~~ Licensed to the Apache Software Foundation (ASF) under one
+ ~~ or more contributor license agreements. See the NOTICE file
+ ~~ distributed with this work for additional information
+ ~~ regarding copyright ownership. The ASF licenses this file
+ ~~ to you under the Apache License, Version 2.0 (the
+ ~~ "License"); you may not use this file except in compliance
+ ~~ with the License. You may obtain a copy of the License at
+ ~~
+ ~~ http://www.apache.org/licenses/LICENSE-2.0
+ ~~
+ ~~ Unless required by applicable law or agreed to in writing,
+ ~~ software distributed under the License is distributed on an
+ ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ ~~ KIND, either express or implied. See the License for the
+ ~~ specific language governing permissions and limitations
+ ~~ under the License.
+
+ ~~ NOTE: For help with the syntax of this file, see:
+ ~~ http://maven.apache.org/doxia/references/apt-format.html
+
+
+Inheritance of the site repository
+
+ Inside your <<>> you can not only configure the
<<>> for the releases and snapshots
+ of your project, but also where to deploy your site pages when using the
<<<{{{../deploy-mojo.html}site:deploy}}>>>
+ goal. The following configuration would deploy the project's site to a local
folder called <<>>.
+
++-+
+
+
+ localFileRepository
+ file:C:\temp\temprepo\
+
+
++-+
+
+ The content of this site-repository would look similar to the following
after your your deployment.
+
++-+
+/ (root of site-repository - here C:\temp\temprepo\)
+ /css
+report.html
++-+
+
+ You see that all files are placed inside the site-repository and that no
subfolder with their name is created.
+ That's a small, but important difference in comparison how the regular
<<>> of the build lifecycle works,
Review Comment:
Note: deploy and site-deploy only share names. That's it.
##
src/site/apt/examples/inheritancesiterepository.apt:
##
@@ -0,0 +1,77 @@
+ --
+ Inheritance Site Repository
+ --
+Matthias Bünger
+ --
+ 2024-07-07
+ --
+
+ ~~ Licensed to the Apache Software Foundation (ASF) under one
+ ~~ or more contributor license agreements. See the NOTICE file
+ ~~ distributed with this work for additional information
+ ~~ regarding copyright ownership. The ASF licenses this file
+ ~~ to you under the Apache License, Version 2.0 (the
+ ~~ "License"); you may not use this file except in compliance
+ ~~ with the License. You may obtain a copy of the License at
+ ~~
+ ~~ http://www.apache.org/licenses/LICENSE-2.0
+ ~~
+ ~~ Unless required by applicable law or agreed to in writing,
+ ~~ software distributed under the License is distributed on an
+ ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ ~~ KIND, either express or implied. See the License for the
+ ~~ specific language governing permissions and limitations
+ ~~ under the License.
+
+ ~~ NOTE: For help with the syntax o
[jira] [Commented] (MSITE-1010) site-deployment for POM projects does not create project directories in site repository
[
https://issues.apache.org/jira/browse/MSITE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863549#comment-17863549
]
ASF GitHub Bot commented on MSITE-1010:
---
Bukama opened a new pull request, #194:
URL: https://github.com/apache/maven-site-plugin/pull/194
Proposed commit message:
```
[MSITE-1010] Add documentation how site repository inheritance
More information including an example how the site repository configuration
is inherited,
when using a parent-pom.
closes #MSITE-1010
```
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/MSITE) 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 `[MSITE-XXX] - Fixes bug in
ApproximateQuantiles`,
where you replace `MSITE-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)
- [x] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
> site-deployment for POM projects does not create project directories in site
> repository
> ---
>
> Key: MSITE-1010
> URL: https://issues.apache.org/jira/browse/MSITE-1010
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:deploy
>Affects Versions: 3.12.0, 4.0.0-M14
> Environment: Nexus, since at least Maven 3.6.3 (not tested with 3.9.7
> or 4.0.0-beta)
>Reporter: Matthias Bünger
>Priority: Minor
> Attachments: pom.xml, webdav.txt
>
>
> I noticed the following issue while updating the plugins in our teams
> META-POM and could backtrack it at least until 3.12 but might be an even
> older issue. Havn't checked 4.0.0-M15 but from the releases notes I doubt it
> is fixed.
> When you do "site-deploy" for a single module or multi module project the
> site files (.html, css-folders, etc.) are stored in the site-repository (we
> have current Nexus version) within a subfolder with the name of the project,
> e.g
> {code}
> / (root of site-repository)
> /- project-A
>/css
>report.html
> /- project-B
>/css
>report.html
> /project-C
> {code}
> If you do the same for a "POM" project (e.g. a META-POM or BOM) the site
> files are all stored at root level (instead of creating a project folder) and
> ofc overwriting the ones from other POM-projects:
> {code}
> / (root of site-repository)
> /css
> /project-A
> /project-B
> /project-C
> report.html
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MSITE-1010] Add documentation how site repository inheritance [maven-site-plugin]
Bukama opened a new pull request, #194: URL: https://github.com/apache/maven-site-plugin/pull/194 Proposed commit message: ``` [MSITE-1010] Add documentation how site repository inheritance More information including an example how the site repository configuration is inherited, when using a parent-pom. closes #MSITE-1010 ``` 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/MSITE) 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 `[MSITE-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MSITE-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) - [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] (MJARSIGNER-76) Print names of processed files
[
https://issues.apache.org/jira/browse/MJARSIGNER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863544#comment-17863544
]
ASF GitHub Bot commented on MJARSIGNER-76:
--
slachiewicz commented on code in PR #20:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/20#discussion_r1667633959
##
src/main/java/org/apache/maven/plugins/jarsigner/AbstractJarsignerMojo.java:
##
@@ -346,6 +350,23 @@ private List findJarfiles() throws
MojoExecutionException {
return archives;
}
+/**
+ * {@linkplain Path#relativize(Path) Relativizes} the path against {@link
MavenProject#getBasedir()}.
+ * Can be used to shorten or simplify paths before displaying them to the
user.
+ */
+private Path relativizePathAgainstBasedir(Path path) {
Review Comment:
This will not have best performance, as You calculate base dir for every file
> Print names of processed files
> --
>
> Key: MJARSIGNER-76
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-76
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Marcono1234
>Priority: Minor
>
> h2. Problem
> Currently the plugin just prints the number of processed artifacts once it is
> done, for example:
> {quote}
> 2 archive(s) processed
> {quote}
> This has these disadvantages:
> - It is not immediately obvious if the intended file has been signed (e.g.
> when using wildcards)
> - If the number is higher than expected, it is not obvious which additional
> files were signed redundantly
> In both cases it is necessary to manually inspect the artifacts of the
> project and check if they have been signed (or use {{jarsigner}} to verify
> them).
> h2. Improvement
> By default the plugin should print the file names of the signed artifacts.
> This information is already available in {{AbstractJarsignerMojo#execute}},
> but currently only {{archives.size()}} is logged.
> - Ideally each file should be logged in a separate line to be easier to read.
> - The relative file path (and not only the file name) should be logged.
> Otherwise there might be confusion if the same file exists in multiple
> directories, e.g. if it is copied by another plugin during the build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MJARSIGNER-76] Print names of processed files [maven-jarsigner-plugin]
slachiewicz commented on code in PR #20:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/20#discussion_r1667633959
##
src/main/java/org/apache/maven/plugins/jarsigner/AbstractJarsignerMojo.java:
##
@@ -346,6 +350,23 @@ private List findJarfiles() throws
MojoExecutionException {
return archives;
}
+/**
+ * {@linkplain Path#relativize(Path) Relativizes} the path against {@link
MavenProject#getBasedir()}.
+ * Can be used to shorten or simplify paths before displaying them to the
user.
+ */
+private Path relativizePathAgainstBasedir(Path path) {
Review Comment:
This will not have best performance, as You calculate base dir for every file
--
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] (MJARSIGNER-76) Print names of processed files
[
https://issues.apache.org/jira/browse/MJARSIGNER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863543#comment-17863543
]
ASF GitHub Bot commented on MJARSIGNER-76:
--
schedin commented on PR #20:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/20#issuecomment-2212361904
I think this is a useful feature and one that I have missed!
I'm not sure the state of this open source project at the moment. I have
tried to push the maintainers for a 3.1.0 release but so far been unsuccessful.
I'm tagging @elharo and @slachiewicz again.
> Print names of processed files
> --
>
> Key: MJARSIGNER-76
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-76
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Marcono1234
>Priority: Minor
>
> h2. Problem
> Currently the plugin just prints the number of processed artifacts once it is
> done, for example:
> {quote}
> 2 archive(s) processed
> {quote}
> This has these disadvantages:
> - It is not immediately obvious if the intended file has been signed (e.g.
> when using wildcards)
> - If the number is higher than expected, it is not obvious which additional
> files were signed redundantly
> In both cases it is necessary to manually inspect the artifacts of the
> project and check if they have been signed (or use {{jarsigner}} to verify
> them).
> h2. Improvement
> By default the plugin should print the file names of the signed artifacts.
> This information is already available in {{AbstractJarsignerMojo#execute}},
> but currently only {{archives.size()}} is logged.
> - Ideally each file should be logged in a separate line to be easier to read.
> - The relative file path (and not only the file name) should be logged.
> Otherwise there might be confusion if the same file exists in multiple
> directories, e.g. if it is copied by another plugin during the build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MJARSIGNER-76] Print names of processed files [maven-jarsigner-plugin]
schedin commented on PR #20: URL: https://github.com/apache/maven-jarsigner-plugin/pull/20#issuecomment-2212361904 I think this is a useful feature and one that I have missed! I'm not sure the state of this open source project at the moment. I have tried to push the maintainers for a 3.1.0 release but so far been unsuccessful. I'm tagging @elharo and @slachiewicz again. -- 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
