[GitHub] [maven-filtering] sebthom commented on pull request #15: [MRESOURCES-268] - Report path of offending file on copy/filter error.
sebthom commented on pull request #15: URL: https://github.com/apache/maven-filtering/pull/15#issuecomment-773855700 I pushed a change since apparently not only checked IOExceptions but also intenral runtime exceptions (e.g. IllegalArgumentExcpetion) are thrown since version 3.2.0 of the maven-resource-plugin when a filtered file has an unexpected encoding. Here is real world example. A submodule of a very large multi-artifact/module enterprise application. Without this PR it have would been very laborious (and maybe impossible for the average developer) to discover the root cause. Before this PR:  After this PR:  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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (MNG-7049) Version range resolution downloads all poms, not just the highest version
[ https://issues.apache.org/jira/browse/MNG-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279326#comment-17279326 ] Xiang Li edited comment on MNG-7049 at 2/5/21, 6:56 AM: [~michael-o] thanks for the reply, the inefficient does cause lot of trouble while you have tons development versions in certain range. Also it can be fragile if there are some "bad" poms. I looked both [DefaultVersionRangeResolver.java|https://github.com/apache/maven/blob/maven-3.6.3/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionRangeResolver.java] and [DefaultModelResolver.java|https://github.com/apache/maven/blob/maven-3.6.3/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultModelResolver.java] (I use maven 3.6.3) but those resolve module seems directly take the highest version instead of caching all previous versions' pom. Forgive my ignorance maven knowledge, but I wonder if maven will cache all pom files in version range that exists in remote metadata.xml? was (Author: xiangli1996): [~michael-o] thanks for the reply, the inefficient does cause lot of trouble while you have tons development versions in certain range. Also it can be fragile if there are some "bad" poms. I looked both [DefaultVersionRangeResolver.java|https://github.com/apache/maven/blob/maven-3.6.3/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionRangeResolver.java] and [DefaultModelResolver.java|https://github.com/apache/maven/blob/maven-3.6.3/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultModelResolver.java] (I use maven 3.6.3) but those resolve module seems directly take the highest version instead of caching all previous versions' pom. Sorry if I am not familiar with maven code, but I wonder if maven will cache all pom files that exists metadata.xml if it is not the versionRangeResolver's issue? > Version range resolution downloads all poms, not just the highest version > - > > Key: MNG-7049 > URL: https://issues.apache.org/jira/browse/MNG-7049 > Project: Maven > Issue Type: Improvement > Components: core >Reporter: Moti Nisenson-Ken >Priority: Major > > When specifying a version range for a dependency, maven will download and try > to resolve all poms in that range which satisfy the range. The usage however > is only to use the highestVersion. This causes two issues: > # Performance - it's downloading numerous poms that aren't needed. > # Fragility - if the version range covers any "bad" poms, then the build > will fail. For example, consider that for a specific version, the parent of a > pom is not present in the repository. This is enough to fail any build with a > version range covering that specific version, as the range resolution stage > will not complete. This is particularly harmful when that version would not > be selected as the highest, anyway. > Recommend to have a system property to control the desired behavior - it > should be possible to short-circuit loading all the versions and to just to > load the highest version. > For another user report of this see: > [https://stackoverflow.com/questions/25047859/restrict-maven-to-not-download-all-poms] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-jlink-plugin] dependabot[bot] opened a new pull request #38: Bump actions/cache from v2.1.3 to v2.1.4
dependabot[bot] opened a new pull request #38: URL: https://github.com/apache/maven-jlink-plugin/pull/38 Bumps [actions/cache](https://github.com/actions/cache) from v2.1.3 to v2.1.4. Release notes Sourced from https://github.com/actions/cache/releases;>actions/cache's releases. v2.1.4 Make caching more verbose https://github-redirect.dependabot.com/actions/toolkit/pull/650;>#650 Use GNU tar on macOS if available https://github-redirect.dependabot.com/actions/toolkit/pull/701;>#701 Commits https://github.com/actions/cache/commit/26968a09c0ea4f3e233fdddbafd1166051a095f6;>26968a0 Make save/restore logs akin (https://github-redirect.dependabot.com/actions/cache/issues/509;>#509) https://github.com/actions/cache/commit/aeaf731ae27476fbdef0ec9028b91f8b07b22c5d;>aeaf731 Use @actions/cache version 1.0.6 (https://github-redirect.dependabot.com/actions/cache/issues/525;>#525) https://github.com/actions/cache/commit/56a8a2f77583e58fcda120d0902eccfbc7b220bf;>56a8a2f Merge pull request https://github-redirect.dependabot.com/actions/cache/issues/514;>#514 from eregon/recommend-setup-ruby-bundler-cache https://github.com/actions/cache/commit/1bfe3accb30cbecd1eb79cdba246c3a7fc899cdf;>1bfe3ac Recommend ruby/setup-ruby's bundler-cache: true option https://github.com/actions/cache/commit/354332455a7a9ae5492723ca9d4d082484e173bc;>3543324 Merge pull request https://github-redirect.dependabot.com/actions/cache/issues/434;>#434 from DanielHabenicht/patch-1 https://github.com/actions/cache/commit/3303695afa44b4dd4776286c04fc1fbffe1ae68c;>3303695 Merge pull request https://github-redirect.dependabot.com/actions/cache/issues/507;>#507 from odin-delrio/patch-1 https://github.com/actions/cache/commit/e64ab303d144824d683711d5c78723c915ff952b;>e64ab30 Improved gradle cache key calculation example https://github.com/actions/cache/commit/26c48dce83c8127f120594ca7290654e35acfa03;>26c48dc Merge pull request https://github-redirect.dependabot.com/actions/cache/issues/506;>#506 from actions/cache-matrix-example https://github.com/actions/cache/commit/72f66cfa6dcadd8440e1382d36b556a7a43a52bc;>72f66cf Added a cache example when using matrix https://github.com/actions/cache/commit/9f3a4d3e65eb0e37d28bc055c0d1a91eac6d76fe;>9f3a4d3 Merge pull request https://github-redirect.dependabot.com/actions/cache/issues/443;>#443 from guilleijo/pipenv-example Additional commits viewable in https://github.com/actions/cache/compare/v2.1.3...26968a09c0ea4f3e233fdddbafd1166051a095f6;>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-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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] dependabot[bot] opened a new pull request #17: Bump junit-jupiter-engine from 5.7.0 to 5.7.1
dependabot[bot] opened a new pull request #17: URL: https://github.com/apache/maven-antrun-plugin/pull/17 Bumps [junit-jupiter-engine](https://github.com/junit-team/junit5) from 5.7.0 to 5.7.1. Release notes Sourced from https://github.com/junit-team/junit5/releases;>junit-jupiter-engine's releases. JUnit 5.7.1 = Platform 1.7.1 + Jupiter 5.7.1 + Vintage 5.7.1 See http://junit.org/junit5/docs/5.7.1/release-notes/;>Release Notes. Commits https://github.com/junit-team/junit5/commit/b5227801590b3a0758c46a4890e6784f7b04649c;>b522780 Release 5.7.1 https://github.com/junit-team/junit5/commit/f8c6d4ab7919781ea7401eac2caeac55c5d99d59;>f8c6d4a Finalize release notes for 5.7.1 https://github.com/junit-team/junit5/commit/8b3d5aa0885f1e0a38283de71c7431a77f234cde;>8b3d5aa Fix container failure XML reporting (https://github-redirect.dependabot.com/junit-team/junit5/issues/2542;>#2542) https://github.com/junit-team/junit5/commit/b394ef08ad2493494032ef9179cbd050e21a614c;>b394ef0 Use jOOX to test XML reports https://github.com/junit-team/junit5/commit/2b7d5b12c19da96eebd37e11ef90df4ebfc0fbed;>2b7d5b1 Use Java 9 collection factory methods https://github.com/junit-team/junit5/commit/5c42adb2b44b3532f5e8563d19d044597e4d8c4f;>5c42adb Fix typos https://github.com/junit-team/junit5/commit/beddaf450158fd81bf0da9400efb5e1d25eedba9;>beddaf4 Remove unnecessary throws clause https://github.com/junit-team/junit5/commit/85ee2126196c403dab7e05b904a84c05bf58f0db;>85ee212 Simplify assertions https://github.com/junit-team/junit5/commit/c704713e51ddfc3e2a7f811db939702a4350fb65;>c704713 Fix assertion https://github.com/junit-team/junit5/commit/7d6edad19aedae80ce5484dc8677390baac768f8;>7d6edad Convert field to local variable Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.7.0...r5.7.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-script-interpreter] dependabot[bot] opened a new pull request #34: Bump actions/cache from v2.1.3 to v2.1.4
dependabot[bot] opened a new pull request #34: URL: https://github.com/apache/maven-script-interpreter/pull/34 Bumps [actions/cache](https://github.com/actions/cache) from v2.1.3 to v2.1.4. Release notes Sourced from https://github.com/actions/cache/releases;>actions/cache's releases. v2.1.4 Make caching more verbose https://github-redirect.dependabot.com/actions/toolkit/pull/650;>#650 Use GNU tar on macOS if available https://github-redirect.dependabot.com/actions/toolkit/pull/701;>#701 Commits https://github.com/actions/cache/commit/26968a09c0ea4f3e233fdddbafd1166051a095f6;>26968a0 Make save/restore logs akin (https://github-redirect.dependabot.com/actions/cache/issues/509;>#509) https://github.com/actions/cache/commit/aeaf731ae27476fbdef0ec9028b91f8b07b22c5d;>aeaf731 Use @actions/cache version 1.0.6 (https://github-redirect.dependabot.com/actions/cache/issues/525;>#525) https://github.com/actions/cache/commit/56a8a2f77583e58fcda120d0902eccfbc7b220bf;>56a8a2f Merge pull request https://github-redirect.dependabot.com/actions/cache/issues/514;>#514 from eregon/recommend-setup-ruby-bundler-cache https://github.com/actions/cache/commit/1bfe3accb30cbecd1eb79cdba246c3a7fc899cdf;>1bfe3ac Recommend ruby/setup-ruby's bundler-cache: true option https://github.com/actions/cache/commit/354332455a7a9ae5492723ca9d4d082484e173bc;>3543324 Merge pull request https://github-redirect.dependabot.com/actions/cache/issues/434;>#434 from DanielHabenicht/patch-1 https://github.com/actions/cache/commit/3303695afa44b4dd4776286c04fc1fbffe1ae68c;>3303695 Merge pull request https://github-redirect.dependabot.com/actions/cache/issues/507;>#507 from odin-delrio/patch-1 https://github.com/actions/cache/commit/e64ab303d144824d683711d5c78723c915ff952b;>e64ab30 Improved gradle cache key calculation example https://github.com/actions/cache/commit/26c48dce83c8127f120594ca7290654e35acfa03;>26c48dc Merge pull request https://github-redirect.dependabot.com/actions/cache/issues/506;>#506 from actions/cache-matrix-example https://github.com/actions/cache/commit/72f66cfa6dcadd8440e1382d36b556a7a43a52bc;>72f66cf Added a cache example when using matrix https://github.com/actions/cache/commit/9f3a4d3e65eb0e37d28bc055c0d1a91eac6d76fe;>9f3a4d3 Merge pull request https://github-redirect.dependabot.com/actions/cache/issues/443;>#443 from guilleijo/pipenv-example Additional commits viewable in https://github.com/actions/cache/compare/v2.1.3...26968a09c0ea4f3e233fdddbafd1166051a095f6;>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-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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7049) Version range resolution downloads all poms, not just the highest version
[ https://issues.apache.org/jira/browse/MNG-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279326#comment-17279326 ] Xiang Li commented on MNG-7049: --- [~michael-o] thanks for the reply, the inefficient does cause lot of trouble while you have tons development versions in certain range. Also it can be fragile if there are some "bad" poms. I looked both [DefaultVersionRangeResolver.java|https://github.com/apache/maven/blob/maven-3.6.3/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionRangeResolver.java] and [DefaultModelResolver.java|https://github.com/apache/maven/blob/maven-3.6.3/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultModelResolver.java] (I use maven 3.6.3) but those resolve module seems directly take the highest version instead of caching all previous versions' pom. Sorry if I am not familiar with maven code, but I wonder if maven will cache all pom files that exists metadata.xml if it is not the versionRangeResolver's issue? > Version range resolution downloads all poms, not just the highest version > - > > Key: MNG-7049 > URL: https://issues.apache.org/jira/browse/MNG-7049 > Project: Maven > Issue Type: Improvement > Components: core >Reporter: Moti Nisenson-Ken >Priority: Major > > When specifying a version range for a dependency, maven will download and try > to resolve all poms in that range which satisfy the range. The usage however > is only to use the highestVersion. This causes two issues: > # Performance - it's downloading numerous poms that aren't needed. > # Fragility - if the version range covers any "bad" poms, then the build > will fail. For example, consider that for a specific version, the parent of a > pom is not present in the repository. This is enough to fail any build with a > version range covering that specific version, as the range resolution stage > will not complete. This is particularly harmful when that version would not > be selected as the highest, anyway. > Recommend to have a system property to control the desired behavior - it > should be possible to short-circuit loading all the versions and to just to > load the highest version. > For another user report of this see: > [https://stackoverflow.com/questions/25047859/restrict-maven-to-not-download-all-poms] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-jlink-plugin] dependabot[bot] opened a new pull request #37: Bump junit-bom from 5.7.0 to 5.7.1
dependabot[bot] opened a new pull request #37: URL: https://github.com/apache/maven-jlink-plugin/pull/37 Bumps [junit-bom](https://github.com/junit-team/junit5) from 5.7.0 to 5.7.1. Release notes Sourced from https://github.com/junit-team/junit5/releases;>junit-bom's releases. JUnit 5.7.1 = Platform 1.7.1 + Jupiter 5.7.1 + Vintage 5.7.1 See http://junit.org/junit5/docs/5.7.1/release-notes/;>Release Notes. Commits https://github.com/junit-team/junit5/commit/b5227801590b3a0758c46a4890e6784f7b04649c;>b522780 Release 5.7.1 https://github.com/junit-team/junit5/commit/f8c6d4ab7919781ea7401eac2caeac55c5d99d59;>f8c6d4a Finalize release notes for 5.7.1 https://github.com/junit-team/junit5/commit/8b3d5aa0885f1e0a38283de71c7431a77f234cde;>8b3d5aa Fix container failure XML reporting (https://github-redirect.dependabot.com/junit-team/junit5/issues/2542;>#2542) https://github.com/junit-team/junit5/commit/b394ef08ad2493494032ef9179cbd050e21a614c;>b394ef0 Use jOOX to test XML reports https://github.com/junit-team/junit5/commit/2b7d5b12c19da96eebd37e11ef90df4ebfc0fbed;>2b7d5b1 Use Java 9 collection factory methods https://github.com/junit-team/junit5/commit/5c42adb2b44b3532f5e8563d19d044597e4d8c4f;>5c42adb Fix typos https://github.com/junit-team/junit5/commit/beddaf450158fd81bf0da9400efb5e1d25eedba9;>beddaf4 Remove unnecessary throws clause https://github.com/junit-team/junit5/commit/85ee2126196c403dab7e05b904a84c05bf58f0db;>85ee212 Simplify assertions https://github.com/junit-team/junit5/commit/c704713e51ddfc3e2a7f811db939702a4350fb65;>c704713 Fix assertion https://github.com/junit-team/junit5/commit/7d6edad19aedae80ce5484dc8677390baac768f8;>7d6edad Convert field to local variable Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.7.0...r5.7.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-162) Restore binary compatibility broken by MRESOLVER-154
[ https://issues.apache.org/jira/browse/MRESOLVER-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279312#comment-17279312 ] Hudson commented on MRESOLVER-162: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #49 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/49/ > Restore binary compatibility broken by MRESOLVER-154 > > > Key: MRESOLVER-162 > URL: https://issues.apache.org/jira/browse/MRESOLVER-162 > Project: Maven Resolver > Issue Type: Task >Reporter: Tamás Cservenák >Assignee: Michael Osipov >Priority: Major > Fix For: 1.7.0 > > > The change how it got implemented broke binary compatibility. > But not only that, it rendered "resolver demo snippets" completely broken > (but see MRESOLVER-161 as well). > For start, let's make "demos" work. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MRESOLVER-154) Move SyncContextFactory interface to SPI module
[ https://issues.apache.org/jira/browse/MRESOLVER-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279313#comment-17279313 ] Hudson commented on MRESOLVER-154: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #49 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/49/ > Move SyncContextFactory interface to SPI module > --- > > Key: MRESOLVER-154 > URL: https://issues.apache.org/jira/browse/MRESOLVER-154 > Project: Maven Resolver > Issue Type: Task >Reporter: Tamás Cservenák >Assignee: Michael Osipov >Priority: Major > Fix For: 1.7.0 > > > Move SyncContextFactory iface to SPI module -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MRESOLVER-156) Active dependency management for Google Guice/Guava
[ https://issues.apache.org/jira/browse/MRESOLVER-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279311#comment-17279311 ] Hudson commented on MRESOLVER-156: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #49 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/49/ > Active dependency management for Google Guice/Guava > --- > > Key: MRESOLVER-156 > URL: https://issues.apache.org/jira/browse/MRESOLVER-156 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Boris Unckel >Assignee: Michael Osipov >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > > The current pom includes com.google.inject:guice with the default transitive > dependency of com.google.guava:guava. Guava has declared several > dependencies, which are not needed at runtime. Onyl > com.google.guava:failureaccess is needed. > The proposal is first to add com.google.guava:guava to the excludes of guice. > Second guava and failureaccess shall be added as direct dependencies. > This has two advantages: Downstream projects only get the needed dependencies > and the version of guava can be independently set. > The runtime dependencies for Guava are explained in the last section of the > [README|https://github.com/google/guava/tree/v30.1] "Important Warnings" #3 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MRESOLVER-160) Deprecate ServiceLocator
[
https://issues.apache.org/jira/browse/MRESOLVER-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279314#comment-17279314
]
Hudson commented on MRESOLVER-160:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #49
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/49/
> Deprecate ServiceLocator
>
>
> Key: MRESOLVER-160
> URL: https://issues.apache.org/jira/browse/MRESOLVER-160
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 1.7.0
>
>
> As prequel to MRESOLVER-157 we need to deprecate (to warn users of) the
> {{ServiceLocator}} in Maven Resolver. This change may go out in some upcoming
> release, as it is not breaking change, unlike MRESOLVER-157 will be.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-pdf-plugin] slachiewicz closed pull request #3: [MPDF-92] Require Java 7 at runtime
slachiewicz closed pull request #3: URL: https://github.com/apache/maven-pdf-plugin/pull/3 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (SUREFIRE-1885) Maven is not running any tests called using testng suitexml files in POM.xml
[ https://issues.apache.org/jira/browse/SUREFIRE-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1885: --- Description: I have seen this issue many times and always it was a user error because the file is in wrong place on the file system. This issue improves sanity check in the plugin and eagerly has to crash the plugin while the file does not exist and explain the root cause on the console. https://sqa.stackexchange.com/questions/45946/maven-is-not-running-any-tests-called-using-testng-suitexml-files-in-pom-xml/46714 was: I have seen this issue many times and always it was a user error because the file is in wrong place on the file system. This issue improves sanity check in the plugin and eagerly has to crash the plugin while the file does not exist and explain the root caus eon the console. https://sqa.stackexchange.com/questions/45946/maven-is-not-running-any-tests-called-using-testng-suitexml-files-in-pom-xml/46714 > Maven is not running any tests called using testng suitexml files in POM.xml > > > Key: SUREFIRE-1885 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1885 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG > support >Reporter: Tibor Digana >Priority: Major > Fix For: 3.0.0-M6 > > > I have seen this issue many times and always it was a user error because the > file is in wrong place on the file system. This issue improves sanity check > in the plugin and eagerly has to crash the plugin while the file does not > exist and explain the root cause on the console. > https://sqa.stackexchange.com/questions/45946/maven-is-not-running-any-tests-called-using-testng-suitexml-files-in-pom-xml/46714 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SUREFIRE-1885) Maven is not running any tests called using testng suitexml files in POM.xml
Tibor Digana created SUREFIRE-1885: -- Summary: Maven is not running any tests called using testng suitexml files in POM.xml Key: SUREFIRE-1885 URL: https://issues.apache.org/jira/browse/SUREFIRE-1885 Project: Maven Surefire Issue Type: Improvement Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG support Reporter: Tibor Digana Fix For: 3.0.0-M6 I have seen this issue many times and always it was a user error because the file is in wrong place on the file system. This issue improves sanity check in the plugin and eagerly has to crash the plugin while the file does not exist and explain the root caus eon the console. https://sqa.stackexchange.com/questions/45946/maven-is-not-running-any-tests-called-using-testng-suitexml-files-in-pom-xml/46714 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JXR-150) AbstractJxrReport.java uses or overrides a deprecated API.
[ https://issues.apache.org/jira/browse/JXR-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated JXR-150: - Labels: up-for-grabs (was: ) > AbstractJxrReport.java uses or overrides a deprecated API. > -- > > Key: JXR-150 > URL: https://issues.apache.org/jira/browse/JXR-150 > Project: Maven JXR > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > Labels: up-for-grabs > > [INFO] > /home/elharo/maven-jxr/maven-jxr-plugin/src/main/java/org/apache/maven/plugin/jxr/AbstractJxrReport.java: > > /home/elharo/maven-jxr/maven-jxr-plugin/src/main/java/org/apache/maven/plugin/jxr/AbstractJxrReport.java > uses or overrides a deprecated API. > [INFO] > /home/elharo/maven-jxr/maven-jxr-plugin/src/main/java/org/apache/maven/plugin/jxr/AbstractJxrReport.java: > Recompile with -Xlint:deprecation for details. > [INFO] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JXR-155) Unknown packaging waring for type bundle
[ https://issues.apache.org/jira/browse/JXR-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated JXR-155: - Affects Version/s: (was: 3.0.0) > Unknown packaging waring for type bundle > > > Key: JXR-155 > URL: https://issues.apache.org/jira/browse/JXR-155 > Project: Maven JXR > Issue Type: Bug >Reporter: Alexander Gängel >Priority: Major > > I have a project importing jackson-bom > > com.fasterxml.jackson > jackson-bom > 2.11.1 > pom > import > > this leads warnings when generation a maven site > [WARNING] Unable to create Maven project for > com.fasterxml.jackson.module:jackson-module-scala_2.13:jar:2.11.1 from > repository. > org.apache.maven.project.ProjectBuildingException: Some problems were > encountered while processing the POMs: > [ERROR] Unknown packaging: bundle @ line 6, column 16 > Is it possible to add the type bundle or configure the plugin to allow this > type > Regards > Alex > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (JXR-155) Unknown packaging waring for type bundle
[ https://issues.apache.org/jira/browse/JXR-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed JXR-155. Resolution: Invalid > Unknown packaging waring for type bundle > > > Key: JXR-155 > URL: https://issues.apache.org/jira/browse/JXR-155 > Project: Maven JXR > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Alexander Gängel >Priority: Major > > I have a project importing jackson-bom > > com.fasterxml.jackson > jackson-bom > 2.11.1 > pom > import > > this leads warnings when generation a maven site > [WARNING] Unable to create Maven project for > com.fasterxml.jackson.module:jackson-module-scala_2.13:jar:2.11.1 from > repository. > org.apache.maven.project.ProjectBuildingException: Some problems were > encountered while processing the POMs: > [ERROR] Unknown packaging: bundle @ line 6, column 16 > Is it possible to add the type bundle or configure the plugin to allow this > type > Regards > Alex > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JXR-155) Unknown packaging waring for type bundle
[ https://issues.apache.org/jira/browse/JXR-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279211#comment-17279211 ] Sylwester Lachiewicz commented on JXR-155: -- It's related to Maven Project Info Reports Plugin - please update to the latest (3.1.1) version. > Unknown packaging waring for type bundle > > > Key: JXR-155 > URL: https://issues.apache.org/jira/browse/JXR-155 > Project: Maven JXR > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Alexander Gängel >Priority: Major > > I have a project importing jackson-bom > > com.fasterxml.jackson > jackson-bom > 2.11.1 > pom > import > > this leads warnings when generation a maven site > [WARNING] Unable to create Maven project for > com.fasterxml.jackson.module:jackson-module-scala_2.13:jar:2.11.1 from > repository. > org.apache.maven.project.ProjectBuildingException: Some problems were > encountered while processing the POMs: > [ERROR] Unknown packaging: bundle @ line 6, column 16 > Is it possible to add the type bundle or configure the plugin to allow this > type > Regards > Alex > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MASFRES-33) Issues with node and node_modules directories created by frontend-maven-plugin included in source-release
[ https://issues.apache.org/jira/browse/MASFRES-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MASFRES-33. --- Resolution: Not A Bug > Issues with node and node_modules directories created by > frontend-maven-plugin included in source-release > - > > Key: MASFRES-33 > URL: https://issues.apache.org/jira/browse/MASFRES-33 > Project: Apache Maven Resource Bundles > Issue Type: Improvement >Reporter: Serge Huber >Priority: Major > > Hello, > I'm using the frontend-maven-plugin in my project (Apache Unomi) and during > the build process it generates a node/ and node_modules/ directory during the > Maven build process and then when generating the source-release assembly it > includes these directories. > I've tried to move the directories to the target/ directory but this makes > the build fail. > You can find the sub project here: > https://github.com/apache/unomi/tree/master/extensions/web-tracker/javascript > Should the descriptor have a "NodeJS" configuration in a similar way that it > is done for the IDE files ? > Or is it allowed to customize the descriptor at a project level (an option I > would prefer to avoid) > Thanks & regards, > Serge... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MASFRES-33) Issues with node and node_modules directories created by frontend-maven-plugin included in source-release
[ https://issues.apache.org/jira/browse/MASFRES-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279208#comment-17279208 ] Sylwester Lachiewicz commented on MASFRES-33: - Please ask questions on Maven's user list > Issues with node and node_modules directories created by > frontend-maven-plugin included in source-release > - > > Key: MASFRES-33 > URL: https://issues.apache.org/jira/browse/MASFRES-33 > Project: Apache Maven Resource Bundles > Issue Type: Improvement >Reporter: Serge Huber >Priority: Major > > Hello, > I'm using the frontend-maven-plugin in my project (Apache Unomi) and during > the build process it generates a node/ and node_modules/ directory during the > Maven build process and then when generating the source-release assembly it > includes these directories. > I've tried to move the directories to the target/ directory but this makes > the build fail. > You can find the sub project here: > https://github.com/apache/unomi/tree/master/extensions/web-tracker/javascript > Should the descriptor have a "NodeJS" configuration in a similar way that it > is done for the IDE files ? > Or is it allowed to customize the descriptor at a project level (an option I > would prefer to avoid) > Thanks & regards, > Serge... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MASFRES-41) Exception in thread "main" java.lang.NoSuchMethodError: com.google.common.base.Preconditions.checkArgument(ZLjava/lang/String;Ljava/lang/Object;)V
[ https://issues.apache.org/jira/browse/MASFRES-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MASFRES-41: Component/s: (was: apache-jar-resource-bundle) > Exception in thread "main" java.lang.NoSuchMethodError: > com.google.common.base.Preconditions.checkArgument(ZLjava/lang/String;Ljava/lang/Object;)V > -- > > Key: MASFRES-41 > URL: https://issues.apache.org/jira/browse/MASFRES-41 > Project: Apache Maven Resource Bundles > Issue Type: Bug > Environment: ubunut 18 >Reporter: ahmed rabie >Priority: Major > Attachments: Untitled.png > > > I have spring boot project and once i run command clean pacakge on > win vm works fine but in ubuntu vm not working fine . > you can find the attahment file all mvn repo that i have > error message > Exception in thread "main" java.lang.NoSuchMethodError: > com.google.common.base.Preconditions.checkArgument(ZLjava/lang/String;Ljava/lang/Object;)V > at com.google.inject.Key.ensureRetainedAtRuntime(Key.java:341) > at com.google.inject.Key.strategyFor(Key.java:335) > at com.google.inject.Key.get(Key.java:219) > at org.eclipse.sisu.wire.ParameterKeys.(ParameterKeys.java:28) > at > org.eclipse.sisu.wire.DependencyAnalyzer.(DependencyAnalyzer.java:93) > at org.eclipse.sisu.wire.ElementAnalyzer.(ElementAnalyzer.java:104) > at org.eclipse.sisu.wire.WireModule.configure(WireModule.java:74) > at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:344) > at com.google.inject.spi.Elements.getElements(Elements.java:103) > at > com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:137) > at > com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103) > at com.google.inject.Guice.createInjector(Guice.java:87) > at com.google.inject.Guice.createInjector(Guice.java:69) > at com.google.inject.Guice.createInjector(Guice.java:59) > at > org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481) > at > org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:206) > at org.apache.maven.cli.MavenCli.container(MavenCli.java:635) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:281) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MASFRES-41) Exception in thread "main" java.lang.NoSuchMethodError: com.google.common.base.Preconditions.checkArgument(ZLjava/lang/String;Ljava/lang/Object;)V
[ https://issues.apache.org/jira/browse/MASFRES-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279206#comment-17279206 ] Sylwester Lachiewicz commented on MASFRES-41: - highly depends on what you have in the maven project configuration - not enough information to diagnose the issue. Please attach a sample project to reproduce or ask on Maven's users mailing list > Exception in thread "main" java.lang.NoSuchMethodError: > com.google.common.base.Preconditions.checkArgument(ZLjava/lang/String;Ljava/lang/Object;)V > -- > > Key: MASFRES-41 > URL: https://issues.apache.org/jira/browse/MASFRES-41 > Project: Apache Maven Resource Bundles > Issue Type: Bug > Components: apache-jar-resource-bundle > Environment: ubunut 18 >Reporter: ahmed rabie >Priority: Major > Attachments: Untitled.png > > > I have spring boot project and once i run command clean pacakge on > win vm works fine but in ubuntu vm not working fine . > you can find the attahment file all mvn repo that i have > error message > Exception in thread "main" java.lang.NoSuchMethodError: > com.google.common.base.Preconditions.checkArgument(ZLjava/lang/String;Ljava/lang/Object;)V > at com.google.inject.Key.ensureRetainedAtRuntime(Key.java:341) > at com.google.inject.Key.strategyFor(Key.java:335) > at com.google.inject.Key.get(Key.java:219) > at org.eclipse.sisu.wire.ParameterKeys.(ParameterKeys.java:28) > at > org.eclipse.sisu.wire.DependencyAnalyzer.(DependencyAnalyzer.java:93) > at org.eclipse.sisu.wire.ElementAnalyzer.(ElementAnalyzer.java:104) > at org.eclipse.sisu.wire.WireModule.configure(WireModule.java:74) > at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:344) > at com.google.inject.spi.Elements.getElements(Elements.java:103) > at > com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:137) > at > com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103) > at com.google.inject.Guice.createInjector(Guice.java:87) > at com.google.inject.Guice.createInjector(Guice.java:69) > at com.google.inject.Guice.createInjector(Guice.java:59) > at > org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481) > at > org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:206) > at org.apache.maven.cli.MavenCli.container(MavenCli.java:635) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:281) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MASFRES-41) Exception in thread "main" java.lang.NoSuchMethodError: com.google.common.base.Preconditions.checkArgument(ZLjava/lang/String;Ljava/lang/Object;)V
[ https://issues.apache.org/jira/browse/MASFRES-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MASFRES-41. --- Resolution: Incomplete > Exception in thread "main" java.lang.NoSuchMethodError: > com.google.common.base.Preconditions.checkArgument(ZLjava/lang/String;Ljava/lang/Object;)V > -- > > Key: MASFRES-41 > URL: https://issues.apache.org/jira/browse/MASFRES-41 > Project: Apache Maven Resource Bundles > Issue Type: Bug > Environment: ubunut 18 >Reporter: ahmed rabie >Priority: Major > Attachments: Untitled.png > > > I have spring boot project and once i run command clean pacakge on > win vm works fine but in ubuntu vm not working fine . > you can find the attahment file all mvn repo that i have > error message > Exception in thread "main" java.lang.NoSuchMethodError: > com.google.common.base.Preconditions.checkArgument(ZLjava/lang/String;Ljava/lang/Object;)V > at com.google.inject.Key.ensureRetainedAtRuntime(Key.java:341) > at com.google.inject.Key.strategyFor(Key.java:335) > at com.google.inject.Key.get(Key.java:219) > at org.eclipse.sisu.wire.ParameterKeys.(ParameterKeys.java:28) > at > org.eclipse.sisu.wire.DependencyAnalyzer.(DependencyAnalyzer.java:93) > at org.eclipse.sisu.wire.ElementAnalyzer.(ElementAnalyzer.java:104) > at org.eclipse.sisu.wire.WireModule.configure(WireModule.java:74) > at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:344) > at com.google.inject.spi.Elements.getElements(Elements.java:103) > at > com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:137) > at > com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103) > at com.google.inject.Guice.createInjector(Guice.java:87) > at com.google.inject.Guice.createInjector(Guice.java:69) > at com.google.inject.Guice.createInjector(Guice.java:59) > at > org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481) > at > org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:206) > at org.apache.maven.cli.MavenCli.container(MavenCli.java:635) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:281) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MASFRES-42) Make maven to parallel job when installing dependencies
[ https://issues.apache.org/jira/browse/MASFRES-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MASFRES-42. --- Resolution: Incomplete > Make maven to parallel job when installing dependencies > --- > > Key: MASFRES-42 > URL: https://issues.apache.org/jira/browse/MASFRES-42 > Project: Apache Maven Resource Bundles > Issue Type: Improvement >Reporter: David Alen >Priority: Trivial > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MASFRES-43) Can't install a project with JavaSE-15
[ https://issues.apache.org/jira/browse/MASFRES-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279205#comment-17279205 ] Sylwester Lachiewicz commented on MASFRES-43: - Thank you for attaching a detailed debug log. Based on stack trace there I would recommend asking org.eclipse.tycho:tycho-maven-plugin developers https://projects.eclipse.org/projects/technology.tycho > Can't install a project with JavaSE-15 > -- > > Key: MASFRES-43 > URL: https://issues.apache.org/jira/browse/MASFRES-43 > Project: Apache Maven Resource Bundles > Issue Type: Bug > Environment: *OS :* > LSB Version: > core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch > Distributor ID: Ubuntu > Description: Ubuntu 18.04.5 LTS > Release: 18.04 > Codename: bionic > *IDE :* > Eclipse IDE for Java Developers (includes Incubating components) > Version: 2020-12 (4.18.0) > Build id: 20201210-1552 > *Maven :* > Apache Maven 3.6.0 > Maven home: /usr/share/maven > Java version: 11.0.9.1, vendor: Ubuntu, runtime: > /usr/lib/jvm/java-11-openjdk-amd64 > Default locale: fr_FR, platform encoding: UTF-8 > OS name: "linux", version: "5.4.0-64-generic", arch: "amd64", family: "unix" > *Java version :* > openjdk version "11.0.9.1" 2020-11-04 > OpenJDK Runtime Environment (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04) > OpenJDK 64-Bit Server VM (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04, mixed mode, > sharing) >Reporter: Gruz Zyh >Priority: Major > Attachments: debug.log > > > Java SE-15 seems to be incompatible with the maven I use. > *Context : i was testing this tutorial > [https://devstory.net/10137/creer-un-projet-java-osgi-avec-maven-et-tycho]* > * i generated 1 plug in project with Osgi (kind of "hello world") > (SimpleOSGi) > * i generated 1 simple project maven (SimpleMaven) > * i generated 1 project parent (MavenParent) > * then i chandes all projects as Maven Projects to have SimpleMaven and > Simple OSGi children of MavenParent > * i made "Run as..." / maven install and I have an error > I found this page : > [https://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException] > So I've used the command to generate logs (see attached) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MASFRES-43) Can't install a project with JavaSE-15
[ https://issues.apache.org/jira/browse/MASFRES-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MASFRES-43. --- Resolution: Invalid > Can't install a project with JavaSE-15 > -- > > Key: MASFRES-43 > URL: https://issues.apache.org/jira/browse/MASFRES-43 > Project: Apache Maven Resource Bundles > Issue Type: Bug > Environment: *OS :* > LSB Version: > core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch > Distributor ID: Ubuntu > Description: Ubuntu 18.04.5 LTS > Release: 18.04 > Codename: bionic > *IDE :* > Eclipse IDE for Java Developers (includes Incubating components) > Version: 2020-12 (4.18.0) > Build id: 20201210-1552 > *Maven :* > Apache Maven 3.6.0 > Maven home: /usr/share/maven > Java version: 11.0.9.1, vendor: Ubuntu, runtime: > /usr/lib/jvm/java-11-openjdk-amd64 > Default locale: fr_FR, platform encoding: UTF-8 > OS name: "linux", version: "5.4.0-64-generic", arch: "amd64", family: "unix" > *Java version :* > openjdk version "11.0.9.1" 2020-11-04 > OpenJDK Runtime Environment (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04) > OpenJDK 64-Bit Server VM (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04, mixed mode, > sharing) >Reporter: Gruz Zyh >Priority: Major > Attachments: debug.log > > > Java SE-15 seems to be incompatible with the maven I use. > *Context : i was testing this tutorial > [https://devstory.net/10137/creer-un-projet-java-osgi-avec-maven-et-tycho]* > * i generated 1 plug in project with Osgi (kind of "hello world") > (SimpleOSGi) > * i generated 1 simple project maven (SimpleMaven) > * i generated 1 project parent (MavenParent) > * then i chandes all projects as Maven Projects to have SimpleMaven and > Simple OSGi children of MavenParent > * i made "Run as..." / maven install and I have an error > I found this page : > [https://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException] > So I've used the command to generate logs (see attached) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-surefire] Tibor17 commented on pull request #333: Add failOnFlakeCount option
Tibor17 commented on pull request #333: URL: https://github.com/apache/maven-surefire/pull/333#issuecomment-773634176 @oehme @eolivelli One more thing I have noticed which could be made better is to improve the condition in method `warnIfIllegalFailOnFlakeCount()` because this should fire an exception in a condition with setting `rerunFailingTestsCount`. The documentation of rerun should mention a new config param. This was also forgotten. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-surefire] Tibor17 commented on pull request #333: Add failOnFlakeCount option
Tibor17 commented on pull request #333: URL: https://github.com/apache/maven-surefire/pull/333#issuecomment-773630782 @oehme @eolivelli Thx for contributing! 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (SUREFIRE-1878) Add failOnFlakeCount option
[ https://issues.apache.org/jira/browse/SUREFIRE-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1878. -- Resolution: Fixed https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=75239c925dc3686072c755267b375665d905ccb0 > Add failOnFlakeCount option > --- > > Key: SUREFIRE-1878 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1878 > Project: Maven Surefire > Issue Type: New Feature > Components: JUnit 5.x support, Maven Surefire Plugin >Reporter: Stefan Oehme >Assignee: Tibor Digana >Priority: Major > Labels: junit5 > Fix For: 3.0.0-M6 > > > The Surefire plugin currently covers two use cases with its > `rerunFailingTestCount` option: > 1. rerunFailingTestCount=0: The build will fail immediately, but I don't know > if it was a real failure or a flake. This option is best for healthy code > bases with very little or no flakiness. > 2. rerunFailingTestCount>0: I will know when a test is flaky, but the build > will be successful, so there is no pressure to fix the flakes. This helps > when the situation is really bad and I just want to get some green build > again to boost team morale :) > I'd like to support a third use case: > 3. rerunFailingTestCount>0 and a new option failOnFlakeCount > 0: The build > will fail (so there is actually pressure to deal with flakiness) and I can > tell the difference between real failures and flakes. I think this would be > the best option for projects with a medium amount of flaky tests and a team > that wants to take care of them. > Edit: To clarify, this is about failing the whole test set when there is > flakiness, not individual tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SUREFIRE-1878) Add failOnFlakeCount option
[ https://issues.apache.org/jira/browse/SUREFIRE-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1878: --- Component/s: JUnit 5.x support > Add failOnFlakeCount option > --- > > Key: SUREFIRE-1878 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1878 > Project: Maven Surefire > Issue Type: New Feature > Components: JUnit 5.x support, Maven Surefire Plugin >Reporter: Stefan Oehme >Assignee: Tibor Digana >Priority: Major > Labels: junit5 > Fix For: 3.0.0-M6 > > > The Surefire plugin currently covers two use cases with its > `rerunFailingTestCount` option: > 1. rerunFailingTestCount=0: The build will fail immediately, but I don't know > if it was a real failure or a flake. This option is best for healthy code > bases with very little or no flakiness. > 2. rerunFailingTestCount>0: I will know when a test is flaky, but the build > will be successful, so there is no pressure to fix the flakes. This helps > when the situation is really bad and I just want to get some green build > again to boost team morale :) > I'd like to support a third use case: > 3. rerunFailingTestCount>0 and a new option failOnFlakeCount > 0: The build > will fail (so there is actually pressure to deal with flakiness) and I can > tell the difference between real failures and flakes. I think this would be > the best option for projects with a medium amount of flaky tests and a team > that wants to take care of them. > Edit: To clarify, this is about failing the whole test set when there is > flakiness, not individual tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SUREFIRE-1878) Add failOnFlakeCount option
[ https://issues.apache.org/jira/browse/SUREFIRE-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1878: --- Labels: junit5 (was: ) > Add failOnFlakeCount option > --- > > Key: SUREFIRE-1878 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1878 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Stefan Oehme >Assignee: Tibor Digana >Priority: Major > Labels: junit5 > Fix For: 3.0.0-M6 > > > The Surefire plugin currently covers two use cases with its > `rerunFailingTestCount` option: > 1. rerunFailingTestCount=0: The build will fail immediately, but I don't know > if it was a real failure or a flake. This option is best for healthy code > bases with very little or no flakiness. > 2. rerunFailingTestCount>0: I will know when a test is flaky, but the build > will be successful, so there is no pressure to fix the flakes. This helps > when the situation is really bad and I just want to get some green build > again to boost team morale :) > I'd like to support a third use case: > 3. rerunFailingTestCount>0 and a new option failOnFlakeCount > 0: The build > will fail (so there is actually pressure to deal with flakiness) and I can > tell the difference between real failures and flakes. I think this would be > the best option for projects with a medium amount of flaky tests and a team > that wants to take care of them. > Edit: To clarify, this is about failing the whole test set when there is > flakiness, not individual tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-surefire] Tibor17 merged pull request #333: Add failOnFlakeCount option
Tibor17 merged pull request #333: URL: https://github.com/apache/maven-surefire/pull/333 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SUREFIRE-1812) Skipped tests (by annotation @EnabledIfEnvironmentVariable on the test class) are not reported
[
https://issues.apache.org/jira/browse/SUREFIRE-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279194#comment-17279194
]
Tibor Digana commented on SUREFIRE-1812:
[~jondruse]
I have used your project and I confirm that the bug presents in M5. The M3
works fine. I guess the issue points to the code in Provider. I do not have
time fix it and therefore I marked this issue with label {{junit5}} and placed
the issue to the Backlog. So we will have a look but I have to continue with
the plan in M6 and then I will continue with these issues.
> Skipped tests (by annotation @EnabledIfEnvironmentVariable on the test class)
> are not reported
> --
>
> Key: SUREFIRE-1812
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1812
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support, Maven Surefire Plugin
>Affects Versions: 3.0.0-M4, 3.0.0-M5
>Reporter: Jiri Ondrusek
>Priority: Major
> Labels: junit5
> Fix For: Backlog
>
>
> I'm upgrading surefire plugin from 2.22.2 and there is a different behavior
> started from 3.0.0-M4.
> When the test class is ignored by using @EnabledIfEnvironmentVariable(...),
> final report shows bad information: (3.0.0.-M4, M5, master)
> {quote}[INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> {quote}
> The same test executed with 3.0.0-M3 shows:
> {quote}[INFO] Results:
> [INFO]
> [WARNING] Tests run: 1, Failures: 0, Errors: 0, Skipped: 1
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-enforcer] elharo commented on a change in pull request #86: [MENFORCER-376] Add excludes/includes functionality to RequireJavaVendor rule
elharo commented on a change in pull request #86: URL: https://github.com/apache/maven-enforcer/pull/86#discussion_r570550213 ## File path: enforcer-rules/src/site/apt/requireJavaVendor.apt.vm ## @@ -53,7 +56,13 @@ Require Java Vendor - AdoptOpenJDK + +Pivotal Review comment: are these the actual vendor names we would see? 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (SUREFIRE-1812) Skipped tests (by annotation @EnabledIfEnvironmentVariable on the test class) are not reported
[
https://issues.apache.org/jira/browse/SUREFIRE-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1812:
---
Fix Version/s: Backlog
> Skipped tests (by annotation @EnabledIfEnvironmentVariable on the test class)
> are not reported
> --
>
> Key: SUREFIRE-1812
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1812
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support, Maven Surefire Plugin
>Affects Versions: 3.0.0-M4, 3.0.0-M5
>Reporter: Jiri Ondrusek
>Priority: Major
> Labels: junit5
> Fix For: Backlog
>
>
> I'm upgrading surefire plugin from 2.22.2 and there is a different behavior
> started from 3.0.0-M4.
> When the test class is ignored by using @EnabledIfEnvironmentVariable(...),
> final report shows bad information: (3.0.0.-M4, M5, master)
> {quote}[INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> {quote}
> The same test executed with 3.0.0-M3 shows:
> {quote}[INFO] Results:
> [INFO]
> [WARNING] Tests run: 1, Failures: 0, Errors: 0, Skipped: 1
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SUREFIRE-1812) Skipped tests (by annotation @EnabledIfEnvironmentVariable on the test class) are not reported
[
https://issues.apache.org/jira/browse/SUREFIRE-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1812:
---
Labels: junit5 (was: )
> Skipped tests (by annotation @EnabledIfEnvironmentVariable on the test class)
> are not reported
> --
>
> Key: SUREFIRE-1812
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1812
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M4, 3.0.0-M5
>Reporter: Jiri Ondrusek
>Priority: Major
> Labels: junit5
>
> I'm upgrading surefire plugin from 2.22.2 and there is a different behavior
> started from 3.0.0-M4.
> When the test class is ignored by using @EnabledIfEnvironmentVariable(...),
> final report shows bad information: (3.0.0.-M4, M5, master)
> {quote}[INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> {quote}
> The same test executed with 3.0.0-M3 shows:
> {quote}[INFO] Results:
> [INFO]
> [WARNING] Tests run: 1, Failures: 0, Errors: 0, Skipped: 1
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SUREFIRE-1812) Skipped tests (by annotation @EnabledIfEnvironmentVariable on the test class) are not reported
[
https://issues.apache.org/jira/browse/SUREFIRE-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1812:
---
Component/s: JUnit 5.x support
> Skipped tests (by annotation @EnabledIfEnvironmentVariable on the test class)
> are not reported
> --
>
> Key: SUREFIRE-1812
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1812
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support, Maven Surefire Plugin
>Affects Versions: 3.0.0-M4, 3.0.0-M5
>Reporter: Jiri Ondrusek
>Priority: Major
> Labels: junit5
>
> I'm upgrading surefire plugin from 2.22.2 and there is a different behavior
> started from 3.0.0-M4.
> When the test class is ignored by using @EnabledIfEnvironmentVariable(...),
> final report shows bad information: (3.0.0.-M4, M5, master)
> {quote}[INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> {quote}
> The same test executed with 3.0.0-M3 shows:
> {quote}[INFO] Results:
> [INFO]
> [WARNING] Tests run: 1, Failures: 0, Errors: 0, Skipped: 1
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SUREFIRE-1603) Pass TestReporter entries to the reports generated by Surefire
[
https://issues.apache.org/jira/browse/SUREFIRE-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1603:
---
Labels: junit5 (was: )
> Pass TestReporter entries to the reports generated by Surefire
> --
>
> Key: SUREFIRE-1603
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1603
> Project: Maven Surefire
> Issue Type: Improvement
> Components: JUnit 5.x support
>Affects Versions: 2.22.1, 3.0.0-M1
>Reporter: John Knight
>Priority: Minor
> Labels: junit5
> Fix For: Backlog
>
>
> Using JUnit 5.31 with the following configuration:
> {noformat}
>
> junit.jupiter.execution.parallel.enabled = true
> junit.jupiter.execution.parallel.config.dynamic.factor = 8
> junit.jupiter.extensions.autodetection.enabled = true
> {noformat}
> and the following tests (for demonstration purposes)
> {noformat}
> public class AppTest
> {
> @Test
> public void mogbyTrue()
> {
> for (int i = 0; i < 5; i++) {
> System.out.println("mogby " + Thread.currentThread().getName());
> }
> assertTrue( false );
> }
> @Test
> public void kermitTrue()
> {
> for (int i = 0; i < 5; i++) {
> System.out.println("kermit " + Thread.currentThread().getName());
> }
> assertTrue( false );
> }{noformat}
> When the tests are executed via mvn test, the messages from both tests appear
> under the output for the first test:
> {noformat}
>
> https://junit.org/junit5/docs/snapshot/user-guide/#running-tests-capturing-output]
> - The output for both tests is still captured within the field
> of the first test, but in a different order:
> {noformat}
> {noformat}
> The original use case for this, is that we have a whole suite of tests
> running via Jenkins, so when tests fail, it's really difficult to see what
> the actual problem is, as the logging is out of sync.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-enforcer] KroArtem commented on pull request #86: [MENFORCER-376] Add excludes/includes functionality to RequireJavaVendor rule
KroArtem commented on pull request #86: URL: https://github.com/apache/maven-enforcer/pull/86#issuecomment-773604746 I may be silly but these changes ARE in the PR right now, still don't get what else should be done. Here is where changes are: https://github.com/apache/maven-enforcer/pull/86/files#diff-b2cfcc9c03ff6b43bade73782c36c14b900b63cb39f57bea78a40a6cf62ae259R33 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-enforcer] elharo commented on pull request #86: [MENFORCER-376] Add excludes/includes functionality to RequireJavaVendor rule
elharo commented on pull request #86: URL: https://github.com/apache/maven-enforcer/pull/86#issuecomment-773597795 Yes, those changes should be in this PR too. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-enforcer] KroArtem commented on pull request #86: [MENFORCER-376] Add excludes/includes functionality to RequireJavaVendor rule
KroArtem commented on pull request #86: URL: https://github.com/apache/maven-enforcer/pull/86#issuecomment-773563518 > The docs that support this feature should be added in this PR as well. @elharo , what exactly do you mean? I've already made corresponding changes in .apt.vm files. Is there something that should be updated too? 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] michael-o commented on pull request #394: [MNG-7020] Remove Maven 2 WagonExcluder backward compat code
michael-o commented on pull request #394: URL: https://github.com/apache/maven/pull/394#issuecomment-773560933 Sure... 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7068) Active dependency management for Google Guice/Guava
[ https://issues.apache.org/jira/browse/MNG-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279053#comment-17279053 ] Hudson commented on MNG-7068: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #98 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/master/98/ > Active dependency management for Google Guice/Guava > --- > > Key: MNG-7068 > URL: https://issues.apache.org/jira/browse/MNG-7068 > Project: Maven > Issue Type: Improvement > Components: Dependencies >Affects Versions: 3.6.3 >Reporter: Boris Unckel >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > The current pom includes com.google.inject:guice with the default transitive > dependency of com.google.guava:guava. Guava has declared several > dependencies, which are not needed at runtime. Only > com.google.guava:failureaccess is needed. > The proposal is first to add com.google.guava:guava to the excludes of guice. > Second guava and failureaccess shall be added as direct dependencies. > This has two advantages: Downstream projects only get the needed dependencies > and the version of guava can be independently set. > The runtime dependencies for Guava are explained in the last section of the > [README|https://github.com/google/guava/tree/v30.1] "Important Warnings" #3 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-7029) Remove super POM release profile
[ https://issues.apache.org/jira/browse/MNG-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279054#comment-17279054 ] Hudson commented on MNG-7029: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #98 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/master/98/ > Remove super POM release profile > > > Key: MNG-7029 > URL: https://issues.apache.org/jira/browse/MNG-7029 > Project: Maven > Issue Type: Task >Affects Versions: 3.6.3 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-1 > > > The release profile has been deprecated for a long time with scheduled for > removal. This ticket formally represents this task. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-enforcer] KroArtem commented on pull request #86: [MENFORCER-376] Add excludes/includes functionality to RequireJavaVendor rule
KroArtem commented on pull request #86: URL: https://github.com/apache/maven-enforcer/pull/86#issuecomment-773508958 @rfscholte , @bmarwell , @elharo , can I kindly ask you to review MR again? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] rfscholte commented on pull request #394: [MNG-7020] Remove Maven 2 WagonExcluder backward compat code
rfscholte commented on pull request #394: URL: https://github.com/apache/maven/pull/394#issuecomment-773483832 IIRC this triggered a new issue. I'll remove my approval and need to have another look at 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] rfscholte commented on pull request #418: [MNG-6114] Elements from the global settings should be ordered before…
rfscholte commented on pull request #418: URL: https://github.com/apache/maven/pull/418#issuecomment-773482877 @cstamas @stephenc as this is a change in the dependency resolution, you should have a look it this too. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] michael-o edited a comment on pull request #418: [MNG-6114] Elements from the global settings should be ordered before…
michael-o edited a comment on pull request #418: URL: https://github.com/apache/maven/pull/418#issuecomment-773440654 @rfscholte Any objections to merge this? 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] michael-o commented on pull request #418: [MNG-6114] Elements from the global settings should be ordered before…
michael-o commented on pull request #418: URL: https://github.com/apache/maven/pull/418#issuecomment-773440654 @rfscholte Any objections to merge this 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] michael-o commented on pull request #394: [MNG-7020] Remove Maven 2 WagonExcluder backward compat code
michael-o commented on pull request #394: URL: https://github.com/apache/maven/pull/394#issuecomment-773440336 @rfscholte Since you approved this, can I go on and merge? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7049) Version range resolution downloads all poms, not just the highest version
[ https://issues.apache.org/jira/browse/MNG-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17278952#comment-17278952 ] Michael Osipov commented on MNG-7049: - [~xiangli1996], likely not, but nothing is wrong here. It is just inefficient. > Version range resolution downloads all poms, not just the highest version > - > > Key: MNG-7049 > URL: https://issues.apache.org/jira/browse/MNG-7049 > Project: Maven > Issue Type: Improvement > Components: core >Reporter: Moti Nisenson-Ken >Priority: Major > > When specifying a version range for a dependency, maven will download and try > to resolve all poms in that range which satisfy the range. The usage however > is only to use the highestVersion. This causes two issues: > # Performance - it's downloading numerous poms that aren't needed. > # Fragility - if the version range covers any "bad" poms, then the build > will fail. For example, consider that for a specific version, the parent of a > pom is not present in the repository. This is enough to fail any build with a > version range covering that specific version, as the range resolution stage > will not complete. This is particularly harmful when that version would not > be selected as the highest, anyway. > Recommend to have a system property to control the desired behavior - it > should be possible to short-circuit loading all the versions and to just to > load the highest version. > For another user report of this see: > [https://stackoverflow.com/questions/25047859/restrict-maven-to-not-download-all-poms] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven] michael-o commented on pull request #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId
michael-o commented on pull request #177: URL: https://github.com/apache/maven/pull/177#issuecomment-773384411 @rmannibucau Please have a look at the update. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MSITE-869) Options to preprocess site sources and resources through Maven filtering
[
https://issues.apache.org/jira/browse/MSITE-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Martin updated MSITE-869:
--
Description:
h1. Use Case
User has source files or resources files where Maven properties like
${project.version} or ${project.name} need to be replaced with their actual
value.
Examples:
* a [REST API specification|https://swagger.io/specification/] in
*src/site/resource/openapi.yaml*
* the title of a Markdown document describing the project (like [Maven Site
Plugin|https://maven.apache.org/plugins/maven-site-plugin/index.html]'s own
documentation)
h1. Workaround
Usually, [it is recommended to add the .vm
suffix|https://stackoverflow.com/questions/7111000/resource-filtering-with-maven-site-plugin]
to the files that need filtering, so that they are processed as a Velocity
template.
But this workaround has several drawbacks:
* [Velocity and Markdown formats are highly
incompatible|https://github.com/apache/maven-archetypes/blob/master/maven-archetype-plugin-site/src/main/resources/archetype-resources/src/site/markdown/markdown-velocity.md.vm]
because of the headings format
* Velocity has 1000 times more features than just filtering, which is great,
but also which can unexpectedly conflict with source files and with resource
files (which may be from external sources, like JS libraries, YAML, etc.)
* .vm files are handled as Velocity templates in most code editors (VSCode,
etc.), which prevents any other advanced features from working (especially on
openapi.yaml, where you can have linting, validation, autosuggest, etc.)
Basically, Velocity templates is a great feature that needs to stay, but it's
overkill for just replacing ${project.version} in a bunch of files.
h1. Specifications
Add options to filter site source files and resource files:
* {{boolean sourceFiltering}} (default: false)
* {{boolean resourceFiltering}} (default: false)
* {{List nonFilteredFileExtensions}} (default: jpg, jpeg, gif, bmp, png)
* {{boolean fileNameFiltering}} (default: false)
Use Maven's filtering component:
{code:java}
@Component(role = MavenResourcesFiltering.class, hint = "default")
private MavenResourcesFiltering mavenResourcesFiltering;
{code}
.vm files don't need to be filtered. There are therefore 3 cases:
* no filtering
* simple filtering (like [Maven Resource
Plugin|https://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html])
* advanced templating
was:
h1. Use Case
User has source files or resources files where Maven properties like
${project.version} or ${project.name} need to be replaced with their actual
value.
Examples:
* a [REST API specification|https://swagger.io/specification/] in
*src/site/resource/openapi.yaml*
* the title of a Markdown document describing the project (like [Maven Site
Plugin|https://maven.apache.org/plugins/maven-site-plugin/index.html]'s own
documentation)
h1. Workaround
Usually, [it is recommended to add the .vm
suffix|https://stackoverflow.com/questions/7111000/resource-filtering-with-maven-site-plugin]
to the files that need filtering, so that they are processed as a Velocity
template.
But this workaround has several drawbacks:
*
[https://github.com/apache/maven-archetypes/blob/master/maven-archetype-plugin-site/src/main/resources/archetype-resources/src/site/markdown/markdown-velocity.md.vm|Velocity
and Markdown formats are highly incompatible] because of the headings format
* Velocity has 1000 times more features than just filtering, which is great,
but also which can conflict with source files when not expected by the doc
writer, and with resource files (which may be from external sources, like JS
libraries, YAML, etc.)
* .vm files are handled as Velocity templates in most code editors (VSCode,
etc.), which prevents any other advanced features from working (especially on
openapi.yaml, where you can have linting, validation, autosuggest, etc.)
Basically, Velocity templates is a great feature that needs to stay, but it's
overkill for just replacing ${project.version} in a bunch of files.
h1. Specifications
Add options to filter site source files and resource files:
* {{boolean sourceFiltering}} (default: false)
* {{boolean resourceFiltering}} (default: false)
* {{List nonFilteredFileExtensions}} (default: jpg, jpeg, gif, bmp, png)
* {{boolean fileNameFiltering}} (default: false)
Use Maven's filtering component:
{code:java}
@Component(role = MavenResourcesFiltering.class, hint = "default")
private MavenResourcesFiltering mavenResourcesFiltering;
{code}
.vm files don't need to be filtered. There are therefore 3 cases:
* no filtering
* simple filtering (like [Maven Resource
Plugin|https://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html])
* advanced templating
> Options to preprocess site sources and resources through Maven filtering
>
[jira] [Updated] (MSITE-869) Options to preprocess site sources and resources through Maven filtering
[
https://issues.apache.org/jira/browse/MSITE-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Martin updated MSITE-869:
--
Description:
h1. Use Case
User has source files or resources files where Maven properties like
${project.version} or ${project.name} need to be replaced with their actual
value.
Examples:
* a [REST API specification|https://swagger.io/specification/] in
*src/site/resource/openapi.yaml*
* the title of a Markdown document describing the project (like [Maven Site
Plugin|https://maven.apache.org/plugins/maven-site-plugin/index.html]'s own
documentation)
h1. Workaround
Usually, [it is recommended to add the .vm
suffix|https://stackoverflow.com/questions/7111000/resource-filtering-with-maven-site-plugin]
to the files that need filtering, so that they are processed as a Velocity
template.
But this workaround has several drawbacks:
*
[https://github.com/apache/maven-archetypes/blob/master/maven-archetype-plugin-site/src/main/resources/archetype-resources/src/site/markdown/markdown-velocity.md.vm|Velocity
and Markdown formats are highly incompatible] because of the headings format
* Velocity has 1000 times more features than just filtering, which is great,
but also which can conflict with source files when not expected by the doc
writer, and with resource files (which may be from external sources, like JS
libraries, YAML, etc.)
* .vm files are handled as Velocity templates in most code editors (VSCode,
etc.), which prevents any other advanced features from working (especially on
openapi.yaml, where you can have linting, validation, autosuggest, etc.)
Basically, Velocity templates is a great feature that needs to stay, but it's
overkill for just replacing ${project.version} in a bunch of files.
h1. Specifications
Add options to filter site source files and resource files:
* {{boolean sourceFiltering}} (default: false)
* {{boolean resourceFiltering}} (default: false)
* {{List nonFilteredFileExtensions}} (default: jpg, jpeg, gif, bmp, png)
* {{boolean fileNameFiltering}} (default: false)
Use Maven's filtering component:
{code:java}
@Component(role = MavenResourcesFiltering.class, hint = "default")
private MavenResourcesFiltering mavenResourcesFiltering;
{code}
.vm files don't need to be filtered. There are therefore 3 cases:
* no filtering
* simple filtering (like [Maven Resource
Plugin|https://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html])
* advanced templating
was:
h1. Use Case
User has source files or resources files where Maven properties like
${project.version} or ${project.name} need to be replaced with their actual
value.
Examples:
* a [REST API specification|https://swagger.io/specification/] in
*src/site/resource/openapi.yaml*
* the title of a Markdown document describing the project (like [Maven Site
Plugin|https://maven.apache.org/plugins/maven-site-plugin/index.html]'s own
documentation)
h1. Workaround
Usually,
[https://stackoverflow.com/questions/7111000/resource-filtering-with-maven-site-plugin|it
is recommended to add the .vm suffix] to the files that need filtering, so
that they are processed as a Velocity template.
But this workaround has several drawbacks:
*
[https://github.com/apache/maven-archetypes/blob/master/maven-archetype-plugin-site/src/main/resources/archetype-resources/src/site/markdown/markdown-velocity.md.vm|Velocity
and Markdown formats are highly incompatible] because of the headings format
* Velocity has 1000 times more features than just filtering, which is great,
but also which can conflict with source files when not expected by the doc
writer, and with resource files (which may be from external sources, like JS
libraries, YAML, etc.)
* .vm files are handled as Velocity templates in most code editors (VSCode,
etc.), which prevents any other advanced features from working (especially on
openapi.yaml, where you can have linting, validation, autosuggest, etc.)
Basically, Velocity templates is a great feature that needs to stay, but it's
overkill for just replacing ${project.version} in a bunch of files.
h1. Specifications
Add options to filter site source files and resource files:
* {{boolean sourceFiltering}} (default: false)
* {{boolean resourceFiltering}} (default: false)
* {{List nonFilteredFileExtensions}} (default: jpg, jpeg, gif, bmp, png)
* {{boolean fileNameFiltering}} (default: false)
Use Maven's filtering component:
{code:java}
@Component(role = MavenResourcesFiltering.class, hint = "default")
private MavenResourcesFiltering mavenResourcesFiltering;
{code}
.vm files don't need to be filtered. There are therefore 3 cases:
* no filtering
* simple filtering (like [Maven Resource
Plugin|https://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html])
* advanced templating
> Options to preprocess site sources and resources through Maven filtering
>
[jira] [Created] (MSITE-869) Options to preprocess site sources and resources through Maven filtering
Bertrand Martin created MSITE-869:
-
Summary: Options to preprocess site sources and resources through
Maven filtering
Key: MSITE-869
URL: https://issues.apache.org/jira/browse/MSITE-869
Project: Maven Site Plugin
Issue Type: Improvement
Components: property interpolation
Reporter: Bertrand Martin
h1. Use Case
User has source files or resources files where Maven properties like
${project.version} or ${project.name} need to be replaced with their actual
value.
Examples:
* a [REST API specification|https://swagger.io/specification/] in
*src/site/resource/openapi.yaml*
* the title of a Markdown document describing the project (like [Maven Site
Plugin|https://maven.apache.org/plugins/maven-site-plugin/index.html]'s own
documentation)
h1. Workaround
Usually,
[https://stackoverflow.com/questions/7111000/resource-filtering-with-maven-site-plugin|it
is recommended to add the .vm suffix] to the files that need filtering, so
that they are processed as a Velocity template.
But this workaround has several drawbacks:
*
[https://github.com/apache/maven-archetypes/blob/master/maven-archetype-plugin-site/src/main/resources/archetype-resources/src/site/markdown/markdown-velocity.md.vm|Velocity
and Markdown formats are highly incompatible] because of the headings format
* Velocity has 1000 times more features than just filtering, which is great,
but also which can conflict with source files when not expected by the doc
writer, and with resource files (which may be from external sources, like JS
libraries, YAML, etc.)
* .vm files are handled as Velocity templates in most code editors (VSCode,
etc.), which prevents any other advanced features from working (especially on
openapi.yaml, where you can have linting, validation, autosuggest, etc.)
Basically, Velocity templates is a great feature that needs to stay, but it's
overkill for just replacing ${project.version} in a bunch of files.
h1. Specifications
Add options to filter site source files and resource files:
* {{boolean sourceFiltering}} (default: false)
* {{boolean resourceFiltering}} (default: false)
* {{List nonFilteredFileExtensions}} (default: jpg, jpeg, gif, bmp, png)
* {{boolean fileNameFiltering}} (default: false)
Use Maven's filtering component:
{code:java}
@Component(role = MavenResourcesFiltering.class, hint = "default")
private MavenResourcesFiltering mavenResourcesFiltering;
{code}
.vm files don't need to be filtered. There are therefore 3 cases:
* no filtering
* simple filtering (like [Maven Resource
Plugin|https://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html])
* advanced templating
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
