[jira] [Created] (MNG-8119) Remove build section in consumer pom profiles
Guillaume Nodet created MNG-8119: Summary: Remove build section in consumer pom profiles Key: MNG-8119 URL: https://issues.apache.org/jira/browse/MNG-8119 Project: Maven Issue Type: Improvement Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.0.0-beta-1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8118] Merge BOM exclusions instead of overwriting [maven]
gnodet merged PR #1504: URL: https://github.com/apache/maven/pull/1504 -- 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-8118) Dependency-management "client" exclusions overwrite BOM exclusions
[ https://issues.apache.org/jira/browse/MNG-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845791#comment-17845791 ] ASF GitHub Bot commented on MNG-8118: - gnodet merged PR #1504: URL: https://github.com/apache/maven/pull/1504 > Dependency-management "client" exclusions overwrite BOM exclusions > -- > > Key: MNG-8118 > URL: https://issues.apache.org/jira/browse/MNG-8118 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-alpha-13, 4.0.x-candidate > Environment: Any >Reporter: Lenny Primak >Assignee: Guillaume Nodet >Priority: Major > > When importing BOM and introducing exclusions, they overwrite exclusions > already present in the BOM. They should not > Slack conversation link: > https://the-asf.slack.com/archives/C7Q9JB404/p1714938396499939 > Regressed by https://issues.apache.org/jira/browse/MNG-5600 > Reproducer app: [https://github.com/lprimak/apps/tree/main/emailmanager] > Fixed by: https://github.com/apache/maven/pull/1504 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump org.apache.maven.shared:maven-invoker from 3.2.0 to 3.3.0 [maven-release]
dependabot[bot] opened a new pull request, #215: URL: https://github.com/apache/maven-release/pull/215 Bumps [org.apache.maven.shared:maven-invoker](https://github.com/apache/maven-invoker) from 3.2.0 to 3.3.0. Release notes Sourced from https://github.com/apache/maven-invoker/releases";>org.apache.maven.shared:maven-invoker's releases. 3.3.0 🚀 New features and improvements https://issues.apache.org/jira/browse/MSHARED-1390";>[MSHARED-1390] - Deprecate InvocationRequest#setGoals (https://redirect.github.com/apache/maven-invoker/pull/76";>#76) https://github.com/slawekjaranowski";>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-1382";>[MSHARED-1382] - support a possibility to disable snapshots update. (https://redirect.github.com/apache/maven-invoker/pull/74";>#74) https://github.com/lrozenblyum";>@lrozenblyum https://issues.apache.org/jira/browse/MSHARED-1150";>[MSHARED-1150] - Add ps1 as detectable file type for PowerShell (https://redirect.github.com/apache/maven-invoker/pull/55";>#55) https://github.com/iofit";>@iofit 🐛 Bug Fixes https://issues.apache.org/jira/browse/MSHARED-971";>[MSHARED-971] - Add test for inherited environment (https://redirect.github.com/apache/maven-invoker/pull/79";>#79) https://github.com/slawekjaranowski";>@slawekjaranowski 📦 Dependency updates https://issues.apache.org/jira/browse/MSHARED-1388";>[MSHARED-1388] - Bump org.apache.maven.shared:maven-shared-components from 41 to 42 (https://redirect.github.com/apache/maven-invoker/pull/73";>#73) https://github.com/dependabot";>@dependabot Bump apache/maven-gh-actions-shared from 3 to 4 (https://redirect.github.com/apache/maven-invoker/pull/72";>#72) https://github.com/dependabot";>@dependabot Bump org.junit:junit-bom from 5.10.1 to 5.10.2 (https://redirect.github.com/apache/maven-invoker/pull/71";>#71) https://github.com/dependabot";>@dependabot Bump org.apache.maven.shared:maven-shared-components from 39 to 41 (https://redirect.github.com/apache/maven-invoker/pull/70";>#70) https://github.com/dependabot";>@dependabot Bump org.junit:junit-bom from 5.10.0 to 5.10.1 (https://redirect.github.com/apache/maven-invoker/pull/69";>#69) https://github.com/dependabot";>@dependabot https://issues.apache.org/jira/browse/MSHARED-1305";>[MSHARED-1305] - update maven-shared-utils to 3.4.2 (https://redirect.github.com/apache/maven-invoker/pull/65";>#65) https://github.com/elharo";>@elharo Bump org.junit:junit-bom from 5.9.2 to 5.10.0 (https://redirect.github.com/apache/maven-invoker/pull/64";>#64) https://github.com/dependabot";>@dependabot Bump junit-bom from 5.9.1 to 5.9.2 (https://redirect.github.com/apache/maven-invoker/pull/60";>#60) https://github.com/dependabot";>@dependabot https://issues.apache.org/jira/browse/MSHARED-1151";>[MSHARED-1151] - Upgrade parent to version 39 (https://redirect.github.com/apache/maven-invoker/pull/58";>#58) https://github.com/psiroky";>@psiroky Bump maven-pmd-plugin from 3.16.0 to 3.18.0 (https://redirect.github.com/apache/maven-invoker/pull/52";>#52) https://github.com/dependabot";>@dependabot 👻 Maintenance https://issues.apache.org/jira/browse/MSHARED-1152";>[MSHARED-1152] - Remove public modifier for JUnit5 tests (https://redirect.github.com/apache/maven-invoker/pull/77";>#77) https://github.com/slawekjaranowski";>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-1391";>[MSHARED-1391] - Code cleanups (https://redirect.github.com/apache/maven-invoker/pull/78";>#78) https://github.com/slawekjaranowski";>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-1389";>[MSHARED-1389] - Refresh download page (https://redirect.github.com/apache/maven-invoker/pull/75";>#75) https://github.com/slawekjaranowski";>@slawekjaranowski Bump org.junit:junit-bom from 5.10.1 to 5.10.2 (https://redirect.github.com/apache/maven-invoker/pull/71";>#71) https://github.com/dependabot";>@dependabot https://issues.apache.org/jira/browse/MSHARED-1307";>[MSHARED-1307] - systemProperties is deprecated: Use systemPropertyVari… (https://redirect.github.com/apache/maven-invoker/pull/68";>#68) https://github.com/elharo";>@elharo https://issues.apache.org/jira/browse/MSHARED-1306";>[MSHARED-1306] - Use fixtures to reduce duplicate code (https://redirect.github.com/apache/maven-invoker/pull/67";>#67) https://github.com/elharo";>@elharo https://issues.apache.org/jira/browse/MSHARED-1306";>[MSHARED-1306] - don't log from passing tests (https://redirect.github.com/apache/maven-invoker/pull/66";>#66) https://github.com/elharo";>@elharo https://issues.apache.org/jira/browse/MNG-6829";>[MNG-6829] - Replace any StringUtils#isEmpty(String) and #isNotEmpty(String) (https://redirect.github.com/apache/maven-invoker/pull/63";>#63) https://github.com/timtebeek";>@timtebeek https://issues.apache.org/jira/browse/MSHARED-1152";>[MSHARED-1152] - Migr
Re: [PR] Bump doxiaVersion from 2.0.0-M10-SNAPSHOT to 2.0.0-M10 [maven-doxia-converter]
dependabot[bot] commented on PR #67: URL: https://github.com/apache/maven-doxia-converter/pull/67#issuecomment-2106651068 Superseded by #71. -- 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 doxiaVersion from 2.0.0-M10-SNAPSHOT to 2.0.0-M10 [maven-doxia-converter]
dependabot[bot] closed pull request #67: Bump doxiaVersion from 2.0.0-M10-SNAPSHOT to 2.0.0-M10 URL: https://github.com/apache/maven-doxia-converter/pull/67 -- 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 doxiaVersion from 2.0.0-M10-SNAPSHOT to 2.0.0-M11 [maven-doxia-converter]
dependabot[bot] opened a new pull request, #71: URL: https://github.com/apache/maven-doxia-converter/pull/71 Bumps `doxiaVersion` from 2.0.0-M10-SNAPSHOT to 2.0.0-M11. Updates `org.apache.maven.doxia:doxia-core` from 2.0.0-M10-SNAPSHOT to 2.0.0-M11 Commits See full diff in https://github.com/apache/maven-doxia/commits/doxia-2.0.0-M11";>compare view Updates `org.apache.maven.doxia:doxia-sink-api` from 2.0.0-M10-SNAPSHOT to 2.0.0-M11 Commits See full diff in https://github.com/apache/maven-doxia/commits/doxia-2.0.0-M11";>compare view Updates `org.apache.maven.doxia:doxia-module-apt` from 2.0.0-M10-SNAPSHOT to 2.0.0-M11 Updates `org.apache.maven.doxia:doxia-module-fml` from 2.0.0-M10-SNAPSHOT to 2.0.0-M11 Updates `org.apache.maven.doxia:doxia-module-xdoc` from 2.0.0-M10-SNAPSHOT to 2.0.0-M11 Updates `org.apache.maven.doxia:doxia-module-xhtml5` from 2.0.0-M10-SNAPSHOT to 2.0.0-M11 Updates `org.apache.maven.doxia:doxia-module-markdown` from 2.0.0-M10-SNAPSHOT to 2.0.0-M11 Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump doxiaVersion from 2.0.0-M10 to 2.0.0-M11 [maven-site-plugin]
dependabot[bot] opened a new pull request, #186: URL: https://github.com/apache/maven-site-plugin/pull/186 Bumps `doxiaVersion` from 2.0.0-M10 to 2.0.0-M11. Updates `org.apache.maven.doxia:doxia-sink-api` from 2.0.0-M10 to 2.0.0-M11 Commits https://github.com/apache/maven-doxia/commit/21c2e55ad4dbffe23165b0cd5da8a751af502c1b";>21c2e55 [maven-release-plugin] prepare release doxia-2.0.0-M11 https://github.com/apache/maven-doxia/commit/6051b7286f8c181bcb38ff57de623e94e84bb546";>6051b72 Explictily set Java version https://github.com/apache/maven-doxia/commit/11c6a53f9308848813fa09ce4a7d111ce2e75ee0";>11c6a53 [DOXIA-736] Upgrade to Parent 42 https://github.com/apache/maven-doxia/commit/5cfb8ee091acb9f036d003a537748cfa7ac1f8a9";>5cfb8ee Remove invalid tag https://github.com/apache/maven-doxia/commit/9c3a6564a22c11a172ad420cc6662e3007b69cff";>9c3a656 Use non-deprecated code https://github.com/apache/maven-doxia/commit/c1a38e62e99d5f100cef4d990c67ee2fcc0f8955";>c1a38e6 Fix Javadoc issue https://github.com/apache/maven-doxia/commit/b3088e760105fd86014b4a1e28fe85e424f868d9";>b3088e7 [maven-release-plugin] prepare for next development iteration See full diff in https://github.com/apache/maven-doxia/compare/doxia-2.0.0-M10...doxia-2.0.0-M11";>compare view Updates `org.apache.maven.doxia:doxia-core` from 2.0.0-M10 to 2.0.0-M11 Commits https://github.com/apache/maven-doxia/commit/21c2e55ad4dbffe23165b0cd5da8a751af502c1b";>21c2e55 [maven-release-plugin] prepare release doxia-2.0.0-M11 https://github.com/apache/maven-doxia/commit/6051b7286f8c181bcb38ff57de623e94e84bb546";>6051b72 Explictily set Java version https://github.com/apache/maven-doxia/commit/11c6a53f9308848813fa09ce4a7d111ce2e75ee0";>11c6a53 [DOXIA-736] Upgrade to Parent 42 https://github.com/apache/maven-doxia/commit/5cfb8ee091acb9f036d003a537748cfa7ac1f8a9";>5cfb8ee Remove invalid tag https://github.com/apache/maven-doxia/commit/9c3a6564a22c11a172ad420cc6662e3007b69cff";>9c3a656 Use non-deprecated code https://github.com/apache/maven-doxia/commit/c1a38e62e99d5f100cef4d990c67ee2fcc0f8955";>c1a38e6 Fix Javadoc issue https://github.com/apache/maven-doxia/commit/b3088e760105fd86014b4a1e28fe85e424f868d9";>b3088e7 [maven-release-plugin] prepare for next development iteration See full diff in https://github.com/apache/maven-doxia/compare/doxia-2.0.0-M10...doxia-2.0.0-M11";>compare view Updates `org.apache.maven.doxia:doxia-module-xhtml5` from 2.0.0-M10 to 2.0.0-M11 Updates `org.apache.maven.doxia:doxia-module-apt` from 2.0.0-M10 to 2.0.0-M11 Updates `org.apache.maven.doxia:doxia-module-xdoc` from 2.0.0-M10 to 2.0.0-M11 Updates `org.apache.maven.doxia:doxia-module-fml` from 2.0.0-M10 to 2.0.0-M11 Updates `org.apache.maven.doxia:doxia-module-markdown` from 2.0.0-M10 to 2.0.0-M11 Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump org.mockito:mockito-core from 5.11.0 to 5.12.0 [maven-resolver]
dependabot[bot] opened a new pull request, #493: URL: https://github.com/apache/maven-resolver/pull/493 Bumps [org.mockito:mockito-core](https://github.com/mockito/mockito) from 5.11.0 to 5.12.0. Release notes Sourced from https://github.com/mockito/mockito/releases";>org.mockito:mockito-core's releases. v5.12.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 5.12.0 2024-05-11 - https://github.com/mockito/mockito/compare/v5.11.0...v5.12.0";>25 commit(s) by Piotr Przybylak, Stefano Cordio, Tim van der Lippe, dependabot[bot], jonghoonpark Bump com.gradle.enterprise from 3.17.2 to 3.17.3 [(https://redirect.github.com/mockito/mockito/issues/3341";>#3341)](https://redirect.github.com/mockito/mockito/pull/3341";>mockito/mockito#3341) Bump org.jetbrains.kotlin:kotlin-stdlib from 1.9.23 to 1.9.24 [(https://redirect.github.com/mockito/mockito/issues/3339";>#3339)](https://redirect.github.com/mockito/mockito/pull/3339";>mockito/mockito#3339) Bump versions.bytebuddy from 1.14.14 to 1.14.15 [(https://redirect.github.com/mockito/mockito/issues/3338";>#3338)](https://redirect.github.com/mockito/mockito/pull/3338";>mockito/mockito#3338) Bump org.shipkit:shipkit-auto-version from 2.0.6 to 2.0.7 [(https://redirect.github.com/mockito/mockito/issues/3337";>#3337)](https://redirect.github.com/mockito/mockito/pull/3337";>mockito/mockito#3337) Bump org.jetbrains.kotlin:kotlin-gradle-plugin from 1.9.23 to 1.9.24 [(https://redirect.github.com/mockito/mockito/issues/3336";>#3336)](https://redirect.github.com/mockito/mockito/pull/3336";>mockito/mockito#3336) Fixes https://redirect.github.com/mockito/mockito/issues/3331";>#3331 : Fix AdditionalMatchers.and() and AdditionalMatchers.or() not to swap the order of matchers [(https://redirect.github.com/mockito/mockito/issues/3335";>#3335)](https://redirect.github.com/mockito/mockito/pull/3335";>mockito/mockito#3335) AdditionalMatchers.and() and or() swap matcher order [(https://redirect.github.com/mockito/mockito/issues/3331";>#3331)](https://redirect.github.com/mockito/mockito/issues/3331";>mockito/mockito#3331) Bump gradle/wrapper-validation-action from 3.3.1 to 3.3.2 [(https://redirect.github.com/mockito/mockito/issues/3327";>#3327)](https://redirect.github.com/mockito/mockito/pull/3327";>mockito/mockito#3327) Bump versions.bytebuddy from 1.14.13 to 1.14.14 [(https://redirect.github.com/mockito/mockito/issues/3324";>#3324)](https://redirect.github.com/mockito/mockito/pull/3324";>mockito/mockito#3324) Bump org.shipkit:shipkit-auto-version from 2.0.5 to 2.0.6 [(https://redirect.github.com/mockito/mockito/issues/3322";>#3322)](https://redirect.github.com/mockito/mockito/pull/3322";>mockito/mockito#3322) Bump gradle/wrapper-validation-action from 3.3.0 to 3.3.1 [(https://redirect.github.com/mockito/mockito/issues/3320";>#3320)](https://redirect.github.com/mockito/mockito/pull/3320";>mockito/mockito#3320) Bump com.gradle.enterprise from 3.17 to 3.17.2 [(https://redirect.github.com/mockito/mockito/issues/3318";>#3318)](https://redirect.github.com/mockito/mockito/pull/3318";>mockito/mockito#3318) Bump gradle/wrapper-validation-action from 2.1.2 to 3.3.0 [(https://redirect.github.com/mockito/mockito/issues/3317";>#3317)](https://redirect.github.com/mockito/mockito/pull/3317";>mockito/mockito#3317) Update codecov-action version [(https://redirect.github.com/mockito/mockito/issues/3316";>#3316)](https://redirect.github.com/mockito/mockito/pull/3316";>mockito/mockito#3316) Bump com.google.googlejavaformat:google-java-format from 1.21.0 to 1.22.0 [(https://redirect.github.com/mockito/mockito/issues/3312";>#3312)](https://redirect.github.com/mockito/mockito/pull/3312";>mockito/mockito#3312) Bump com.gradle.enterprise from 3.16.2 to 3.17 [(https://redirect.github.com/mockito/mockito/issues/3311";>#3311)](https://redirect.github.com/mockito/mockito/pull/3311";>mockito/mockito#3311) Bump versions.bytebuddy from 1.14.12 to 1.14.13 [(https://redirect.github.com/mockito/mockito/issues/3308";>#3308)](https://redirect.github.com/mockito/mockito/pull/3308";>mockito/mockito#3308) Fix README logo [(https://redirect.github.com/mockito/mockito/issues/3305";>#3305)](https://redirect.github.com/mockito/mockito/pull/3305";>mockito/mockito#3305) Bump gradle/wrapper-validation-action from 2.1.1 to 2.1.2 [(https://redirect.github.com/mockito/mockito/issues/3303";>#3303)](https://redirect.github.com/mockito/mockito/pull/3303";>mockito/mockito#3303) Bump org.shipkit:shipkit-auto-version from 2.0.4 to 2.0.5 [(https://redirect.github.com/mockito/mockito/issues/3298";>#3298)](https://redirect.github.com/mockito/mockito/pull/3298";>mockito/mockito#3298) Bump org.jetbrains.kotlin:kotlin-gradle-plugin from 1.9.22 to 1.9.23 [(https://redirect.github.com/mockito/mockito/issues/3296";>#3296)](https://redirect.github.com/mockito/mockito/pull/3296";>mockito/mockito#3
[PR] Bump org.redisson:redisson from 3.29.0 to 3.30.0 [maven-resolver]
dependabot[bot] opened a new pull request, #492: URL: https://github.com/apache/maven-resolver/pull/492 Bumps [org.redisson:redisson](https://github.com/redisson/redisson) from 3.29.0 to 3.30.0. Release notes Sourced from https://github.com/redisson/redisson/releases";>org.redisson:redisson's releases. redisson-3.30.0 Feature - sslKeystoreType setting added Feature - RPatternTopic.getActiveTopic() method added (thanks to https://github.com/MasterShi";>@MasterShi) Feature - RJsonBucket.merge() method added Feature - Async, Rx, Reactive interfaces implemented for RBloomFilter object Feature - fallback mode for JCache Feature - https://github.com/redisson/redisson/wiki/2.-Configuration#223-passwords-encryption";>passwords encryption support Feature - https://github.com/redisson/redisson/wiki/14.-Integration-with-frameworks/#149-spring-cloud-stream";>Spring Cloud Stream integration Improvement - configuration variable defined as Java system property overrides environment variable Fixed - io.projectreactor package should be defined as optional in OSGi Manifest Fixed - Spring Data Redis StreamPollTask.deserializeAndEmitRecords() method throws NPE after failover Fixed - Spring Data Redis blocking poll commands can't be reattached after failover Fixed - Unable to find session error reported by RedissonSessionManager Fixed - Sentinels discovery is applied at Redisson startup if sentinelsDiscovery = true Fixed - master node is used for read operations after slave node addition if readMode = SLAVE in replicated mode Fixed - failover handling of blocking methods calls with defined timeout. RStream, RBlockingQueue objects Fixed - multiple RLocalCachedMap objects don't work in the same RTransaction (thanks to https://github.com/vlad-ogol";>@vlad-ogol https://github.com/RajaJaisankar";>@RajaJaisankar) Fixed - codec setting isn't applied in redisson.getMap(MapOptions) method Fixed - Live Object field can't set to null value Fixed - SentinelConnectionManager stops scheduling topology change change / dns check after host resolution error Fixed - RMapCache.fastPutIfExistsOperation() method uses incorrect pubsub channel Changelog Sourced from https://github.com/redisson/redisson/blob/master/CHANGELOG.md";>org.redisson:redisson's changelog. 10-May-2024 - 3.30.0 released Feature - sslKeystoreType setting added Feature - RPatternTopic.getActiveTopic() method added (thanks to https://github.com/MasterShi";>@MasterShi) Feature - RJsonBucket.merge() method added Feature - Async, Rx, Reactive interfaces implemented for RBloomFilter object Feature - fallback mode for JCache Feature - https://github.com/redisson/redisson/wiki/2.-Configuration#223-passwords-encryption";>passwords encryption support Feature - https://github.com/redisson/redisson/wiki/14.-Integration-with-frameworks/#149-spring-cloud-stream";>Spring Cloud Stream integration Improvement - configuration variable defined as Java system property overrides environment variable Fixed - io.projectreactor package should be defined as optional in OSGi Manifest Fixed - Spring Data Redis StreamPollTask.deserializeAndEmitRecords() method throws NPE after failover Fixed - Spring Data Redis blocking poll commands can't be reattached after failover Fixed - Unable to find session error reported by RedissonSessionManager Fixed - Sentinels discovery is applied at Redisson startup if sentinelsDiscovery = true Fixed - master node is used for read operations after slave node addition if readMode = SLAVE in replicated mode Fixed - failover handling of blocking methods calls with defined timeout. RStream, RBlockingQueue objects Fixed - multiple RLocalCachedMap objects don't work in the same RTransaction (thanks to https://github.com/vlad-ogol";>@vlad-ogol https://github.com/RajaJaisankar";>@RajaJaisankar) Fixed - codec setting isn't applied in redisson.getMap(MapOptions) method Fixed - Live Object field can't set to null value Fixed - SentinelConnectionManager stops scheduling topology change change / dns check after host resolution error Fixed - RMapCache.fastPutIfExistsOperation() method uses incorrect pubsub channel Commits https://github.com/redisson/redisson/commit/49dcea0be6e58d64e7554c3aa8b05060c9377432";>49dcea0 [maven-release-plugin] prepare release redisson-3.30.0 https://github.com/redisson/redisson/commit/6f3acebe56f9ac11403b4b47708abfcd6c11abae";>6f3aceb refactoring https://github.com/redisson/redisson/commit/c1d3e4881a02782cfaf12142f0eec556935fa576";>c1d3e48 test fixed https://github.com/redisson/redisson/commit/7a8ee736dac95ba057eada10d39066083e8cdb5c";>7a8ee73 refactoring https://github.com/redisson/redisson/commit/ab31631880c0f5dd8ed2d50c6e043730ab6a1cb4";>ab31631 Fixed - io.projectreactor should be defined as optional in OSGi MANI
[PR] Bump org.apache.maven.shared:maven-invoker from 3.2.0 to 3.3.0 [maven-gpg-plugin]
dependabot[bot] opened a new pull request, #102: URL: https://github.com/apache/maven-gpg-plugin/pull/102 Bumps [org.apache.maven.shared:maven-invoker](https://github.com/apache/maven-invoker) from 3.2.0 to 3.3.0. Release notes Sourced from https://github.com/apache/maven-invoker/releases";>org.apache.maven.shared:maven-invoker's releases. 3.3.0 🚀 New features and improvements https://issues.apache.org/jira/browse/MSHARED-1390";>[MSHARED-1390] - Deprecate InvocationRequest#setGoals (https://redirect.github.com/apache/maven-invoker/pull/76";>#76) https://github.com/slawekjaranowski";>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-1382";>[MSHARED-1382] - support a possibility to disable snapshots update. (https://redirect.github.com/apache/maven-invoker/pull/74";>#74) https://github.com/lrozenblyum";>@lrozenblyum https://issues.apache.org/jira/browse/MSHARED-1150";>[MSHARED-1150] - Add ps1 as detectable file type for PowerShell (https://redirect.github.com/apache/maven-invoker/pull/55";>#55) https://github.com/iofit";>@iofit 🐛 Bug Fixes https://issues.apache.org/jira/browse/MSHARED-971";>[MSHARED-971] - Add test for inherited environment (https://redirect.github.com/apache/maven-invoker/pull/79";>#79) https://github.com/slawekjaranowski";>@slawekjaranowski 📦 Dependency updates https://issues.apache.org/jira/browse/MSHARED-1388";>[MSHARED-1388] - Bump org.apache.maven.shared:maven-shared-components from 41 to 42 (https://redirect.github.com/apache/maven-invoker/pull/73";>#73) https://github.com/dependabot";>@dependabot Bump apache/maven-gh-actions-shared from 3 to 4 (https://redirect.github.com/apache/maven-invoker/pull/72";>#72) https://github.com/dependabot";>@dependabot Bump org.junit:junit-bom from 5.10.1 to 5.10.2 (https://redirect.github.com/apache/maven-invoker/pull/71";>#71) https://github.com/dependabot";>@dependabot Bump org.apache.maven.shared:maven-shared-components from 39 to 41 (https://redirect.github.com/apache/maven-invoker/pull/70";>#70) https://github.com/dependabot";>@dependabot Bump org.junit:junit-bom from 5.10.0 to 5.10.1 (https://redirect.github.com/apache/maven-invoker/pull/69";>#69) https://github.com/dependabot";>@dependabot https://issues.apache.org/jira/browse/MSHARED-1305";>[MSHARED-1305] - update maven-shared-utils to 3.4.2 (https://redirect.github.com/apache/maven-invoker/pull/65";>#65) https://github.com/elharo";>@elharo Bump org.junit:junit-bom from 5.9.2 to 5.10.0 (https://redirect.github.com/apache/maven-invoker/pull/64";>#64) https://github.com/dependabot";>@dependabot Bump junit-bom from 5.9.1 to 5.9.2 (https://redirect.github.com/apache/maven-invoker/pull/60";>#60) https://github.com/dependabot";>@dependabot https://issues.apache.org/jira/browse/MSHARED-1151";>[MSHARED-1151] - Upgrade parent to version 39 (https://redirect.github.com/apache/maven-invoker/pull/58";>#58) https://github.com/psiroky";>@psiroky Bump maven-pmd-plugin from 3.16.0 to 3.18.0 (https://redirect.github.com/apache/maven-invoker/pull/52";>#52) https://github.com/dependabot";>@dependabot 👻 Maintenance https://issues.apache.org/jira/browse/MSHARED-1152";>[MSHARED-1152] - Remove public modifier for JUnit5 tests (https://redirect.github.com/apache/maven-invoker/pull/77";>#77) https://github.com/slawekjaranowski";>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-1391";>[MSHARED-1391] - Code cleanups (https://redirect.github.com/apache/maven-invoker/pull/78";>#78) https://github.com/slawekjaranowski";>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-1389";>[MSHARED-1389] - Refresh download page (https://redirect.github.com/apache/maven-invoker/pull/75";>#75) https://github.com/slawekjaranowski";>@slawekjaranowski Bump org.junit:junit-bom from 5.10.1 to 5.10.2 (https://redirect.github.com/apache/maven-invoker/pull/71";>#71) https://github.com/dependabot";>@dependabot https://issues.apache.org/jira/browse/MSHARED-1307";>[MSHARED-1307] - systemProperties is deprecated: Use systemPropertyVari… (https://redirect.github.com/apache/maven-invoker/pull/68";>#68) https://github.com/elharo";>@elharo https://issues.apache.org/jira/browse/MSHARED-1306";>[MSHARED-1306] - Use fixtures to reduce duplicate code (https://redirect.github.com/apache/maven-invoker/pull/67";>#67) https://github.com/elharo";>@elharo https://issues.apache.org/jira/browse/MSHARED-1306";>[MSHARED-1306] - don't log from passing tests (https://redirect.github.com/apache/maven-invoker/pull/66";>#66) https://github.com/elharo";>@elharo https://issues.apache.org/jira/browse/MNG-6829";>[MNG-6829] - Replace any StringUtils#isEmpty(String) and #isNotEmpty(String) (https://redirect.github.com/apache/maven-invoker/pull/63";>#63) https://github.com/timtebeek";>@timtebeek https://issues.apache.org/jira/browse/MSHARED-1152";>[MSHARED-1152] - M
Re: [PR] Bump Maven Site Plugin AND Maven Fluido Skin [maven-site]
kwin commented on PR #525: URL: https://github.com/apache/maven-site/pull/525#issuecomment-2106355412 I have not deliberately changed anything about being more strict with section nesting, I think we should still allow starting with an h2. Could be an unintended side effect of fixing the nesting levels. Do we have a minimum example in MD? Any warning emitted? -- 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 Maven Site Plugin AND Maven Fluido Skin [maven-site]
michael-o commented on PR #525: URL: https://github.com/apache/maven-site/pull/525#issuecomment-2106353685 > > It is broken, the parsers are strict now for sections: > > So the build should fail when page is not generated at all due to error. From the top of my head I have no idea because this is now only with Markdown and most of the parsing is done with Flexmark anyway. But some of the strictness has been added by @kwin recently. The purpose is that the output should be parseable again from a Doxia point of view. Broken output cannot be parsed :-( -- 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 Maven Site Plugin AND Maven Fluido Skin [maven-site]
michael-o commented on PR #525: URL: https://github.com/apache/maven-site/pull/525#issuecomment-2106353225 > release history: https://private-user-images.githubusercontent.com/3578921/329851510-76c2c23e-53cd-4ee0-9fc7-7bc695c8bbb3.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTU1NDE0MDgsIm5iZiI6MTcxNTU0MTEwOCwicGF0aCI6Ii8zNTc4OTIxLzMyOTg1MTUxMC03NmMyYzIzZS01M2NkLTRlZTAtOWZjNy03YmM2OTVjOGJiYjMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDUxMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA1MTJUMTkxMTQ4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YjExMWM4ZjU0MWMyMmFhNzMzYjk2ZGZiNTNjODYwY2FmN2NmODYzNDAxZTExYzI1OTc3ZDljZGIxNzUyNTM3YiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.uF8lYoXangFAQq2bHYGICwRJVCEl1mfctxs_5JjQVgI";> Done. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump Maven Site Plugin AND Maven Fluido Skin [maven-site]
michael-o commented on PR #525: URL: https://github.com/apache/maven-site/pull/525#issuecomment-2106353179 > alignment also changed: https://private-user-images.githubusercontent.com/3578921/329851741-e46b6c30-1083-41a6-91d1-461197969493.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTU1NDE0MDgsIm5iZiI6MTcxNTU0MTEwOCwicGF0aCI6Ii8zNTc4OTIxLzMyOTg1MTc0MS1lNDZiNmMzMC0xMDgzLTQxYTYtOTFkMS00NjExOTc5Njk0OTMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDUxMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA1MTJUMTkxMTQ4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MjM4ODNkYThmM2IxZDhiMGQxYWM5NzRhMTA5N2Q4MjU1NWU5YWFiMjA3MjVmMzk2NWYzMjhjZmM2NWM3MzljYSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.FiQxmCs67onCsQxcvLCgf5M1XTpa0K_hIXcLzvO1kGQ";> Comes from https://issues.apache.org/jira/browse/MSKINS-230. We need to decide whether we want to keep it it have bootstrap style enforced. -- 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 Maven Site Plugin AND Maven Fluido Skin [maven-site]
michael-o commented on PR #525: URL: https://github.com/apache/maven-site/pull/525#issuecomment-2106351824 > > It is broken, the parsers are strict now for sections: > > So the build should fail when page is not generated at all due to error. @kwin, WDYT? -- 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] (MTOOLCHAINS-54) [regression] Paths with spaces trigger a build-time warning
[
https://issues.apache.org/jira/browse/MTOOLCHAINS-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MTOOLCHAINS-54.
-
Resolution: Not A Problem
> [regression] Paths with spaces trigger a build-time warning
> ---
>
> Key: MTOOLCHAINS-54
> URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-54
> Project: Maven Toolchains Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
> Environment: Maven 3.9.6
>Reporter: Gili
>Priority: Major
>
> When upgrading from version 3.1.0 to 3.2.0 I started getting the following
> build-time warning:
>
> {{[WARNING] Unrecognized output form C:\Program
> Files\Java\zulu-8\bin\javac.exe -version - 'C:\Program' is not recognized as
> an internal or external command,}}
> {{operable program or batch file.}}
>
> The contents of toolchain.xml is:
>
> {{}}
> {{}}
> {{ }}
> {{ jdk}}
> {{ }}
> {{ 8}}
> {{ zulu}}
> {{ }}
> {{ }}
> {{ C:\Program Files\Java\zulu-8}}
> {{ }}
> {{ }}
> {{}}
>
> I don't know if this warning breaks anything.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MJAR-310) [regression] Version 3.4.x fails to handle toolchain paths that contain spaces
Gili created MJAR-310:
-
Summary: [regression] Version 3.4.x fails to handle toolchain
paths that contain spaces
Key: MJAR-310
URL: https://issues.apache.org/jira/browse/MJAR-310
Project: Maven JAR Plugin
Issue Type: Bug
Environment: Maven 3.9.6
Windows 10
Reporter: Gili
When upgrading from version 3.3.0 to 3.4.0 I started getting the following
build-time warning:
{{[WARNING] Unrecognized output form C:\Program Files\Java\zulu-8\bin\javac.exe
-version - 'C:\Program' is not recognized as an internal or external command,}}
{{operable program or batch file.}}
The contents of toolchain.xml is:
{{}}
{{}}
{{ }}
{{ jdk}}
{{ }}
{{ 8}}
{{ zulu}}
{{ }}
{{ }}
{{ C:\Program Files\Java\zulu-8}}
{{ }}
{{ }}
{{}}
I don't know if this warning breaks anything.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MTOOLCHAINS-54) [regression] Paths with spaces trigger a build-time warning
[
https://issues.apache.org/jira/browse/MTOOLCHAINS-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845741#comment-17845741
]
Gili commented on MTOOLCHAINS-54:
-
Sorry, please close this issue. The bug seems to be in the JAR plugin.
> [regression] Paths with spaces trigger a build-time warning
> ---
>
> Key: MTOOLCHAINS-54
> URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-54
> Project: Maven Toolchains Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
> Environment: Maven 3.9.6
>Reporter: Gili
>Priority: Major
>
> When upgrading from version 3.1.0 to 3.2.0 I started getting the following
> build-time warning:
>
> {{[WARNING] Unrecognized output form C:\Program
> Files\Java\zulu-8\bin\javac.exe -version - 'C:\Program' is not recognized as
> an internal or external command,}}
> {{operable program or batch file.}}
>
> The contents of toolchain.xml is:
>
> {{}}
> {{}}
> {{ }}
> {{ jdk}}
> {{ }}
> {{ 8}}
> {{ zulu}}
> {{ }}
> {{ }}
> {{ C:\Program Files\Java\zulu-8}}
> {{ }}
> {{ }}
> {{}}
>
> I don't know if this warning breaks anything.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MTOOLCHAINS-54) [regression] Paths with spaces trigger a build-time warning
Gili created MTOOLCHAINS-54:
---
Summary: [regression] Paths with spaces trigger a build-time
warning
Key: MTOOLCHAINS-54
URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-54
Project: Maven Toolchains Plugin
Issue Type: Bug
Affects Versions: 3.2.0
Environment: Maven 3.9.6
Reporter: Gili
When upgrading from version 3.1.0 to 3.2.0 I started getting the following
build-time warning:
{{[WARNING] Unrecognized output form C:\Program Files\Java\zulu-8\bin\javac.exe
-version - 'C:\Program' is not recognized as an internal or external command,}}
{{operable program or batch file.}}
The contents of toolchain.xml is:
{{}}
{{}}
{{ }}
{{ jdk}}
{{ }}
{{ 8}}
{{ zulu}}
{{ }}
{{ }}
{{ C:\Program Files\Java\zulu-8}}
{{ }}
{{ }}
{{}}
I don't know if this warning breaks anything.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MSHARED-1394) Upgrade Maven core dependencies to the latest and make as provided
[ https://issues.apache.org/jira/browse/MSHARED-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MSHARED-1394. Resolution: Fixed > Upgrade Maven core dependencies to the latest and make as provided > -- > > Key: MSHARED-1394 > URL: https://issues.apache.org/jira/browse/MSHARED-1394 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-dependency-analyzer >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-dependency-analyzer-1.14.0 > > > We need not to have a Maven core dependencies in compile scope. > When we use this artifact in another for analyze project all Maven > dependencies are in place also in provided scope. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1394) Upgrade Maven core dependencies to the latest and make as provided
[ https://issues.apache.org/jira/browse/MSHARED-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845724#comment-17845724 ] ASF GitHub Bot commented on MSHARED-1394: - slawekjaranowski merged PR #119: URL: https://github.com/apache/maven-dependency-analyzer/pull/119 > Upgrade Maven core dependencies to the latest and make as provided > -- > > Key: MSHARED-1394 > URL: https://issues.apache.org/jira/browse/MSHARED-1394 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-dependency-analyzer >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: maven-dependency-analyzer-1.14.0 > > > We need not to have a Maven core dependencies in compile scope. > When we use this artifact in another for analyze project all Maven > dependencies are in place also in provided scope. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MSHARED-1394] Upgrade Maven core dependencies to the latest and maka as provided [maven-dependency-analyzer]
slawekjaranowski merged PR #119: URL: https://github.com/apache/maven-dependency-analyzer/pull/119 -- 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] (MRESOURCES-306) Delete Extracting Javadoc metadata for log message
Elliotte Rusty Harold created MRESOURCES-306: Summary: Delete Extracting Javadoc metadata for log message Key: MRESOURCES-306 URL: https://issues.apache.org/jira/browse/MRESOURCES-306 Project: Maven Resources Plugin Issue Type: Improvement Reporter: Elliotte Rusty Harold More log junk no one cares about that gets in the way while trying to debug real failures in a build: [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ presto-client --- [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.valuesets.PrestoThriftRangeValueSet [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.valuesets.PrestoThriftRangeValueSet.PrestoThriftMarker [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.valuesets.PrestoThriftRangeValueSet.PrestoThriftRange [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftDomain [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.datatypes.PrestoThriftVarchar [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.datatypes.PrestoThriftDouble [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.datatypes.PrestoThriftBoolean [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.datatypes.PrestoThriftHyperLogLog [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftNullableSchemaName [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.datatypes.PrestoThriftJson [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.datatypes.PrestoThriftInteger [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftServiceException [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftNullableColumnSet [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftNullableToken [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.udf.ThriftUdfRequest [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftHostAddress [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.valuesets.PrestoThriftValueSet [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.valuesets.PrestoThriftEquatableValueSet [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.valuesets.PrestoThriftAllOrNoneValueSet [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftSchemaTableName [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.datatypes.PrestoThriftBigintArray [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftNullableTableMetadata [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftColumnMetadata [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.udf.ThriftFunctionHandle [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.udf.ThriftUdfStats [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftPageResult [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.udf.ThriftUdfServiceException [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.udf.ThriftUdfResult [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftTupleDomain [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.udf.UdfExecutionFailureInfo [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.udf.ThriftSerializedPage [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.udf.PrestoThriftPage [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftTableMetadata [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.datatypes.PrestoThriftTimestamp [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftSplit [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.datatypes.PrestoThriftBlock [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftId [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.udf.ThriftUdfPage [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.datatypes.PrestoThriftDate [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.datatypes.PrestoThriftBigint [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.connector.PrestoThriftSplitBatch [INFO] Extracting Javadoc metadata for com.facebook.presto.thrift.api.valuesets.PrestoThriftRangeValueSet.PrestoThriftBound [INFO] Extracting Javadoc
[jira] [Commented] (ARCHETYPE-637) PomUtils.addNewModule Pretty-Printing has issue on java 9+
[ https://issues.apache.org/jira/browse/ARCHETYPE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845722#comment-17845722 ] ASF GitHub Bot commented on ARCHETYPE-637: -- slawekjaranowski commented on PR #128: URL: https://github.com/apache/maven-archetype/pull/128#issuecomment-2106279995 Ok, We need review / resolve existing issues planed for next version: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317122%20AND%20fixVersion%20%3D%2012351178%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC Helping in this case is appreciated By the way there are many resolved issues and the last release was a more than two years ago So I added it to my release queue 😄 > PomUtils.addNewModule Pretty-Printing has issue on java 9+ > -- > > Key: ARCHETYPE-637 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-637 > Project: Maven Archetype > Issue Type: Bug > Components: Generator >Reporter: qxo >Assignee: Tamas Cservenak >Priority: Minor > Fix For: 3.3.0 > > > > *As of Java 9, the _Transformer_ class's pretty-print feature doesn't define > the actual format. Therefore, whitespace-only nodes will be outputted as > well.* This has been discussed in this [JDK bug > ticket|https://bugs.openjdk.java.net/browse/JDK-8262285?attachmentViewMode=list]. > Also, [Java 9's release > note|https://www.oracle.com/java/technologies/javase/9-notes.html] has > explained this in the xml/jaxp section. > *If we want our pretty-print method to always generate the same format under > various Java versions, we need to provide a stylesheet file.* > ref： > [https://bugs.openjdk.java.net/browse/JDK-8262285?attachmentViewMode=list] > > [https://www.baeldung.com/java-pretty-print-xml#pretty-printing-xml-with-the-transformer-class] -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [ARCHETYPE-637] fix PomUtils.addNewModule Pretty-Printing issue on java 9+ [maven-archetype]
slawekjaranowski commented on PR #128: URL: https://github.com/apache/maven-archetype/pull/128#issuecomment-2106279995 Ok, We need review / resolve existing issues planed for next version: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317122%20AND%20fixVersion%20%3D%2012351178%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC Helping in this case is appreciated By the way there are many resolved issues and the last release was a more than two years ago So I added it to my release queue 😄 -- 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 Maven Site Plugin AND Maven Fluido Skin [maven-site]
slawekjaranowski commented on PR #525: URL: https://github.com/apache/maven-site/pull/525#issuecomment-2106240810 alignment also changed: https://github.com/apache/maven-site/assets/3578921/e46b6c30-1083-41a6-91d1-461197969493";> -- 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 Maven Site Plugin AND Maven Fluido Skin [maven-site]
slawekjaranowski commented on PR #525: URL: https://github.com/apache/maven-site/pull/525#issuecomment-2106240343 > > It is broken, the parsers are strict now for sections: > So the build should fail when page is not generated at all due to error. -- 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 Maven Site Plugin AND Maven Fluido Skin [maven-site]
slawekjaranowski commented on PR #525: URL: https://github.com/apache/maven-site/pull/525#issuecomment-2106239721 release history: https://github.com/apache/maven-site/assets/3578921/76c2c23e-53cd-4ee0-9fc7-7bc695c8bbb3";> -- 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 Maven Site Plugin AND Maven Fluido Skin [maven-site]
michael-o commented on PR #525: URL: https://github.com/apache/maven-site/pull/525#issuecomment-2106223558 @slawekjaranowski This should fix it. The Markdown files were logically incorrect. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (MWRAPPER-133) MAVEN_CONFIG populated by Jenkins Maven Pipeline is no longer read,
[
https://issues.apache.org/jira/browse/MWRAPPER-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845700#comment-17845700
]
Ashley Scopes edited comment on MWRAPPER-133 at 5/12/24 11:57 AM:
--
We had the same issue, which was unfortunate.
For us, we have a Groovy function that we reuse to inject our default Maven
settings via the `withMaven` pipeline script plugin. To address this, we
injected the fixed environment variables into the function.
{code:groovy}
// vars/withMavenConfig.groovy
void call(Closure closure) {
withMaven(...) {
withEnv(["MAVEN_ARGS='${env.MAVEN_CONFIG}'"]) {
closure()
}
}
}
{code}
{code:groovy}
pipeline {
agent { label "master" }
environment { ... }
stages {
stage("Run") {
steps {
script {
withMavenConfig {
sh("./mvnw -B clean verify")
}
}
}
}
}
}
{code}
This is far from ideal though...
That being said, I feel that maybe Apache shouldn't have just totally removed
this, and instead deprecated it explicitly and made the wrapper log a warning
when encountered this, as this caused a lot of issues for us.
was (Author: JIRAUSER291213):
We had the same issue, which was unfortunate.
For us, we have a Groovy function that we reuse to inject our default Maven
settings via the `withMaven` pipeline script plugin. To address this, we
injected the fixed environment variables into the function.
{code:groovy}
void withCommonMavenSettings(Closure closure) {
withMaven(...) {
withEnv(["MAVEN_ARGS='${MAVEN_CONFIG}'"]) {
closure()
}
}
}
{code}
This is far from ideal though...
That being said, I feel that maybe Apache shouldn't have just totally removed
this, and instead deprecated it explicitly and made the wrapper log a warning
when encountered this, as this caused a lot of issues for us.
> MAVEN_CONFIG populated by Jenkins Maven Pipeline is no longer read,
> ---
>
> Key: MWRAPPER-133
> URL: https://issues.apache.org/jira/browse/MWRAPPER-133
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.0
>Reporter: Rocher Suchard
>Priority: Major
>
> Hello,
> Due to an update by Renovate in one of our project, I've seen some error
> related to internal dependencies not being picked up by Maven : while we were
> using a custom settings, it did not use it and was using Central instead of
> our Artifactory.
> Upon analysis, it seems that Maven Pipeline define a MAVEN_CONFIG
> environnement variable here :
> https://github.com/jenkinsci/pipeline-maven-plugin/blob/8cfaff9c021c971d19e5469c553a86d954c05387/pipeline-maven/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution2.java#L400
> The MAVEN_CONFIG variables was used in our Maven 3.2.0 Wrapper script and
> I've played around with the default value and type:
> {code:bash}
> $ mvn wrapper:3.3.0:wrapper -Dmaven=3.9.6
> # use scripts-only
> $ grep -r MAVEN_CONFIG mvnw mvnw.cmd .mvn/
> # nothing
> $ mvn wrapper:3.2.0:wrapper -Dmaven=3.9.6
> # use bin
> $ grep -r MAVEN_CONFIG mvnw mvnw.cmd .mvn/
> mvnw:MAVEN_CMD_LINE_ARGS="$MAVEN_CONFIG $*"
> mvnw: ${WRAPPER_LAUNCHER} $MAVEN_CONFIG "$@"
> mvnw.cmd: %WRAPPER_LAUNCHER% %MAVEN_CONFIG% %
> $ mvn wrapper:3.3.0:wrapper -Dmaven=3.9.6 -Dtype=bin
> ...
> [INFO] Unpacked bin type wrapper distribution
> org.apache.maven.wrapper:maven-wrapper-distribution:zip:bin:3.3.0
> [INFO] Configuring .mvn/wrapper/maven-wrapper.properties to use Maven 3.9.6
> and download from https://repo.maven.apache.org/maven2
> ...
> $ grep -r MAVEN_CONFIG mvnw mvnw.cmd .mvn/
> mvnw:MAVEN_CMD_LINE_ARGS="$MAVEN_CONFIG $*"
> mvnw: ${WRAPPER_LAUNCHER} $MAVEN_CONFIG "$@"
> mvnw.cmd: %WRAPPER_LAUNCHER% %MAVEN_CONFIG% %*
> {code}
> Is there a way to do the same for the script-only if this is to be the
> default ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MWRAPPER-133) MAVEN_CONFIG populated by Jenkins Maven Pipeline is no longer read,
[
https://issues.apache.org/jira/browse/MWRAPPER-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845700#comment-17845700
]
Ashley Scopes commented on MWRAPPER-133:
We had the same issue, which was unfortunate.
For us, we have a Groovy function that we reuse to inject our default Maven
settings via the `withMaven` pipeline script plugin. To address this, we
injected the fixed environment variables into the function.
{code:groovy}
void withCommonMavenSettings(Closure closure) {
withMaven(...) {
withEnv(["MAVEN_ARGS='${MAVEN_CONFIG}'"]) {
closure()
}
}
}
{code}
This is far from ideal though...
That being said, I feel that maybe Apache shouldn't have just totally removed
this, and instead deprecated it explicitly and made the wrapper log a warning
when encountered this, as this caused a lot of issues for us.
> MAVEN_CONFIG populated by Jenkins Maven Pipeline is no longer read,
> ---
>
> Key: MWRAPPER-133
> URL: https://issues.apache.org/jira/browse/MWRAPPER-133
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.0
>Reporter: Rocher Suchard
>Priority: Major
>
> Hello,
> Due to an update by Renovate in one of our project, I've seen some error
> related to internal dependencies not being picked up by Maven : while we were
> using a custom settings, it did not use it and was using Central instead of
> our Artifactory.
> Upon analysis, it seems that Maven Pipeline define a MAVEN_CONFIG
> environnement variable here :
> https://github.com/jenkinsci/pipeline-maven-plugin/blob/8cfaff9c021c971d19e5469c553a86d954c05387/pipeline-maven/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution2.java#L400
> The MAVEN_CONFIG variables was used in our Maven 3.2.0 Wrapper script and
> I've played around with the default value and type:
> {code:bash}
> $ mvn wrapper:3.3.0:wrapper -Dmaven=3.9.6
> # use scripts-only
> $ grep -r MAVEN_CONFIG mvnw mvnw.cmd .mvn/
> # nothing
> $ mvn wrapper:3.2.0:wrapper -Dmaven=3.9.6
> # use bin
> $ grep -r MAVEN_CONFIG mvnw mvnw.cmd .mvn/
> mvnw:MAVEN_CMD_LINE_ARGS="$MAVEN_CONFIG $*"
> mvnw: ${WRAPPER_LAUNCHER} $MAVEN_CONFIG "$@"
> mvnw.cmd: %WRAPPER_LAUNCHER% %MAVEN_CONFIG% %
> $ mvn wrapper:3.3.0:wrapper -Dmaven=3.9.6 -Dtype=bin
> ...
> [INFO] Unpacked bin type wrapper distribution
> org.apache.maven.wrapper:maven-wrapper-distribution:zip:bin:3.3.0
> [INFO] Configuring .mvn/wrapper/maven-wrapper.properties to use Maven 3.9.6
> and download from https://repo.maven.apache.org/maven2
> ...
> $ grep -r MAVEN_CONFIG mvnw mvnw.cmd .mvn/
> mvnw:MAVEN_CMD_LINE_ARGS="$MAVEN_CONFIG $*"
> mvnw: ${WRAPPER_LAUNCHER} $MAVEN_CONFIG "$@"
> mvnw.cmd: %WRAPPER_LAUNCHER% %MAVEN_CONFIG% %*
> {code}
> Is there a way to do the same for the script-only if this is to be the
> default ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MWRAPPER-137) Can't match distributionUrl when using MINGW64
[
https://issues.apache.org/jira/browse/MWRAPPER-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845699#comment-17845699
]
Ashley Scopes commented on MWRAPPER-137:
Didn't see this until after I'd raised a ticket and raised a fix for this...
JIRA hid this issue from me for some odd reason.
Raised a fix for this under MWRAPPER-139 at
https://github.com/apache/maven-wrapper/pull/139
> Can't match distributionUrl when using MINGW64
> --
>
> Key: MWRAPPER-137
> URL: https://issues.apache.org/jira/browse/MWRAPPER-137
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.1
>Reporter: Robert Scholte
>Priority: Major
>
> Any mvnw command fails with the following message:
> {noformat}
> $ ./mvnw verify
> 'istributionUrl is not valid, must match *-bin.zip or maven-mvnd-*.zip, but
> found
> 'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/4.0.0-alpha-13/apache-maven-4.0.0-alpha-13-bin.zip
> {noformat}
> Also notice that the {{d}} from distributionUrl has been replaced with a
> single quote.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MWRAPPER-139) Shell scripts break on LF in config for Windows
[
https://issues.apache.org/jira/browse/MWRAPPER-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845698#comment-17845698
]
ASF GitHub Bot commented on MWRAPPER-139:
-
ascopes opened a new pull request, #139:
URL: https://github.com/apache/maven-wrapper/pull/139
MWRAPPER-139: Remove trailing whitespace from fields in
maven-wrapper.properties
This prevents issues due to confusion between CRLF and LF when running in
more exotic locations such as MINGW on Windows but using ./mvnw rather than
./mvnw.cmd. A prime example of where this is an issue would be on
windows-latest GitHub Actions runners.
Fixes MWRAPPER-139, MWRAPPER-137 (which I didn't spot for some reason when
reviewing the
existing tickets on JIRA... might have been a blip in JIRA that didn't
display it?).
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [x] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
> Shell scripts break on LF in config for Windows
> ---
>
> Key: MWRAPPER-139
> URL: https://issues.apache.org/jira/browse/MWRAPPER-139
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.1
>Reporter: Ashley Scopes
>Priority: Major
>
> Today, I updated the Maven Wrapper in a project I have on GitHub by running
> `./mvnw wrapper:wrapper`, and then pushed it to GitHub.
> It appears that upon doing this, the bash scripts no longer work due to how
> newlines are being interpreted in the maven-wrapper.properties file.
> {code}
> + ./mvnw --version
> distributionUrl is not valid, must match *-bin.zip or maven-mvnd-*.zip, but
> found
> 'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.6/apache-maven-3.9.6-bin.zip
> '
> {code}
> This appears to just affect when running on GitHub actions with a Windows
> runner and the `bash` shell.
> I will see if I can find the issue and raise a fix in an MR
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump Maven Site Plugin AND Maven Fluido Skin [maven-site]
michael-o commented on PR #525: URL: https://github.com/apache/maven-site/pull/525#issuecomment-2106219738 > We should check it ... by other hands My test: > > * `What is Maven?`, `Maven Extensions` - is empty - markdown problems? > > * `Release Notes` - is almost empty - looks like macros not working > > > I not checked all pages 😄 Which release notes are empty? -- 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 Maven Site Plugin AND Maven Fluido Skin [maven-site]
michael-o commented on PR #525: URL: https://github.com/apache/maven-site/pull/525#issuecomment-2106219203 > We should check it ... by other hands My test: > > * `What is Maven?`, `Maven Extensions` - is empty - markdown problems? > > * `Release Notes` - is almost empty - looks like macros not working > > > I not checked all pages 😄 It is broken, the parsers are strict now for sections: ```patch D:\Entwicklung\Projekte\maven-site [bump-site-and-fluido-version ≡ +0 ~2 -0 !]> git diff content/markdown/what-is-maven.md diff --git a/content/markdown/what-is-maven.md b/content/markdown/what-is-maven.md index 9a8f73d4..bb848972 100644 --- a/content/markdown/what-is-maven.md +++ b/content/markdown/what-is-maven.md @@ -1,4 +1,4 @@ -## Introduction +# Introduction
[jira] [Created] (MWRAPPER-139) Shell scripts break on LF in config for Windows
Ashley Scopes created MWRAPPER-139:
--
Summary: Shell scripts break on LF in config for Windows
Key: MWRAPPER-139
URL: https://issues.apache.org/jira/browse/MWRAPPER-139
Project: Maven Wrapper
Issue Type: Bug
Components: Maven Wrapper Scripts
Affects Versions: 3.3.1
Reporter: Ashley Scopes
Today, I updated the Maven Wrapper in a project I have on GitHub by running
`./mvnw wrapper:wrapper`, and then pushed it to GitHub.
It appears that upon doing this, the bash scripts no longer work due to how
newlines are being interpreted in the maven-wrapper.properties file.
{code}
+ ./mvnw --version
distributionUrl is not valid, must match *-bin.zip or maven-mvnd-*.zip, but
found
'https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.6/apache-maven-3.9.6-bin.zip
'
{code}
This appears to just affect when running on GitHub actions with a Windows
runner and the `bash` shell.
I will see if I can find the issue and raise a fix in an MR
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MASSEMBLY-1030) Manifest entries from archive configuration are not added in final MANIFEST
[
https://issues.apache.org/jira/browse/MASSEMBLY-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MASSEMBLY-1030.
---
Resolution: Fixed
> Manifest entries from archive configuration are not added in final MANIFEST
> ---
>
> Key: MASSEMBLY-1030
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-1030
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: manifest
>Affects Versions: 3.7.1
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Major
> Fix For: 3.7.2
>
>
> given the follow configuration
> {code:java}
>
>
> src/main/assembly/web-bundle.xml
>
>
>
> ${project.build.outputDirectory}/META-INF/MANIFEST.MF
>
> ee10
>
>
> merge
> {code}
> he entries from manifestEntries are not added to MANIFEST file
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MASSEMBLY-1030) Manifest entries from archive configuration are not added in final MANIFEST
[
https://issues.apache.org/jira/browse/MASSEMBLY-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845690#comment-17845690
]
ASF GitHub Bot commented on MASSEMBLY-1030:
---
olamy merged PR #205:
URL: https://github.com/apache/maven-assembly-plugin/pull/205
> Manifest entries from archive configuration are not added in final MANIFEST
> ---
>
> Key: MASSEMBLY-1030
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-1030
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: manifest
>Affects Versions: 3.7.1
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Major
> Fix For: 3.7.2
>
>
> given the follow configuration
> {code:java}
>
>
> src/main/assembly/web-bundle.xml
>
>
>
> ${project.build.outputDirectory}/META-INF/MANIFEST.MF
>
> ee10
>
>
> merge
> {code}
> he entries from manifestEntries are not added to MANIFEST file
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MASSEMBLY-1030] Manifest entries from archive configuration are not added in final MANIFEST [maven-assembly-plugin]
olamy merged PR #205: URL: https://github.com/apache/maven-assembly-plugin/pull/205 -- 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 Maven Site Plugin AND Maven Fluido Skin [maven-site]
slawekjaranowski commented on PR #525: URL: https://github.com/apache/maven-site/pull/525#issuecomment-2106199112 We should check it ... by other hands My test: - `What is Maven?`, `Maven Extensions` - is empty - markdown problems? - `Release Notes` - is almost empty - looks like macros not working I not checked all pages 😄 -- 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] Drop banner name [maven-parent]
michael-o commented on code in PR #180:
URL: https://github.com/apache/maven-parent/pull/180#discussion_r1597606337
##
src/site/site.xml:
##
@@ -23,7 +23,6 @@ under the License.
xsi:schemaLocation="http://maven.apache.org/DECORATION/1.8.1
https://maven.apache.org/xsd/decoration-1.8.1.xsd";>
-${project.name}
Review Comment:
Just tried, does work.
--
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] Drop banner name [maven-parent]
michael-o commented on PR #180: URL: https://github.com/apache/maven-parent/pull/180#issuecomment-2106197890 > And should we also change in: > > https://github.com/apache/maven-parent/blob/c6750dfc7a8aa7161d0afd56550ab79965b331e9/docs/src/site/site.xml#L26-L30 Good catch! -- 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] Drop banner name [maven-parent]
slawekjaranowski commented on PR #180: URL: https://github.com/apache/maven-parent/pull/180#issuecomment-2106196425 And should we also change in: https://github.com/apache/maven-parent/blob/c6750dfc7a8aa7161d0afd56550ab79965b331e9/docs/src/site/site.xml#L27 -- 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] Drop banner name [maven-parent]
slawekjaranowski commented on code in PR #180:
URL: https://github.com/apache/maven-parent/pull/180#discussion_r1597604977
##
src/site/site.xml:
##
@@ -23,7 +23,6 @@ under the License.
xsi:schemaLocation="http://maven.apache.org/DECORATION/1.8.1
https://maven.apache.org/xsd/decoration-1.8.1.xsd";>
-${project.name}
Review Comment:
I hope that can be also done for old version of m-site-p
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[PR] Bump Maven Site Plugin AND Maven Fluido Skin [maven-site]
michael-o opened a new pull request, #525: URL: https://github.com/apache/maven-site/pull/525 Both need to be updated in tandem to get proper rendering results. Addresses one of the issues from https://the-asf.slack.com/archives/C7Q9JB404/p1715479275966359 -- 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] Drop banner name [maven-parent]
michael-o opened a new pull request, #180: URL: https://github.com/apache/maven-parent/pull/180 We don't need a banner name since we use an image as a banner. Both we be displayed side-by-side with Maven Fluido Skin 2.0.0. If the banner image needs an alternative text, the new Site Model does provide such an attribute. Addresses one of the issues from https://the-asf.slack.com/archives/C7Q9JB404/p1715479275966359 -- 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] Run Fail fast build with Java 22 [maven-gh-actions-shared]
slachiewicz closed pull request #99: Run Fail fast build with Java 22 URL: https://github.com/apache/maven-gh-actions-shared/pull/99 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MINVOKER-351) Prevent XML-prohibited characters from entering JUnit report
[
https://issues.apache.org/jira/browse/MINVOKER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845678#comment-17845678
]
Slawomir Jaranowski commented on MINVOKER-351:
--
[~mkjeldsen] thank it looks like we can simple use your example a next IT
> Prevent XML-prohibited characters from entering JUnit report
>
>
> Key: MINVOKER-351
> URL: https://issues.apache.org/jira/browse/MINVOKER-351
> Project: Maven Invoker Plugin
> Issue Type: Improvement
>Reporter: Mikkel Kjeldsen
>Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: minvoker-351.tar.gz
>
>
> Neither the Maven Invoker plugin's implementation of {{}}
> nor the underlying XML infrastructure directly protect against the presence
> of character literals prohibited by the XML specification, meaning such
> literals can appear in the JUnit report and render it unreadable. *I would
> appreciate if the Maven Invoker plugin could learn to strip prohibited
> literals to protect its users from creative plugins.* I argue that this is a
> safe and expected transformation that is not materially lossy.
>
> h2. Background
> MINVOKER-196 added the {{}} option [back in
> maven-invoker-plugin-3.2.1|https://github.com/apache/maven-invoker-plugin/blob/maven-invoker-plugin-3.2.1/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java#L1878-L1946].
> As of [maven-invoker-plugin-3.6.0 the effective implementation of the JUnit
> report remains effectively
> unchanged|https://github.com/apache/maven-invoker-plugin/blob/maven-invoker-plugin-3.6.0/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java#L1695-L1754].
> The JUnit report includes a {{}} element ([example
> documentation|https://github.com/testmoapp/junitxml]) whose value Maven
> Invoker populates with the raw build log contents. I've observed that this
> value is XML-escaped, which I imagine is well understood in the
> implementation, although I can't immediately find documentation to support
> that.
> However, escaping notwithstanding, a number of character literals are
> outright prohibited by the XML specifications. These literals cannot be
> escaped, and their presence renders an XML document not well formed. The
> exact set of prohibited characters varies by XML version; the report produced
> by the Maven Invoker plugin is XML version 1.0. When the Maven Invoker plugin
> reads in the build log it does not strip these character literals and neither
> does the XML writer the Maven Invoker plugin relies on. Consequently, if a
> build log ends up including a prohibited character the resulting JUnit report
> will not be well formed.
> The set of prohibited characters is the complement of [the XML
> specification's definition of {{Char}}|https://www.w3.org/TR/xml/#NT-Char].
> h2. Example
> Among the literals prohibited by XML version 1.0 is {{^H}} (backspace). When
> [pitest runs via Maven|https://pitest.org/quickstart/maven/] it prints a
> spinner to standard out, and the implementation uses backspace to render the
> spinner in place. I have used the Maven Invoker plugin with
> {{}} to verify a pitest configuration, whereby I discovered
> this limitation.
> h2. Remediation
> h3. Blame plugins
> Perhaps pitest should not behave this way but we can't change pitest, and
> even if pitest could be changed that offers no protection against any other
> plugin, so blaming plugins is an ineffective course of action.
> h3. Work-arounds
> The user can manually clean the build log in-place via
> {{}}. This is technically fairly easy to do, and makes
> the transformation very explicit, but it requires considerable local work to
> address an issue many would find obscure and the transformation is
> permanently lossy unless the user also backs up the raw log to another file
> name.
> h3. Strip prohibited literals inside Maven Invoker plugin
> If the Maven Invoker plugin learns to strip offending character literals
> in-between reading the build log and writing to the {{}} value
> then {{}} will Just Work™, which I assert is what a user
> will typically expect. Although the {{}} value will no longer
> exactly match the build log contents, this lossy translation is acceptable:
> the prohibited characters are overwhelmingly unprintable to begin with and
> therefore cannot be meaningfully rendered in a static context, and the raw
> build log remains unchanged in the event that the user needs to investigate
> or assert against the raw output.
> This change would be backwards compatible, because any existing user that
> would be affected by it would already have unparseable JUnit reports.
> * I _believe_ that Java's {{j.u.r.Pattern}} can trivially express the
> complement of allowed cha
[jira] [Commented] (MINVOKER-351) Prevent XML-prohibited characters from entering JUnit report
[
https://issues.apache.org/jira/browse/MINVOKER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845665#comment-17845665
]
Mikkel Kjeldsen commented on MINVOKER-351:
--
[~sjaranowski], see [^minvoker-351.tar.gz] . {{verify}} successfully runs an
Invoker test and generates a JUnit test report. The test prints ASCII to
standard out; some of those characters are not allowed in XML (IIRC there are
more). {{site}} then fails to generate a Surefire report.
> Prevent XML-prohibited characters from entering JUnit report
>
>
> Key: MINVOKER-351
> URL: https://issues.apache.org/jira/browse/MINVOKER-351
> Project: Maven Invoker Plugin
> Issue Type: Improvement
>Reporter: Mikkel Kjeldsen
>Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: minvoker-351.tar.gz
>
>
> Neither the Maven Invoker plugin's implementation of {{}}
> nor the underlying XML infrastructure directly protect against the presence
> of character literals prohibited by the XML specification, meaning such
> literals can appear in the JUnit report and render it unreadable. *I would
> appreciate if the Maven Invoker plugin could learn to strip prohibited
> literals to protect its users from creative plugins.* I argue that this is a
> safe and expected transformation that is not materially lossy.
>
> h2. Background
> MINVOKER-196 added the {{}} option [back in
> maven-invoker-plugin-3.2.1|https://github.com/apache/maven-invoker-plugin/blob/maven-invoker-plugin-3.2.1/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java#L1878-L1946].
> As of [maven-invoker-plugin-3.6.0 the effective implementation of the JUnit
> report remains effectively
> unchanged|https://github.com/apache/maven-invoker-plugin/blob/maven-invoker-plugin-3.6.0/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java#L1695-L1754].
> The JUnit report includes a {{}} element ([example
> documentation|https://github.com/testmoapp/junitxml]) whose value Maven
> Invoker populates with the raw build log contents. I've observed that this
> value is XML-escaped, which I imagine is well understood in the
> implementation, although I can't immediately find documentation to support
> that.
> However, escaping notwithstanding, a number of character literals are
> outright prohibited by the XML specifications. These literals cannot be
> escaped, and their presence renders an XML document not well formed. The
> exact set of prohibited characters varies by XML version; the report produced
> by the Maven Invoker plugin is XML version 1.0. When the Maven Invoker plugin
> reads in the build log it does not strip these character literals and neither
> does the XML writer the Maven Invoker plugin relies on. Consequently, if a
> build log ends up including a prohibited character the resulting JUnit report
> will not be well formed.
> The set of prohibited characters is the complement of [the XML
> specification's definition of {{Char}}|https://www.w3.org/TR/xml/#NT-Char].
> h2. Example
> Among the literals prohibited by XML version 1.0 is {{^H}} (backspace). When
> [pitest runs via Maven|https://pitest.org/quickstart/maven/] it prints a
> spinner to standard out, and the implementation uses backspace to render the
> spinner in place. I have used the Maven Invoker plugin with
> {{}} to verify a pitest configuration, whereby I discovered
> this limitation.
> h2. Remediation
> h3. Blame plugins
> Perhaps pitest should not behave this way but we can't change pitest, and
> even if pitest could be changed that offers no protection against any other
> plugin, so blaming plugins is an ineffective course of action.
> h3. Work-arounds
> The user can manually clean the build log in-place via
> {{}}. This is technically fairly easy to do, and makes
> the transformation very explicit, but it requires considerable local work to
> address an issue many would find obscure and the transformation is
> permanently lossy unless the user also backs up the raw log to another file
> name.
> h3. Strip prohibited literals inside Maven Invoker plugin
> If the Maven Invoker plugin learns to strip offending character literals
> in-between reading the build log and writing to the {{}} value
> then {{}} will Just Work™, which I assert is what a user
> will typically expect. Although the {{}} value will no longer
> exactly match the build log contents, this lossy translation is acceptable:
> the prohibited characters are overwhelmingly unprintable to begin with and
> therefore cannot be meaningfully rendered in a static context, and the raw
> build log remains unchanged in the event that the user needs to investigate
> or assert against the raw output.
> This change would be backwards compatib
[jira] [Updated] (MINVOKER-351) Prevent XML-prohibited characters from entering JUnit report
[
https://issues.apache.org/jira/browse/MINVOKER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikkel Kjeldsen updated MINVOKER-351:
-
Attachment: minvoker-351.tar.gz
> Prevent XML-prohibited characters from entering JUnit report
>
>
> Key: MINVOKER-351
> URL: https://issues.apache.org/jira/browse/MINVOKER-351
> Project: Maven Invoker Plugin
> Issue Type: Improvement
>Reporter: Mikkel Kjeldsen
>Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: minvoker-351.tar.gz
>
>
> Neither the Maven Invoker plugin's implementation of {{}}
> nor the underlying XML infrastructure directly protect against the presence
> of character literals prohibited by the XML specification, meaning such
> literals can appear in the JUnit report and render it unreadable. *I would
> appreciate if the Maven Invoker plugin could learn to strip prohibited
> literals to protect its users from creative plugins.* I argue that this is a
> safe and expected transformation that is not materially lossy.
>
> h2. Background
> MINVOKER-196 added the {{}} option [back in
> maven-invoker-plugin-3.2.1|https://github.com/apache/maven-invoker-plugin/blob/maven-invoker-plugin-3.2.1/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java#L1878-L1946].
> As of [maven-invoker-plugin-3.6.0 the effective implementation of the JUnit
> report remains effectively
> unchanged|https://github.com/apache/maven-invoker-plugin/blob/maven-invoker-plugin-3.6.0/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java#L1695-L1754].
> The JUnit report includes a {{}} element ([example
> documentation|https://github.com/testmoapp/junitxml]) whose value Maven
> Invoker populates with the raw build log contents. I've observed that this
> value is XML-escaped, which I imagine is well understood in the
> implementation, although I can't immediately find documentation to support
> that.
> However, escaping notwithstanding, a number of character literals are
> outright prohibited by the XML specifications. These literals cannot be
> escaped, and their presence renders an XML document not well formed. The
> exact set of prohibited characters varies by XML version; the report produced
> by the Maven Invoker plugin is XML version 1.0. When the Maven Invoker plugin
> reads in the build log it does not strip these character literals and neither
> does the XML writer the Maven Invoker plugin relies on. Consequently, if a
> build log ends up including a prohibited character the resulting JUnit report
> will not be well formed.
> The set of prohibited characters is the complement of [the XML
> specification's definition of {{Char}}|https://www.w3.org/TR/xml/#NT-Char].
> h2. Example
> Among the literals prohibited by XML version 1.0 is {{^H}} (backspace). When
> [pitest runs via Maven|https://pitest.org/quickstart/maven/] it prints a
> spinner to standard out, and the implementation uses backspace to render the
> spinner in place. I have used the Maven Invoker plugin with
> {{}} to verify a pitest configuration, whereby I discovered
> this limitation.
> h2. Remediation
> h3. Blame plugins
> Perhaps pitest should not behave this way but we can't change pitest, and
> even if pitest could be changed that offers no protection against any other
> plugin, so blaming plugins is an ineffective course of action.
> h3. Work-arounds
> The user can manually clean the build log in-place via
> {{}}. This is technically fairly easy to do, and makes
> the transformation very explicit, but it requires considerable local work to
> address an issue many would find obscure and the transformation is
> permanently lossy unless the user also backs up the raw log to another file
> name.
> h3. Strip prohibited literals inside Maven Invoker plugin
> If the Maven Invoker plugin learns to strip offending character literals
> in-between reading the build log and writing to the {{}} value
> then {{}} will Just Work™, which I assert is what a user
> will typically expect. Although the {{}} value will no longer
> exactly match the build log contents, this lossy translation is acceptable:
> the prohibited characters are overwhelmingly unprintable to begin with and
> therefore cannot be meaningfully rendered in a static context, and the raw
> build log remains unchanged in the event that the user needs to investigate
> or assert against the raw output.
> This change would be backwards compatible, because any existing user that
> would be affected by it would already have unparseable JUnit reports.
> * I _believe_ that Java's {{j.u.r.Pattern}} can trivially express the
> complement of allowed characters but there may exist more efficient solutions.
> * Consider also applying this transformation to
