Re: [PR] Bump resolverVersion from 1.9.18 to 1.9.19 [maven-resolver-ant-tasks]
dependabot[bot] commented on PR #38: URL: https://github.com/apache/maven-resolver-ant-tasks/pull/38#issuecomment-2084425284 Superseded by #39. -- 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.19 [maven-resolver-ant-tasks]
dependabot[bot] closed pull request #38: Bump resolverVersion from 1.9.18 to 1.9.19 URL: https://github.com/apache/maven-resolver-ant-tasks/pull/38 -- 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 1.9.20 [maven-resolver-ant-tasks]
dependabot[bot] opened a new pull request, #39: URL: https://github.com/apache/maven-resolver-ant-tasks/pull/39 Bumps `resolverVersion` from 1.9.18 to 1.9.20. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-api's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent POM 42 (https://redirect.github.com/apache/maven-resolver/issues/484;>#484) https://github.com/apache/maven-resolver/commit/4f16d5ecd94f85e6e7d793e6b6b82f20c9afbf56;>4f16d5e [MRESOLVER-547] Just use setVersion (https://redirect.github.com/apache/maven-resolver/issues/483;>#483) https://github.com/apache/maven-resolver/commit/c1b24c699621930f4eb77721400f2f6c46930626;>c1b24c6 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-resolver/commit/c1b03574961fd2daa7a678bb3fbf9f0779afee56;>c1b0357 [maven-release-plugin] prepare release maven-resolver-1.9.19 https://github.com/apache/maven-resolver/commit/adadd42d1642f39bafedb2ddd619b044fecb12b0;>adadd42 [MRESOLVER-536] Do not belly up if FS does not support setting mtime (https://redirect.github.com/apache/maven-resolver/issues/469;>#469) https://github.com/apache/maven-resolver/commit/31df8a3dc503895172d277de56b1c4a53da0a27c;>31df8a3 [1.9.x] Update dependencies (https://redirect.github.com/apache/maven-resolver/issues/462;>#462) https://github.com/apache/maven-resolver/commit/b225076e5d5b2fe3f166a4018802ac94b7cc94f7;>b225076 [MRESOLVER-522] Improve congested file locks behaviour (https://redirect.github.com/apache/maven-resolver/issues/455;>#455) (https://redirect.github.com/apache/maven-resolver/issues/461;>#461) https://github.com/apache/maven-resolver/commit/fc969c2570041bb72c3f0141ff4957e8754f365c;>fc969c2 [1.9.x][MRESOLVER-483] Fix path concatenation logic (https://redirect.github.com/apache/maven-resolver/issues/420;>#420) https://github.com/apache/maven-resolver/commit/a3e620d6d2ab6ca58d42d264347341b31da00dde;>a3e620d Use one Maven in CI Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.18...maven-resolver-1.9.20;>compare view Updates `org.apache.maven.resolver:maven-resolver-util` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-util's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551]
Re: [PR] Bump resolver.version from 1.9.18 to 1.9.19 [maven-indexer]
dependabot[bot] commented on PR #361: URL: https://github.com/apache/maven-indexer/pull/361#issuecomment-2084363088 Superseded by #362. -- 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 resolver.version from 1.9.18 to 1.9.19 [maven-indexer]
dependabot[bot] closed pull request #361: Bump resolver.version from 1.9.18 to 1.9.19 URL: https://github.com/apache/maven-indexer/pull/361 -- 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 resolver.version from 1.9.18 to 1.9.20 [maven-indexer]
dependabot[bot] opened a new pull request, #362: URL: https://github.com/apache/maven-indexer/pull/362 Bumps `resolver.version` from 1.9.18 to 1.9.20. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-api's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent POM 42 (https://redirect.github.com/apache/maven-resolver/issues/484;>#484) https://github.com/apache/maven-resolver/commit/4f16d5ecd94f85e6e7d793e6b6b82f20c9afbf56;>4f16d5e [MRESOLVER-547] Just use setVersion (https://redirect.github.com/apache/maven-resolver/issues/483;>#483) https://github.com/apache/maven-resolver/commit/c1b24c699621930f4eb77721400f2f6c46930626;>c1b24c6 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-resolver/commit/c1b03574961fd2daa7a678bb3fbf9f0779afee56;>c1b0357 [maven-release-plugin] prepare release maven-resolver-1.9.19 https://github.com/apache/maven-resolver/commit/adadd42d1642f39bafedb2ddd619b044fecb12b0;>adadd42 [MRESOLVER-536] Do not belly up if FS does not support setting mtime (https://redirect.github.com/apache/maven-resolver/issues/469;>#469) https://github.com/apache/maven-resolver/commit/31df8a3dc503895172d277de56b1c4a53da0a27c;>31df8a3 [1.9.x] Update dependencies (https://redirect.github.com/apache/maven-resolver/issues/462;>#462) https://github.com/apache/maven-resolver/commit/b225076e5d5b2fe3f166a4018802ac94b7cc94f7;>b225076 [MRESOLVER-522] Improve congested file locks behaviour (https://redirect.github.com/apache/maven-resolver/issues/455;>#455) (https://redirect.github.com/apache/maven-resolver/issues/461;>#461) https://github.com/apache/maven-resolver/commit/fc969c2570041bb72c3f0141ff4957e8754f365c;>fc969c2 [1.9.x][MRESOLVER-483] Fix path concatenation logic (https://redirect.github.com/apache/maven-resolver/issues/420;>#420) https://github.com/apache/maven-resolver/commit/a3e620d6d2ab6ca58d42d264347341b31da00dde;>a3e620d Use one Maven in CI Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.18...maven-resolver-1.9.20;>compare view Updates `org.apache.maven.resolver:maven-resolver-util` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-util's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent POM
Re: [PR] Bump resolverVersion from 1.9.18 to 1.9.19 [maven-gpg-plugin]
dependabot[bot] closed pull request #99: Bump resolverVersion from 1.9.18 to 1.9.19 URL: https://github.com/apache/maven-gpg-plugin/pull/99 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump resolverVersion from 1.9.18 to 1.9.19 [maven-gpg-plugin]
dependabot[bot] commented on PR #99: URL: https://github.com/apache/maven-gpg-plugin/pull/99#issuecomment-2084357297 Superseded by #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 1.9.20 [maven-gpg-plugin]
dependabot[bot] opened a new pull request, #101: URL: https://github.com/apache/maven-gpg-plugin/pull/101 Bumps `resolverVersion` from 1.9.18 to 1.9.20. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-api's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent POM 42 (https://redirect.github.com/apache/maven-resolver/issues/484;>#484) https://github.com/apache/maven-resolver/commit/4f16d5ecd94f85e6e7d793e6b6b82f20c9afbf56;>4f16d5e [MRESOLVER-547] Just use setVersion (https://redirect.github.com/apache/maven-resolver/issues/483;>#483) https://github.com/apache/maven-resolver/commit/c1b24c699621930f4eb77721400f2f6c46930626;>c1b24c6 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-resolver/commit/c1b03574961fd2daa7a678bb3fbf9f0779afee56;>c1b0357 [maven-release-plugin] prepare release maven-resolver-1.9.19 https://github.com/apache/maven-resolver/commit/adadd42d1642f39bafedb2ddd619b044fecb12b0;>adadd42 [MRESOLVER-536] Do not belly up if FS does not support setting mtime (https://redirect.github.com/apache/maven-resolver/issues/469;>#469) https://github.com/apache/maven-resolver/commit/31df8a3dc503895172d277de56b1c4a53da0a27c;>31df8a3 [1.9.x] Update dependencies (https://redirect.github.com/apache/maven-resolver/issues/462;>#462) https://github.com/apache/maven-resolver/commit/b225076e5d5b2fe3f166a4018802ac94b7cc94f7;>b225076 [MRESOLVER-522] Improve congested file locks behaviour (https://redirect.github.com/apache/maven-resolver/issues/455;>#455) (https://redirect.github.com/apache/maven-resolver/issues/461;>#461) https://github.com/apache/maven-resolver/commit/fc969c2570041bb72c3f0141ff4957e8754f365c;>fc969c2 [1.9.x][MRESOLVER-483] Fix path concatenation logic (https://redirect.github.com/apache/maven-resolver/issues/420;>#420) https://github.com/apache/maven-resolver/commit/a3e620d6d2ab6ca58d42d264347341b31da00dde;>a3e620d Use one Maven in CI Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.18...maven-resolver-1.9.20;>compare view Updates `org.apache.maven.resolver:maven-resolver-util` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-util's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent POM
Re: [PR] Bump resolverVersion from 1.9.18 to 1.9.19 [maven-install-plugin]
dependabot[bot] closed pull request #63: Bump resolverVersion from 1.9.18 to 1.9.19 URL: https://github.com/apache/maven-install-plugin/pull/63 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump resolverVersion from 1.9.18 to 1.9.19 [maven-install-plugin]
dependabot[bot] commented on PR #63: URL: https://github.com/apache/maven-install-plugin/pull/63#issuecomment-2084352830 Superseded by #65. -- 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 1.9.20 [maven-install-plugin]
dependabot[bot] opened a new pull request, #65: URL: https://github.com/apache/maven-install-plugin/pull/65 Bumps `resolverVersion` from 1.9.18 to 1.9.20. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-api's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent POM 42 (https://redirect.github.com/apache/maven-resolver/issues/484;>#484) https://github.com/apache/maven-resolver/commit/4f16d5ecd94f85e6e7d793e6b6b82f20c9afbf56;>4f16d5e [MRESOLVER-547] Just use setVersion (https://redirect.github.com/apache/maven-resolver/issues/483;>#483) https://github.com/apache/maven-resolver/commit/c1b24c699621930f4eb77721400f2f6c46930626;>c1b24c6 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-resolver/commit/c1b03574961fd2daa7a678bb3fbf9f0779afee56;>c1b0357 [maven-release-plugin] prepare release maven-resolver-1.9.19 https://github.com/apache/maven-resolver/commit/adadd42d1642f39bafedb2ddd619b044fecb12b0;>adadd42 [MRESOLVER-536] Do not belly up if FS does not support setting mtime (https://redirect.github.com/apache/maven-resolver/issues/469;>#469) https://github.com/apache/maven-resolver/commit/31df8a3dc503895172d277de56b1c4a53da0a27c;>31df8a3 [1.9.x] Update dependencies (https://redirect.github.com/apache/maven-resolver/issues/462;>#462) https://github.com/apache/maven-resolver/commit/b225076e5d5b2fe3f166a4018802ac94b7cc94f7;>b225076 [MRESOLVER-522] Improve congested file locks behaviour (https://redirect.github.com/apache/maven-resolver/issues/455;>#455) (https://redirect.github.com/apache/maven-resolver/issues/461;>#461) https://github.com/apache/maven-resolver/commit/fc969c2570041bb72c3f0141ff4957e8754f365c;>fc969c2 [1.9.x][MRESOLVER-483] Fix path concatenation logic (https://redirect.github.com/apache/maven-resolver/issues/420;>#420) https://github.com/apache/maven-resolver/commit/a3e620d6d2ab6ca58d42d264347341b31da00dde;>a3e620d Use one Maven in CI Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.18...maven-resolver-1.9.20;>compare view Updates `org.apache.maven.resolver:maven-resolver-util` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-util's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent
[PR] Bump org.apache.maven.plugins:maven-install-plugin from 3.1.1 to 3.1.2 [maven-apache-parent]
dependabot[bot] opened a new pull request, #222: URL: https://github.com/apache/maven-apache-parent/pull/222 Bumps [org.apache.maven.plugins:maven-install-plugin](https://github.com/apache/maven-install-plugin) from 3.1.1 to 3.1.2. Release notes Sourced from https://github.com/apache/maven-install-plugin/releases;>org.apache.maven.plugins:maven-install-plugin's releases. 3.1.2 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317524version=12353548;>Release Notes - Maven Install Plugin - Version 3.1.2 What's Changed [MNG-6829] Replace StringUtils#isEmpty(String) #isNotEmpty(String) by https://github.com/timtebeek;>@timtebeek in https://redirect.github.com/apache/maven-install-plugin/pull/58;>apache/maven-install-plugin#58 [MINSTALL-197] Update to parent 41, cleanup by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-install-plugin/pull/61;>apache/maven-install-plugin#61 [MINSTALL-193] Parent 42, min Maven 3.6.3 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-install-plugin/pull/64;>apache/maven-install-plugin#64 New Contributors https://github.com/timtebeek;>@timtebeek made their first contribution in https://redirect.github.com/apache/maven-install-plugin/pull/58;>apache/maven-install-plugin#58 Full Changelog: https://github.com/apache/maven-install-plugin/compare/maven-install-plugin-3.1.1...maven-install-plugin-3.1.2;>https://github.com/apache/maven-install-plugin/compare/maven-install-plugin-3.1.1...maven-install-plugin-3.1.2 Commits https://github.com/apache/maven-install-plugin/commit/e1494c1296b022b72b19f2a3a1a1cf702495253f;>e1494c1 [maven-release-plugin] prepare release maven-install-plugin-3.1.2 https://github.com/apache/maven-install-plugin/commit/6712ae82ed5943218fc63dd08f2ec5583532c5b7;>6712ae8 Remove workaround, handle it centrally https://github.com/apache/maven-install-plugin/commit/1fa847f674199397696ddb61661ddbc70a6875e5;>1fa847f Bump workflow https://github.com/apache/maven-install-plugin/commit/bdc93d5a648ae96968bd1ee8eb5ad6964f7de4fc;>bdc93d5 Quickfix: move to zulu https://github.com/apache/maven-install-plugin/commit/7b9bf5138c482000dc0b8654ef88b35c17d3073d;>7b9bf51 [MINSTALL-193] Parent 42, min Maven 3.6.3 (https://redirect.github.com/apache/maven-install-plugin/issues/64;>#64) https://github.com/apache/maven-install-plugin/commit/e9143678bac698483693b3b2ed2d58407920;>e914367 [MINSTALL-195] Include artifactId in InstallMojo#processProject messages https://github.com/apache/maven-install-plugin/commit/3ebb44860673e141e3d5f680df434cd5ac61d46b;>3ebb448 [MINSTALL-197] Update to parent 41, cleanup (https://redirect.github.com/apache/maven-install-plugin/issues/61;>#61) https://github.com/apache/maven-install-plugin/commit/30d2b530f7199bed86a03caf53cf884f68e76376;>30d2b53 [MINSTALL-192] - Code cleanups https://github.com/apache/maven-install-plugin/commit/429ad5b9fcd3e700f8ce6d3f42cc135a740e20ba;>429ad5b [MNG-6829] Replace StringUtils#isEmpty(String) #isNotEmpty(String) (https://redirect.github.com/apache/maven-install-plugin/issues/58;>#58) https://github.com/apache/maven-install-plugin/commit/f6377c406baf35fb148fc320f0c10de78e70639b;>f6377c4 configure notifications Additional commits viewable in https://github.com/apache/maven-install-plugin/compare/maven-install-plugin-3.1.1...maven-install-plugin-3.1.2;>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
[PR] Bump org.apache.maven.plugins:maven-deploy-plugin from 3.1.1 to 3.1.2 [maven-apache-parent]
dependabot[bot] opened a new pull request, #221: URL: https://github.com/apache/maven-apache-parent/pull/221 Bumps [org.apache.maven.plugins:maven-deploy-plugin](https://github.com/apache/maven-deploy-plugin) from 3.1.1 to 3.1.2. Release notes Sourced from https://github.com/apache/maven-deploy-plugin/releases;>org.apache.maven.plugins:maven-deploy-plugin's releases. 3.1.2 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317228version=12354128;>Release Notes - Maven Deploy Plugin - Version 3.1.2 What's Changed [MNG-6829] Replace StringUtils#isEmpty(String) #isNotEmpty(String) by https://github.com/timtebeek;>@timtebeek in https://redirect.github.com/apache/maven-deploy-plugin/pull/40;>apache/maven-deploy-plugin#40 Type: fill -- file by https://github.com/elharo;>@elharo in https://redirect.github.com/apache/maven-deploy-plugin/pull/41;>apache/maven-deploy-plugin#41 DeployFileMojo#readModel(File): fixed MojoExecutionException javadoc by https://github.com/Scrappers-glitch;>@Scrappers-glitch in https://redirect.github.com/apache/maven-deploy-plugin/pull/43;>apache/maven-deploy-plugin#43 [MDEPLOY-313] Update to parent 41, cleanup by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-deploy-plugin/pull/47;>apache/maven-deploy-plugin#47 Bump apache/maven-gh-actions-shared from 3 to 4 by https://github.com/dependabot;>@dependabot in https://redirect.github.com/apache/maven-deploy-plugin/pull/50;>apache/maven-deploy-plugin#50 Bump org.mockito:mockito-core from 2.28.2 to 4.11.0 by https://github.com/dependabot;>@dependabot in https://redirect.github.com/apache/maven-deploy-plugin/pull/51;>apache/maven-deploy-plugin#51 [MDEPLOY-316] Parent 42 and prerequisite 3.6.3 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-deploy-plugin/pull/54;>apache/maven-deploy-plugin#54 New Contributors https://github.com/timtebeek;>@timtebeek made their first contribution in https://redirect.github.com/apache/maven-deploy-plugin/pull/40;>apache/maven-deploy-plugin#40 https://github.com/Scrappers-glitch;>@Scrappers-glitch made their first contribution in https://redirect.github.com/apache/maven-deploy-plugin/pull/43;>apache/maven-deploy-plugin#43 https://github.com/dependabot;>@dependabot made their first contribution in https://redirect.github.com/apache/maven-deploy-plugin/pull/50;>apache/maven-deploy-plugin#50 Full Changelog: https://github.com/apache/maven-deploy-plugin/compare/maven-deploy-plugin-3.1.1...maven-deploy-plugin-3.1.2;>https://github.com/apache/maven-deploy-plugin/compare/maven-deploy-plugin-3.1.1...maven-deploy-plugin-3.1.2 Commits https://github.com/apache/maven-deploy-plugin/commit/4f016bce38dd9016f7c0357a75fbbe3427ed8b31;>4f016bc [maven-release-plugin] prepare release maven-deploy-plugin-3.1.2 https://github.com/apache/maven-deploy-plugin/commit/0ed18be3d93fa0f28886d47a664c8eff2590c944;>0ed18be Remove workaround, handle it centrally https://github.com/apache/maven-deploy-plugin/commit/b9c1c8bc486c7defb92171e1ea9169075b76695c;>b9c1c8b [MDEPLOY-314] Include artifactId in DeployMojo#processProject messages https://github.com/apache/maven-deploy-plugin/commit/74d331be89ed010b5d38dc6e755dcab327baf56c;>74d331b [MDEPLOY-316] Parent 42 and prerequisite 3.6.3 (https://redirect.github.com/apache/maven-deploy-plugin/issues/54;>#54) https://github.com/apache/maven-deploy-plugin/commit/ac9c49dd973ed2ca806066e4da8c296cc603b4e1;>ac9c49d Bump org.mockito:mockito-core from 2.28.2 to 4.11.0 https://github.com/apache/maven-deploy-plugin/commit/de7cefbd3da75e28a4c49caa674d06cd32d820f5;>de7cefb Bump apache/maven-gh-actions-shared from 3 to 4 https://github.com/apache/maven-deploy-plugin/commit/edf85d72c5dd03f19fcf06b96b172573e8e4a696;>edf85d7 Add Dependabot https://github.com/apache/maven-deploy-plugin/commit/390e610c65ef0ec2ec0e4851d7e1eaf53e7787f3;>390e610 [MDEPLOY-313] Update to parent 41, cleanup (https://redirect.github.com/apache/maven-deploy-plugin/issues/47;>#47) https://github.com/apache/maven-deploy-plugin/commit/29f3c81dfc5e3e603bf68870075161dc674680dc;>29f3c81 DeployFileMojo#readModel(File): fixed MojoExecutionException javadoc https://github.com/apache/maven-deploy-plugin/commit/9039fc610f67dfd101a3e4bb8b7510994b2656d0;>9039fc6 Type: fill -- file Additional commits viewable in https://github.com/apache/maven-deploy-plugin/compare/maven-deploy-plugin-3.1.1...maven-deploy-plugin-3.1.2;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any
Re: [PR] Bump resolverVersion from 1.9.18 to 1.9.19 [maven-artifact-plugin]
dependabot[bot] closed pull request #33: Bump resolverVersion from 1.9.18 to 1.9.19 URL: https://github.com/apache/maven-artifact-plugin/pull/33 -- 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.19 [maven-artifact-plugin]
dependabot[bot] commented on PR #33: URL: https://github.com/apache/maven-artifact-plugin/pull/33#issuecomment-2084338553 Superseded by #42. -- 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 1.9.20 [maven-artifact-plugin]
dependabot[bot] opened a new pull request, #42: URL: https://github.com/apache/maven-artifact-plugin/pull/42 Bumps `resolverVersion` from 1.9.18 to 1.9.20. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-api's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent POM 42 (https://redirect.github.com/apache/maven-resolver/issues/484;>#484) https://github.com/apache/maven-resolver/commit/4f16d5ecd94f85e6e7d793e6b6b82f20c9afbf56;>4f16d5e [MRESOLVER-547] Just use setVersion (https://redirect.github.com/apache/maven-resolver/issues/483;>#483) https://github.com/apache/maven-resolver/commit/c1b24c699621930f4eb77721400f2f6c46930626;>c1b24c6 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-resolver/commit/c1b03574961fd2daa7a678bb3fbf9f0779afee56;>c1b0357 [maven-release-plugin] prepare release maven-resolver-1.9.19 https://github.com/apache/maven-resolver/commit/adadd42d1642f39bafedb2ddd619b044fecb12b0;>adadd42 [MRESOLVER-536] Do not belly up if FS does not support setting mtime (https://redirect.github.com/apache/maven-resolver/issues/469;>#469) https://github.com/apache/maven-resolver/commit/31df8a3dc503895172d277de56b1c4a53da0a27c;>31df8a3 [1.9.x] Update dependencies (https://redirect.github.com/apache/maven-resolver/issues/462;>#462) https://github.com/apache/maven-resolver/commit/b225076e5d5b2fe3f166a4018802ac94b7cc94f7;>b225076 [MRESOLVER-522] Improve congested file locks behaviour (https://redirect.github.com/apache/maven-resolver/issues/455;>#455) (https://redirect.github.com/apache/maven-resolver/issues/461;>#461) https://github.com/apache/maven-resolver/commit/fc969c2570041bb72c3f0141ff4957e8754f365c;>fc969c2 [1.9.x][MRESOLVER-483] Fix path concatenation logic (https://redirect.github.com/apache/maven-resolver/issues/420;>#420) https://github.com/apache/maven-resolver/commit/a3e620d6d2ab6ca58d42d264347341b31da00dde;>a3e620d Use one Maven in CI Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.18...maven-resolver-1.9.20;>compare view Updates `org.apache.maven.resolver:maven-resolver-util` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-util's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent
[PR] Bump org.apache.maven.resolver:maven-resolver-api from 1.9.18 to 1.9.20 [maven-wrapper]
dependabot[bot] opened a new pull request, #136: URL: https://github.com/apache/maven-wrapper/pull/136 Bumps [org.apache.maven.resolver:maven-resolver-api](https://github.com/apache/maven-resolver) from 1.9.18 to 1.9.20. Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-api's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent POM 42 (https://redirect.github.com/apache/maven-resolver/issues/484;>#484) https://github.com/apache/maven-resolver/commit/4f16d5ecd94f85e6e7d793e6b6b82f20c9afbf56;>4f16d5e [MRESOLVER-547] Just use setVersion (https://redirect.github.com/apache/maven-resolver/issues/483;>#483) https://github.com/apache/maven-resolver/commit/c1b24c699621930f4eb77721400f2f6c46930626;>c1b24c6 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-resolver/commit/c1b03574961fd2daa7a678bb3fbf9f0779afee56;>c1b0357 [maven-release-plugin] prepare release maven-resolver-1.9.19 https://github.com/apache/maven-resolver/commit/adadd42d1642f39bafedb2ddd619b044fecb12b0;>adadd42 [MRESOLVER-536] Do not belly up if FS does not support setting mtime (https://redirect.github.com/apache/maven-resolver/issues/469;>#469) https://github.com/apache/maven-resolver/commit/31df8a3dc503895172d277de56b1c4a53da0a27c;>31df8a3 [1.9.x] Update dependencies (https://redirect.github.com/apache/maven-resolver/issues/462;>#462) https://github.com/apache/maven-resolver/commit/b225076e5d5b2fe3f166a4018802ac94b7cc94f7;>b225076 [MRESOLVER-522] Improve congested file locks behaviour (https://redirect.github.com/apache/maven-resolver/issues/455;>#455) (https://redirect.github.com/apache/maven-resolver/issues/461;>#461) https://github.com/apache/maven-resolver/commit/fc969c2570041bb72c3f0141ff4957e8754f365c;>fc969c2 [1.9.x][MRESOLVER-483] Fix path concatenation logic (https://redirect.github.com/apache/maven-resolver/issues/420;>#420) https://github.com/apache/maven-resolver/commit/a3e620d6d2ab6ca58d42d264347341b31da00dde;>a3e620d Use one Maven in CI Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.18...maven-resolver-1.9.20;>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
Re: [PR] Bump org.apache.maven.resolver:maven-resolver-api from 1.9.18 to 1.9.19 [maven-wrapper]
dependabot[bot] commented on PR #134: URL: https://github.com/apache/maven-wrapper/pull/134#issuecomment-2084064830 Superseded by #136. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.maven.resolver:maven-resolver-api from 1.9.18 to 1.9.19 [maven-wrapper]
dependabot[bot] closed pull request #134: Bump org.apache.maven.resolver:maven-resolver-api from 1.9.18 to 1.9.19 URL: https://github.com/apache/maven-wrapper/pull/134 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump org.htmlunit:htmlunit from 4.0.0 to 4.1.0 [maven-doxia-sitetools]
dependabot[bot] opened a new pull request, #152: URL: https://github.com/apache/maven-doxia-sitetools/pull/152 Bumps [org.htmlunit:htmlunit](https://github.com/HtmlUnit/htmlunit) from 4.0.0 to 4.1.0. Release notes Sourced from https://github.com/HtmlUnit/htmlunit/releases;>org.htmlunit:htmlunit's releases. HtmlUnit 4.1.0 Highlights This release is not compatible with 3.xx versions Chrome/Edge 124, Firefox 125 some deprecations to prepare moving to HTTP/2 improved encoding support (based on improvements done for the neko html parser) as usual some core-js fixes Please have a look at the https://www.htmlunit.org/changes-report.html#a4.1.0;>full release notes for details about this release. Thank you to all who have contributed and to the sponsors (more sponsoring is welcome https://github.com/sponsors/rbri;>https://github.com/sponsors/rbri). Full Changelog: https://github.com/HtmlUnit/htmlunit/compare/4.0.0...4.1.0;>https://github.com/HtmlUnit/htmlunit/compare/4.0.0...4.1.0 Commits https://github.com/HtmlUnit/htmlunit/commit/3a74aa1a8bd1c33d960791bc6ce079b090073c24;>3a74aa1 ups https://github.com/HtmlUnit/htmlunit/commit/5dd84bb85df68a0b1f4c511b9f7fca1fe258ed02;>5dd84bb version 4.1.0 https://github.com/HtmlUnit/htmlunit/commit/a51ddc7ecd3d3926f948cc2b636811b777e361a4;>a51ddc7 customize the fluido skin to remove some of the link decorations https://github.com/HtmlUnit/htmlunit/commit/fcee702f794a02246e9c2c12c3fdd80cd8df3b0a;>fcee702 add a bit more info about sponsoring https://github.com/HtmlUnit/htmlunit/commit/b0f9b3d85a613a463974ff9310b688adec58dd1c;>b0f9b3d core-js released https://github.com/HtmlUnit/htmlunit/commit/040d155f823729d51d0751de71a593029062000c;>040d155 upgrade commons-codec to 1.17.0 https://github.com/HtmlUnit/htmlunit/commit/6f68a420e5330c87800bf59e8f9ea9f069ef1b02;>6f68a42 always use commons codec base64 https://github.com/HtmlUnit/htmlunit/commit/2886a98fd8f2e8041db46066bc85c55b4db2dc02;>2886a98 the libs are released https://github.com/HtmlUnit/htmlunit/commit/a64d5a88a1df06c7a3419afcadb9a1750e10909f;>a64d5a8 pmd fixes https://github.com/HtmlUnit/htmlunit/commit/fb4c098281fa345278cfeeb52b552c8fe9b6ef2b;>fb4c098 Internal class WebClientInternals removed Additional commits viewable in https://github.com/HtmlUnit/htmlunit/compare/4.0.0...4.1.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
[jira] [Commented] (MNG-8111) Version 3.9.6 is not reproducible
[
https://issues.apache.org/jira/browse/MNG-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842175#comment-17842175
]
Slawomir Jaranowski commented on MNG-8111:
--
Maven 3.9.6 was build by JDK 21 ... so maybe it is a difference when you use
JDK 8
Please look at
[https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/maven/README.md]
> Version 3.9.6 is not reproducible
> -
>
> Key: MNG-8111
> URL: https://issues.apache.org/jira/browse/MNG-8111
> Project: Maven
> Issue Type: Bug
> Components: Core, General
>Affects Versions: 3.9.6
> Environment: Arch Linux updated (29/04/2024)
>Reporter: Leonidas Spyropoulos
>Priority: Major
> Labels: reproducibility
>
> Version 3.9.6 is not reproducible. It seems like the compiled classes are
> different.
> - JDK used: OpenJDK version 8.412.u08
> - Command line used:
> {code:bash}
> mvn package \
> -DbuildNumber="bc0240f3c744dd6b6ec2920b3cd08dcc295161ae" \
> -Dline.separator=$'\r\n' \
> -Dproject.build.sourceEncoding=UTF-8 -e \
> -Dmaven.repo.local="./repo" \
> -DskipTests
> {code}
> buildNumber is found from:
> {code}
> bsdtar xOf <(bsdtar xOf apache-maven-3.9.6-bin.tar.gz
> apache-maven-3.9.6/lib/maven-core-3.9.6.jar) \
> org/apache/maven/messages/build.properties | grep buildNumber | cut -d=
> -f2 | tr -cd '[:print:]'
> {code}
> Relevant issue: https://issues.apache.org/jira/browse/MNG-6276
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump org.htmlunit:htmlunit from 3.11.0 to 4.0.0 [maven-surefire]
dependabot[bot] closed pull request #730: Bump org.htmlunit:htmlunit from 3.11.0 to 4.0.0 URL: https://github.com/apache/maven-surefire/pull/730 -- 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.htmlunit:htmlunit from 3.11.0 to 4.0.0 [maven-surefire]
dependabot[bot] commented on PR #730: URL: https://github.com/apache/maven-surefire/pull/730#issuecomment-2083559994 Superseded by #733. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump org.xmlunit:xmlunit-core from 2.9.1 to 2.10.0 [maven-surefire]
dependabot[bot] opened a new pull request, #732: URL: https://github.com/apache/maven-surefire/pull/732 Bumps [org.xmlunit:xmlunit-core](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-core'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-core'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 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 - `@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 -
[PR] Bump org.htmlunit:htmlunit from 3.11.0 to 4.1.0 [maven-surefire]
dependabot[bot] opened a new pull request, #733: URL: https://github.com/apache/maven-surefire/pull/733 Bumps [org.htmlunit:htmlunit](https://github.com/HtmlUnit/htmlunit) from 3.11.0 to 4.1.0. Release notes Sourced from https://github.com/HtmlUnit/htmlunit/releases;>org.htmlunit:htmlunit's releases. HtmlUnit 4.1.0 Highlights This release is not compatible with 3.xx versions Chrome/Edge 124, Firefox 125 some deprecations to prepare moving to HTTP/2 improved encoding support (based on improvements done for the neko html parser) as usual some core-js fixes Please have a look at the https://www.htmlunit.org/changes-report.html#a4.1.0;>full release notes for details about this release. Thank you to all who have contributed and to the sponsors (more sponsoring is welcome https://github.com/sponsors/rbri;>https://github.com/sponsors/rbri). Full Changelog: https://github.com/HtmlUnit/htmlunit/compare/4.0.0...4.1.0;>https://github.com/HtmlUnit/htmlunit/compare/4.0.0...4.1.0 HtmlUnit 4.0.0 Highlights This release is not compatible with 3.xx versions Internet Explorer is no longer supported Chrome/Edge 123, Firefox 124 new subproject htmlunit-websocket-client many fixes for the neko html parser improved encoding support as usual some core-js fixes Please have a look at the https://www.htmlunit.org/changes-report.html#a4.0.0;>full release notes for details about this release. Thank you to all who have contributed and to the sponsors (more sponsoring is welcome https://github.com/sponsors/rbri;>https://github.com/sponsors/rbri). Full Changelog: https://github.com/HtmlUnit/htmlunit/compare/3.11.0...4.0.0;>https://github.com/HtmlUnit/htmlunit/compare/3.11.0...4.0.0 Commits https://github.com/HtmlUnit/htmlunit/commit/3a74aa1a8bd1c33d960791bc6ce079b090073c24;>3a74aa1 ups https://github.com/HtmlUnit/htmlunit/commit/5dd84bb85df68a0b1f4c511b9f7fca1fe258ed02;>5dd84bb version 4.1.0 https://github.com/HtmlUnit/htmlunit/commit/a51ddc7ecd3d3926f948cc2b636811b777e361a4;>a51ddc7 customize the fluido skin to remove some of the link decorations https://github.com/HtmlUnit/htmlunit/commit/fcee702f794a02246e9c2c12c3fdd80cd8df3b0a;>fcee702 add a bit more info about sponsoring https://github.com/HtmlUnit/htmlunit/commit/b0f9b3d85a613a463974ff9310b688adec58dd1c;>b0f9b3d core-js released https://github.com/HtmlUnit/htmlunit/commit/040d155f823729d51d0751de71a593029062000c;>040d155 upgrade commons-codec to 1.17.0 https://github.com/HtmlUnit/htmlunit/commit/6f68a420e5330c87800bf59e8f9ea9f069ef1b02;>6f68a42 always use commons codec base64 https://github.com/HtmlUnit/htmlunit/commit/2886a98fd8f2e8041db46066bc85c55b4db2dc02;>2886a98 the libs are released https://github.com/HtmlUnit/htmlunit/commit/a64d5a88a1df06c7a3419afcadb9a1750e10909f;>a64d5a8 pmd fixes https://github.com/HtmlUnit/htmlunit/commit/fb4c098281fa345278cfeeb52b552c8fe9b6ef2b;>fb4c098 Internal class WebClientInternals removed Additional commits viewable in https://github.com/HtmlUnit/htmlunit/compare/3.11.0...4.1.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
[jira] [Updated] (MNG-8112) extension.xml is ignored when extension is loaded by -Dmaven.ext.class.path
[ https://issues.apache.org/jira/browse/MNG-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich DiCroce updated MNG-8112: -- Description: As the title says: extension.xml is ignored when an extension is loaded by -Dmaven.ext.class.path, which makes it impossible to expose any additional packages. I am filing this as a bug due to [this comment|https://issues.apache.org/jira/browse/MNG-6906?focusedCommentId=17719869=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17719869] on MNG-6906, which says that lib/ext and -Dmaven.ext.class.path are supposed to be synonymous. Note that MNG-6906 is a related but different problem. When looking at org.apache.maven.cli.MavenCli, the problems aren't too hard to see: # lib/ext extensions get loaded into the plexus.core realm (as per m2.conf), but -Dmaven.ext.class.path extensions are loaded into the maven.ext realm (as per MavenCli#setupContainerRealm()). # loadCoreExtensions() operates on the coreRealm, but due to #1, the extensions are not in that realm. Also, the result of parseExtClasspath() is not passed to loadCoreExtensions(), so there is no way for loadCoreExtensions() to find the relevant files. The most obvious solution would be to call coreRealm.addURL() for each of the files discovered by parseExtClasspath(). This would solve #1 above which would implicitly fix #2. Though I don't know if it would have other consequences. If this is not a bug and is instead "works as designed", then [https://maven.apache.org/guides/mini/guide-using-extensions.html] needs to be updated to explain that the three methods of loading core extensions are not equivalent. was: As the title says: extension.xml is ignored when an extension is loaded by -Dmaven.ext.class.path, which makes it impossible to expose any additional packages. I am filing this as a bug due to this comment on MNG-6906, which says that lib/ext and -Dmaven.ext.class.path are supposed to be synonymous. Note that MNG-6906 is a related but different problem. When looking at org.apache.maven.cli.MavenCli, the problems aren't too hard to see: # lib/ext extensions get loaded into the plexus.core realm (as per m2.conf), but -Dmaven.ext.class.path extensions are loaded into the maven.ext realm (as per MavenCli#setupContainerRealm()). # loadCoreExtensions() operates on the coreRealm, but due to #1, the extensions are not in that realm. Also, the result of parseExtClasspath() is not passed to loadCoreExtensions(), so there is no way for loadCoreExtensions() to find the relevant files. The most obvious solution would be to call coreRealm.addURL() for each of the files discovered by parseExtClasspath(). This would solve #1 above which would implicitly fix #2. Though I don't know if it would have other consequences. If this is not a bug and is instead "works as designed", then [https://maven.apache.org/guides/mini/guide-using-extensions.html] needs to be updated to explain that the three methods of loading core extensions are not equivalent. > extension.xml is ignored when extension is loaded by -Dmaven.ext.class.path > --- > > Key: MNG-8112 > URL: https://issues.apache.org/jira/browse/MNG-8112 > Project: Maven > Issue Type: Bug > Components: Class Loading >Affects Versions: 3.9.6 >Reporter: Rich DiCroce >Priority: Major > > As the title says: extension.xml is ignored when an extension is loaded by > -Dmaven.ext.class.path, which makes it impossible to expose any additional > packages. > I am filing this as a bug due to [this > comment|https://issues.apache.org/jira/browse/MNG-6906?focusedCommentId=17719869=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17719869] > on MNG-6906, which says that lib/ext and -Dmaven.ext.class.path are supposed > to be synonymous. Note that MNG-6906 is a related but different problem. > When looking at org.apache.maven.cli.MavenCli, the problems aren't too hard > to see: > # lib/ext extensions get loaded into the plexus.core realm (as per m2.conf), > but -Dmaven.ext.class.path extensions are loaded into the maven.ext realm (as > per MavenCli#setupContainerRealm()). > # loadCoreExtensions() operates on the coreRealm, but due to #1, the > extensions are not in that realm. Also, the result of parseExtClasspath() is > not passed to loadCoreExtensions(), so there is no way for > loadCoreExtensions() to find the relevant files. > The most obvious solution would be to call coreRealm.addURL() for each of the > files discovered by parseExtClasspath(). This would solve #1 above which > would implicitly fix #2. Though I don't know if it would have other > consequences. > If this is not a bug and is instead "works as designed", then >
[jira] [Created] (MNG-8112) extension.xml is ignored when extension is loaded by -Dmaven.ext.class.path
Rich DiCroce created MNG-8112: - Summary: extension.xml is ignored when extension is loaded by -Dmaven.ext.class.path Key: MNG-8112 URL: https://issues.apache.org/jira/browse/MNG-8112 Project: Maven Issue Type: Bug Components: Class Loading Affects Versions: 3.9.6 Reporter: Rich DiCroce As the title says: extension.xml is ignored when an extension is loaded by -Dmaven.ext.class.path, which makes it impossible to expose any additional packages. I am filing this as a bug due to this comment on MNG-6906, which says that lib/ext and -Dmaven.ext.class.path are supposed to be synonymous. Note that MNG-6906 is a related but different problem. When looking at org.apache.maven.cli.MavenCli, the problems aren't too hard to see: # lib/ext extensions get loaded into the plexus.core realm (as per m2.conf), but -Dmaven.ext.class.path extensions are loaded into the maven.ext realm (as per MavenCli#setupContainerRealm()). # loadCoreExtensions() operates on the coreRealm, but due to #1, the extensions are not in that realm. Also, the result of parseExtClasspath() is not passed to loadCoreExtensions(), so there is no way for loadCoreExtensions() to find the relevant files. The most obvious solution would be to call coreRealm.addURL() for each of the files discovered by parseExtClasspath(). This would solve #1 above which would implicitly fix #2. Though I don't know if it would have other consequences. If this is not a bug and is instead "works as designed", then [https://maven.apache.org/guides/mini/guide-using-extensions.html] needs to be updated to explain that the three methods of loading core extensions are not equivalent. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8111) Version 3.9.6 is not reproducible
Leonidas Spyropoulos created MNG-8111:
-
Summary: Version 3.9.6 is not reproducible
Key: MNG-8111
URL: https://issues.apache.org/jira/browse/MNG-8111
Project: Maven
Issue Type: Bug
Components: Core, General
Affects Versions: 3.9.6
Environment: Arch Linux updated (29/04/2024)
Reporter: Leonidas Spyropoulos
Version 3.9.6 is not reproducible. It seems like the compiled classes are
different.
- JDK used: OpenJDK version 8.412.u08
- Command line used:
{code:bash}
mvn package \
-DbuildNumber="bc0240f3c744dd6b6ec2920b3cd08dcc295161ae" \
-Dline.separator=$'\r\n' \
-Dproject.build.sourceEncoding=UTF-8 -e \
-Dmaven.repo.local="./repo" \
-DskipTests
{code}
buildNumber is found from:
{code}
bsdtar xOf <(bsdtar xOf apache-maven-3.9.6-bin.tar.gz
apache-maven-3.9.6/lib/maven-core-3.9.6.jar) \
org/apache/maven/messages/build.properties | grep buildNumber | cut -d= -f2
| tr -cd '[:print:]'
{code}
Relevant issue: https://issues.apache.org/jira/browse/MNG-6276
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MSHARED-1362) Upgrade plugins and components (in ITs)
[ https://issues.apache.org/jira/browse/MSHARED-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1362. --- Resolution: Fixed Fixed with [55262efc9800e0b874b50f0c2e222b08db4208a5|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git=commit=55262efc9800e0b874b50f0c2e222b08db4208a5]. > Upgrade plugins and components (in ITs) > --- > > Key: MSHARED-1362 > URL: https://issues.apache.org/jira/browse/MSHARED-1362 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0, > maven-reporting-exec-2.0.0-M13 > > > * Upgrade to Maven Site Plugin 4.0.0-M13 > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Reporting Impl 4.0.0-M14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1362) Upgrade plugins and components (in ITs)
[ https://issues.apache.org/jira/browse/MSHARED-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1362: Description: * Upgrade to Maven Site Plugin 4.0.0-M13 * Upgrade to Doxia 2.0.0-M10 * Upgrade to Doxia Sitetools 2.0.0-M18 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Reporting Impl 4.0.0-M14 was: * Upgrade to Maven Site Plugin 4.0.0-M13 * Upgrade to Doxia 2.0.0-M10 * Upgrade to Doxia Sitetools 2.0.0-M18 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Reporting Impl 4.0.0-M14 * Upgrade to Maven Plugin Tools 3.12.0 > Upgrade plugins and components (in ITs) > --- > > Key: MSHARED-1362 > URL: https://issues.apache.org/jira/browse/MSHARED-1362 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0, > maven-reporting-exec-2.0.0-M13 > > > * Upgrade to Maven Site Plugin 4.0.0-M13 > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Reporting Impl 4.0.0-M14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump org.apache.maven:maven-core from 3.2.5 to 3.8.1 [maven-reporting-exec]
dependabot[bot] opened a new pull request, #21: URL: https://github.com/apache/maven-reporting-exec/pull/21 Bumps [org.apache.maven:maven-core](https://github.com/apache/maven) from 3.2.5 to 3.8.1. Commits https://github.com/apache/maven/commit/05c21c65bdfed0f71a2f2ada8b84da59348c4c5d;>05c21c6 [maven-release-plugin] prepare release maven-3.8.1 https://github.com/apache/maven/commit/d295dc362fe7d7b189b4976a5742a17362eb51a1;>d295dc3 [MNG-7128] keep blocked attribute from mirrors in artifact repositories https://github.com/apache/maven/commit/a46906806a31edb462b935e380a657b6efde6231;>a469068 next version in branch 3.8.x is 3.8.1-SNAPSHOT https://github.com/apache/maven/commit/dad8a3e1c55f34b7949945bc622f26447ddbf4f9;>dad8a3e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/6aa1f4acf5d6323e9aa08b763cb9933dc96749b9;>6aa1f4a [maven-release-plugin] prepare release maven-3.8.0 https://github.com/apache/maven/commit/907d53ad3264718f66ff15e1363d76b07dd0c05f;>907d53a [MNG-7118] block HTTP repositories by default https://github.com/apache/maven/commit/899465aeec03753ea91e15a79579eab76369c016;>899465a [MNG-7117] add support for blocked mirror https://github.com/apache/maven/commit/fa79cb22e456cc65522b5bab8c4240fe08c5775f;>fa79cb2 [MNG-7116] add support for mirrorOf external:http:* https://github.com/apache/maven/commit/e5f6634e17362387282b3867c9b23d4b54fea871;>e5f6634 use Maven Resolver 1.6.2 https://github.com/apache/maven/commit/09f77da9b0c39848fe763bdd4a392151eec0d8c3;>09f77da [MNG-7119] Upgrade Maven Wagon to 3.4.3 Additional commits viewable in https://github.com/apache/maven/compare/maven-3.2.5...maven-3.8.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will 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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/maven-reporting-exec/network/alerts). -- 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] (MSHARED-1387) Clean up dependencies
[ https://issues.apache.org/jira/browse/MSHARED-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1387. --- Resolution: Fixed Fixed with [a087b1e0770d3fbf844d473842d533c4fe97bf18|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git=commit=a087b1e0770d3fbf844d473842d533c4fe97bf18]. > Clean up dependencies > - > > Key: MSHARED-1387 > URL: https://issues.apache.org/jira/browse/MSHARED-1387 > Project: Maven Shared Components > Issue Type: Task > Components: maven-reporting-exec >Affects Versions: maven-reporting-exec-2.0.0-M12 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0, > maven-reporting-exec-2.0.0-M13 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] No maven compat [maven-reporting-exec]
michael-o merged PR #20: URL: https://github.com/apache/maven-reporting-exec/pull/20 -- 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] No maven compat [maven-reporting-exec]
michael-o closed pull request #20: No maven compat URL: https://github.com/apache/maven-reporting-exec/pull/20 -- 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] (MSHARED-1387) Clean up dependencies
Michael Osipov created MSHARED-1387: --- Summary: Clean up dependencies Key: MSHARED-1387 URL: https://issues.apache.org/jira/browse/MSHARED-1387 Project: Maven Shared Components Issue Type: Task Components: maven-reporting-exec Affects Versions: maven-reporting-exec-2.0.0-M12 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: maven-reporting-exec-2.0.0, maven-reporting-exec-2.0.0-M13 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump resolverVersion from 1.9.18 to 1.9.19 [maven-deploy-plugin]
dependabot[bot] commented on PR #53: URL: https://github.com/apache/maven-deploy-plugin/pull/53#issuecomment-2083255982 Superseded by #55. -- 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.19 [maven-deploy-plugin]
dependabot[bot] closed pull request #53: Bump resolverVersion from 1.9.18 to 1.9.19 URL: https://github.com/apache/maven-deploy-plugin/pull/53 -- 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 1.9.20 [maven-deploy-plugin]
dependabot[bot] opened a new pull request, #55: URL: https://github.com/apache/maven-deploy-plugin/pull/55 Bumps `resolverVersion` from 1.9.18 to 1.9.20. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-api's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent POM 42 (https://redirect.github.com/apache/maven-resolver/issues/484;>#484) https://github.com/apache/maven-resolver/commit/4f16d5ecd94f85e6e7d793e6b6b82f20c9afbf56;>4f16d5e [MRESOLVER-547] Just use setVersion (https://redirect.github.com/apache/maven-resolver/issues/483;>#483) https://github.com/apache/maven-resolver/commit/c1b24c699621930f4eb77721400f2f6c46930626;>c1b24c6 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-resolver/commit/c1b03574961fd2daa7a678bb3fbf9f0779afee56;>c1b0357 [maven-release-plugin] prepare release maven-resolver-1.9.19 https://github.com/apache/maven-resolver/commit/adadd42d1642f39bafedb2ddd619b044fecb12b0;>adadd42 [MRESOLVER-536] Do not belly up if FS does not support setting mtime (https://redirect.github.com/apache/maven-resolver/issues/469;>#469) https://github.com/apache/maven-resolver/commit/31df8a3dc503895172d277de56b1c4a53da0a27c;>31df8a3 [1.9.x] Update dependencies (https://redirect.github.com/apache/maven-resolver/issues/462;>#462) https://github.com/apache/maven-resolver/commit/b225076e5d5b2fe3f166a4018802ac94b7cc94f7;>b225076 [MRESOLVER-522] Improve congested file locks behaviour (https://redirect.github.com/apache/maven-resolver/issues/455;>#455) (https://redirect.github.com/apache/maven-resolver/issues/461;>#461) https://github.com/apache/maven-resolver/commit/fc969c2570041bb72c3f0141ff4957e8754f365c;>fc969c2 [1.9.x][MRESOLVER-483] Fix path concatenation logic (https://redirect.github.com/apache/maven-resolver/issues/420;>#420) https://github.com/apache/maven-resolver/commit/a3e620d6d2ab6ca58d42d264347341b31da00dde;>a3e620d Use one Maven in CI Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.18...maven-resolver-1.9.20;>compare view Updates `org.apache.maven.resolver:maven-resolver-util` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-util's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent
Re: [PR] [MSITE-1000] Introduce parser configuration parameter [maven-site-plugin]
kwin commented on code in PR #177:
URL: https://github.com/apache/maven-site-plugin/pull/177#discussion_r1583435793
##
src/main/java/org/apache/maven/plugins/site/render/ParserConfiguratorImpl.java:
##
@@ -0,0 +1,156 @@
+/*
+ * 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.
+ */
+package org.apache.maven.plugins.site.render;
+
+import java.io.Closeable;
+import java.io.IOException;
+import java.nio.file.FileSystem;
+import java.nio.file.FileSystems;
+import java.nio.file.Path;
+import java.nio.file.PathMatcher;
+import java.util.Collection;
+import java.util.LinkedHashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.Optional;
+import java.util.stream.Collectors;
+
+import org.apache.maven.doxia.parser.Parser;
+import org.apache.maven.doxia.siterenderer.ParserConfigurator;
+import org.apache.maven.plugin.descriptor.MojoDescriptor;
+import org.codehaus.plexus.PlexusContainer;
+import
org.codehaus.plexus.component.configurator.ComponentConfigurationException;
+import org.codehaus.plexus.component.configurator.ComponentConfigurator;
+import
org.codehaus.plexus.component.repository.exception.ComponentLifecycleException;
+import
org.codehaus.plexus.component.repository.exception.ComponentLookupException;
+import org.codehaus.plexus.configuration.PlexusConfiguration;
+
+/**
+ * Configures a parser based on a {@link PlexusConfiguration} for a particular
parser id and optionally matching one of multiple patterns.
+ * It internally leverages the {@link ComponentConfigurator} for calling the
right methods inside the parser implementation.
+ */
+public class ParserConfiguratorImpl implements ParserConfigurator, Closeable {
+
+private static final class ParserConfigurationKey {
+
+ParserConfigurationKey(String parserId, PlexusConfiguration
patternsConfiguration) {
+this(parserId,
PlexusConfigurationUtils.getStringArrayValues(patternsConfiguration));
+}
+
+ParserConfigurationKey(String parserId, Collection patterns) {
+this.parserId = parserId;
+// lazily populate all matchers
+matchers = patterns.stream()
+.map(p -> FileSystems.getDefault().getPathMatcher(p))
+.collect(Collectors.toList());
Review Comment:
Hopefully the javadoc comment on the affected parameter is clear enough. I
really don't want to rely on plexus classes for the ant pattern support.
--
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-1000) Allow parametrisation of Doxia parser per file
[
https://issues.apache.org/jira/browse/MSITE-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842108#comment-17842108
]
ASF GitHub Bot commented on MSITE-1000:
---
kwin commented on code in PR #177:
URL: https://github.com/apache/maven-site-plugin/pull/177#discussion_r1583435793
##
src/main/java/org/apache/maven/plugins/site/render/ParserConfiguratorImpl.java:
##
@@ -0,0 +1,156 @@
+/*
+ * 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.
+ */
+package org.apache.maven.plugins.site.render;
+
+import java.io.Closeable;
+import java.io.IOException;
+import java.nio.file.FileSystem;
+import java.nio.file.FileSystems;
+import java.nio.file.Path;
+import java.nio.file.PathMatcher;
+import java.util.Collection;
+import java.util.LinkedHashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.Optional;
+import java.util.stream.Collectors;
+
+import org.apache.maven.doxia.parser.Parser;
+import org.apache.maven.doxia.siterenderer.ParserConfigurator;
+import org.apache.maven.plugin.descriptor.MojoDescriptor;
+import org.codehaus.plexus.PlexusContainer;
+import
org.codehaus.plexus.component.configurator.ComponentConfigurationException;
+import org.codehaus.plexus.component.configurator.ComponentConfigurator;
+import
org.codehaus.plexus.component.repository.exception.ComponentLifecycleException;
+import
org.codehaus.plexus.component.repository.exception.ComponentLookupException;
+import org.codehaus.plexus.configuration.PlexusConfiguration;
+
+/**
+ * Configures a parser based on a {@link PlexusConfiguration} for a particular
parser id and optionally matching one of multiple patterns.
+ * It internally leverages the {@link ComponentConfigurator} for calling the
right methods inside the parser implementation.
+ */
+public class ParserConfiguratorImpl implements ParserConfigurator, Closeable {
+
+private static final class ParserConfigurationKey {
+
+ParserConfigurationKey(String parserId, PlexusConfiguration
patternsConfiguration) {
+this(parserId,
PlexusConfigurationUtils.getStringArrayValues(patternsConfiguration));
+}
+
+ParserConfigurationKey(String parserId, Collection patterns) {
+this.parserId = parserId;
+// lazily populate all matchers
+matchers = patterns.stream()
+.map(p -> FileSystems.getDefault().getPathMatcher(p))
+.collect(Collectors.toList());
Review Comment:
Hopefully the javadoc comment on the affected parameter is clear enough. I
really don't want to rely on plexus classes for the ant pattern support.
> Allow parametrisation of Doxia parser per file
> --
>
> Key: MSITE-1000
> URL: https://issues.apache.org/jira/browse/MSITE-1000
> Project: Maven Site Plugin
> Issue Type: New Feature
> Components: doxia integration
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> Currently only the attributes used for rendering the site can be
> parameterized in
> https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#attributes.
> There is no possibility to configure the parser in
> https://github.com/apache/maven-doxia-sitetools/blob/dacaa552c1b8e89eed84db0f43b6b0a72be91d0c/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java#L322
> per document.
> This would be nice in the context of
> https://issues.apache.org/jira/browse/DOXIA-722 where generation of anchors
> should be switched on/off for certain documents. Also generation of comments
> may be desirable for certain documents.
> I propose the following additional plugin goal parameter:
> {code}
>
>
>
> **/apt/**
>
> false
> true
>
>
> {code}
> where {{parserConfigurations}} is an array of a complex type with (include)
> patterns on the source path (String array) and boolean methods for features.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSITE-1000) Allow parametrisation of Doxia parser per file
[
https://issues.apache.org/jira/browse/MSITE-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842105#comment-17842105
]
ASF GitHub Bot commented on MSITE-1000:
---
kwin commented on code in PR #177:
URL: https://github.com/apache/maven-site-plugin/pull/177#discussion_r1583427213
##
src/main/java/org/apache/maven/plugins/site/render/AbstractSiteRenderingMojo.java:
##
@@ -94,6 +97,37 @@ public abstract class AbstractSiteRenderingMojo extends
AbstractSiteDescriptorMo
@Parameter
private Map attributes;
+/**
+ * Parser configurations (per matching Doxia markup source file path
patterns).
+ * Each configuration item has the following format:
+ *
+ *
+ * parserId
+ * configurations
+ * configuration
+ * patterns
+ * patternglob:***.md/pattern!
> Allow parametrisation of Doxia parser per file
> --
>
> Key: MSITE-1000
> URL: https://issues.apache.org/jira/browse/MSITE-1000
> Project: Maven Site Plugin
> Issue Type: New Feature
> Components: doxia integration
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> Currently only the attributes used for rendering the site can be
> parameterized in
> https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#attributes.
> There is no possibility to configure the parser in
> https://github.com/apache/maven-doxia-sitetools/blob/dacaa552c1b8e89eed84db0f43b6b0a72be91d0c/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java#L322
> per document.
> This would be nice in the context of
> https://issues.apache.org/jira/browse/DOXIA-722 where generation of anchors
> should be switched on/off for certain documents. Also generation of comments
> may be desirable for certain documents.
> I propose the following additional plugin goal parameter:
> {code}
>
>
>
> **/apt/**
>
> false
> true
>
>
> {code}
> where {{parserConfigurations}} is an array of a complex type with (include)
> patterns on the source path (String array) and boolean methods for features.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MSITE-1000] Introduce parser configuration parameter [maven-site-plugin]
kwin commented on code in PR #177: URL: https://github.com/apache/maven-site-plugin/pull/177#discussion_r1583427213 ## src/main/java/org/apache/maven/plugins/site/render/AbstractSiteRenderingMojo.java: ## @@ -94,6 +97,37 @@ public abstract class AbstractSiteRenderingMojo extends AbstractSiteDescriptorMo @Parameter private Map attributes; +/** + * Parser configurations (per matching Doxia markup source file path patterns). + * Each configuration item has the following format: + * + * + * parserId + * configurations + * configuration + * patterns + * patternglob:***.md/pattern!-- is either glob or regex syntax with the according prefix -- + * /patterns + * !-- all configurations apart from pattern are directly applied to the underlying parser -- + * emitCommentstrue/emitComments!-- false by default -- + * emitAnchorsForIndexableEntriesfalse/emitAnchorsForIndexableEntries!-- true by default -- + * /configuration + * /configurations + * /parserId + * + * The configuration is only applied if both + * + * the parser id matches the parser used for a specific markup source file and + * one of the given patterns matches the Doxia markup source file path (or no pattern is given at all). + * + * + * The first matching configuration wins (i.e. is applied). + * @since 4.0.0 + * @see java.nio.file.FileSystem#getPathMatcher(String) FileSystem.getPathMatcher(String) for the supported patterns + */ +@Parameter +private Map> parserConfigurations; Review Comment: This will make it more complex as then we need to merge multiple configurations potentially -- 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] (MSKINS-245) Maven Site 4 will break code highlight of site generated by Markdown
[ https://issues.apache.org/jira/browse/MSKINS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842100#comment-17842100 ] ASF GitHub Bot commented on MSKINS-245: --- kwin commented on PR #58: URL: https://github.com/apache/maven-fluido-skin/pull/58#issuecomment-2083228383 Still requires a m-site-p version depending on m-doxia-sitetools M18+... > Maven Site 4 will break code highlight of site generated by Markdown > > > Key: MSKINS-245 > URL: https://issues.apache.org/jira/browse/MSKINS-245 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Reporter: Xavi Lee >Assignee: Konrad Windszus >Priority: Major > Fix For: fluido-2.0.0-M9, fluido-2.0.0 > > Attachments: maven-site-3.png, maven-site-4.png, test-v3.html, > test-v4.html > > > repro repo https://github.com/awxiaoxian2020/code-render-bug > master branch is Maven Site 3 with Fluido skin 1 > v4 branch is Maven Site 4 with Fluido skin 2. > Open their respective `target/site/test.html` files in local to see the > rendered result. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSKINS-245) Maven Site 4 will break code highlight of site generated by Markdown
[ https://issues.apache.org/jira/browse/MSKINS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MSKINS-245: --- Component/s: Fluido Skin > Maven Site 4 will break code highlight of site generated by Markdown > > > Key: MSKINS-245 > URL: https://issues.apache.org/jira/browse/MSKINS-245 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Reporter: Xavi Lee >Assignee: Konrad Windszus >Priority: Major > Attachments: maven-site-3.png, maven-site-4.png, test-v3.html, > test-v4.html > > > repro repo https://github.com/awxiaoxian2020/code-render-bug > master branch is Maven Site 3 with Fluido skin 1 > v4 branch is Maven Site 4 with Fluido skin 2. > Open their respective `target/site/test.html` files in local to see the > rendered result. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSKINS-245) Maven Site 4 will break code highlight of site generated by Markdown
[ https://issues.apache.org/jira/browse/MSKINS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MSKINS-245: --- Fix Version/s: fluido-2.0.0-M9 fluido-2.0.0 > Maven Site 4 will break code highlight of site generated by Markdown > > > Key: MSKINS-245 > URL: https://issues.apache.org/jira/browse/MSKINS-245 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Reporter: Xavi Lee >Assignee: Konrad Windszus >Priority: Major > Fix For: fluido-2.0.0-M9, fluido-2.0.0 > > Attachments: maven-site-3.png, maven-site-4.png, test-v3.html, > test-v4.html > > > repro repo https://github.com/awxiaoxian2020/code-render-bug > master branch is Maven Site 3 with Fluido skin 1 > v4 branch is Maven Site 4 with Fluido skin 2. > Open their respective `target/site/test.html` files in local to see the > rendered result. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1386) Context ClassLoader for current thread should be managed
[ https://issues.apache.org/jira/browse/MSHARED-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MSHARED-1386. Resolution: Fixed > Context ClassLoader for current thread should be managed > > > Key: MSHARED-1386 > URL: https://issues.apache.org/jira/browse/MSHARED-1386 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-script-interpreter >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-script-interpreter-next-release > > > We create dedicated class loader for groovy and bsh scripts interpreters. > We should also set Context ClassLoader for current thread, to allow use it by > external library, one example is WireMock. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1386) Context ClassLoader for current thread should be managed
[ https://issues.apache.org/jira/browse/MSHARED-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842047#comment-17842047 ] ASF GitHub Bot commented on MSHARED-1386: - slawekjaranowski merged PR #121: URL: https://github.com/apache/maven-script-interpreter/pull/121 > Context ClassLoader for current thread should be managed > > > Key: MSHARED-1386 > URL: https://issues.apache.org/jira/browse/MSHARED-1386 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-script-interpreter >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-script-interpreter-next-release > > > We create dedicated class loader for groovy and bsh scripts interpreters. > We should also set Context ClassLoader for current thread, to allow use it by > external library, one example is WireMock. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MSHARED-1386] Manage context ClassLoader for current thread [maven-script-interpreter]
slawekjaranowski merged PR #121: URL: https://github.com/apache/maven-script-interpreter/pull/121 -- 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] (MINVOKER-284) Upgrade JUnit to version 5, drop maven-compat
[ https://issues.apache.org/jira/browse/MINVOKER-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MINVOKER-284: - Summary: Upgrade JUnit to version 5, drop maven-compat (was: Upgrade JUnit to version 5) > Upgrade JUnit to version 5, drop maven-compat > - > > Key: MINVOKER-284 > URL: https://issues.apache.org/jira/browse/MINVOKER-284 > Project: Maven Invoker Plugin > Issue Type: Improvement >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Minor > Fix For: 3.6.2 > > > We can use new features and > [https://github.com/codehaus-plexus/plexus-testing] for integration tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINVOKER-284) Upgrade JUnit to version 5
[ https://issues.apache.org/jira/browse/MINVOKER-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842034#comment-17842034 ] ASF GitHub Bot commented on MINVOKER-284: - slawekjaranowski opened a new pull request, #228: URL: https://github.com/apache/maven-invoker-plugin/pull/228 https://issues.apache.org/jira/browse/MINVOKER-284 > Upgrade JUnit to version 5 > -- > > Key: MINVOKER-284 > URL: https://issues.apache.org/jira/browse/MINVOKER-284 > Project: Maven Invoker Plugin > Issue Type: Improvement >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Minor > Fix For: 3.6.2 > > > We can use new features and > [https://github.com/codehaus-plexus/plexus-testing] for integration tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MINVOKER-284) Upgrade JUnit to version 5
[ https://issues.apache.org/jira/browse/MINVOKER-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MINVOKER-284: - Fix Version/s: 3.6.2 > Upgrade JUnit to version 5 > -- > > Key: MINVOKER-284 > URL: https://issues.apache.org/jira/browse/MINVOKER-284 > Project: Maven Invoker Plugin > Issue Type: Improvement >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Minor > Fix For: 3.6.2 > > > We can use new features and > [https://github.com/codehaus-plexus/plexus-testing] for integration tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MINVOKER-284) Upgrade JUnit to version 5
[ https://issues.apache.org/jira/browse/MINVOKER-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski reassigned MINVOKER-284: Assignee: Slawomir Jaranowski > Upgrade JUnit to version 5 > -- > > Key: MINVOKER-284 > URL: https://issues.apache.org/jira/browse/MINVOKER-284 > Project: Maven Invoker Plugin > Issue Type: Improvement >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Minor > > We can use new features and > [https://github.com/codehaus-plexus/plexus-testing] for integration tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump commons-codec:commons-codec from 1.16.1 to 1.17.0 [maven-enforcer]
dependabot[bot] opened a new pull request, #312: URL: https://github.com/apache/maven-enforcer/pull/312 Bumps [commons-codec:commons-codec](https://github.com/apache/commons-codec) from 1.16.1 to 1.17.0. Changelog Sourced from https://github.com/apache/commons-codec/blob/master/RELEASE-NOTES.txt;>commons-codec:commons-codec's changelog. Apache Commons Codec 1.17.0 RELEASE NOTES The Apache Commons Codec component contains encoders and decoders for various formats such as Base16, Base32, Base64, digest, and Hexadecimal. In addition to these widely used encoders and decoders, the codec package also maintains a collection of phonetic encoding utilities. Feature and fix release. Requires a minimum of Java 8. New features Add override org.apache.commons.codec.language.bm.Rule.PhonemeExpr.size(). Thanks to Gary Gregory. Add support for Base64 custom alphabets [#266](https://github.com/apache/commons-codec/issues/266). Thanks to Chris Kocel, Gary Gregory. Add Base64.Builder (allows custom alphabets). Thanks to Gary Gregory. Add Base32.Builder (allows custom alphabets). Thanks to Gary Gregory. Add Base64 support for a custom padding byte (like Base32). Thanks to Gary Gregory. Fixed Bugs CODEC-320: Wrong output of DoubleMetaphone in 1.16.1. Thanks to Martin Frydl, Gary Gregory. Optimize memory allocation in PhoneticEngine. Thanks to Gary Gregory. BCodec and QCodec encode() methods throw UnsupportedCharsetException instead of EncoderException. Thanks to Gary Gregory. Set Javadoc link to latest Java API LTS version. Thanks to Gary Gregory. Base32 constructor fails-fast with a NullPointerException if the custom alphabet array is null. Thanks to Gary Gregory. Base32 constructor makes a defensive copy of the line separator array. Thanks to Gary Gregory. Base64 constructor makes a defensive copy of the line separator array. Thanks to Gary Gregory. Base64 constructor makes a defensive copy of a custom alphabet array. Thanks to Gary Gregory. Changes Bump org.apache.commons:commons-parent from 66 to 69 [#250](https://github.com/apache/commons-codec/issues/250), [#261](https://github.com/apache/commons-codec/issues/261). Thanks to Dependabot, Gary Gregory. Bump commons-io:commons-io from 2.15.1 to 2.16.1 [#258](https://github.com/apache/commons-codec/issues/258), [#265](https://github.com/apache/commons-codec/issues/265). Thanks to Dependabot, Gary Gregory. For complete information on Apache Commons Codec, including instructions on how to submit bug reports, patches, or suggestions for improvement, see the Apache Commons Codec website: https://commons.apache.org/proper/commons-codec/;>https://commons.apache.org/proper/commons-codec/ Download page: https://commons.apache.org/proper/commons-codec/download_codec.cgi;>https://commons.apache.org/proper/commons-codec/download_codec.cgi Commits https://github.com/apache/commons-codec/commit/5d809fe3d729bde9b507a51d2b2ed659da053692;>5d809fe Prepare for the next release candidate https://github.com/apache/commons-codec/commit/9a59c1c47b02ca795270b758c8d0591f5925b10f;>9a59c1c Prepare for the next release candidate https://github.com/apache/commons-codec/commit/5f0cfd46c89df69b579f37562ff1eded7ffd4b5c;>5f0cfd4 Longer lines https://github.com/apache/commons-codec/commit/8714b5f62bb5fa5950aa5e8908bd0d8d3334dba5;>8714b5f Remove dead comment https://github.com/apache/commons-codec/commit/c56b95664913aab406f768c66f9264481b28c1bb;>c56b956 Bullet-proof internals https://github.com/apache/commons-codec/commit/d2215d5dec3031f819c3bb514587d92a6aec8eff;>d2215d5 Base32 constructor fails-fast with a NullPointerException if the custom https://github.com/apache/commons-codec/commit/fcc70e6fa1271158dd8f3a90350fa2589713f257;>fcc70e6 Base32 constructor makes a defensive copy of the line separator https://github.com/apache/commons-codec/commit/ebe805a2730ad38886f9f04bd4d242e0a8c9caaa;>ebe805a Base64 constructor makes a defensive copy of a custom alphabet array https://github.com/apache/commons-codec/commit/55043334240eb2a1838e37ea1c8a6e434d328fdf;>5504333 Better exception message https://github.com/apache/commons-codec/commit/c6c5f11eae145d8e8c655e622f0fc5dd74e6db2a;>c6c5f11 Base64 constructor makes a better defensive copy of the line separator Additional commits viewable in https://github.com/apache/commons-codec/compare/rel/commons-codec-1.16.1...rel/commons-codec-1.17.0;>compare view [![Dependabot compatibility
[PR] Bump version.xmlunit from 2.9.1 to 2.10.0 [maven-antrun-plugin]
dependabot[bot] opened a new pull request, #97: URL: https://github.com/apache/maven-antrun-plugin/pull/97 Bumps `version.xmlunit` from 2.9.1 to 2.10.0. Updates `org.xmlunit:xmlunit-core` from 2.9.1 to 2.10.0 Release notes Sourced from https://github.com/xmlunit/xmlunit/releases;>org.xmlunit:xmlunit-core'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-core'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 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 Updates `org.xmlunit:xmlunit-matchers` 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
[jira] [Assigned] (MPLUGIN-520) Get rid of maven-compat classes use
[ https://issues.apache.org/jira/browse/MPLUGIN-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MPLUGIN-520: --- Assignee: Tamas Cservenak > Get rid of maven-compat classes use > --- > > Key: MPLUGIN-520 > URL: https://issues.apache.org/jira/browse/MPLUGIN-520 > Project: Maven Plugin Tools > Issue Type: Improvement > Components: Plugin Plugin >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.12.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7266) Remove maven-compat module
[ https://issues.apache.org/jira/browse/MNG-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841992#comment-17841992 ] ASF GitHub Bot commented on MNG-7266: - cstamas commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2082768935 Fix for m-p-p on the way https://github.com/apache/maven-plugin-tools/pull/280 > Remove maven-compat module > -- > > Key: MNG-7266 > URL: https://issues.apache.org/jira/browse/MNG-7266 > Project: Maven > Issue Type: Sub-task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.x-candidate > > > Maven-core does not depend on maven-compat anymore (runtime or compile time). > Do we want to carry it over up to 4.0.0 and delete it in 4.1.0, or do we > want to drop it before 4.0.0 ? > [~cstamas] [~olamy] [~romain.manni-bucau] [~sjaranowski] and others... ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-7266] Remove maven-compat [maven]
cstamas commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2082768935 Fix for m-p-p on the way https://github.com/apache/maven-plugin-tools/pull/280 -- 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] (MPLUGIN-520) Get rid of maven-compat classes use
Tamas Cservenak created MPLUGIN-520: --- Summary: Get rid of maven-compat classes use Key: MPLUGIN-520 URL: https://issues.apache.org/jira/browse/MPLUGIN-520 Project: Maven Plugin Tools Issue Type: Improvement Components: Plugin Plugin Reporter: Tamas Cservenak Fix For: 3.12.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-519) Update to Parent POM 42, prerequisite 3.6.3
[ https://issues.apache.org/jira/browse/MPLUGIN-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841990#comment-17841990 ] ASF GitHub Bot commented on MPLUGIN-519: cstamas commented on code in PR #280: URL: https://github.com/apache/maven-plugin-tools/pull/280#discussion_r1583083285 ## maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/metadata/AddPluginArtifactMetadataMojo.java: ## @@ -18,10 +18,8 @@ */ package org.apache.maven.plugin.plugin.metadata; -import org.apache.maven.artifact.Artifact; import org.apache.maven.artifact.repository.metadata.ArtifactRepositoryMetadata; import org.apache.maven.artifact.repository.metadata.GroupRepositoryMetadata; Review Comment: Removed > Update to Parent POM 42, prerequisite 3.6.3 > --- > > Key: MPLUGIN-519 > URL: https://issues.apache.org/jira/browse/MPLUGIN-519 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.12.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-519] Get rid of maven-compat [maven-plugin-tools]
cstamas commented on code in PR #280: URL: https://github.com/apache/maven-plugin-tools/pull/280#discussion_r1583083285 ## maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/metadata/AddPluginArtifactMetadataMojo.java: ## @@ -18,10 +18,8 @@ */ package org.apache.maven.plugin.plugin.metadata; -import org.apache.maven.artifact.Artifact; import org.apache.maven.artifact.repository.metadata.ArtifactRepositoryMetadata; import org.apache.maven.artifact.repository.metadata.GroupRepositoryMetadata; Review Comment: Removed -- 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] (SUREFIRE-2010) Parameterized Selection Does not Work
[
https://issues.apache.org/jira/browse/SUREFIRE-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841989#comment-17841989
]
ASF GitHub Bot commented on SUREFIRE-2010:
--
AlexShmydov commented on PR #476:
URL: https://github.com/apache/maven-surefire/pull/476#issuecomment-2082726468
Guys, can somebody to help?
I am talking about https://github.com/junit-team/junit5/pull/2743
How we can run single invocation of test?
> Parameterized Selection Does not Work
> -
>
> Key: SUREFIRE-2010
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2010
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support, JUnit 5.x support
>Affects Versions: 3.0.0-M5
> Environment: Maven 3.6.3 and Ubuntu 20.04, but I suppose it happens
> everywhere
>Reporter: David Georg Reichelt
>Priority: Major
>
> In the current version (and also M6-SNAPSHOT), maven surefire is not capable
> of selecting parameterized tests based on the index. In
> [https://maven.apache.org/surefire/maven-surefire-plugin/examples/single-test.html,]
> it is described that this should work by providing the index, e.g. using
> {code:java}
> -Dtest=MyTest#method[$INDEX]{code}
> or
> {code:java}
> -Dtest=MyTest#method[*]{code}
> for all.
>
> This happens both for JUnit 4 and JUnit 5.
> I created a mwe demonstrating this problem:
> [https://github.com/DaGeRe/parameterized-selection-demo]
> As far as I see it, the TestMethodFilter in
> [https://github.com/apache/maven-surefire/blob/master/surefire-providers/surefire-junit-platform/src/main/java/org/apache/maven/surefire/junitplatform/TestMethodFilter.java#L45]
> does the filtering, but has only a descriptor in the form:
>
> {code:java}
> [engine:junit-jupiter]/[class:de.dagere.peass.ExampleTest]/[test-template:test(int)]{code}
>
> So there is not the concrete value, but only the information that an int
> should be provided. Therefore, I currently see not any option to fix this
> easily or get this running using a regex pattern.
> Do I oversee something, or is it planned to fix this? If not, it would be
> better to update the documentation site accordingly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [SUREFIRE-2010] Parameterized Selection Does not Work [maven-surefire]
AlexShmydov commented on PR #476: URL: https://github.com/apache/maven-surefire/pull/476#issuecomment-2082726468 Guys, can somebody to help? I am talking about https://github.com/junit-team/junit5/pull/2743 How we can run single invocation of test? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPLUGIN-519) Update to Parent POM 42, prerequisite 3.6.3
[ https://issues.apache.org/jira/browse/MPLUGIN-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841988#comment-17841988 ] ASF GitHub Bot commented on MPLUGIN-519: gnodet commented on code in PR #280: URL: https://github.com/apache/maven-plugin-tools/pull/280#discussion_r1583074758 ## maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/metadata/AddPluginArtifactMetadataMojo.java: ## @@ -18,10 +18,8 @@ */ package org.apache.maven.plugin.plugin.metadata; -import org.apache.maven.artifact.Artifact; import org.apache.maven.artifact.repository.metadata.ArtifactRepositoryMetadata; import org.apache.maven.artifact.repository.metadata.GroupRepositoryMetadata; Review Comment: Those two imports should be removed, they are referenced from the javadoc and they should be moved to LegacySupport. > Update to Parent POM 42, prerequisite 3.6.3 > --- > > Key: MPLUGIN-519 > URL: https://issues.apache.org/jira/browse/MPLUGIN-519 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.12.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-519] Get rid of maven-compat [maven-plugin-tools]
gnodet commented on code in PR #280: URL: https://github.com/apache/maven-plugin-tools/pull/280#discussion_r1583074758 ## maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/metadata/AddPluginArtifactMetadataMojo.java: ## @@ -18,10 +18,8 @@ */ package org.apache.maven.plugin.plugin.metadata; -import org.apache.maven.artifact.Artifact; import org.apache.maven.artifact.repository.metadata.ArtifactRepositoryMetadata; import org.apache.maven.artifact.repository.metadata.GroupRepositoryMetadata; Review Comment: Those two imports should be removed, they are referenced from the javadoc and they should be moved to LegacySupport. -- 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] (MBUILDCACHE-95) Improve efficiency of cache when adding/removing modules
Marquis Wang created MBUILDCACHE-95: --- Summary: Improve efficiency of cache when adding/removing modules Key: MBUILDCACHE-95 URL: https://issues.apache.org/jira/browse/MBUILDCACHE-95 Project: Maven Build Cache Extension Issue Type: Improvement Reporter: Marquis Wang Right now, if you add or remove a module from your multi-module project, it invalidates your cache for your entire project, since the base pom has changed. (My project adds all modules to the dependency management of the base pom.) This is silly, since * When you remove a module, you should be able to reuse all of the cache * When you add a module, you should be able to build only that one new module -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPLUGIN-519) Update to Parent POM 42, prerequisite 3.6.3
Tamas Cservenak created MPLUGIN-519: --- Summary: Update to Parent POM 42, prerequisite 3.6.3 Key: MPLUGIN-519 URL: https://issues.apache.org/jira/browse/MPLUGIN-519 Project: Maven Plugin Tools Issue Type: Dependency upgrade Reporter: Tamas Cservenak Fix For: 3.12.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MPLUGIN-519) Update to Parent POM 42, prerequisite 3.6.3
[ https://issues.apache.org/jira/browse/MPLUGIN-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MPLUGIN-519: --- Assignee: Tamas Cservenak > Update to Parent POM 42, prerequisite 3.6.3 > --- > > Key: MPLUGIN-519 > URL: https://issues.apache.org/jira/browse/MPLUGIN-519 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.12.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump xmlunitVersion from 2.9.1 to 2.10.0 [maven-doxia]
dependabot[bot] opened a new pull request, #212: URL: https://github.com/apache/maven-doxia/pull/212 Bumps `xmlunitVersion` from 2.9.1 to 2.10.0. Updates `org.xmlunit:xmlunit-core` from 2.9.1 to 2.10.0 Release notes Sourced from https://github.com/xmlunit/xmlunit/releases;>org.xmlunit:xmlunit-core'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-core'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 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 Updates `org.xmlunit:xmlunit-matchers` 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
[jira] [Commented] (MNG-7266) Remove maven-compat module
[ https://issues.apache.org/jira/browse/MNG-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841952#comment-17841952 ] ASF GitHub Bot commented on MNG-7266: - michael-o commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2082487297 > > Someone needs to fix maven-plugin-plugin first: > > Does this still stands? Or latest one works? Both are unrelated. Maven Plugin Plugin remains broken without Maven Compat. > Remove maven-compat module > -- > > Key: MNG-7266 > URL: https://issues.apache.org/jira/browse/MNG-7266 > Project: Maven > Issue Type: Sub-task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.x-candidate > > > Maven-core does not depend on maven-compat anymore (runtime or compile time). > Do we want to carry it over up to 4.0.0 and delete it in 4.1.0, or do we > want to drop it before 4.0.0 ? > [~cstamas] [~olamy] [~romain.manni-bucau] [~sjaranowski] and others... ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-7266] Remove maven-compat [maven]
michael-o commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2082487297 > > Someone needs to fix maven-plugin-plugin first: > > Does this still stands? Or latest one works? Both are unrelated. Maven Plugin Plugin remains broken without Maven Compat. -- 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-7266) Remove maven-compat module
[ https://issues.apache.org/jira/browse/MNG-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841946#comment-17841946 ] ASF GitHub Bot commented on MNG-7266: - cstamas commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2082445871 > Someone needs to fix maven-plugin-plugin first: > Does this still stands? Or latest one works? > Remove maven-compat module > -- > > Key: MNG-7266 > URL: https://issues.apache.org/jira/browse/MNG-7266 > Project: Maven > Issue Type: Sub-task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.x-candidate > > > Maven-core does not depend on maven-compat anymore (runtime or compile time). > Do we want to carry it over up to 4.0.0 and delete it in 4.1.0, or do we > want to drop it before 4.0.0 ? > [~cstamas] [~olamy] [~romain.manni-bucau] [~sjaranowski] and others... ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-7266] Remove maven-compat [maven]
cstamas commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2082445871 > Someone needs to fix maven-plugin-plugin first: > Does this still stands? Or latest one works? -- 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] (DOXIASITETOOLS-337) Move maven-compat to test scope
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-337: -- Fix Version/s: 2.0.0-M19 > Move maven-compat to test scope > --- > > Key: DOXIASITETOOLS-337 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-337 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade > Components: Integration Tools >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-M19 > > > As maven-compat is not runtime/transitive dependency, is used in tests only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-337) Move maven-compat to test scope
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-337: -- Fix Version/s: (was: 2.0.0-M18) > Move maven-compat to test scope > --- > > Key: DOXIASITETOOLS-337 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-337 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade > Components: Integration Tools >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0 > > > As maven-compat is not runtime/transitive dependency, is used in tests only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-337) Move maven-compat to test scope
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-337: -- Fix Version/s: 2.0.0-M18 > Move maven-compat to test scope > --- > > Key: DOXIASITETOOLS-337 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-337 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade > Components: Integration Tools >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-M18 > > > As maven-compat is not runtime/transitive dependency, is used in tests only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (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=17841932#comment-17841932
]
Thomas Nikolay edited comment on MPMD-383 at 4/29/24 10:12 AM:
---
Andreas Dangel The parameter was not explicitly set - so it should use the
default value = true. That is, it works as designed. But from my point of view
this is a bad design decision.
Use case:
* Setting up a new project
* Setup PMD with errors
* New developer without experience develops some code - no errors appear
* Developer doesn't know he made some bugs
* after a while, someone with experience discovers that PMD does not work and
activates it. Then the code needs to be refactored.
My proposal would to set the default value to false
was (Author: tnikolay):
Andreas Dangel The parameter was not explicitly set - so it should use the
default value = true. That is, it works as designed. But from my point of view
this is a bad design decision.
Use case:
* Setting up a new project
* Setup PMD with errors
* New developer without experience develops some code - no errors appear
* Developer doesn't know he made some bugs
* after a while, someone with experience discovers that PMD does not work and
activates it. Then the code needs to be refactored.
> 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-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=17841932#comment-17841932
]
Thomas Nikolay commented on MPMD-383:
-
Andreas Dangel The parameter was not explicitly set - so it should use the
default value = true. That is, it works as designed. But from my point of view
this is a bad design decision.
Use case:
* Setting up a new project
* Setup PMD with errors
* New developer without experience develops some code - no errors appear
* Developer doesn't know he made some bugs
* after a while, someone with experience discovers that PMD does not work and
activates it. Then the code needs to be refactored.
> 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] (MBUILDCACHE-94) Provide a build cache report on builds
[
https://issues.apache.org/jira/browse/MBUILDCACHE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841906#comment-17841906
]
Marquis Wang commented on MBUILDCACHE-94:
-
Never mind, I see now that a report is put in {{target/maven-incremental/}} of
the base module.
I was saving {{target/incremental-maven}} as build artifacts, so I missed this.
It would be nice if the log message below included the path.
{code}
[INFO] Saving cache report on build completion
{code}
Additionally... I assume the inconsistency between `incremental-maven` and
`maven-incremental` is unintended?
> Provide a build cache report on builds
> --
>
> Key: MBUILDCACHE-94
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-94
> Project: Maven Build Cache Extension
> Issue Type: Improvement
>Reporter: Marquis Wang
>Priority: Major
>
> When building with the build cache, it would be really helpful to provide a
> report of which modules were unable to utilize and cache, as well as
> information about why.
> Right now, when looking at build cache performance, we can use
> {{maven.build.cache.failFast}} and {{maven.build.cache.baselineUrl}} to
> understand which module(s) were unable to utilize the build cache and why.
> However, this process is entirely manual.
> It would be really helpful to provide some base cache statistics on every
> run, even if no baselineUrl is provided. That way, we can gather overall
> statistics and figure out how to change our project to better utilize the
> cache.
> For example, we have a multi-module project with hundreds of modules. I want
> to know if there is one module that is constantly changing and is depended on
> (possibly unnecessarily) by lots of other modules, which is causing cache
> misses.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MINVOKER-361) Bump commons-codec:commons-codec from 1.16.1 to 1.17.0
[ https://issues.apache.org/jira/browse/MINVOKER-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MINVOKER-361. Resolution: Fixed > Bump commons-codec:commons-codec from 1.16.1 to 1.17.0 > -- > > Key: MINVOKER-361 > URL: https://issues.apache.org/jira/browse/MINVOKER-361 > Project: Maven Invoker Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINVOKER-361) Bump commons-codec:commons-codec from 1.16.1 to 1.17.0
[ https://issues.apache.org/jira/browse/MINVOKER-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841904#comment-17841904 ] ASF GitHub Bot commented on MINVOKER-361: - slawekjaranowski merged PR #227: URL: https://github.com/apache/maven-invoker-plugin/pull/227 > Bump commons-codec:commons-codec from 1.16.1 to 1.17.0 > -- > > Key: MINVOKER-361 > URL: https://issues.apache.org/jira/browse/MINVOKER-361 > Project: Maven Invoker Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MINVOKER-361] Bump commons-codec:commons-codec from 1.16.1 to 1.17.0 [maven-invoker-plugin]
slawekjaranowski merged PR #227: URL: https://github.com/apache/maven-invoker-plugin/pull/227 -- 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] (MBUILDCACHE-94) Provide a build cache report on builds
Marquis Wang created MBUILDCACHE-94:
---
Summary: Provide a build cache report on builds
Key: MBUILDCACHE-94
URL: https://issues.apache.org/jira/browse/MBUILDCACHE-94
Project: Maven Build Cache Extension
Issue Type: Improvement
Reporter: Marquis Wang
When building with the build cache, it would be really helpful to provide a
report of which modules were unable to utilize and cache, as well as
information about why.
Right now, when looking at build cache performance, we can use
{{maven.build.cache.failFast}} and {{maven.build.cache.baselineUrl}} to
understand which module(s) were unable to utilize the build cache and why.
However, this process is entirely manual.
It would be really helpful to provide some base cache statistics on every run,
even if no baselineUrl is provided. That way, we can gather overall statistics
and figure out how to change our project to better utilize the cache.
For example, we have a multi-module project with hundreds of modules. I want to
know if there is one module that is constantly changing and is depended on
(possibly unnecessarily) by lots of other modules, which is causing cache
misses.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-8109) Resolver 1.9.20
[ https://issues.apache.org/jira/browse/MNG-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-8109. Resolution: Fixed > Resolver 1.9.20 > --- > > Key: MNG-8109 > URL: https://issues.apache.org/jira/browse/MNG-8109 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > > Upgrade resolver to 1.9.20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [3.9.x][MNG-8109] Resolver 1.9.20 [maven]
cstamas merged PR #1490: URL: https://github.com/apache/maven/pull/1490 -- 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-8109) Resolver 1.9.20
[ https://issues.apache.org/jira/browse/MNG-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841893#comment-17841893 ] ASF GitHub Bot commented on MNG-8109: - cstamas merged PR #1490: URL: https://github.com/apache/maven/pull/1490 > Resolver 1.9.20 > --- > > Key: MNG-8109 > URL: https://issues.apache.org/jira/browse/MNG-8109 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > > Upgrade resolver to 1.9.20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [mvnd-1.x] Update provisio [maven-mvnd]
cstamas merged PR #978: URL: https://github.com/apache/maven-mvnd/pull/978 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-8070) Document Maven Runtime Requirement for Java 17
[ https://issues.apache.org/jira/browse/MNG-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-8070. Resolution: Fixed > Document Maven Runtime Requirement for Java 17 > -- > > Key: MNG-8070 > URL: https://issues.apache.org/jira/browse/MNG-8070 > Project: Maven > Issue Type: Task > Components: Documentation: General >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > > Followup for MNG-8061 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8070) Document Maven Runtime Requirement for Java 17
[ https://issues.apache.org/jira/browse/MNG-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841892#comment-17841892 ] ASF GitHub Bot commented on MNG-8070: - cstamas merged PR #516: URL: https://github.com/apache/maven-site/pull/516 > Document Maven Runtime Requirement for Java 17 > -- > > Key: MNG-8070 > URL: https://issues.apache.org/jira/browse/MNG-8070 > Project: Maven > Issue Type: Task > Components: Documentation: General >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > > Followup for MNG-8061 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8070] Document requirement for Java 17 [maven-site]
cstamas merged PR #516: URL: https://github.com/apache/maven-site/pull/516 -- 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] (DOXIASITETOOLS-337) Move maven-compat to test scope
Tamas Cservenak created DOXIASITETOOLS-337: -- Summary: Move maven-compat to test scope Key: DOXIASITETOOLS-337 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-337 Project: Maven Doxia Sitetools Issue Type: Dependency upgrade Components: Integration Tools Reporter: Tamas Cservenak Fix For: 2.0.0 As maven-compat is not runtime/transitive dependency, is used in tests only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MBUILDCACHE-90) Configuration option to make mandatory the use of the clean phase in order to cache the build result
[ https://issues.apache.org/jira/browse/MBUILDCACHE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841861#comment-17841861 ] ASF GitHub Bot commented on MBUILDCACHE-90: --- kbuntrock commented on PR #103: URL: https://github.com/apache/maven-build-cache-extension/pull/103#issuecomment-2081973553 @olamy: Merge conflicts are resolved. Please merge this one before [MBUILDCACHE-86] (which I will fix after this merge) > Configuration option to make mandatory the use of the clean phase in order to > cache the build result > > > Key: MBUILDCACHE-90 > URL: https://issues.apache.org/jira/browse/MBUILDCACHE-90 > Project: Maven Build Cache Extension > Issue Type: New Feature >Reporter: Kevin Buntrock >Priority: Minor > Labels: pull-request-available > > Add a configuration option to make mandatory the use of the clean phase in > order to cache the build result. > The goal is to offer the possibility of denying as much as possible the > possibility to cache a faulty build. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MBUILDCACHE-88] Fix tests execution on jdk > 20 [maven-build-cache-extension]
kbuntrock commented on PR #147: URL: https://github.com/apache/maven-build-cache-extension/pull/147#issuecomment-2081974049 @olamy: thank you :) -- 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] (MBUILDCACHE-88) Tests in failure when ran on jdk21
[
https://issues.apache.org/jira/browse/MBUILDCACHE-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841862#comment-17841862
]
ASF GitHub Bot commented on MBUILDCACHE-88:
---
kbuntrock commented on PR #147:
URL:
https://github.com/apache/maven-build-cache-extension/pull/147#issuecomment-2081974049
@olamy: thank you :)
> Tests in failure when ran on jdk21
> --
>
> Key: MBUILDCACHE-88
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-88
> Project: Maven Build Cache Extension
> Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Kevin Buntrock
>Assignee: Olivier Lamy
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.2.0
>
>
> The project tests cannot be run on jdk21. Result is :
> {code:java}
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] CacheConfigImplTest.testInitializationDisabledInXML:234 expected:
> but was:
> [ERROR]
> CacheConfigImplTest.testRemoteDisableByUserPropertyOverride:330->assertDefaults:137->assertDefaults:201->lambda$testRemoteDisableByUserPropertyOverride$39:330
> expected: but was:
> [ERROR]
> CacheConfigImplTest.testRemoteEnableByUserPropertyOverrideWithURL:313->assertDefaults:137->assertDefaults:201->lambda$testRemoteEnableByUserPropertyOverrideWithURL$38:315
> expected: but was:
> [ERROR]
> CacheConfigImplTest.testRemoteEnableInXMLWithURL:288->assertDefaults:137->assertDefaults:201->lambda$testRemoteEnableInXMLWithURL$36:290
> expected: but was:
> [ERROR]
> CacheConfigImplTest.testRemoteSaveIgnoredWhenRemoteDisabledByUserPropertyOverride:420->assertDefaults:137->assertDefaults:201->lambda$testRemoteSaveIgnoredWhenRemoteDisabledByUserPropertyOverride$48:420
> expected: but was:
> [ERROR]
> CacheConfigImplTest.testRemoveSaveDisabledByUserProperty:381->assertDefaults:137->assertDefaults:201->lambda$testRemoveSaveDisabledByUserProperty$47:383
> expected: but was:
> [ERROR]
> CacheConfigImplTest.testRemoveSaveEnabledByUserProperty:362->assertDefaults:137->assertDefaults:201->lambda$testRemoveSaveEnabledByUserProperty$45:365
> expected: but was:
> [ERROR]
> CacheConfigImplTest.testRemoveSaveEnabledInXML:344->assertDefaults:137->assertDefaults:201->lambda$testRemoveSaveEnabledInXML$42:347
> expected: but was:
> [ERROR]
> CacheConfigImplTest.testRemoveSaveFinalEnabledByUserProperty:436->assertDefaults:137->assertDefaults:201->lambda$testRemoveSaveFinalEnabledByUserProperty$51:439
> expected: but was:
> [ERROR]
> CacheConfigImplTest.testRemoveSaveFinalIgnoredWhenRemoteSaveDisabled:455->assertDefaults:137->assertDefaults:201->lambda$testRemoveSaveFinalIgnoredWhenRemoteSaveDisabled$54:457
> expected: but was:
> [INFO]
> [ERROR] Tests run: 71, Failures: 10, Errors: 0, Skipped: 4
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
> {code}
> In class "CacheConfigImplTest", a method "deepMockConfigFile" mocks the
> result of the call to java.nio.file.Files.exists (via
> "FileSystemProvider.checkAccess").
> In jdk21 version, "Files.exists" does not rely on the same underlying
> "FileSystemProvider" method, therefore breaking the mocking purpose.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MBUILDCACHE-93) Command line configuration to disable saving in cache
[ https://issues.apache.org/jira/browse/MBUILDCACHE-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841863#comment-17841863 ] ASF GitHub Bot commented on MBUILDCACHE-93: --- kbuntrock commented on PR #148: URL: https://github.com/apache/maven-build-cache-extension/pull/148#issuecomment-2081974274 @olamy: thank you :) > Command line configuration to disable saving in cache > - > > Key: MBUILDCACHE-93 > URL: https://issues.apache.org/jira/browse/MBUILDCACHE-93 > Project: Maven Build Cache Extension > Issue Type: New Feature >Reporter: Kevin Buntrock >Assignee: Olivier Lamy >Priority: Minor > Labels: pull-request-available > > Command line configuration to disable saving in cache. > We have already a configuration to : > - Disable totally any cache interaction > - Disable restoring from the cache > - Disable saving on the remote cache > But there is no configuration to disable "classic" saving to the cache. > Use case can be : > Having limited space on machine and therefore a limited number of saved build > allowed. > -> Restricting cache save to the "master" branch / configuring PR branch > build to benefits from the cache, but disallowing any save from them > It's personally a functionality I use since November and the cache hit rate > on my project with this technic is pretty nice. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MBUILDCACHE-93] Command line configuration to skip saving in cache [maven-build-cache-extension]
kbuntrock commented on PR #148: URL: https://github.com/apache/maven-build-cache-extension/pull/148#issuecomment-2081974274 @olamy: thank you :) -- 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] No maven compat [maven-reporting-exec]
michael-o commented on PR #20: URL: https://github.com/apache/maven-reporting-exec/pull/20#issuecomment-2081972300 @cstamas Please take a look today. Want to start the vote this late afternoon. -- 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] [MBUILDCACHE-90] A "mandatory clean" option to enable the caching functionnality [maven-build-cache-extension]
kbuntrock commented on PR #103: URL: https://github.com/apache/maven-build-cache-extension/pull/103#issuecomment-2081973553 @olamy: Merge conflicts are resolved. Please merge this one before [MBUILDCACHE-86] (which I will fix after this merge) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8084] add API metadata group [maven]
hboutemy merged PR #1492: URL: https://github.com/apache/maven/pull/1492 -- 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-8084) Make the v4 api usable outside the Maven runtime
[ https://issues.apache.org/jira/browse/MNG-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841857#comment-17841857 ] ASF GitHub Bot commented on MNG-8084: - hboutemy opened a new pull request, #1492: URL: https://github.com/apache/maven/pull/1492 (no comment) > Make the v4 api usable outside the Maven runtime > > > Key: MNG-8084 > URL: https://issues.apache.org/jira/browse/MNG-8084 > Project: Maven > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
