[jira] [Updated] (MNG-7604) Removal of pom.* interpolation makes some older plugins defunct
[
https://issues.apache.org/jira/browse/MNG-7604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Mulders updated MNG-7604:
-
Summary: Removal of pom.* interpolation makes some older plugins defunct
(was: The MNG-7244 makes some older plugins defunct)
> Removal of pom.* interpolation makes some older plugins defunct
> ---
>
> Key: MNG-7604
> URL: https://issues.apache.org/jira/browse/MNG-7604
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 4.0.0-alpha-2
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-3
>
>
> The MNG-7244 removed completely the {{pom.*}} prefix interpolation, but IMHO
> intent was to do it for "currently built projects". The problem is that same
> interpolator is used in model builder to build transitive dependency models,
> and with the change Maven 4 lost it's ability to resolve artifacts like
> wagon-http 1.0-beta-6 (used by things like surefire 2.22.2 and so on).
> The implication is that Maven4 CANNOT resolve wagon-http 1.0-beta-6 (and
> implicitly surefire plugin 2.22.2 is defunct it seems as it uses it). Given
> we have NO 3.x release of surefire (just M releases), I bet many of users out
> there still use 2.22.2. Also, we have no idea how many other (used as
> transitive dependencies) artifact exists out there doing same/similar thing
> that wagon POM does.
> IMHO: rollback the change from master and we need alt fix for it, as making
> Maven 4 unable to resolve transitive deps using pom.* placeholder introduces
> a huge toll.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-archetype] sorin86-dan closed pull request #31: archetype-574: Added fix to use default values on integration-test if…
sorin86-dan closed pull request #31: archetype-574: Added fix to use default values on integration-test if… URL: https://github.com/apache/maven-archetype/pull/31 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-indexer] dependabot[bot] closed pull request #265: Bump version.spring from 5.3.23 to 6.0.0
dependabot[bot] closed pull request #265: Bump version.spring from 5.3.23 to 6.0.0 URL: https://github.com/apache/maven-indexer/pull/265 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-indexer] dependabot[bot] opened a new pull request, #272: Bump version.spring from 5.3.23 to 6.0.1
dependabot[bot] opened a new pull request, #272: URL: https://github.com/apache/maven-indexer/pull/272 Bumps `version.spring` from 5.3.23 to 6.0.1. Updates `spring-beans` from 5.3.23 to 6.0.1 Release notes Sourced from https://github.com/spring-projects/spring-framework/releases";>spring-beans's releases. v6.0.1 :star: New Features Make SourceHttpMessageConverter optional https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29535";>#29535 Deprecate LocalVariableTableParameterNameDiscoverer completely (avoiding its exposure in native images) https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/29531";>#29531 Make GeneratorStrategy.generate unreachable on native https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/29521";>#29521 Update LogAdapter to allow build-time code removal https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/29506";>#29506 :lady_beetle: Bug Fixes Unhandled exceptions should mark Servlet observation outcome as error https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29512";>#29512 :notebook_with_decorative_cover: Documentation Broken link in documentation section 6.10 https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29554";>#29554 Fix Javadoc link text in BindingResult https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/29551";>#29551 Fix some typos in Kotlin WebClient example code https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/29538";>#29538 Fix link to Bean Utils Light Library in BeanUtils Javadoc https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/29534";>#29534 Fix link to WebFlux section in reference manual https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/29525";>#29525 Document RuntimeHints testing strategies https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29523";>#29523 Reorganize and modularize the Testing chapter in the reference manual https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29522";>#29522 Document switch to SQLExceptionSubclassTranslator in the upgrade guide https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29518";>#29518 Update documentation to mention Java 17+ baseline https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29514";>#29514 Link to Spring WebFlux section is broken https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29513";>#29513 Update javadoc of Jackson-based decoders to reflect 2.14 baseline https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/29508";>#29508 Code example has callout from a different code example https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29505";>#29505 Code listing callouts are displayed incorrectly in core-beans.adoc https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29457";>#29457 Fix a syntax error in an XML listing in core-validation.adoc https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/29456";>#29456 :hammer: Dependency Upgrades Upgrade to Jackson 2.14.1 https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29539";>#29539 Upgrade to Kotlin 1.7.21 https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29543";>#29543 :heart: Contributors Thank you to all the contributors who worked on this release: https://github.com/Encyclopedias";>@Encyclopedias, https://github.com/andregasser";>@andregasser, https://github.com/davidcostanzo";>@davidcostanzo, https://github.com/divcon";>@divcon, https://github.com/jiangying000";>@jiangying000, https://github.com/mdeinum";>@mdeinum, and https://github.com/wilkinsona";>@wilkinsona v6.0.0 See https://github.com/spring-projects/spring-framework/wiki/What%27s-New-in-Spring-Framework-6.x";>What's New in Spring Framework 6.x and https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-6.x";>Upgrading to Spring Framework 6.x for upgrade instructions and details of new features. :star: New Features Avoid direct URL construction and URL equality checks https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29486";>#29486 Simplify creating RFC 7807 responses from functional endpoints https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29462";>#29462 Allow test classes to provide runtime hints via declarative mechanisms https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29455";>#29455 :notebook_with_decorative_cover: Documentation ... (truncated)
[GitHub] [maven-indexer] dependabot[bot] commented on pull request #265: Bump version.spring from 5.3.23 to 6.0.0
dependabot[bot] commented on PR #265: URL: https://github.com/apache/maven-indexer/pull/265#issuecomment-1325926577 Superseded by #272. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MDEP-809) Javadoc was not updated to reflect that :tree's verbose option is now ok
[ https://issues.apache.org/jira/browse/MDEP-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637995#comment-17637995 ] Hudson commented on MDEP-809: - Build succeeded in Jenkins: Maven » Maven TLP » maven-dependency-plugin » master #63 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/master/63/ > Javadoc was not updated to reflect that :tree's verbose option is now ok > > > Key: MDEP-809 > URL: https://issues.apache.org/jira/browse/MDEP-809 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: tree >Affects Versions: 3.3.0 >Reporter: Francois MAROT >Assignee: Slawomir Jaranowski >Priority: Trivial > Fix For: 3.4.0 > > > The TreeMojo's verbose option has been broken for a while but was corrected a > while ago. Nevertheless, the javadoc has not been updated to reflect that it > is useable again. > Many people, including me, may have been discouraged to use it due to this > broken javadoc. > ThomGeg has wrote here an extensive history analysis to what happened: > https://github.com/CycloneDX/cyclonedx-maven-plugin/pull/187#issuecomment-1130859621 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-doxia-sitetools] dependabot[bot] opened a new pull request, #72: Bump plexus-utils from 3.4.2 to 3.5.0
dependabot[bot] opened a new pull request, #72: URL: https://github.com/apache/maven-doxia-sitetools/pull/72 Bumps [plexus-utils](https://github.com/codehaus-plexus/plexus-utils) from 3.4.2 to 3.5.0. Release notes Sourced from https://github.com/codehaus-plexus/plexus-utils/releases";>plexus-utils's releases. 3.5.0 Don't throw IOException when none is required (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/206";>#206) (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/pull/221";>#221) https://github.com/michael-o";>@michael-o Always preserve dominant node value (even if empty) (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/pull/217";>#217) https://github.com/kwin";>@kwin Don't overwrite blank (but non-empty) dominant values during mergeXpp3Dom (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/pull/213";>#213) https://github.com/kwin";>@kwin Deprecate isEmpty(String) and isNotEmpty(String) in favour of same named (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/pull/218";>#218) https://github.com/kwin";>@kwin isEmpty(String) must not return false for whitespace-only values (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/pull/219";>#219) https://github.com/kwin";>@kwin Get rid maven-plugin-testing-harness from dependency (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/pull/208";>#208) https://github.com/slawekjaranowski";>@slawekjaranowski 📦 Dependency updates Bump plexus from 8 to 10 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/pull/207";>#207) https://github.com/dependabot";>@dependabot Bump release-drafter/release-drafter from 5.19.0 to 5.20.0 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/pull/205";>#205) https://github.com/dependabot";>@dependabot Commits https://github.com/codehaus-plexus/plexus-utils/commit/2b784ba7f518257c2215a34103c38bbda2a45056";>2b784ba [maven-release-plugin] prepare release plexus-utils-3.5.0 https://github.com/codehaus-plexus/plexus-utils/commit/f3771379bce9e64d985f0c1e73dbc6aae48b6d5b";>f377137 Don't throw IOException when none is required (https://github-redirect.dependabot.com/codehaus-plexus/plexus-utils/issues/206";>#206) https://github.com/codehaus-plexus/plexus-utils/commit/67ac243dbc6434c03a9b1582d94aef6bf2b5cf95";>67ac243 Xpp3DomUtils#mergeIntoXpp3Dom() must not override the dominant value in case ... https://github.com/codehaus-plexus/plexus-utils/commit/748933c5442ff13c9cca12bcdd88f64a209924ff";>748933c Xpp3DomUtils#mergeIntoXpp3Dom() must not override the dominant value in case ... https://github.com/codehaus-plexus/plexus-utils/commit/e2cafcf899e032d391f811c121a6d6cb7e2b8bdd";>e2cafcf Deprecate Xpp3DomUtils#isEmpty(String) and Xpp3DomUtils#isNotEmpty(String) in... https://github.com/codehaus-plexus/plexus-utils/commit/7f5114af7d0c4d19838a9e0082758ec0f5e0269e";>7f5114a isEmpty(String) must not return false for whitespace-only values https://github.com/codehaus-plexus/plexus-utils/commit/8a9147a07332b9ef554c9aa695aa4105532167e2";>8a9147a Update release-drafter.yml https://github.com/codehaus-plexus/plexus-utils/commit/d1fc4dc3c11cd2840b5d0750271bd4e21337b75c";>d1fc4dc Get rid maven-plugin-testing-harness from dependency https://github.com/codehaus-plexus/plexus-utils/commit/18a9836fbf0a30a1bf271e623da2a69c00d494b6";>18a9836 Bump plexus from 8 to 10 https://github.com/codehaus-plexus/plexus-utils/commit/5f702abf7d3b048b2ad58e789e7a4332c87da31a";>5f702ab we already have dependabot Additional commits viewable in https://github.com/codehaus-plexus/plexus-utils/compare/plexus-utils-3.4.2...plexus-utils-3.5.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 requ
[GitHub] [maven-doxia-sitetools] dependabot[bot] commented on pull request #62: Bump maven-parent from 36 to 37
dependabot[bot] commented on PR #62: URL: https://github.com/apache/maven-doxia-sitetools/pull/62#issuecomment-1325753668 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
[GitHub] [maven-doxia-sitetools] dependabot[bot] closed pull request #62: Bump maven-parent from 36 to 37
dependabot[bot] closed pull request #62: Bump maven-parent from 36 to 37 URL: https://github.com/apache/maven-doxia-sitetools/pull/62 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-doxia-sitetools] dependabot[bot] opened a new pull request, #71: Bump maven-parent from 36 to 38
dependabot[bot] opened a new pull request, #71: URL: https://github.com/apache/maven-doxia-sitetools/pull/71 Bumps [maven-parent](https://github.com/apache/maven-parent) from 36 to 38. Release notes Sourced from https://github.com/apache/maven-parent/releases";>maven-parent's releases. 38 Improvement [https://issues.apache.org/jira/browse/MPOM-340";>MPOM-340] - Remove test-javadoc reports [https://issues.apache.org/jira/browse/MPOM-353";>MPOM-353] - Use standard value for ignoreFailures at m-invoker-p [https://issues.apache.org/jira/browse/MPOM-357";>MPOM-357] - Execute checkstyle after enforcer Task [https://issues.apache.org/jira/browse/MPOM-349";>MPOM-349] - Enable spotless for autoformatting [https://issues.apache.org/jira/browse/MPOM-350";>MPOM-350] - Raise JDK requirement to 1.8 [https://issues.apache.org/jira/browse/MPOM-352";>MPOM-352] - Remove managed dependency on deprecated plexus-component-annotations Dependency upgrade [https://issues.apache.org/jira/browse/MPOM-341";>MPOM-341] - Bump extra-enforcer-rules from 1.6.0 to 1.6.1 [https://issues.apache.org/jira/browse/MPOM-343";>MPOM-343] - Upgrade Maven Checkstyle Plugin to 3.2.0 [https://issues.apache.org/jira/browse/MPOM-348";>MPOM-348] - Remove configuration for Maven Changes Plugin [https://issues.apache.org/jira/browse/MPOM-351";>MPOM-351] - Upgrade plexus-utils to 3.5.0 [https://issues.apache.org/jira/browse/MPOM-355";>MPOM-355] - Bump maven-pmd-plugin from 3.17.0 to 3.19.0 [https://issues.apache.org/jira/browse/MPOM-356";>MPOM-356] - Bump maven-jxr-plugin from 3.2.0 to 3.3.0 37 What's Changed [MPOM-317] Upgrade fluido skin to 1.11.0 by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/66";>apache/maven-parent#66 Bump maven-pmd-plugin from 3.16.0 to 3.17.0 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/64";>apache/maven-parent#64 [MPOM-322] Add ASF Data Privacy by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/65";>apache/maven-parent#65 [MPOM-324] Drop Social Media Plug-ins from documentation by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/67";>apache/maven-parent#67 [MPOM-331] Upgrade Surefire to 3.0.0-M7 by https://github.com/slachiewicz";>@slachiewicz in https://github-redirect.dependabot.com/apache/maven-parent/pull/68";>apache/maven-parent#68 [MPOM-334] Upgrade fluido skin to 1.11.1 by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/70";>apache/maven-parent#70 Bump maven-toolchains-plugin from 3.0.0 to 3.1.0 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/69";>apache/maven-parent#69 Bump extra-enforcer-rules from 1.5.1 to 1.6.0 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/71";>apache/maven-parent#71 Bump apache from 26 to 27 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/72";>apache/maven-parent#72 Full Changelog: https://github.com/apache/maven-parent/compare/maven-parent-36...maven-parent-37";>https://github.com/apache/maven-parent/compare/maven-parent-36...maven-parent-37 Commits See full diff in https://github.com/apache/maven-parent/commits";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and 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 an
[GitHub] [maven-doxia-sitetools] dependabot[bot] closed pull request #63: Bump junitVersion from 5.8.2 to 5.9.0
dependabot[bot] closed pull request #63: Bump junitVersion from 5.8.2 to 5.9.0 URL: https://github.com/apache/maven-doxia-sitetools/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
[GitHub] [maven-doxia-sitetools] dependabot[bot] commented on pull request #63: Bump junitVersion from 5.8.2 to 5.9.0
dependabot[bot] commented on PR #63: URL: https://github.com/apache/maven-doxia-sitetools/pull/63#issuecomment-1325753558 Superseded by #70. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-doxia-sitetools] dependabot[bot] opened a new pull request, #70: Bump junitVersion from 5.8.2 to 5.9.1
dependabot[bot] opened a new pull request, #70: URL: https://github.com/apache/maven-doxia-sitetools/pull/70 Bumps `junitVersion` from 5.8.2 to 5.9.1. Updates `junit-jupiter-api` from 5.8.2 to 5.9.1 Release notes Sourced from https://github.com/junit-team/junit5/releases";>junit-jupiter-api's releases. JUnit 5.9.1 = Platform 1.9.1 + Jupiter 5.9.1 + Vintage 5.9.1 See http://junit.org/junit5/docs/5.9.1/release-notes/";>Release Notes. JUnit 5.9.0 = Platform 1.9.0 + Jupiter 5.9.0 + Vintage 5.9.0 See http://junit.org/junit5/docs/5.9.0/release-notes/";>Release Notes. JUnit 5.9.0-RC1 = Platform 1.9.0-RC1 + Jupiter 5.9.0-RC1 + Vintage 5.9.0-RC1 See http://junit.org/junit5/docs/5.9.0-RC1/release-notes/";>Release Notes. JUnit 5.9.0-M1 = Platform 1.9.0-M1 + Jupiter 5.9.0-M1 + Vintage 5.9.0-M1 See http://junit.org/junit5/docs/5.9.0-M1/release-notes/";>Release Notes. Commits https://github.com/junit-team/junit5/commit/732a5400f80c8f446daa8b43eaa4b41b3da929be";>732a540 Release 5.9.1 https://github.com/junit-team/junit5/commit/88bf48d54534b90f74b64b7060f3d09205c9ff9a";>88bf48d Prepare release notes for 5.9.1 https://github.com/junit-team/junit5/commit/d75e34d20f3b9c297b6c38a679888a676f0b92a3";>d75e34d Update scope for 5.9.1 https://github.com/junit-team/junit5/commit/9823f7329a97b4ca6d0922b1c62b6526d615f761";>9823f73 Link to all 5.9 milestone pages https://github.com/junit-team/junit5/commit/76719bb085c1e395824af8d941ed40b9ac359d1d";>76719bb Increase timeout for GraalVM test https://github.com/junit-team/junit5/commit/2a809848e56c7d26b3dbd964a1d99e37ca61acc6";>2a80984 Install GraalVM for main CI build on Linux https://github.com/junit-team/junit5/commit/79f47f51aa8880c78ceeb04e8c837b28d73a2b94";>79f47f5 Refactor OpenTestReportGeneratingListener to work in native images https://github.com/junit-team/junit5/commit/7229385d5edc7f2b78363f8bd0026a86c53bc44e";>7229385 Add failing integration test for execution on GraalVM native image https://github.com/junit-team/junit5/commit/343170f314221ac8d91fea52617234058abfc39a";>343170f Fix running tests in documentation from IntelliJ IDEA https://github.com/junit-team/junit5/commit/352d06b3b27d5f1921dda1876c2dedb6f4f6b70f";>352d06b Attempt to stabilize test on Windows Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.8.2...r5.9.1";>compare view Updates `junit-jupiter-engine` from 5.8.2 to 5.9.1 Release notes Sourced from https://github.com/junit-team/junit5/releases";>junit-jupiter-engine's releases. JUnit 5.9.1 = Platform 1.9.1 + Jupiter 5.9.1 + Vintage 5.9.1 See http://junit.org/junit5/docs/5.9.1/release-notes/";>Release Notes. JUnit 5.9.0 = Platform 1.9.0 + Jupiter 5.9.0 + Vintage 5.9.0 See http://junit.org/junit5/docs/5.9.0/release-notes/";>Release Notes. JUnit 5.9.0-RC1 = Platform 1.9.0-RC1 + Jupiter 5.9.0-RC1 + Vintage 5.9.0-RC1 See http://junit.org/junit5/docs/5.9.0-RC1/release-notes/";>Release Notes. JUnit 5.9.0-M1 = Platform 1.9.0-M1 + Jupiter 5.9.0-M1 + Vintage 5.9.0-M1 See http://junit.org/junit5/docs/5.9.0-M1/release-notes/";>Release Notes. Commits https://github.com/junit-team/junit5/commit/732a5400f80c8f446daa8b43eaa4b41b3da929be";>732a540 Release 5.9.1 https://github.com/junit-team/junit5/commit/88bf48d54534b90f74b64b7060f3d09205c9ff9a";>88bf48d Prepare release notes for 5.9.1 https://github.com/junit-team/junit5/commit/d75e34d20f3b9c297b6c38a679888a676f0b92a3";>d75e34d Update scope for 5.9.1 https://github.com/junit-team/junit5/commit/9823f7329a97b4ca6d0922b1c62b6526d615f761";>9823f73 Link to all 5.9 milestone pages https://github.com/junit-team/junit5/commit/76719bb085c1e395824af8d941ed40b9ac359d1d";>76719bb Increase timeout for GraalVM test https://github.com/junit-team/junit5/commit/2a809848e56c7d26b3dbd964a1d99e37ca61acc6";>2a80984 Install GraalVM for main CI build on Linux https://github.com/junit-team/junit5/commit/79f47f51aa8880c78ceeb04e8c837b28d73a2b94";>79f47f5 Refactor OpenTestReportGeneratingListener to work in native images https://github.com/junit-team/junit5/commit/7229385d5edc7f2b78363f8bd0026a86c53bc44e";>7229385 Add failing integration test for execution on GraalVM native image https://github.com/junit-team/junit5/commit/343170f314221ac8d91fea52617234058abfc39a";>343170f Fix running tests in documentation from IntelliJ IDEA https://github.com/junit-team/junit5/commit/352d06b3b27d5f1921dda1876c2dedb6f4f6b70f";>352d06b Attempt to stabilize test on Windows Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.8.2...r5.9.1";>compare view 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-st
[jira] [Commented] (MDEP-809) Javadoc was not updated to reflect that :tree's verbose option is now ok
[ https://issues.apache.org/jira/browse/MDEP-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637988#comment-17637988 ] Slawomir Jaranowski commented on MDEP-809: -- Fixed in: https://github.com/apache/maven-dependency-plugin/commit/f2e192ae263531e50948082d4fb544cac43f9fa9 > Javadoc was not updated to reflect that :tree's verbose option is now ok > > > Key: MDEP-809 > URL: https://issues.apache.org/jira/browse/MDEP-809 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: tree >Affects Versions: 3.3.0 >Reporter: Francois MAROT >Assignee: Slawomir Jaranowski >Priority: Trivial > > The TreeMojo's verbose option has been broken for a while but was corrected a > while ago. Nevertheless, the javadoc has not been updated to reflect that it > is useable again. > Many people, including me, may have been discouraged to use it due to this > broken javadoc. > ThomGeg has wrote here an extensive history analysis to what happened: > https://github.com/CycloneDX/cyclonedx-maven-plugin/pull/187#issuecomment-1130859621 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEP-809) Javadoc was not updated to reflect that :tree's verbose option is now ok
[ https://issues.apache.org/jira/browse/MDEP-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MDEP-809. Fix Version/s: 3.4.0 Resolution: Fixed > Javadoc was not updated to reflect that :tree's verbose option is now ok > > > Key: MDEP-809 > URL: https://issues.apache.org/jira/browse/MDEP-809 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: tree >Affects Versions: 3.3.0 >Reporter: Francois MAROT >Assignee: Slawomir Jaranowski >Priority: Trivial > Fix For: 3.4.0 > > > The TreeMojo's verbose option has been broken for a while but was corrected a > while ago. Nevertheless, the javadoc has not been updated to reflect that it > is useable again. > Many people, including me, may have been discouraged to use it due to this > broken javadoc. > ThomGeg has wrote here an extensive history analysis to what happened: > https://github.com/CycloneDX/cyclonedx-maven-plugin/pull/187#issuecomment-1130859621 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-assembly-plugin] dependabot[bot] closed pull request #93: Bump postgresql from 42.3.3 to 42.3.7 in /src/it/projects/bugs/massembly-730
dependabot[bot] closed pull request #93: Bump postgresql from 42.3.3 to 42.3.7 in /src/it/projects/bugs/massembly-730 URL: https://github.com/apache/maven-assembly-plugin/pull/93 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-assembly-plugin] dependabot[bot] commented on pull request #93: Bump postgresql from 42.3.3 to 42.3.7 in /src/it/projects/bugs/massembly-730
dependabot[bot] commented on PR #93: URL: https://github.com/apache/maven-assembly-plugin/pull/93#issuecomment-1325730113 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
[GitHub] [maven-assembly-plugin] dependabot[bot] opened a new pull request, #101: Bump postgresql from 42.3.3 to 42.3.8 in /src/it/projects/bugs/massembly-730
dependabot[bot] opened a new pull request, #101: URL: https://github.com/apache/maven-assembly-plugin/pull/101 Bumps [postgresql](https://github.com/pgjdbc/pgjdbc) from 42.3.3 to 42.3.8. Changelog Sourced from https://github.com/pgjdbc/pgjdbc/blob/master/CHANGELOG.md";>postgresql's changelog. Changelog Notable changes since version 42.0.0, read the complete https://jdbc.postgresql.org/documentation/changelog.html";>History of Changes. The format is based on http://keepachangelog.com/en/1.0.0/";>Keep a Changelog. [Unreleased] Changed Added Fixed [42.5.1] (2022-11-21 15:21:59 -0500) Security security: StreamWrapper spills to disk if setText, or setBytea sends very large Strings or arrays to the server. createTempFile creates a file which can be read by other users on unix like systems (Not macos). This has been fixed in this version fixes CVE-2022-41946 see the https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-562r-vg33-8x8h";>security advisory for more details. Reported by https://github.com/JLLeitschuh";>Jonathan Leitschuh This has been fixed in versions 42.5.1, 42.4.3 42.3.8, 42.2.27.jre7. Note there is no fix for 42.2.26.jre6. See the security advisory for work arounds. Fixed fix: make sure we select array_in from pg_catalog to avoid duplicate array_in functions fixes https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2548";>#Issue 2548 [PR https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2552";>#2552](https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2552";>pgjdbc/pgjdbc#2552) fix: binary decoding of bool values [PR https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2640";>#2640](https://github-redirect.dependabot.com/pgjdbc/pgjdbc/pull/2640";>pgjdbc/pgjdbc#2640) perf: improve performance of PgResultSet getByte/getShort/getInt/getLong for float-typed columns [PR https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2634";>#2634](https://github-redirect.dependabot.com/pgjdbc/pgjdbc/pull/2634";>pgjdbc/pgjdbc#2634) chore: fix various spelling errors [PR https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2592";>#2592](https://github-redirect.dependabot.com/pgjdbc/pgjdbc/pull/2592";>pgjdbc/pgjdbc#2592) chore: Feature/urlparser improve URLParser [PR https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2641";>#2641](https://github-redirect.dependabot.com/pgjdbc/pgjdbc/pull/2592";>pgjdbc/pgjdbc#2592) [42.5.0] (2022-08-23 11:20:11 -0400) Changed fix: revert change in [PR https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/1986";>#1986](https://github-redirect.dependabot.com/pgjdbc/pgjdbc/pull/1986";>pgjdbc/pgjdbc#1986) where float was aliased to float4 from float8. float now aliases to float8 [PR https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2598";>#2598](https://github-redirect.dependabot.com/pgjdbc/pgjdbc/pull/2598";>pgjdbc/pgjdbc#2598) fixes [Issue https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2597";>#2597](https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2597";>pgjdbc/pgjdbc#2597) [42.4.2] (2022-08-17 10:33:40 -0400) Changed fix: add alias to the generated getUDT() query for clarity (PR https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2553";>#2553)[https://github-redirect.dependabot.com/pgjdbc/pgjdbc/pull/2553] Added fix: make setObject accept UUID array [PR https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2587";>#2587](https://github-redirect.dependabot.com/pgjdbc/pgjdbc/pull/2587";>pgjdbc/pgjdbc#2587) Fixed fix: regression with GSS. Changes introduced to support building with Java 17 caused failures [Issue https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2588";>#2588](https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2588";>pgjdbc/pgjdbc#2588) fix: set a timeout to get the return from requesting SSL upgrade. [PR https://github-redirect.dependabot.com/pgjdbc/pgjdbc/issues/2572";>#2572](https://github-redirect.dependabot.com/pgjdbc/pgjdbc/pull/2572";>pgjdbc/pgjdbc#2572) feat: synchronize statement executions (e.g. avoid deadlock when Connection.isValid is executed from concurrent threads) [42.4.1] (2022-08-01 16:24:20 -0400) Security fix: CVE-2022-31197 Fixes SQL generated in PgResultSet.refresh() to escape column identifiers so as to prevent SQL injection. Previously, the column names for both key and data columns in the table were copied as-is into the generated SQL. This allowed a malicious table with column names that include statement terminator to be parsed and executed as multiple separate commands. Also adds a new test class ResultSetRefreshTest to verify this change. Reported by https://github.com/kato-sho";>Sho Kato ... (truncated) Commits https://github.com/pgjdbc/pgjdbc/commit/e73c6b6b53ff11bc0b
[GitHub] [maven-doxia-sitetools] michael-o commented on pull request #67: [DOXIASITETOOLS-271] Overhaul locale support (make Locale#ROOT instead of Locale#ENGLISH default and use full locale)
michael-o commented on PR #67: URL: https://github.com/apache/maven-doxia-sitetools/pull/67#issuecomment-1325709555 @hboutemy tested entire chain now with m-site-p, m-r-impl and m-project-info-reports-p. For me, this is good to be. Please have a look. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-indexer] dependabot[bot] commented on pull request #264: Bump modernizer-maven-plugin from 2.4.0 to 2.5.0
dependabot[bot] commented on PR #264: URL: https://github.com/apache/maven-indexer/pull/264#issuecomment-1325695111 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-indexer] slachiewicz closed pull request #264: Bump modernizer-maven-plugin from 2.4.0 to 2.5.0
slachiewicz closed pull request #264: Bump modernizer-maven-plugin from 2.4.0 to 2.5.0 URL: https://github.com/apache/maven-indexer/pull/264 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-indexer] dependabot[bot] commented on pull request #270: Bump lucene.version from 9.4.1 to 9.4.2
dependabot[bot] commented on PR #270: URL: https://github.com/apache/maven-indexer/pull/270#issuecomment-1325694793 OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-indexer] slachiewicz closed pull request #270: Bump lucene.version from 9.4.1 to 9.4.2
slachiewicz closed pull request #270: Bump lucene.version from 9.4.1 to 9.4.2 URL: https://github.com/apache/maven-indexer/pull/270 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-indexer] slachiewicz commented on pull request #271: [MINDEXER-177][MINDEXER-178] Update Lucene and modernizer
slachiewicz commented on PR #271: URL: https://github.com/apache/maven-indexer/pull/271#issuecomment-1325694479 Closes #270 -- 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] (MINDEXER-178) Update modernizer plugin
[ https://issues.apache.org/jira/browse/MINDEXER-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637965#comment-17637965 ] Hudson commented on MINDEXER-178: - Build succeeded in Jenkins: Maven » Maven TLP » maven-indexer » master #81 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-indexer/job/master/81/ > Update modernizer plugin > > > Key: MINDEXER-178 > URL: https://issues.apache.org/jira/browse/MINDEXER-178 > Project: Maven Indexer > Issue Type: Task >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.0.1 > > > To latest 2.5.0 to have build work with Maven 3.9+ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINDEXER-177) Update to Lucene 9.4.2
[ https://issues.apache.org/jira/browse/MINDEXER-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637964#comment-17637964 ] Hudson commented on MINDEXER-177: - Build succeeded in Jenkins: Maven » Maven TLP » maven-indexer » master #81 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-indexer/job/master/81/ > Update to Lucene 9.4.2 > -- > > Key: MINDEXER-177 > URL: https://issues.apache.org/jira/browse/MINDEXER-177 > Project: Maven Indexer > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.0.1 > > > Update to latest bugfix release 9.4.2. > Changelog: https://lucene.apache.org/core/9_4_2/changes/Changes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MINDEXER-178) Update modernizer plugin
[ https://issues.apache.org/jira/browse/MINDEXER-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MINDEXER-178. Resolution: Fixed > Update modernizer plugin > > > Key: MINDEXER-178 > URL: https://issues.apache.org/jira/browse/MINDEXER-178 > Project: Maven Indexer > Issue Type: Task >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.0.1 > > > To latest 2.5.0 to have build work with Maven 3.9+ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MINDEXER-177) Update to Lucene 9.4.2
[ https://issues.apache.org/jira/browse/MINDEXER-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MINDEXER-177. Resolution: Fixed > Update to Lucene 9.4.2 > -- > > Key: MINDEXER-177 > URL: https://issues.apache.org/jira/browse/MINDEXER-177 > Project: Maven Indexer > Issue Type: Dependency upgrade >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 7.0.1 > > > Update to latest bugfix release 9.4.2. > Changelog: https://lucene.apache.org/core/9_4_2/changes/Changes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-indexer] cstamas merged pull request #271: [MINDEXER-177][MINDEXER-178] Update Lucene and modernizer
cstamas merged PR #271: URL: https://github.com/apache/maven-indexer/pull/271 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-indexer] cstamas opened a new pull request, #271: [MINDEXER-177][MINDEXER-178] Update Lucene and modernizer
cstamas opened a new pull request, #271: URL: https://github.com/apache/maven-indexer/pull/271 Updates to dependencies: * Lucene 9.4.2 Updates to plugins: * modernizer 2.5.0 --- https://issues.apache.org/jira/browse/MINDEXER-177 https://issues.apache.org/jira/browse/MINDEXER-178 -- 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] (MINDEXER-178) Update modernizer plugin
Tamas Cservenak created MINDEXER-178: Summary: Update modernizer plugin Key: MINDEXER-178 URL: https://issues.apache.org/jira/browse/MINDEXER-178 Project: Maven Indexer Issue Type: Task Reporter: Tamas Cservenak Assignee: Tamas Cservenak Fix For: 7.0.1 To latest 2.5.0 to have build work with Maven 3.9+ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MINDEXER-177) Update to Lucene 9.4.2
Tamas Cservenak created MINDEXER-177: Summary: Update to Lucene 9.4.2 Key: MINDEXER-177 URL: https://issues.apache.org/jira/browse/MINDEXER-177 Project: Maven Indexer Issue Type: Dependency upgrade Reporter: Tamas Cservenak Assignee: Tamas Cservenak Fix For: 7.0.1 Update to latest bugfix release 9.4.2. Changelog: https://lucene.apache.org/core/9_4_2/changes/Changes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MINDEXER-176) Core's IndexDataReader does not clean up after itself
[ https://issues.apache.org/jira/browse/MINDEXER-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MINDEXER-176: - Summary: Core's IndexDataReader does not clean up after itself (was: Core;s IndexDataReader does not clean up after itself) > Core's IndexDataReader does not clean up after itself > - > > Key: MINDEXER-176 > URL: https://issues.apache.org/jira/browse/MINDEXER-176 > Project: Maven Indexer > Issue Type: Bug >Affects Versions: 7.0.0 >Reporter: Tamas Cservenak >Priority: Major > Fix For: 7.0.1 > > > As MT index update was implemented that uses split "silos", it seems that > silos are not cleaned up. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-777) String index out of range when using FlattenFileMapper
[
https://issues.apache.org/jira/browse/MDEP-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637956#comment-17637956
]
Elliotte Rusty Harold commented on MDEP-777:
What's the chance that the bug is in
org.codehaus.plexus.components.io.filemappers.FlattenFileMapper and not in
Maven at all? A stack trace might tell us which project has the bug.
> String index out of range when using FlattenFileMapper
> --
>
> Key: MDEP-777
> URL: https://issues.apache.org/jira/browse/MDEP-777
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: unpack
>Affects Versions: 3.2.0
>Reporter: Lieven Cardoen
>Priority: Minor
> Fix For: waiting-for-feedback
>
>
> When using FlattenFileMapper I'm getting a *String index out of range 0*
> If I comment out the FileMappers then everything runs fine.
> {code:xml}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 3.2.0
>
>
>
> copy-databases-to-dbf-folder
> install
>
> unpack
>
>
>
>
> be.mips.appl.database
>
> ${db.variant}-db-oe${oe.major.version}-${os.classifier}
> ${be.mips.appl.database.version}
> zip
> true
>
>
> implementation="org.codehaus.plexus.components.io.filemappers.FlattenFileMapper"/>
>
>
>
> be.mips.appl.database
>
> name-db-oe${oe.major.version}-${os.classifier}
> ${be.mips.appl.database.version}
> zip
> true
>
>
> **/*
> ${custom.build.directory}/dbf
> true
> true
>
>
>
>
> {code}
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.2.0:unpack
> (copy-databases-to-dbf-folder) on project build-appl: Execution
> copy-databases-to-dbf-folder of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.2.0:unpack failed: String
> index out of range: 0 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
> The ZIP contains two folders with files in both of the folders. So no empty
> folders.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MBUILDCACHE-33) Support remote cache credentials from environment variables
[ https://issues.apache.org/jira/browse/MBUILDCACHE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637934#comment-17637934 ] Guillaume Nodet commented on MBUILDCACHE-33: The settings do not have to be put in scm. Of course that would be a bad idea if they contain credentials. > Support remote cache credentials from environment variables > > > Key: MBUILDCACHE-33 > URL: https://issues.apache.org/jira/browse/MBUILDCACHE-33 > Project: Maven Build Cache Extension > Issue Type: New Feature >Reporter: Alexander Ashitkin >Priority: Major > Labels: pull-request-available > > In my current environment settings.xml are managed by a build team which is > not allowing any modification because the same build service is used by all > teams. Atop of that, maven build runs in a fresh container which doesn't have > any credentials injected for security reasons. Because of that cache cannot > read/deploy build artifacts to an authenticated http server. Still, our build > service allows to inject credentials from environment variables into build > container. Need to support cache setup without settings.xml by injecting > environment variables: > * MAVEN_BUILD_CACHE_DIRECT_CONNECT > * MAVEN_BUILD_CACHE_USER > * MAVEN_BUILD_CACHE_PASSWORD > * MAVEN_BUILD_CACHE_PROXY_USER > * MAVEN_BUILD_CACHE_PROXY_PASSWORD -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MBUILDCACHE-33) Support remote cache credentials from environment variables
[ https://issues.apache.org/jira/browse/MBUILDCACHE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637930#comment-17637930 ] Michael Osipov commented on MBUILDCACHE-33: --- A couple of years ago I had the idea to completely abstract the credential provider similar to what Git or Subversion to. We provide the resource and/or id and the provider returns creds. > Support remote cache credentials from environment variables > > > Key: MBUILDCACHE-33 > URL: https://issues.apache.org/jira/browse/MBUILDCACHE-33 > Project: Maven Build Cache Extension > Issue Type: New Feature >Reporter: Alexander Ashitkin >Priority: Major > Labels: pull-request-available > > In my current environment settings.xml are managed by a build team which is > not allowing any modification because the same build service is used by all > teams. Atop of that, maven build runs in a fresh container which doesn't have > any credentials injected for security reasons. Because of that cache cannot > read/deploy build artifacts to an authenticated http server. Still, our build > service allows to inject credentials from environment variables into build > container. Need to support cache setup without settings.xml by injecting > environment variables: > * MAVEN_BUILD_CACHE_DIRECT_CONNECT > * MAVEN_BUILD_CACHE_USER > * MAVEN_BUILD_CACHE_PASSWORD > * MAVEN_BUILD_CACHE_PROXY_USER > * MAVEN_BUILD_CACHE_PROXY_PASSWORD -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MBUILDCACHE-33) Support remote cache credentials from environment variables
[ https://issues.apache.org/jira/browse/MBUILDCACHE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637926#comment-17637926 ] Michael Osipov commented on MBUILDCACHE-33: --- A per project settings does not make sense since you would expose credentials via SCM... > Support remote cache credentials from environment variables > > > Key: MBUILDCACHE-33 > URL: https://issues.apache.org/jira/browse/MBUILDCACHE-33 > Project: Maven Build Cache Extension > Issue Type: New Feature >Reporter: Alexander Ashitkin >Priority: Major > Labels: pull-request-available > > In my current environment settings.xml are managed by a build team which is > not allowing any modification because the same build service is used by all > teams. Atop of that, maven build runs in a fresh container which doesn't have > any credentials injected for security reasons. Because of that cache cannot > read/deploy build artifacts to an authenticated http server. Still, our build > service allows to inject credentials from environment variables into build > container. Need to support cache setup without settings.xml by injecting > environment variables: > * MAVEN_BUILD_CACHE_DIRECT_CONNECT > * MAVEN_BUILD_CACHE_USER > * MAVEN_BUILD_CACHE_PASSWORD > * MAVEN_BUILD_CACHE_PROXY_USER > * MAVEN_BUILD_CACHE_PROXY_PASSWORD -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-shared-utils] dependabot[bot] opened a new pull request, #122: Bump maven-shared-components from 37 to 38
dependabot[bot] opened a new pull request, #122: URL: https://github.com/apache/maven-shared-utils/pull/122 Bumps [maven-shared-components](https://github.com/apache/maven-parent) from 37 to 38. Release notes Sourced from https://github.com/apache/maven-parent/releases";>maven-shared-components's releases. 38 Improvement [https://issues.apache.org/jira/browse/MPOM-340";>MPOM-340] - Remove test-javadoc reports [https://issues.apache.org/jira/browse/MPOM-353";>MPOM-353] - Use standard value for ignoreFailures at m-invoker-p [https://issues.apache.org/jira/browse/MPOM-357";>MPOM-357] - Execute checkstyle after enforcer Task [https://issues.apache.org/jira/browse/MPOM-349";>MPOM-349] - Enable spotless for autoformatting [https://issues.apache.org/jira/browse/MPOM-350";>MPOM-350] - Raise JDK requirement to 1.8 [https://issues.apache.org/jira/browse/MPOM-352";>MPOM-352] - Remove managed dependency on deprecated plexus-component-annotations Dependency upgrade [https://issues.apache.org/jira/browse/MPOM-341";>MPOM-341] - Bump extra-enforcer-rules from 1.6.0 to 1.6.1 [https://issues.apache.org/jira/browse/MPOM-343";>MPOM-343] - Upgrade Maven Checkstyle Plugin to 3.2.0 [https://issues.apache.org/jira/browse/MPOM-348";>MPOM-348] - Remove configuration for Maven Changes Plugin [https://issues.apache.org/jira/browse/MPOM-351";>MPOM-351] - Upgrade plexus-utils to 3.5.0 [https://issues.apache.org/jira/browse/MPOM-355";>MPOM-355] - Bump maven-pmd-plugin from 3.17.0 to 3.19.0 [https://issues.apache.org/jira/browse/MPOM-356";>MPOM-356] - Bump maven-jxr-plugin from 3.2.0 to 3.3.0 Commits See full diff in https://github.com/apache/maven-parent/commits";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and 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 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
[GitHub] [maven-plugin-testing] gnodet commented on pull request #24: Switch to maven 4 and the new api
gnodet commented on PR #24: URL: https://github.com/apache/maven-plugin-testing/pull/24#issuecomment-1325492698 > Do I good see - it is not a switching, rather extension for Maven 4. > Old classes are still present. Yes, that's right, but there's a need to switch the maven dependency to 4.x to build against the v3 + v4 api. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-filtering] dependabot[bot] closed pull request #42: Bump maven-shared-components from 36 to 37
dependabot[bot] closed pull request #42: Bump maven-shared-components from 36 to 37 URL: https://github.com/apache/maven-filtering/pull/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
[GitHub] [maven-filtering] dependabot[bot] opened a new pull request, #57: Bump maven-shared-components from 36 to 38
dependabot[bot] opened a new pull request, #57: URL: https://github.com/apache/maven-filtering/pull/57 Bumps [maven-shared-components](https://github.com/apache/maven-parent) from 36 to 38. Release notes Sourced from https://github.com/apache/maven-parent/releases";>maven-shared-components's releases. 38 Improvement [https://issues.apache.org/jira/browse/MPOM-340";>MPOM-340] - Remove test-javadoc reports [https://issues.apache.org/jira/browse/MPOM-353";>MPOM-353] - Use standard value for ignoreFailures at m-invoker-p [https://issues.apache.org/jira/browse/MPOM-357";>MPOM-357] - Execute checkstyle after enforcer Task [https://issues.apache.org/jira/browse/MPOM-349";>MPOM-349] - Enable spotless for autoformatting [https://issues.apache.org/jira/browse/MPOM-350";>MPOM-350] - Raise JDK requirement to 1.8 [https://issues.apache.org/jira/browse/MPOM-352";>MPOM-352] - Remove managed dependency on deprecated plexus-component-annotations Dependency upgrade [https://issues.apache.org/jira/browse/MPOM-341";>MPOM-341] - Bump extra-enforcer-rules from 1.6.0 to 1.6.1 [https://issues.apache.org/jira/browse/MPOM-343";>MPOM-343] - Upgrade Maven Checkstyle Plugin to 3.2.0 [https://issues.apache.org/jira/browse/MPOM-348";>MPOM-348] - Remove configuration for Maven Changes Plugin [https://issues.apache.org/jira/browse/MPOM-351";>MPOM-351] - Upgrade plexus-utils to 3.5.0 [https://issues.apache.org/jira/browse/MPOM-355";>MPOM-355] - Bump maven-pmd-plugin from 3.17.0 to 3.19.0 [https://issues.apache.org/jira/browse/MPOM-356";>MPOM-356] - Bump maven-jxr-plugin from 3.2.0 to 3.3.0 37 What's Changed [MPOM-317] Upgrade fluido skin to 1.11.0 by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/66";>apache/maven-parent#66 Bump maven-pmd-plugin from 3.16.0 to 3.17.0 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/64";>apache/maven-parent#64 [MPOM-322] Add ASF Data Privacy by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/65";>apache/maven-parent#65 [MPOM-324] Drop Social Media Plug-ins from documentation by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/67";>apache/maven-parent#67 [MPOM-331] Upgrade Surefire to 3.0.0-M7 by https://github.com/slachiewicz";>@slachiewicz in https://github-redirect.dependabot.com/apache/maven-parent/pull/68";>apache/maven-parent#68 [MPOM-334] Upgrade fluido skin to 1.11.1 by https://github.com/slawekjaranowski";>@slawekjaranowski in https://github-redirect.dependabot.com/apache/maven-parent/pull/70";>apache/maven-parent#70 Bump maven-toolchains-plugin from 3.0.0 to 3.1.0 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/69";>apache/maven-parent#69 Bump extra-enforcer-rules from 1.5.1 to 1.6.0 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/71";>apache/maven-parent#71 Bump apache from 26 to 27 by https://github.com/dependabot";>@dependabot in https://github-redirect.dependabot.com/apache/maven-parent/pull/72";>apache/maven-parent#72 Full Changelog: https://github.com/apache/maven-parent/compare/maven-parent-36...maven-parent-37";>https://github.com/apache/maven-parent/compare/maven-parent-36...maven-parent-37 Commits See full diff in https://github.com/apache/maven-parent/commits";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and 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 - `@depe
[GitHub] [maven-filtering] dependabot[bot] commented on pull request #42: Bump maven-shared-components from 36 to 37
dependabot[bot] commented on PR #42: URL: https://github.com/apache/maven-filtering/pull/42#issuecomment-1325397355 Superseded by #57. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-plugin-testing] slawekjaranowski commented on pull request #24: Switch to maven 4 and the new api
slawekjaranowski commented on PR #24: URL: https://github.com/apache/maven-plugin-testing/pull/24#issuecomment-1325353791 Do I good see - it is not a switching, rather extension for Maven 4. Old classes are still present. -- 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] (MDEP-805) artifactItem documentation
[
https://issues.apache.org/jira/browse/MDEP-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MDEP-805:
-
Fix Version/s: (was: wontfix-candidate)
> artifactItem documentation
> --
>
> Key: MDEP-805
> URL: https://issues.apache.org/jira/browse/MDEP-805
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Reporter: Ewa Śliwińska
>Priority: Minor
>
> I'm trying to find information about {_}type{_}, _overWrite_ and
> _outputDirectory_ tags in _artifactItem_ in _unpack_ goal (if they are
> mandatory and what should be their content).
> When googling, I'm finding those two sites:
> * [Apache Maven Dependency Plugin –
> dependency:unpack|https://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html]
> * [Apache Maven Dependency Plugin –
> Usage|https://maven.apache.org/plugins/maven-dependency-plugin/usage.html]
> The former roughly mentions what the _artifactItem_ contains, but without
> detailed explanation.
> The latter shows an example, but also does not specify the possible contents
> in details. Also it says
> {quote}A default outputDirectory is specified
> {quote}
> but doesn't mention what is the default.
> Could you please add more comprehensive description of those tags?
> Thank you in advance.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637839#comment-17637839 ] ASF GitHub Bot commented on MNG-7586: - gnodet commented on PR #881: URL: https://github.com/apache/maven/pull/881#issuecomment-1325272550 > Does not, this is for 3.9.x... or? Sorry I missed that. I was wondering why you raised 2 similar PRs... ;-) > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] gnodet commented on pull request #881: [MNG-7586] Update Maven Resolver to 1.9.2
gnodet commented on PR #881: URL: https://github.com/apache/maven/pull/881#issuecomment-1325272550 > Does not, this is for 3.9.x... or? Sorry I missed that. I was wondering why you raised 2 similar PRs... ;-) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-plugin-testing] gnodet commented on pull request #24: Switch to maven 4 and the new api
gnodet commented on PR #24: URL: https://github.com/apache/maven-plugin-testing/pull/24#issuecomment-1325269076 @slawekjaranowski @kwin @cstamas it would be good to get the PR merged to start having PRs for plugin migration be able to at least run with snapshots... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MDEP-805) artifactItem documentation
[
https://issues.apache.org/jira/browse/MDEP-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski closed MDEP-805.
Resolution: Information Provided
> artifactItem documentation
> --
>
> Key: MDEP-805
> URL: https://issues.apache.org/jira/browse/MDEP-805
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Reporter: Ewa Śliwińska
>Priority: Minor
> Fix For: wontfix-candidate
>
>
> I'm trying to find information about {_}type{_}, _overWrite_ and
> _outputDirectory_ tags in _artifactItem_ in _unpack_ goal (if they are
> mandatory and what should be their content).
> When googling, I'm finding those two sites:
> * [Apache Maven Dependency Plugin –
> dependency:unpack|https://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html]
> * [Apache Maven Dependency Plugin –
> Usage|https://maven.apache.org/plugins/maven-dependency-plugin/usage.html]
> The former roughly mentions what the _artifactItem_ contains, but without
> detailed explanation.
> The latter shows an example, but also does not specify the possible contents
> in details. Also it says
> {quote}A default outputDirectory is specified
> {quote}
> but doesn't mention what is the default.
> Could you please add more comprehensive description of those tags?
> Thank you in advance.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-777) String index out of range when using FlattenFileMapper
[
https://issues.apache.org/jira/browse/MDEP-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MDEP-777:
-
Priority: Minor (was: Blocker)
> String index out of range when using FlattenFileMapper
> --
>
> Key: MDEP-777
> URL: https://issues.apache.org/jira/browse/MDEP-777
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: unpack
>Affects Versions: 3.2.0
>Reporter: Lieven Cardoen
>Priority: Minor
> Fix For: waiting-for-feedback
>
>
> When using FlattenFileMapper I'm getting a *String index out of range 0*
> If I comment out the FileMappers then everything runs fine.
> {code:xml}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 3.2.0
>
>
>
> copy-databases-to-dbf-folder
> install
>
> unpack
>
>
>
>
> be.mips.appl.database
>
> ${db.variant}-db-oe${oe.major.version}-${os.classifier}
> ${be.mips.appl.database.version}
> zip
> true
>
>
> implementation="org.codehaus.plexus.components.io.filemappers.FlattenFileMapper"/>
>
>
>
> be.mips.appl.database
>
> name-db-oe${oe.major.version}-${os.classifier}
> ${be.mips.appl.database.version}
> zip
> true
>
>
> **/*
> ${custom.build.directory}/dbf
> true
> true
>
>
>
>
> {code}
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.2.0:unpack
> (copy-databases-to-dbf-folder) on project build-appl: Execution
> copy-databases-to-dbf-folder of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.2.0:unpack failed: String
> index out of range: 0 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
> The ZIP contains two folders with files in both of the folders. So no empty
> folders.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7604) The MNG-7244 makes some older plugins defunct
[
https://issues.apache.org/jira/browse/MNG-7604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7604:
Fix Version/s: 4.0.0
> The MNG-7244 makes some older plugins defunct
> -
>
> Key: MNG-7604
> URL: https://issues.apache.org/jira/browse/MNG-7604
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 4.0.0-alpha-2
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-3
>
>
> The MNG-7244 removed completely the {{pom.*}} prefix interpolation, but IMHO
> intent was to do it for "currently built projects". The problem is that same
> interpolator is used in model builder to build transitive dependency models,
> and with the change Maven 4 lost it's ability to resolve artifacts like
> wagon-http 1.0-beta-6 (used by things like surefire 2.22.2 and so on).
> The implication is that Maven4 CANNOT resolve wagon-http 1.0-beta-6 (and
> implicitly surefire plugin 2.22.2 is defunct it seems as it uses it). Given
> we have NO 3.x release of surefire (just M releases), I bet many of users out
> there still use 2.22.2. Also, we have no idea how many other (used as
> transitive dependencies) artifact exists out there doing same/similar thing
> that wagon POM does.
> IMHO: rollback the change from master and we need alt fix for it, as making
> Maven 4 unable to resolve transitive deps using pom.* placeholder introduces
> a huge toll.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637806#comment-17637806 ] ASF GitHub Bot commented on MNG-7586: - cstamas commented on PR #881: URL: https://github.com/apache/maven/pull/881#issuecomment-1325166726 Does not, this is for 3.9.x... or? > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637803#comment-17637803 ] ASF GitHub Bot commented on MNG-7586: - cstamas opened a new pull request, #881: URL: https://github.com/apache/maven/pull/881 Updates resolver to latest release. --- https://issues.apache.org/jira/browse/MNG-7586 > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] cstamas commented on pull request #881: [MNG-7586] Update Maven Resolver to 1.9.2
cstamas commented on PR #881: URL: https://github.com/apache/maven/pull/881#issuecomment-1325166726 Does not, this is for 3.9.x... or? -- 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] (MBUILDCACHE-33) Support remote cache credentials from environment variables
[
https://issues.apache.org/jira/browse/MBUILDCACHE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637030#comment-17637030
]
Guillaume Nodet edited comment on MBUILDCACHE-33 at 11/23/22 2:25 PM:
--
[~alex_ashitkin] I fail to see how this issue is specific to
maven-build-cache-extension. If the credentials mechanism in maven is somehow
flawed, it should be fixed in maven, rather than for each specific
plugin/extension I'd think.
I think a per-project {{settings.xml}} has been proposed. Wouldn't that solve
the problem ?
See https://issues.apache.org/jira/browse/MNG-5659
was (Author: gnt):
[~alex_ashitkin] I fail to see how this issue is specific to
maven-build-cache-extension. If the credentials mechanism in maven is somehow
flawed, it should be fixed in maven, rather than for each specific
plugin/extension I'd think.
I think a per-project {{settings.xml}} has been proposed. Wouldn't that solve
the problem ?
> Support remote cache credentials from environment variables
>
>
> Key: MBUILDCACHE-33
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-33
> Project: Maven Build Cache Extension
> Issue Type: New Feature
>Reporter: Alexander Ashitkin
>Priority: Major
> Labels: pull-request-available
>
> In my current environment settings.xml are managed by a build team which is
> not allowing any modification because the same build service is used by all
> teams. Atop of that, maven build runs in a fresh container which doesn't have
> any credentials injected for security reasons. Because of that cache cannot
> read/deploy build artifacts to an authenticated http server. Still, our build
> service allows to inject credentials from environment variables into build
> container. Need to support cache setup without settings.xml by injecting
> environment variables:
> * MAVEN_BUILD_CACHE_DIRECT_CONNECT
> * MAVEN_BUILD_CACHE_USER
> * MAVEN_BUILD_CACHE_PASSWORD
> * MAVEN_BUILD_CACHE_PROXY_USER
> * MAVEN_BUILD_CACHE_PROXY_PASSWORD
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637785#comment-17637785 ] ASF GitHub Bot commented on MNG-7586: - gnodet commented on PR #881: URL: https://github.com/apache/maven/pull/881#issuecomment-1325149051 Duplicates #882 > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637784#comment-17637784 ] ASF GitHub Bot commented on MNG-7586: - gnodet closed pull request #881: [MNG-7586] Update Maven Resolver to 1.9.2 URL: https://github.com/apache/maven/pull/881 > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] gnodet commented on pull request #881: [MNG-7586] Update Maven Resolver to 1.9.2
gnodet commented on PR #881: URL: https://github.com/apache/maven/pull/881#issuecomment-1325149051 Duplicates #882 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] gnodet closed pull request #881: [MNG-7586] Update Maven Resolver to 1.9.2
gnodet closed pull request #881: [MNG-7586] Update Maven Resolver to 1.9.2 URL: https://github.com/apache/maven/pull/881 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-compiler-plugin] dependabot[bot] opened a new pull request, #156: Bump maven-plugins from 37 to 38
dependabot[bot] opened a new pull request, #156: URL: https://github.com/apache/maven-compiler-plugin/pull/156 Bumps [maven-plugins](https://github.com/apache/maven-parent) from 37 to 38. Release notes Sourced from https://github.com/apache/maven-parent/releases";>maven-plugins's releases. 38 Improvement [https://issues.apache.org/jira/browse/MPOM-340";>MPOM-340] - Remove test-javadoc reports [https://issues.apache.org/jira/browse/MPOM-353";>MPOM-353] - Use standard value for ignoreFailures at m-invoker-p [https://issues.apache.org/jira/browse/MPOM-357";>MPOM-357] - Execute checkstyle after enforcer Task [https://issues.apache.org/jira/browse/MPOM-349";>MPOM-349] - Enable spotless for autoformatting [https://issues.apache.org/jira/browse/MPOM-350";>MPOM-350] - Raise JDK requirement to 1.8 [https://issues.apache.org/jira/browse/MPOM-352";>MPOM-352] - Remove managed dependency on deprecated plexus-component-annotations Dependency upgrade [https://issues.apache.org/jira/browse/MPOM-341";>MPOM-341] - Bump extra-enforcer-rules from 1.6.0 to 1.6.1 [https://issues.apache.org/jira/browse/MPOM-343";>MPOM-343] - Upgrade Maven Checkstyle Plugin to 3.2.0 [https://issues.apache.org/jira/browse/MPOM-348";>MPOM-348] - Remove configuration for Maven Changes Plugin [https://issues.apache.org/jira/browse/MPOM-351";>MPOM-351] - Upgrade plexus-utils to 3.5.0 [https://issues.apache.org/jira/browse/MPOM-355";>MPOM-355] - Bump maven-pmd-plugin from 3.17.0 to 3.19.0 [https://issues.apache.org/jira/browse/MPOM-356";>MPOM-356] - Bump maven-jxr-plugin from 3.2.0 to 3.3.0 Commits See full diff in https://github.com/apache/maven-parent/commits";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and 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 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
[GitHub] [maven-mvnd] gnodet merged pull request #744: Update ITs to recent maven plugins
gnodet merged PR #744: URL: https://github.com/apache/maven-mvnd/pull/744 -- 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] (MDEP-824) Bump plexus-utils from 3.4.1 to 3.5.0
[ https://issues.apache.org/jira/browse/MDEP-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MDEP-824: - Summary: Bump plexus-utils from 3.4.1 to 3.5.0 (was: Bump plexus-utils from 3.4.1 to 3.4.2) > Bump plexus-utils from 3.4.1 to 3.5.0 > - > > Key: MDEP-824 > URL: https://issues.apache.org/jira/browse/MDEP-824 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-dependency-plugin] slawekjaranowski merged pull request #259: Bump plexus-utils from 3.4.2 to 3.5.0
slawekjaranowski merged PR #259: URL: https://github.com/apache/maven-dependency-plugin/pull/259 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-indexer] cstamas commented on a diff in pull request #255: [MINDEXER-151] Speed up Index update from remote
cstamas commented on code in PR #255:
URL: https://github.com/apache/maven-indexer/pull/255#discussion_r1030448625
##
indexer-core/src/main/java/org/apache/maven/index/updater/IndexDataReader.java:
##
@@ -88,44 +133,175 @@ public IndexDataReadResult readIndex( IndexWriter w,
IndexingContext context )
int n = 0;
Document doc;
-Set rootGroups = new LinkedHashSet<>();
-Set allGroups = new LinkedHashSet<>();
+ConcurrentMap rootGroups = new ConcurrentHashMap<>();
+ConcurrentMap allGroups = new ConcurrentHashMap<>();
while ( ( doc = readDocument() ) != null )
{
-ArtifactInfo ai = IndexUtils.constructArtifactInfo( doc, context );
-if ( ai != null )
+addToIndex( doc, context, w, rootGroups, allGroups );
+n++;
+}
+
+w.commit();
+
+IndexDataReadResult result = new IndexDataReadResult();
+result.setDocumentCount( n );
+result.setTimestamp( date );
+result.setRootGroups( rootGroups.keySet() );
+result.setAllGroups( allGroups.keySet() );
+
+LOGGER.debug( "Reading ST index done in {} sec", Duration.between(
start, Instant.now() ).getSeconds() );
+return result;
+}
+
+private IndexDataReadResult readIndexMT( IndexWriter w, IndexingContext
context )
+throws IOException
+{
+LOGGER.debug( "Reading MT index..." );
+Instant start = Instant.now();
+long timestamp = readHeader();
+
+int n = 0;
+
+final Document theEnd = new Document();
+
+ConcurrentMap rootGroups = new ConcurrentHashMap<>();
+ConcurrentMap allGroups = new ConcurrentHashMap<>();
+ArrayBlockingQueue queue = new ArrayBlockingQueue<>( 1 );
+
+ExecutorService executorService = Executors.newFixedThreadPool(
threads );
+ArrayList errors = new ArrayList<>();
+ArrayList silos = new ArrayList<>( threads );
+for ( int i = 0; i < threads; i++ )
+{
+final int silo = i;
+silos.add( tempWriter( "silo" + i ) );
+executorService.execute( () ->
{
-w.addDocument( IndexUtils.updateDocument( doc, context, false,
ai ) );
+LOGGER.debug( "Starting thread {}",
Thread.currentThread().getName() );
+try
+{
+while ( true )
+{
+try
+{
+Document doc = queue.take();
+if ( doc == theEnd )
+{
+break;
+}
+addToIndex( doc, context, silos.get( silo ),
rootGroups, allGroups );
+}
+catch ( InterruptedException | IOException e )
+{
+errors.add( e );
+break;
+}
+}
+}
+finally
+{
+LOGGER.debug( "Done thread {}",
Thread.currentThread().getName() );
+}
+} );
+}
-rootGroups.add( ai.getRootGroup() );
-allGroups.add( ai.getGroupId() );
-}
-else if ( doc.getField( ArtifactInfo.ALL_GROUPS ) != null
-|| doc.getField( ArtifactInfo.ROOT_GROUPS ) != null )
+try
+{
+Document doc;
+while ( ( doc = readDocument() ) != null )
{
-// skip it
+queue.put( doc );
+n++;
}
-else
+LOGGER.debug( "Signalling END" );
+for ( int i = 0; i < threads; i++ )
{
-w.addDocument( doc );
+queue.put( theEnd );
}
-n++;
+
+LOGGER.debug( "Shutting down threads" );
+executorService.shutdown();
+executorService.awaitTermination( 5L, TimeUnit.MINUTES );
+}
+catch ( InterruptedException e )
+{
+throw new IOException( "Interrupted", e );
+}
+
+if ( !errors.isEmpty() )
+{
+IOException exception = new IOException( "Error during load of
index" );
+errors.forEach( exception::addSuppressed );
+throw exception;
+}
+
+LOGGER.debug( "Silos loaded..." );
+Date date = null;
+if ( timestamp != -1 )
+{
+date = new Date( timestamp );
+IndexUtils.updateTimestamp( w.getDirectory(), date );
}
+LOGGER.debug( "Merging silos..." );
+for ( IndexWriter silo : silos )
+{
+IndexUtils.close( silo );
+w.addIndexes( silo.getDirectory() );
+
[jira] [Created] (MINDEXER-176) Core;s IndexDataReader does not clean up after itself
Tamas Cservenak created MINDEXER-176: Summary: Core;s IndexDataReader does not clean up after itself Key: MINDEXER-176 URL: https://issues.apache.org/jira/browse/MINDEXER-176 Project: Maven Indexer Issue Type: Bug Affects Versions: 7.0.0 Reporter: Tamas Cservenak Fix For: 7.0.1 As MT index update was implemented that uses split "silos", it seems that silos are not cleaned up. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7244) Remove deprecated WARNING for usage of pom.X placeholders
[
https://issues.apache.org/jira/browse/MNG-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637737#comment-17637737
]
Michael Osipov commented on MNG-7244:
-
[~cstamas], support it forever?
> Remove deprecated WARNING for usage of pom.X placeholders
> -
>
> Key: MNG-7244
> URL: https://issues.apache.org/jira/browse/MNG-7244
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 4.0.0-alpha-1
>Reporter: Karl Heinz Marbaise
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0-alpha-2, 4.0.0
>
>
> Currently, we produce a {{WARNING}} in case of using {{pom.version}} or alike.
> We've been doing that for years so people have had enough time to update
> their projects. We can now remove the support and the accompanying warning,
> resorting to the default behaviour of not resolving the expression at all.
> {code}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for 'com.soebes.examples.j2ee:appasm:pom:1.0-SNAPSHOT'
> [WARNING] The expression ${pom.version} is deprecated. Please use
> ${project.version} instead.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
install-file bug
Hi ! I've found an issue in the latest maven-install-plugin version (3.1.0) and liked to be able to create a JIRA ticket to properly submit my fix. I don't know if it is the proper place to ask that, but the Guide is not very precise about the steps to follow. Thanks for your help ! Romain
[jira] [Updated] (MNG-7604) The MNG-7244 makes some older plugins defunct
[
https://issues.apache.org/jira/browse/MNG-7604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-7604:
-
Description:
The MNG-7244 removed completely the {{pom.*}} prefix interpolation, but IMHO
intent was to do it for "currently built projects". The problem is that same
interpolator is used in model builder to build transitive dependency models,
and with the change Maven 4 lost it's ability to resolve artifacts like
wagon-http 1.0-beta-6 (used by things like surefire 2.22.2 and so on).
The implication is that Maven4 CANNOT resolve wagon-http 1.0-beta-6 (and
implicitly surefire plugin 2.22.2 is defunct it seems as it uses it). Given we
have NO 3.x release of surefire (just M releases), I bet many of users out
there still use 2.22.2. Also, we have no idea how many other (used as
transitive dependencies) artifact exists out there doing same/similar thing
that wagon POM does.
IMHO: rollback the change from master and we need alt fix for it, as making
Maven 4 unable to resolve transitive deps using pom.* placeholder introduces a
huge toll.
was:The MNG-7244 removed completely the {{pom.*}} prefix interpolation, but
IMHO intent was to do it for "currently built projects". The problem is that
same interpolator is used in model builder to build transitive dependency
models, and with the change Maven 4 lost it's ability to resolve artifacts like
wagon-http 1.0-beta-6 (used by things like surefire 2.22.2 and so on).
> The MNG-7244 makes some older plugins defunct
> -
>
> Key: MNG-7604
> URL: https://issues.apache.org/jira/browse/MNG-7604
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 4.0.0-alpha-2
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 4.0.0-alpha-3
>
>
> The MNG-7244 removed completely the {{pom.*}} prefix interpolation, but IMHO
> intent was to do it for "currently built projects". The problem is that same
> interpolator is used in model builder to build transitive dependency models,
> and with the change Maven 4 lost it's ability to resolve artifacts like
> wagon-http 1.0-beta-6 (used by things like surefire 2.22.2 and so on).
> The implication is that Maven4 CANNOT resolve wagon-http 1.0-beta-6 (and
> implicitly surefire plugin 2.22.2 is defunct it seems as it uses it). Given
> we have NO 3.x release of surefire (just M releases), I bet many of users out
> there still use 2.22.2. Also, we have no idea how many other (used as
> transitive dependencies) artifact exists out there doing same/similar thing
> that wagon POM does.
> IMHO: rollback the change from master and we need alt fix for it, as making
> Maven 4 unable to resolve transitive deps using pom.* placeholder introduces
> a huge toll.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-mvnd] gnodet merged pull request #741: Clean up and upgrade dependencies/plugins versions
gnodet merged PR #741: URL: https://github.com/apache/maven-mvnd/pull/741 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-mvnd] gnodet merged pull request #743: Fix usage of the wrong groovy plugin
gnodet merged PR #743: URL: https://github.com/apache/maven-mvnd/pull/743 -- 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] (MNG-7604) The MNG-7244 makes some older plugins defunct
Tamas Cservenak created MNG-7604:
Summary: The MNG-7244 makes some older plugins defunct
Key: MNG-7604
URL: https://issues.apache.org/jira/browse/MNG-7604
Project: Maven
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 4.0.0-alpha-2
Reporter: Tamas Cservenak
Fix For: 4.0.0-alpha-3
The MNG-7244 removed completely the {{pom.*}} prefix interpolation, but IMHO
intent was to do it for "currently built projects". The problem is that same
interpolator is used in model builder to build transitive dependency models,
and with the change Maven 4 lost it's ability to resolve artifacts like
wagon-http 1.0-beta-6 (used by things like surefire 2.22.2 and so on).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7244) Remove deprecated WARNING for usage of pom.X placeholders
[
https://issues.apache.org/jira/browse/MNG-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637710#comment-17637710
]
Tamas Cservenak edited comment on MNG-7244 at 11/23/22 11:56 AM:
-
The Maven PR is wrong: the PR removes pom. prefix interpolation completely, but
alas, this same interpolator is used to interpolate models for transitive
dependencies.
Hence, it results that maven4 lost ability to resolve wagon-http 1.0-beta-6
that is used by some (older) plugins like surefire 2.22.2 and so on.
Current master (w/ the PR) produces output like this:
{noformat}
[WARNING] The POM for org.apache.maven.wagon:wagon-http:jar:1.0-beta-6 is
invalid, transitive dependencies (if any) will not be available: 1 problem was
encountered while building the effective model for
/home/cstamas/Worx/apache-maven/maven-mvnd/integration-tests/src/test/projects/module-and-plugin/local/org/apache/maven/wagon/wagon-http/1.0-beta-6/wagon-http-1.0-beta-6.pom
[ERROR] 'dependencies.dependency.groupId' for
${pom.groupId}:wagon-http-shared:jar with value '${pom.groupId}' does not match
a valid coordinate id pattern. @
org.apache.maven.wagon:wagon-http:1.0-beta-6{noformat}
And it results in wagon-http being completely defunct, as HttpWagon super class
is in wagon-http-shared but class is not on CP and boom.
was (Author: cstamas):
The Maven PR is wrong: the PR removes pom. prefix interpolation completely, but
alas, this same interpolator is used to interpolate models for transitive
dependencies.
Hence, it results that maven4 lost ability to resolve wagon-http 1.0-beta-6
that is used by some (older) plugins like surefire 2.22.2 and so on.
> Remove deprecated WARNING for usage of pom.X placeholders
> -
>
> Key: MNG-7244
> URL: https://issues.apache.org/jira/browse/MNG-7244
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 4.0.0-alpha-1
>Reporter: Karl Heinz Marbaise
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0-alpha-2, 4.0.0
>
>
> Currently, we produce a {{WARNING}} in case of using {{pom.version}} or alike.
> We've been doing that for years so people have had enough time to update
> their projects. We can now remove the support and the accompanying warning,
> resorting to the default behaviour of not resolving the expression at all.
> {code}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for 'com.soebes.examples.j2ee:appasm:pom:1.0-SNAPSHOT'
> [WARNING] The expression ${pom.version} is deprecated. Please use
> ${project.version} instead.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MWRAPPER-76) Error "{6}" was unexpected at this time (Windows 10)
[
https://issues.apache.org/jira/browse/MWRAPPER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637711#comment-17637711
]
Artur commented on MWRAPPER-76:
---
Thanks, we faced the same problem and are now using a manually patched version
of mvnw.cmd with this fix
> Error "{6}" was unexpected at this time (Windows 10)
>
>
> Key: MWRAPPER-76
> URL: https://issues.apache.org/jira/browse/MWRAPPER-76
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.1.1
>Reporter: Svein
>Priority: Major
>
> {color:#00}Testes and i worked on this path: C:\tmp\New (2)\{6}
> folder\my-app57(2). The problem is the ')' character.{color}
> {color:#00}My solution is:{color}
> {color:#00}@setlocal EnableDelayedExpansion and !WRAPPER_JAR!.{color}
>
> {code:java}
> @setlocal EnableDelayedExpansion
> powershell -Command "&{"^
> "$webclient = new-object System.Net.WebClient;"^
> "if (-not ([string]::IsNullOrEmpty('%MVNW_USERNAME%') -and
> [string]::IsNullOrEmpty('%MVNW_PASSWORD%'))) {"^
> "$webclient.Credentials = new-object
> System.Net.NetworkCredential('%MVNW_USERNAME%', '%MVNW_PASSWORD%');"^
> "}"^
> "[Net.ServicePointManager]::SecurityProtocol =
> [Net.SecurityProtocolType]::Tls12; $webclient.DownloadFile('%DOWNLOAD_URL%',
> '!WRAPPER_JAR!')"^
> "}"
> @endlocal
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7244) Remove deprecated WARNING for usage of pom.X placeholders
[
https://issues.apache.org/jira/browse/MNG-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637710#comment-17637710
]
Tamas Cservenak commented on MNG-7244:
--
The Maven PR is wrong: the PR removes pom. prefix interpolation completely, but
alas, this same interpolator is used to interpolate models for transitive
dependencies.
Hence, it results that maven4 lost ability to resolve wagon-http 1.0-beta-6
that is used by some (older) plugins like surefire 2.22.2 and so on.
> Remove deprecated WARNING for usage of pom.X placeholders
> -
>
> Key: MNG-7244
> URL: https://issues.apache.org/jira/browse/MNG-7244
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 4.0.0-alpha-1
>Reporter: Karl Heinz Marbaise
>Assignee: Maarten Mulders
>Priority: Minor
> Fix For: 4.0.0-alpha-2, 4.0.0
>
>
> Currently, we produce a {{WARNING}} in case of using {{pom.version}} or alike.
> We've been doing that for years so people have had enough time to update
> their projects. We can now remove the support and the accompanying warning,
> resorting to the default behaviour of not resolving the expression at all.
> {code}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for 'com.soebes.examples.j2ee:appasm:pom:1.0-SNAPSHOT'
> [WARNING] The expression ${pom.version} is deprecated. Please use
> ${project.version} instead.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7603) Build cache XSD is not published
[ https://issues.apache.org/jira/browse/MNG-7603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637696#comment-17637696 ] Michael Osipov commented on MNG-7603: - For the truly unpatient. > Build cache XSD is not published > > > Key: MNG-7603 > URL: https://issues.apache.org/jira/browse/MNG-7603 > Project: Maven > Issue Type: Bug >Reporter: David Phillips >Priority: Major > > The [build cache > XSD|https://maven.apache.org/xsd/build-cache-config-1.0.0.xsd] which is > [referenced > here|https://maven.apache.org/extensions/maven-build-cache-extension/build-cache-build.html] > is not published on the Maven website. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-7603) Build cache XSD is not published
David Phillips created MNG-7603: --- Summary: Build cache XSD is not published Key: MNG-7603 URL: https://issues.apache.org/jira/browse/MNG-7603 Project: Maven Issue Type: Bug Reporter: David Phillips The [build cache XSD|https://maven.apache.org/xsd/build-cache-config-1.0.0.xsd] which is [referenced here|https://maven.apache.org/extensions/maven-build-cache-extension/build-cache-build.html] is not published on the Maven website. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-297) Chained LRM
[ https://issues.apache.org/jira/browse/MRESOLVER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637690#comment-17637690 ] Slawomir Jaranowski commented on MRESOLVER-297: --- How "chained" LRM can be used ... similar situation is in m-invoker-p, local repo for tests is prepared by "outer" Maven and in tests "inner" is executed. > Chained LRM > --- > > Key: MRESOLVER-297 > URL: https://issues.apache.org/jira/browse/MRESOLVER-297 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.2 > > > Implement "chained" LRM. This utility would NOT meant to be used in any > production env, but rather in some confined use cases like "isolated" > environment like running IT tests. > If you split "inner" and "outer" build when for example running Maven IT > Suite, the "outer" build is directly affected by user setup (user > settings.xml and other things), while "inner" is (should be) isolated. > Moreover, the "outer" build builds plugins and dependencies that are required > by "inner" build. Simply sharing same local repository does not work, see for > example MNG-5185 but it boils down to this: > * Maven3 enhanced local repo tracks "artifact availability", by repo ID and > this is affected by user env (ie. MRM being used with own repo ID) > * inner IT build has central repo "shut down" (file/null), as it expects all > resolved and present in local repo by "outer" build > * while this is true (files are present) they may be not available, as > "outer" build user env may use different settings than inner (ie. a MRM with > own repo ID) > The implemented "chained" LRM can isolate local repo for ITs: > * sandbox "inner" build ITs into own local repo > * but allow artifact resolution from local repo used by "outer" build > * this 2nd is needed as dependencies and artifacts resolved and installed by > "outer" build and are needed in "inner" build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-mvnd] gnodet closed pull request #736: Resolver 1.9.0
gnodet closed pull request #736: Resolver 1.9.0 URL: https://github.com/apache/maven-mvnd/pull/736 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-mvnd] gnodet commented on pull request #736: Resolver 1.9.0
gnodet commented on PR #736: URL: https://github.com/apache/maven-mvnd/pull/736#issuecomment-1324815259 Superseded by #742 -- 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-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637670#comment-17637670 ] ASF GitHub Bot commented on MNG-7586: - cstamas opened a new pull request, #882: URL: https://github.com/apache/maven/pull/882 Updates resolver to latest release. --- https://issues.apache.org/jira/browse/MNG-7586 > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637671#comment-17637671 ] ASF GitHub Bot commented on MNG-7586: - cstamas opened a new pull request, #742: URL: https://github.com/apache/maven-mvnd/pull/742 Updates resolver to latest release. --- https://issues.apache.org/jira/browse/MNG-7586 > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637669#comment-17637669 ] ASF GitHub Bot commented on MNG-7586: - cstamas opened a new pull request, #881: URL: https://github.com/apache/maven/pull/881 Updates resolver to latest release. --- https://issues.apache.org/jira/browse/MNG-7586 > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-mvnd] cstamas opened a new pull request, #742: [MNG-7586] Update Maven Resolver to 1.9.2
cstamas opened a new pull request, #742: URL: https://github.com/apache/maven-mvnd/pull/742 Updates resolver to latest release. --- https://issues.apache.org/jira/browse/MNG-7586 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] cstamas opened a new pull request, #882: [MNG-7586] Update Maven Resolver to 1.9.2
cstamas opened a new pull request, #882: URL: https://github.com/apache/maven/pull/882 Updates resolver to latest release. --- https://issues.apache.org/jira/browse/MNG-7586 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] cstamas opened a new pull request, #881: [MNG-7586] Update Maven Resolver to 1.9.2
cstamas opened a new pull request, #881: URL: https://github.com/apache/maven/pull/881 Updates resolver to latest release. --- https://issues.apache.org/jira/browse/MNG-7586 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRELEASE-1110) release:prepare fails on Jenkins agent with " 'cmd' is not recognized as an internal or external command"
[
https://issues.apache.org/jira/browse/MRELEASE-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637662#comment-17637662
]
Thorsten Heit commented on MRELEASE-1110:
-
The job was configured to ask a few (string) parameters that are needed by an
Ant script executed at the end in a post-step. One of these parameters was
called "path" that obviosly overrode the PATH environment variable. Renaming
that did the trick...
> release:prepare fails on Jenkins agent with " 'cmd' is not recognized as an
> internal or external command"
> -
>
> Key: MRELEASE-1110
> URL: https://issues.apache.org/jira/browse/MRELEASE-1110
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 3.0.0-M6, 3.0.0-M7
>Reporter: Thorsten Heit
>Priority: Major
>
> We have a project that is configured as a Maven project in Jenkins and is
> built by a Jenkins agent running on a Windows machine. Using "clean verify"
> as goals I can build the project successfully. So far, so good.
> Changing this to "-B -DdevelopmentVersion=1.3.1-SNAPSHOT
> -DreleaseVersion=1.3.0 -Dresume=false -DdryRun=true
> -DautoResolveSnapshots=all release:prepare", the build fails:
> {noformat}
> (...)
> [EasyMailServer] $ D:\Build\Tools\Java\JDKs\jdk1.8.0/bin/java
> -Dorg.apache.maven.global-settings=C:\Users\continteg\.m2\settings.xml
> -Djava.awt.headless=true -cp
> d:\.j\maven35-agent.jar;D:\Build\Tools\Java\maven\apache-maven-3.8.3\boot\plexus-classworlds-2.6.0.jar;D:\Build\Tools\Java\maven\apache-maven-3.8.3/conf/logging
> jenkins.maven3.agent.Maven35Main
> D:\Build\Tools\Java\maven\apache-maven-3.8.3
> D:\Build\Tools\jenkins-agent\agent.jar d:\.j\maven35-interceptor.jar
> d:\.j\maven3-interceptor-commons.jar 53433
> <===[JENKINS REMOTING CAPACITY]===>channel started
> Executing Maven: -B -f d:\.j\workspace\EasyMailServer\pom.xml
> -DdevelopmentVersion=1.3.1-SNAPSHOT -DreleaseVersion=1.3.0 -Dresume=false
> -DdryRun=true -DautoResolveSnapshots=all release:prepare verify
> [INFO] Scanning for projects...
> (...)
> [INFO] starting prepare goal in dry-run mode, composed of 17 phases:
> check-poms, scm-check-modifications, check-dependency-snapshots,
> create-backup-poms, map-release-versions, input-variables,
> map-development-versions, rewrite-poms-for-release, generate-release-poms,
> run-preparation-goals, scm-commit-release, scm-tag,
> rewrite-poms-for-development, remove-release-poms, run-completion-goals,
> scm-commit-development, end-release
> [INFO] 1/17 prepare:check-poms dry-run
> (...)
> [INFO] 10/17 prepare:run-preparation-goals dry-run
> [INFO] Executing preparation goals - since this is simulation mode it is
> running against the original project, not the rewritten ones
> [INFO] Executing goals 'clean verify'...
> [INFO] with additional arguments: -P
> override_defaults,signing,jdks,infport,sonarqubevariables
> [INFO] [INFO] Scanning for projects...
> (...)
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD SUCCESS
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 4.782 s
> [INFO] [INFO] Finished at: 2022-11-22T09:52:03+01:00
> [INFO] [INFO]
>
> [ERROR] 'cmd' is not recognized as an internal or external command,
> [ERROR] operable program or batch file.
> [JENKINS] Archiving disabled
> [INFO]
> [INFO]
>
> [INFO] Skipping easyMailServer
> [INFO] This project has been banned from the build due to previous failures.
> [INFO]
>
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 8.628 s
> [JENKINS] Archiving disabled[INFO] Finished at: 2022-11-22T09:52:03+01:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli)
> on project easyMailServer: Maven execution failed, exit code: 1 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecuti
[GitHub] [maven-mvnd] gnodet merged pull request #740: Switch graalvm to 22.3.0
gnodet merged PR #740: URL: https://github.com/apache/maven-mvnd/pull/740 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-mvnd] gnodet merged pull request #739: Fix possible NullPointerException
gnodet merged PR #739: URL: https://github.com/apache/maven-mvnd/pull/739 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MRELEASE-1110) release:prepare fails on Jenkins agent with " 'cmd' is not recognized as an internal or external command"
[
https://issues.apache.org/jira/browse/MRELEASE-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-1110.
Resolution: Not A Problem
Who fiddled with PATH on your end?
> release:prepare fails on Jenkins agent with " 'cmd' is not recognized as an
> internal or external command"
> -
>
> Key: MRELEASE-1110
> URL: https://issues.apache.org/jira/browse/MRELEASE-1110
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 3.0.0-M6, 3.0.0-M7
>Reporter: Thorsten Heit
>Priority: Major
>
> We have a project that is configured as a Maven project in Jenkins and is
> built by a Jenkins agent running on a Windows machine. Using "clean verify"
> as goals I can build the project successfully. So far, so good.
> Changing this to "-B -DdevelopmentVersion=1.3.1-SNAPSHOT
> -DreleaseVersion=1.3.0 -Dresume=false -DdryRun=true
> -DautoResolveSnapshots=all release:prepare", the build fails:
> {noformat}
> (...)
> [EasyMailServer] $ D:\Build\Tools\Java\JDKs\jdk1.8.0/bin/java
> -Dorg.apache.maven.global-settings=C:\Users\continteg\.m2\settings.xml
> -Djava.awt.headless=true -cp
> d:\.j\maven35-agent.jar;D:\Build\Tools\Java\maven\apache-maven-3.8.3\boot\plexus-classworlds-2.6.0.jar;D:\Build\Tools\Java\maven\apache-maven-3.8.3/conf/logging
> jenkins.maven3.agent.Maven35Main
> D:\Build\Tools\Java\maven\apache-maven-3.8.3
> D:\Build\Tools\jenkins-agent\agent.jar d:\.j\maven35-interceptor.jar
> d:\.j\maven3-interceptor-commons.jar 53433
> <===[JENKINS REMOTING CAPACITY]===>channel started
> Executing Maven: -B -f d:\.j\workspace\EasyMailServer\pom.xml
> -DdevelopmentVersion=1.3.1-SNAPSHOT -DreleaseVersion=1.3.0 -Dresume=false
> -DdryRun=true -DautoResolveSnapshots=all release:prepare verify
> [INFO] Scanning for projects...
> (...)
> [INFO] starting prepare goal in dry-run mode, composed of 17 phases:
> check-poms, scm-check-modifications, check-dependency-snapshots,
> create-backup-poms, map-release-versions, input-variables,
> map-development-versions, rewrite-poms-for-release, generate-release-poms,
> run-preparation-goals, scm-commit-release, scm-tag,
> rewrite-poms-for-development, remove-release-poms, run-completion-goals,
> scm-commit-development, end-release
> [INFO] 1/17 prepare:check-poms dry-run
> (...)
> [INFO] 10/17 prepare:run-preparation-goals dry-run
> [INFO] Executing preparation goals - since this is simulation mode it is
> running against the original project, not the rewritten ones
> [INFO] Executing goals 'clean verify'...
> [INFO] with additional arguments: -P
> override_defaults,signing,jdks,infport,sonarqubevariables
> [INFO] [INFO] Scanning for projects...
> (...)
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD SUCCESS
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 4.782 s
> [INFO] [INFO] Finished at: 2022-11-22T09:52:03+01:00
> [INFO] [INFO]
>
> [ERROR] 'cmd' is not recognized as an internal or external command,
> [ERROR] operable program or batch file.
> [JENKINS] Archiving disabled
> [INFO]
> [INFO]
>
> [INFO] Skipping easyMailServer
> [INFO] This project has been banned from the build due to previous failures.
> [INFO]
>
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 8.628 s
> [JENKINS] Archiving disabled[INFO] Finished at: 2022-11-22T09:52:03+01:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli)
> on project easyMailServer: Maven execution failed, exit code: 1 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
> (...)
> The same error occurs with m-release-3.0.0-M7 (stacktrace turned on by
> additionally using "-X" in the goals):
> {noformat}
> (...)
> [INFO] [INFO]
> ---
[jira] [Commented] (MRELEASE-1110) release:prepare fails on Jenkins agent with " 'cmd' is not recognized as an internal or external command"
[
https://issues.apache.org/jira/browse/MRELEASE-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637656#comment-17637656
]
Thorsten Heit commented on MRELEASE-1110:
-
I finally found out the reason why it failed:
The environment variable "PATH" only contained $MAVEN_HOME/bin, $JAVA_HOME/bin
and some other directory, but not the path to %WINDIR%\system32. Fixing that,
now the release:prepare job works with m-release-p 3.0.0-M7.
Thanks for your hints and patience :)
> release:prepare fails on Jenkins agent with " 'cmd' is not recognized as an
> internal or external command"
> -
>
> Key: MRELEASE-1110
> URL: https://issues.apache.org/jira/browse/MRELEASE-1110
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 3.0.0-M6, 3.0.0-M7
>Reporter: Thorsten Heit
>Priority: Major
>
> We have a project that is configured as a Maven project in Jenkins and is
> built by a Jenkins agent running on a Windows machine. Using "clean verify"
> as goals I can build the project successfully. So far, so good.
> Changing this to "-B -DdevelopmentVersion=1.3.1-SNAPSHOT
> -DreleaseVersion=1.3.0 -Dresume=false -DdryRun=true
> -DautoResolveSnapshots=all release:prepare", the build fails:
> {noformat}
> (...)
> [EasyMailServer] $ D:\Build\Tools\Java\JDKs\jdk1.8.0/bin/java
> -Dorg.apache.maven.global-settings=C:\Users\continteg\.m2\settings.xml
> -Djava.awt.headless=true -cp
> d:\.j\maven35-agent.jar;D:\Build\Tools\Java\maven\apache-maven-3.8.3\boot\plexus-classworlds-2.6.0.jar;D:\Build\Tools\Java\maven\apache-maven-3.8.3/conf/logging
> jenkins.maven3.agent.Maven35Main
> D:\Build\Tools\Java\maven\apache-maven-3.8.3
> D:\Build\Tools\jenkins-agent\agent.jar d:\.j\maven35-interceptor.jar
> d:\.j\maven3-interceptor-commons.jar 53433
> <===[JENKINS REMOTING CAPACITY]===>channel started
> Executing Maven: -B -f d:\.j\workspace\EasyMailServer\pom.xml
> -DdevelopmentVersion=1.3.1-SNAPSHOT -DreleaseVersion=1.3.0 -Dresume=false
> -DdryRun=true -DautoResolveSnapshots=all release:prepare verify
> [INFO] Scanning for projects...
> (...)
> [INFO] starting prepare goal in dry-run mode, composed of 17 phases:
> check-poms, scm-check-modifications, check-dependency-snapshots,
> create-backup-poms, map-release-versions, input-variables,
> map-development-versions, rewrite-poms-for-release, generate-release-poms,
> run-preparation-goals, scm-commit-release, scm-tag,
> rewrite-poms-for-development, remove-release-poms, run-completion-goals,
> scm-commit-development, end-release
> [INFO] 1/17 prepare:check-poms dry-run
> (...)
> [INFO] 10/17 prepare:run-preparation-goals dry-run
> [INFO] Executing preparation goals - since this is simulation mode it is
> running against the original project, not the rewritten ones
> [INFO] Executing goals 'clean verify'...
> [INFO] with additional arguments: -P
> override_defaults,signing,jdks,infport,sonarqubevariables
> [INFO] [INFO] Scanning for projects...
> (...)
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD SUCCESS
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 4.782 s
> [INFO] [INFO] Finished at: 2022-11-22T09:52:03+01:00
> [INFO] [INFO]
>
> [ERROR] 'cmd' is not recognized as an internal or external command,
> [ERROR] operable program or batch file.
> [JENKINS] Archiving disabled
> [INFO]
> [INFO]
>
> [INFO] Skipping easyMailServer
> [INFO] This project has been banned from the build due to previous failures.
> [INFO]
>
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 8.628 s
> [JENKINS] Archiving disabled[INFO] Finished at: 2022-11-22T09:52:03+01:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli)
> on project easyMailServer: Maven execution failed, exit code: 1 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cw
[GitHub] [maven-ear-plugin] dependabot[bot] opened a new pull request, #83: Bump maven-plugins from 37 to 38
dependabot[bot] opened a new pull request, #83: URL: https://github.com/apache/maven-ear-plugin/pull/83 Bumps [maven-plugins](https://github.com/apache/maven-parent) from 37 to 38. Release notes Sourced from https://github.com/apache/maven-parent/releases";>maven-plugins's releases. 38 Improvement [https://issues.apache.org/jira/browse/MPOM-340";>MPOM-340] - Remove test-javadoc reports [https://issues.apache.org/jira/browse/MPOM-353";>MPOM-353] - Use standard value for ignoreFailures at m-invoker-p [https://issues.apache.org/jira/browse/MPOM-357";>MPOM-357] - Execute checkstyle after enforcer Task [https://issues.apache.org/jira/browse/MPOM-349";>MPOM-349] - Enable spotless for autoformatting [https://issues.apache.org/jira/browse/MPOM-350";>MPOM-350] - Raise JDK requirement to 1.8 [https://issues.apache.org/jira/browse/MPOM-352";>MPOM-352] - Remove managed dependency on deprecated plexus-component-annotations Dependency upgrade [https://issues.apache.org/jira/browse/MPOM-341";>MPOM-341] - Bump extra-enforcer-rules from 1.6.0 to 1.6.1 [https://issues.apache.org/jira/browse/MPOM-343";>MPOM-343] - Upgrade Maven Checkstyle Plugin to 3.2.0 [https://issues.apache.org/jira/browse/MPOM-348";>MPOM-348] - Remove configuration for Maven Changes Plugin [https://issues.apache.org/jira/browse/MPOM-351";>MPOM-351] - Upgrade plexus-utils to 3.5.0 [https://issues.apache.org/jira/browse/MPOM-355";>MPOM-355] - Bump maven-pmd-plugin from 3.17.0 to 3.19.0 [https://issues.apache.org/jira/browse/MPOM-356";>MPOM-356] - Bump maven-jxr-plugin from 3.2.0 to 3.3.0 Commits See full diff in https://github.com/apache/maven-parent/commits";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and 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 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] [Updated] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7586: - Description: Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due different reasons). > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (MNG-7586) Update Maven Resolver to 1.9.1
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reopened MNG-7586: -- > Update Maven Resolver to 1.9.1 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7586: - Summary: Update Maven Resolver to 1.9.2 (was: Update Maven Resolver to 1.9.1) > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-297) Chained LRM
[ https://issues.apache.org/jira/browse/MRESOLVER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637640#comment-17637640 ] Hudson commented on MRESOLVER-297: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #89 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/89/ > Chained LRM > --- > > Key: MRESOLVER-297 > URL: https://issues.apache.org/jira/browse/MRESOLVER-297 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.2 > > > Implement "chained" LRM. This utility would NOT meant to be used in any > production env, but rather in some confined use cases like "isolated" > environment like running IT tests. > If you split "inner" and "outer" build when for example running Maven IT > Suite, the "outer" build is directly affected by user setup (user > settings.xml and other things), while "inner" is (should be) isolated. > Moreover, the "outer" build builds plugins and dependencies that are required > by "inner" build. Simply sharing same local repository does not work, see for > example MNG-5185 but it boils down to this: > * Maven3 enhanced local repo tracks "artifact availability", by repo ID and > this is affected by user env (ie. MRM being used with own repo ID) > * inner IT build has central repo "shut down" (file/null), as it expects all > resolved and present in local repo by "outer" build > * while this is true (files are present) they may be not available, as > "outer" build user env may use different settings than inner (ie. a MRM with > own repo ID) > The implemented "chained" LRM can isolate local repo for ITs: > * sandbox "inner" build ITs into own local repo > * but allow artifact resolution from local repo used by "outer" build > * this 2nd is needed as dependencies and artifacts resolved and installed by > "outer" build and are needed in "inner" build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-297) Chained LRM
[ https://issues.apache.org/jira/browse/MRESOLVER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-297. - Resolution: Fixed > Chained LRM > --- > > Key: MRESOLVER-297 > URL: https://issues.apache.org/jira/browse/MRESOLVER-297 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.2 > > > Implement "chained" LRM. This utility would NOT meant to be used in any > production env, but rather in some confined use cases like "isolated" > environment like running IT tests. > If you split "inner" and "outer" build when for example running Maven IT > Suite, the "outer" build is directly affected by user setup (user > settings.xml and other things), while "inner" is (should be) isolated. > Moreover, the "outer" build builds plugins and dependencies that are required > by "inner" build. Simply sharing same local repository does not work, see for > example MNG-5185 but it boils down to this: > * Maven3 enhanced local repo tracks "artifact availability", by repo ID and > this is affected by user env (ie. MRM being used with own repo ID) > * inner IT build has central repo "shut down" (file/null), as it expects all > resolved and present in local repo by "outer" build > * while this is true (files are present) they may be not available, as > "outer" build user env may use different settings than inner (ie. a MRM with > own repo ID) > The implemented "chained" LRM can isolate local repo for ITs: > * sandbox "inner" build ITs into own local repo > * but allow artifact resolution from local repo used by "outer" build > * this 2nd is needed as dependencies and artifacts resolved and installed by > "outer" build and are needed in "inner" build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-297) Chained LRM
[ https://issues.apache.org/jira/browse/MRESOLVER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-297: - Assignee: Tamas Cservenak > Chained LRM > --- > > Key: MRESOLVER-297 > URL: https://issues.apache.org/jira/browse/MRESOLVER-297 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.2 > > > Implement "chained" LRM. This utility would NOT meant to be used in any > production env, but rather in some confined use cases like "isolated" > environment like running IT tests. > If you split "inner" and "outer" build when for example running Maven IT > Suite, the "outer" build is directly affected by user setup (user > settings.xml and other things), while "inner" is (should be) isolated. > Moreover, the "outer" build builds plugins and dependencies that are required > by "inner" build. Simply sharing same local repository does not work, see for > example MNG-5185 but it boils down to this: > * Maven3 enhanced local repo tracks "artifact availability", by repo ID and > this is affected by user env (ie. MRM being used with own repo ID) > * inner IT build has central repo "shut down" (file/null), as it expects all > resolved and present in local repo by "outer" build > * while this is true (files are present) they may be not available, as > "outer" build user env may use different settings than inner (ie. a MRM with > own repo ID) > The implemented "chained" LRM can isolate local repo for ITs: > * sandbox "inner" build ITs into own local repo > * but allow artifact resolution from local repo used by "outer" build > * this 2nd is needed as dependencies and artifacts resolved and installed by > "outer" build and are needed in "inner" build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-297) Chained LRM
[ https://issues.apache.org/jira/browse/MRESOLVER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637633#comment-17637633 ] ASF GitHub Bot commented on MRESOLVER-297: -- cstamas merged PR #223: URL: https://github.com/apache/maven-resolver/pull/223 > Chained LRM > --- > > Key: MRESOLVER-297 > URL: https://issues.apache.org/jira/browse/MRESOLVER-297 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 1.9.2 > > > Implement "chained" LRM. This utility would NOT meant to be used in any > production env, but rather in some confined use cases like "isolated" > environment like running IT tests. > If you split "inner" and "outer" build when for example running Maven IT > Suite, the "outer" build is directly affected by user setup (user > settings.xml and other things), while "inner" is (should be) isolated. > Moreover, the "outer" build builds plugins and dependencies that are required > by "inner" build. Simply sharing same local repository does not work, see for > example MNG-5185 but it boils down to this: > * Maven3 enhanced local repo tracks "artifact availability", by repo ID and > this is affected by user env (ie. MRM being used with own repo ID) > * inner IT build has central repo "shut down" (file/null), as it expects all > resolved and present in local repo by "outer" build > * while this is true (files are present) they may be not available, as > "outer" build user env may use different settings than inner (ie. a MRM with > own repo ID) > The implemented "chained" LRM can isolate local repo for ITs: > * sandbox "inner" build ITs into own local repo > * but allow artifact resolution from local repo used by "outer" build > * this 2nd is needed as dependencies and artifacts resolved and installed by > "outer" build and are needed in "inner" build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-resolver] cstamas merged pull request #223: [MRESOLVER-297] Chained LRM
cstamas merged PR #223: URL: https://github.com/apache/maven-resolver/pull/223 -- 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] (MRESOLVER-297) Chained LRM
[ https://issues.apache.org/jira/browse/MRESOLVER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-297: -- Description: Implement "chained" LRM. This utility would NOT meant to be used in any production env, but rather in some confined use cases like "isolated" environment like running IT tests. If you split "inner" and "outer" build when for example running Maven IT Suite, the "outer" build is directly affected by user setup (user settings.xml and other things), while "inner" is (should be) isolated. Moreover, the "outer" build builds plugins and dependencies that are required by "inner" build. Simply sharing same local repository does not work, see for example MNG-5185 but it boils down to this: * Maven3 enhanced local repo tracks "artifact availability", by repo ID and this is affected by user env (ie. MRM being used with own repo ID) * inner IT build has central repo "shut down" (file/null), as it expects all resolved and present in local repo by "outer" build * while this is true (files are present) they may be not available, as "outer" build user env may use different settings than inner (ie. a MRM with own repo ID) The implemented "chained" LRM can isolate local repo for ITs: * sandbox "inner" build ITs into own local repo * but allow artifact resolution from local repo used by "outer" build * this 2nd is needed as dependencies and artifacts resolved and installed by "outer" build and are needed in "inner" build was: Implement "chained" LRM. This utility would NOT meant to be used in any production env, but rather in some confined use cases like "isolated" environment like running IT tests. If you split "inner" and "outer" build when for example running Maven IT Suite, the "outer" build is directly affected by user setup (user settings.xml and other things), while "inner" is (should be) isolated. Moreover, the "outer" build builds plugins and dependencies that are required by "inner" build. Simply sharing same local repository does not work, see for example MNG-5185 but it boils down to this: * Maven3 enhanced local repo tracks "artifact availability", by repo ID and this is affected by user env (ie. MRM being used with own repo ID) * inner IT build has central repo "shut down" (file/null), as it expects all resolved and present in local repo by "outer" build * while this is true (files are present) they may be not available, as "outer" build user env may use different settings than inner (ie. a MRM with own repo ID) The implemented "chained" LRM can isolate local repo for ITs: * sandbox "inner" build ITs into own local repo * but allow artifact resolution from local repo used by "outer" build * this 2nd is needed as dependencies and artifacts built by "outer" build are needed in "inner" build > Chained LRM > --- > > Key: MRESOLVER-297 > URL: https://issues.apache.org/jira/browse/MRESOLVER-297 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 1.9.2 > > > Implement "chained" LRM. This utility would NOT meant to be used in any > production env, but rather in some confined use cases like "isolated" > environment like running IT tests. > If you split "inner" and "outer" build when for example running Maven IT > Suite, the "outer" build is directly affected by user setup (user > settings.xml and other things), while "inner" is (should be) isolated. > Moreover, the "outer" build builds plugins and dependencies that are required > by "inner" build. Simply sharing same local repository does not work, see for > example MNG-5185 but it boils down to this: > * Maven3 enhanced local repo tracks "artifact availability", by repo ID and > this is affected by user env (ie. MRM being used with own repo ID) > * inner IT build has central repo "shut down" (file/null), as it expects all > resolved and present in local repo by "outer" build > * while this is true (files are present) they may be not available, as > "outer" build user env may use different settings than inner (ie. a MRM with > own repo ID) > The implemented "chained" LRM can isolate local repo for ITs: > * sandbox "inner" build ITs into own local repo > * but allow artifact resolution from local repo used by "outer" build > * this 2nd is needed as dependencies and artifacts resolved and installed by > "outer" build and are needed in "inner" build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-297) Chained LRM
[ https://issues.apache.org/jira/browse/MRESOLVER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-297: -- Description: Implement "chained" LRM. This utility would NOT meant to be used in any production env, but rather in some confined use cases like "isolated" environment like running IT tests. If you split "inner" and "outer" build when for example running Maven IT Suite, the "outer" build is directly affected by user setup (user settings.xml and other things), while "inner" is (should be) isolated. Moreover, the "outer" build builds plugins and dependencies that are required by "inner" build. Simply sharing same local repository does not work, see for example MNG-5185 but it boils down to this: * Maven3 enhanced local repo tracks "artifact availability", by repo ID and this is affected by user env (ie. MRM being used with own repo ID) * inner IT build has central repo "shut down" (file/null), as it expects all resolved and present in local repo by "outer" build * while this is true (files are present) they may be not available, as "outer" build user env may use different settings than inner (ie. a MRM with own repo ID) The implemented "chained" LRM can isolate local repo for ITs: * sandbox "inner" build ITs into own local repo * but allow artifact resolution from local repo used by "outer" build * this 2nd is needed as dependencies and artifacts built by "outer" build are needed in "inner" build was: Implement "chained" LRM. This utility would NOT meant to be used in any production env, but rather in some confined use cases like "isolated" environment like running IT tests. If you split "inner" and "outer" build when for example running Maven IT Suite, the "outer" build is directly affected by user setup (user settings.xml and other things), while "inner" is (should be) isolated. Moreover, the "outer" build builds plugins and dependencies that are required by "inner" build. Simply sharing same local repository does not work, see for example MNG-5185 but it boils down to this: * Maven3 enhanced local repo tracks "artifact availability", by repo ID and this is affected by user env (ie. MRM being used with own repo ID) * inner IT build has central repo "shut down" (file/null), as it expects all resolved and present in local repo by "outer" build * while this is true (files are present) they may be not available (as outer build user env uses different settings than inner) The implemented "chained" LRM can isolate local repo for ITs: * sandbox "inner" build ITs into own local repo * but allow artifact resolution from local repo used by "outer" build * this 2nd is needed as dependencies and artifacts built by "outer" build are needed in "inner" build > Chained LRM > --- > > Key: MRESOLVER-297 > URL: https://issues.apache.org/jira/browse/MRESOLVER-297 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 1.9.2 > > > Implement "chained" LRM. This utility would NOT meant to be used in any > production env, but rather in some confined use cases like "isolated" > environment like running IT tests. > If you split "inner" and "outer" build when for example running Maven IT > Suite, the "outer" build is directly affected by user setup (user > settings.xml and other things), while "inner" is (should be) isolated. > Moreover, the "outer" build builds plugins and dependencies that are required > by "inner" build. Simply sharing same local repository does not work, see for > example MNG-5185 but it boils down to this: > * Maven3 enhanced local repo tracks "artifact availability", by repo ID and > this is affected by user env (ie. MRM being used with own repo ID) > * inner IT build has central repo "shut down" (file/null), as it expects all > resolved and present in local repo by "outer" build > * while this is true (files are present) they may be not available, as > "outer" build user env may use different settings than inner (ie. a MRM with > own repo ID) > The implemented "chained" LRM can isolate local repo for ITs: > * sandbox "inner" build ITs into own local repo > * but allow artifact resolution from local repo used by "outer" build > * this 2nd is needed as dependencies and artifacts built by "outer" build > are needed in "inner" build -- This message was sent by Atlassian Jira (v8.20.10#820010)
