[GitHub] [maven-surefire] dependabot[bot] commented on pull request #414: Bump maven-plugin-testing-harness from 2.1 to 3.3.0
dependabot[bot] commented on pull request #414: URL: https://github.com/apache/maven-surefire/pull/414#issuecomment-1000113801 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-surefire] slawekjaranowski closed pull request #414: Bump maven-plugin-testing-harness from 2.1 to 3.3.0
slawekjaranowski closed pull request #414: URL: https://github.com/apache/maven-surefire/pull/414 -- 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 #150: Bump wagon.version from 3.4.3 to 3.5.0
dependabot[bot] opened a new pull request #150: URL: https://github.com/apache/maven-indexer/pull/150 Bumps `wagon.version` from 3.4.3 to 3.5.0. Updates `wagon-provider-api` from 3.4.3 to 3.5.0 Commits https://github.com/apache/maven-wagon/commit/59c3cbbcf53d43689c6bfaeb897a764aa39f7832";>59c3cbb [maven-release-plugin] prepare release wagon-3.5.0 https://github.com/apache/maven-wagon/commit/f23b6a350e1f1e6d90a539429a88ebaeb069df8d";>f23b6a3 [WAGON-618] Remove HTTP file listing with JSoup https://github.com/apache/maven-wagon/commit/bd44727b8c86ee10f783adab3c0d100a8ba1a8ea";>bd44727 Add grant deprecation notice https://github.com/apache/maven-wagon/commit/e869d50c485aca96b331e911827d8251aeeab252";>e869d50 [WAGON-617] Deprecate Wagon WebDAV Provider https://github.com/apache/maven-wagon/commit/dd9b583788a71e8e956f93a5cd8b0dccfeb2d71f";>dd9b583 [WAGON-616] Deprecate Wagon SSH Provider https://github.com/apache/maven-wagon/commit/790f404d5e11dc6da4737e769e7e058a01131aeb";>790f404 [WAGON-615] Deprecate Wagon HTTP Lightweight Provider https://github.com/apache/maven-wagon/commit/5106193db8eb18862d0df3142c31012248b8f1ef";>5106193 [WAGON-614] Deprecate Wagon FTP Provider https://github.com/apache/maven-wagon/commit/fd69ac13e8e7accab521638f968a6908f9b4f0bc";>fd69ac1 Bump version to 3.5.0-SNAPSHOT https://github.com/apache/maven-wagon/commit/87702aebc23843e7daa511d34ee9bca9b1bcd4f6";>87702ae update CI url https://github.com/apache/maven-wagon/commit/ab39b7209f121fd4c4025447efb90d39f0ce89f6";>ab39b72 [maven-release-plugin] prepare for next development iteration See full diff in https://github.com/apache/maven-wagon/compare/wagon-3.4.3...wagon-3.5.0";>compare view Updates `wagon-http` from 3.4.3 to 3.5.0 Updates `wagon-http-lightweight` from 3.4.3 to 3.5.0 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-surefire] dependabot[bot] opened a new pull request #414: Bump maven-plugin-testing-harness from 2.1 to 3.3.0
dependabot[bot] opened a new pull request #414: URL: https://github.com/apache/maven-surefire/pull/414 Bumps [maven-plugin-testing-harness](https://github.com/apache/maven-plugin-testing) from 2.1 to 3.3.0. Commits https://github.com/apache/maven-plugin-testing/commit/7733ae9dfa24bba9f92c4d2335acf35f553fae82";>7733ae9 [maven-release-plugin] prepare release maven-plugin-testing-3.3.0 https://github.com/apache/maven-plugin-testing/commit/2e40b464d160a8b85f8879421ec91388933218a1";>2e40b46 depend on maven 3.2.5 https://github.com/apache/maven-plugin-testing/commit/6bf55326ace4a78c49be055a571a2b6b399e7407";>6bf5532 MPLUGINTESTING-44 version 3.3.0 to signify maven 3.2.4+ requirement https://github.com/apache/maven-plugin-testing/commit/65c28851c702a295cdb0cd4014ad65fd530b9d30";>65c2885 MPLUGINTESTING-44 enforce maven 3.2.4 as minimal supported version https://github.com/apache/maven-plugin-testing/commit/81f2998fa34c54976a5396f39e635e1de9583801";>81f2998 MPLUGINTESTING-44 maven 3.2.4 compatibility https://github.com/apache/maven-plugin-testing/commit/08cbd184768439ab0625ab142be7cd2a2231a6a0";>08cbd18 code format https://github.com/apache/maven-plugin-testing/commit/1023486e887922615512b7e364a469c33f04d40d";>1023486 better default test projects work directory https://github.com/apache/maven-plugin-testing/commit/6164685996f14b58bd7c952a9ba39b738f93e6ce";>6164685 sanitize test work directory name https://github.com/apache/maven-plugin-testing/commit/058d763b55bdde6d158a3cbc98c399c0ad3eeb89";>058d763 enforced use of TestResources as junit https://github.com/Rule";>@Rule https://github.com/apache/maven-plugin-testing/commit/1ac163885e4defc98ee62f4ea8ba8d7879e42382";>1ac1638 Make test Windows proof Additional commits viewable in https://github.com/apache/maven-plugin-testing/compare/maven-plugin-testing-2.1...maven-plugin-testing-3.3.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot 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-jlink-plugin] dependabot[bot] opened a new pull request #85: Bump mockito-core from 4.1.0 to 4.2.0
dependabot[bot] opened a new pull request #85: URL: https://github.com/apache/maven-jlink-plugin/pull/85 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.1.0 to 4.2.0. Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-core's releases. v4.2.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.2.0 2021-12-16 - https://github.com/mockito/mockito/compare/v4.1.0...v4.2.0";>21 commit(s) by Liam Miller-Cushon, Rafael Winterhalter, Tim van der Lippe, dependabot[bot], temp-droid Update ByteBuddy to 1.12.4 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2515";>#2515)](https://github-redirect.dependabot.com/mockito/mockito/pull/2515";>mockito/mockito#2515) Bump kotlinVersion from 1.6.0 to 1.6.10 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2514";>#2514)](https://github-redirect.dependabot.com/mockito/mockito/pull/2514";>mockito/mockito#2514) Add DoNotMock mention to main JavaDoc [(https://github-redirect.dependabot.com/mockito/mockito/issues/2512";>#2512)](https://github-redirect.dependabot.com/mockito/mockito/pull/2512";>mockito/mockito#2512) Replace ExpectedException in MissingInvocationInOrderCheckerTest [(https://github-redirect.dependabot.com/mockito/mockito/issues/2511";>#2511)](https://github-redirect.dependabot.com/mockito/mockito/pull/2511";>mockito/mockito#2511) Update Gradle to version 7.3.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2509";>#2509)](https://github-redirect.dependabot.com/mockito/mockito/pull/2509";>mockito/mockito#2509) Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2497";>#2497: Throw exception on invalid matchers for mockStatic [(https://github-redirect.dependabot.com/mockito/mockito/issues/2506";>#2506)](https://github-redirect.dependabot.com/mockito/mockito/pull/2506";>mockito/mockito#2506) Make sure interface types are initialized before inline mocking to avoid blocking code of static initializers. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2505";>#2505)](https://github-redirect.dependabot.com/mockito/mockito/pull/2505";>mockito/mockito#2505) Bump org.eclipse.osgi from 3.17.0 to 3.17.100 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2504";>#2504)](https://github-redirect.dependabot.com/mockito/mockito/pull/2504";>mockito/mockito#2504) Bump com.diffplug.spotless from 6.0.2 to 6.0.4 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2501";>#2501)](https://github-redirect.dependabot.com/mockito/mockito/pull/2501";>mockito/mockito#2501) Bump com.diffplug.spotless from 6.0.1 to 6.0.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2498";>#2498)](https://github-redirect.dependabot.com/mockito/mockito/pull/2498";>mockito/mockito#2498) ArgumentMatchers not working for Mockito.mockStatic [(https://github-redirect.dependabot.com/mockito/mockito/issues/2497";>#2497)](https://github-redirect.dependabot.com/mockito/mockito/issues/2497";>mockito/mockito#2497) Bump versions.bytebuddy from 1.12.2 to 1.12.3 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2496";>#2496)](https://github-redirect.dependabot.com/mockito/mockito/pull/2496";>mockito/mockito#2496) Bump com.diffplug.spotless from 6.0.0 to 6.0.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2495";>#2495)](https://github-redirect.dependabot.com/mockito/mockito/pull/2495";>mockito/mockito#2495) Remove the recommendation to import ArgumentMatchers methods using Mockito [(https://github-redirect.dependabot.com/mockito/mockito/issues/2494";>#2494)](https://github-redirect.dependabot.com/mockito/mockito/pull/2494";>mockito/mockito#2494) Bump versions.junitJupiter from 5.8.1 to 5.8.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2491";>#2491)](https://github-redirect.dependabot.com/mockito/mockito/pull/2491";>mockito/mockito#2491) Bump junit-platform-launcher from 1.8.1 to 1.8.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2490";>#2490)](https://github-redirect.dependabot.com/mockito/mockito/pull/2490";>mockito/mockito#2490) Fix typo 'DoNoMock' should be 'DoNotMock' [(https://github-redirect.dependabot.com/mockito/mockito/issues/2487";>#2487)](https://github-redirect.dependabot.com/mockito/mockito/pull/2487";>mockito/mockito#2487) Bump biz.aQute.bnd.gradle from 6.0.0 to 6.1.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2486";>#2486)](https://github-redirect.dependabot.com/mockito/mockito/pull/2486";>mockito/mockito#2486) Bump biz.aQute.bnd.builder from 6.0.0 to 6.1.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2485";>#2485)](https://github-redirect.dependabot.com/mockito/mockito/pull/2485";>mockito/mockito#2485) Bump versions.bytebuddy from 1.12.1 to 1.12.2 [(https://github-redirect.dependabot.com/moc
[GitHub] [maven-indexer] dependabot[bot] opened a new pull request #149: Bump checkstyle from 9.1 to 9.2
dependabot[bot] opened a new pull request #149: URL: https://github.com/apache/maven-indexer/pull/149 Bumps [checkstyle](https://github.com/checkstyle/checkstyle) from 9.1 to 9.2. Release notes Sourced from https://github.com/checkstyle/checkstyle/releases";>checkstyle's releases. checkstyle-9.2 https://checkstyle.org/releasenotes.html#Release_9.2";>https://checkstyle.org/releasenotes.html#Release_9.2 Commits https://github.com/checkstyle/checkstyle/commit/1654fc2602651b9d48f7e583c401c118d93c6dd9";>1654fc2 [maven-release-plugin] prepare release checkstyle-9.2 https://github.com/checkstyle/checkstyle/commit/d47afe43cffce1ad37f1e4c6e3212bb688c034cb";>d47afe4 doc: release notes 9.2 https://github.com/checkstyle/checkstyle/commit/bb69e10d39fa6adc67d4ac4873cd362177926a0a";>bb69e10 Issue https://github-redirect.dependabot.com/checkstyle/checkstyle/issues/9412";>#9412: updated example of AST for TokenTypes.CTOR_CALL https://github.com/checkstyle/checkstyle/commit/b0dbb10c4ffe1327d676a87bc6635604baef78df";>b0dbb10 infra: update xwiki-platform commit https://github.com/checkstyle/checkstyle/commit/bd095d753c236159d790a91ec9c7978e21a49210";>bd095d7 Issue https://github-redirect.dependabot.com/checkstyle/checkstyle/issues/10978";>#10978: Record inside interface is parsed as method https://github.com/checkstyle/checkstyle/commit/73c5d4763abb5771fe81e2aa0ac8eb0ae7f0c652";>73c5d47 Issue https://github-redirect.dependabot.com/checkstyle/checkstyle/issues/9450";>#9450: update example of AST for TokenTypes.IDENT https://github.com/checkstyle/checkstyle/commit/4bd9856de41ae74c903bf8468b3355ded0b73a58";>4bd9856 Issue https://github-redirect.dependabot.com/checkstyle/checkstyle/issues/10943";>#10943: Message validation in our Inputs should not have trailing and l... https://github.com/checkstyle/checkstyle/commit/3895bdee4908f0d8790cdc50dd10dcc38f14b0f6";>3895bde Issue https://github-redirect.dependabot.com/checkstyle/checkstyle/issues/9463";>#9463: update example of AST for TokenTypes.LITERAL_BOOLEAN https://github.com/checkstyle/checkstyle/commit/66b7b00bb347b9385fdd4dbadcc72b37dc4fd936";>66b7b00 Issue https://github-redirect.dependabot.com/checkstyle/checkstyle/issues/9464";>#9464: updated example of AST for TokenTypes.LITERAL_BREAK https://github.com/checkstyle/checkstyle/commit/9afeb2bcd0af59045c67dff35ae6de31dab2d961";>9afeb2b config: change escape single quotes policy for crowdin Additional commits viewable in https://github.com/checkstyle/checkstyle/compare/checkstyle-9.1...checkstyle-9.2";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot 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-javadoc-plugin] dependabot[bot] opened a new pull request #114: Bump maven-plugin-plugin from 3.6.1 to 3.6.2
dependabot[bot] opened a new pull request #114: URL: https://github.com/apache/maven-javadoc-plugin/pull/114 Bumps [maven-plugin-plugin](https://github.com/apache/maven-plugin-tools) from 3.6.1 to 3.6.2. Commits https://github.com/apache/maven-plugin-tools/commit/c813ad9883dce7d449b9bf609d32f24669ce4496";>c813ad9 [maven-release-plugin] prepare release maven-plugin-tools-3.6.2 https://github.com/apache/maven-plugin-tools/commit/fefa7ca9cd787add15c9aa9f5885cc3cc200a35d";>fefa7ca [MPLUGIN-381] Upgrade QDox to 2.0.1 https://github.com/apache/maven-plugin-tools/commit/9c7b822d689aa450fe95cc5f8ad4cd5e2159191f";>9c7b822 fix wording https://github.com/apache/maven-plugin-tools/commit/2ee1d603e2a71bcd99d58a5e6a4c4b2d2669d9c4";>2ee1d60 [MPLUGIN-380] Always include thread safety in report https://github.com/apache/maven-plugin-tools/commit/64ec552c1721ed4de7e044ea807b0f32cfaafbb5";>64ec552 [MPLUGIN-379] Report goal does not include threadSafe attribute in generated ... https://github.com/apache/maven-plugin-tools/commit/2b4756dd67138ac85a18499fc39f31767b10fd3e";>2b4756d use shared gh action - v1 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/47";>#47) https://github.com/apache/maven-plugin-tools/commit/d57eaff72823b0ee9b043d369b565f98c07ba4e5";>d57eaff [MPLUGIN-376] Drop legacy dependencies (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/42";>#42) https://github.com/apache/maven-plugin-tools/commit/6d3d92e48534e6da29baf142ad9e5247c01d0d7e";>6d3d92e fix links to CI https://github.com/apache/maven-plugin-tools/commit/73e32d10e5ef6d42d3438fb34f6bb5561bce952c";>73e32d1 [MPLUGIN-377] Upgrade to maven 3.x and avoid using deprecated API (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/37";>#37) https://github.com/apache/maven-plugin-tools/commit/960d1500211b0211528dd34d2c3baa3d44bfcff4";>960d150 Weed out ITs (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/45";>#45) Additional commits viewable in https://github.com/apache/maven-plugin-tools/compare/maven-plugin-tools-3.6.1...maven-plugin-tools-3.6.2";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot 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] [Created] (SUREFIRE-1970) rerunFailingTestsCount option marks some spock tests as false positive
Casey Jones created SUREFIRE-1970:
-
Summary: rerunFailingTestsCount option marks some spock tests as
false positive
Key: SUREFIRE-1970
URL: https://issues.apache.org/jira/browse/SUREFIRE-1970
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 3.0.0-M5, 3.0.0-M4
Reporter: Casey Jones
I have a project which uses [Spock Framework|https://spockframework.org/] for
tests. There is a single test which intentionally fails, no matter how many
times it was ran:
{code:java}
class FalsePositiveTest extends Specification {
def "test"() {
expect:
1 == number
where:
number << [2, 3]
}
} {code}
When test is executed with {{mvn test}} command, the build fails, as expected.
However, when using surefire's
[rerunFailingTestsCount|https://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html]
option, the test in question is executed two times, as expected, but then it
is marked as flaky, and the build is successful:
{code:java}
mvn test -Dsurefire.rerunFailingTestsCount=1
...
Warning: Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Flakes: 1
126[INFO]
127[INFO]
128[INFO] BUILD SUCCESS
129[INFO]
{code}
Please check the links below for a full build log.
This issue happens only when using Spock's data-driven tests with a [where
block|https://spockframework.org/spock/docs/1.0/data_driven_testing.html] and
surefire's {{rerunFailingTestsCount}} option together. It seems like there is
something wrong in the way surefire detects if test has failed or passed.
I asked this [question on
StackOverflow|https://stackoverflow.com/questions/70454980/spock-data-driven-tests-surefire-rerunfailingtestscount-gives-false-positive-t]
and Spock's maintainer suggested to raise an issue in surefire's bugtracker.
Here is a simple github project which reproduces the issue:
[https://github.com/streetturtle/FalsePositiveTest]
Please check build logs of a github action here:
[https://github.com/streetturtle/FalsePositiveTest/runs/4613803891?check_suite_focus=true#step:4:128]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-jar-plugin] dependabot[bot] commented on pull request #21: Bump mavenVersion from 3.1.0 to 3.8.3
dependabot[bot] commented on pull request #21: URL: https://github.com/apache/maven-jar-plugin/pull/21#issuecomment-51657 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-jar-plugin] slachiewicz closed pull request #21: Bump mavenVersion from 3.1.0 to 3.8.3
slachiewicz closed pull request #21: URL: https://github.com/apache/maven-jar-plugin/pull/21 -- 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-jar-plugin] slachiewicz merged pull request #27: Bump maven-archiver from 3.5.0 to 3.5.1
slachiewicz merged pull request #27: URL: https://github.com/apache/maven-jar-plugin/pull/27 -- 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] (WAGON-622) Upgrade Plexus Interactivity to 1.1
[ https://issues.apache.org/jira/browse/WAGON-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-622. Resolution: Fixed Fixed with [c9aa4c51fd256b4a949c658aabbdcc057bcc253e|https://gitbox.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=c9aa4c51fd256b4a949c658aabbdcc057bcc253e]. > Upgrade Plexus Interactivity to 1.1 > --- > > Key: WAGON-622 > URL: https://issues.apache.org/jira/browse/WAGON-622 > Project: Maven Wagon > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.5.1 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (WAGON-623) Upgrade HttpCore to 4.4.15
[ https://issues.apache.org/jira/browse/WAGON-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-623. Resolution: Fixed Fixed with [fd2ae925fab62da455df61d915126cee13a1d31b|https://gitbox.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=fd2ae925fab62da455df61d915126cee13a1d31b]. > Upgrade HttpCore to 4.4.15 > -- > > Key: WAGON-623 > URL: https://issues.apache.org/jira/browse/WAGON-623 > Project: Maven Wagon > Issue Type: Dependency upgrade > Components: wagon-http, wagon-webdav >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.5.1 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (WAGON-621) Upgrade JUnit to 4.13.2
[ https://issues.apache.org/jira/browse/WAGON-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-621. Resolution: Fixed Fixed with [3b5f142b7054962cd28b91cc9f3e2cf94e24f4f8|https://gitbox.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=3b5f142b7054962cd28b91cc9f3e2cf94e24f4f8]. > Upgrade JUnit to 4.13.2 > --- > > Key: WAGON-621 > URL: https://issues.apache.org/jira/browse/WAGON-621 > Project: Maven Wagon > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.5.1 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (WAGON-620) Upgrade SLF4J to 1.7.32
[ https://issues.apache.org/jira/browse/WAGON-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-620. Resolution: Fixed Fixed with [90a952d6ab4ba676128a377aba13f0af88d26896|https://gitbox.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=90a952d6ab4ba676128a377aba13f0af88d26896]. > Upgrade SLF4J to 1.7.32 > --- > > Key: WAGON-620 > URL: https://issues.apache.org/jira/browse/WAGON-620 > Project: Maven Wagon > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.5.1 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (WAGON-619) Remove shading of JSoup
[ https://issues.apache.org/jira/browse/WAGON-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-619. Resolution: Fixed Fixed with [561fe11029c1aa6199d1658259f85c4bca6b0eac|https://gitbox.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=561fe11029c1aa6199d1658259f85c4bca6b0eac]. > Remove shading of JSoup > --- > > Key: WAGON-619 > URL: https://issues.apache.org/jira/browse/WAGON-619 > Project: Maven Wagon > Issue Type: Task > Components: wagon-http >Affects Versions: 3.5.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.5.1 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-enforcer] electrum opened a new pull request #133: [MENFORCER-409] Log at ERROR level when is set
electrum opened a new pull request #133: URL: https://github.com/apache/maven-enforcer/pull/133 Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MENFORCER) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Format the pull request title like `[MENFORCER-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MENFORCER-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (WAGON-623) Upgrade HttpCore to 4.4.15
Michael Osipov created WAGON-623: Summary: Upgrade HttpCore to 4.4.15 Key: WAGON-623 URL: https://issues.apache.org/jira/browse/WAGON-623 Project: Maven Wagon Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.5.1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (WAGON-623) Upgrade HttpCore to 4.4.15
[ https://issues.apache.org/jira/browse/WAGON-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-623: - Component/s: wagon-http wagon-webdav > Upgrade HttpCore to 4.4.15 > -- > > Key: WAGON-623 > URL: https://issues.apache.org/jira/browse/WAGON-623 > Project: Maven Wagon > Issue Type: Dependency upgrade > Components: wagon-http, wagon-webdav >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.5.1 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (WAGON-622) Upgrade Plexus Interactivity to 1.1
Michael Osipov created WAGON-622: Summary: Upgrade Plexus Interactivity to 1.1 Key: WAGON-622 URL: https://issues.apache.org/jira/browse/WAGON-622 Project: Maven Wagon Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.5.1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (WAGON-621) Upgrade JUnit to 4.13.2
Michael Osipov created WAGON-621: Summary: Upgrade JUnit to 4.13.2 Key: WAGON-621 URL: https://issues.apache.org/jira/browse/WAGON-621 Project: Maven Wagon Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.5.1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (WAGON-620) Upgrade SLF4J to 1.7.32
Michael Osipov created WAGON-620: Summary: Upgrade SLF4J to 1.7.32 Key: WAGON-620 URL: https://issues.apache.org/jira/browse/WAGON-620 Project: Maven Wagon Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.5.1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-7046) Revert MNG-5639 and make repo config static only (no ${param} interpolation)
[
https://issues.apache.org/jira/browse/MNG-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-7046:
---
Summary: Revert MNG-5639 and make repo config static only (no ${param}
interpolation) (was: Revert MNG-5639 and make repo config static only (no ${}
interpolation))
> Revert MNG-5639 and make repo config static only (no ${param} interpolation)
>
>
> Key: MNG-7046
> URL: https://issues.apache.org/jira/browse/MNG-7046
> Project: Maven
> Issue Type: Task
> Components: Artifacts and Repositories, Dependencies
>Affects Versions: 3.6.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> As discussed in MNG-5639 repositories should always be known upfront, they
> have to be static to avoid chicken and egg situations, a project should not
> influence settings. It should be the way around.
> In subsequent ticket it will be verified that repo configuration does not
> contain any expression:
> https://github.com/apache/maven/commit/d411c3fa98832e7d86d901fe86ff63ba907cf868#commitcomment-44782281.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MNG-7046) Revert MNG-5639 and make repo config static only (no ${} interpolation)
[
https://issues.apache.org/jira/browse/MNG-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-7046:
---
Summary: Revert MNG-5639 and make repo config static only (no ${}
interpolation) (was: Revert MNG-5639 and make repo config static only)
> Revert MNG-5639 and make repo config static only (no ${} interpolation)
> ---
>
> Key: MNG-7046
> URL: https://issues.apache.org/jira/browse/MNG-7046
> Project: Maven
> Issue Type: Task
> Components: Artifacts and Repositories, Dependencies
>Affects Versions: 3.6.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> As discussed in MNG-5639 repositories should always be known upfront, they
> have to be static to avoid chicken and egg situations, a project should not
> influence settings. It should be the way around.
> In subsequent ticket it will be verified that repo configuration does not
> contain any expression:
> https://github.com/apache/maven/commit/d411c3fa98832e7d86d901fe86ff63ba907cf868#commitcomment-44782281.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (WAGON-619) Remove shading of JSoup
Michael Osipov created WAGON-619: Summary: Remove shading of JSoup Key: WAGON-619 URL: https://issues.apache.org/jira/browse/WAGON-619 Project: Maven Wagon Issue Type: Task Components: wagon-http Affects Versions: 3.5.0 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.5.1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MENFORCER-409) Log at ERROR level when is set
David Phillips created MENFORCER-409:
Summary: Log at ERROR level when is set
Key: MENFORCER-409
URL: https://issues.apache.org/jira/browse/MENFORCER-409
Project: Maven Enforcer Plugin
Issue Type: Bug
Reporter: David Phillips
When {{true}} is set, messages for problems that will fail the
build should be logged at {{ERROR}} level, so that they are easier to find in
the log:
{noformat}
[WARN] Rule 1: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps failed
with message:
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build succeeded in Jenkins: Maven TLP » maven » MNG-6071 #33 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6071/33/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build unstable in Jenkins: Maven TLP » maven » MNG-5868 #40 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5868/40/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6555 #29 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6555/29/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4 See https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build succeeded in Jenkins: Maven TLP » maven » MNG-5868 #51 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5868/51/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6556_MJAR-3.0.0 #12 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556_MJAR-3.0.0/12/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build unstable in Jenkins: Maven TLP » maven » MPOM-215 #19 See https://builds.apache.org/job/maven-box/job/maven/job/MPOM-215/19/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6550 #25 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/25/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build unstable in Jenkins: Maven TLP » maven » MNG-5666 #30 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5666/30/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build failed in Jenkins: Maven TLP » maven » runITsWithJavaEA #52 See https://builds.apache.org/job/maven-box/job/maven/job/runITsWithJavaEA/52/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build unstable in Jenkins: Maven TLP » maven » MNG-5567 #39 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-5567/39/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6551 #28 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6551/28/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build unstable in Jenkins: Maven TLP » maven » slf4j-1.8-modules #20 See https://builds.apache.org/job/maven-box/job/maven/job/slf4j-1.8-modules/20/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6552 #22 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6552/22/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build unstable in Jenkins: Maven TLP » maven » MNG-6548 #7 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6548/7/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build unstable in Jenkins: Maven TLP » maven » MNG-6169/MNG-6554 #21 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6554/21/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build unstable in Jenkins: Maven TLP » maven » EOL #20 See https://builds.apache.org/job/maven-box/job/maven/job/EOL/20/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build succeeded in Jenkins: Maven TLP » maven » archives #10 See https://builds.apache.org/job/maven-box/job/maven/job/archives/10/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build succeeded in Jenkins: Maven TLP » maven » master #303 See https://builds.apache.org/job/maven-box/job/maven/job/master/303/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MNG-6584) Maven version 3.6.0 does not show ReasonPhrase anymore
[ https://issues.apache.org/jira/browse/MNG-6584 ] Herve Boutemy deleted comment on MNG-6584: was (Author: hudson): Build succeeded in Jenkins: Maven TLP » maven » MNG-6695 #9 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6695/9/ > Maven version 3.6.0 does not show ReasonPhrase anymore > -- > > Key: MNG-6584 > URL: https://issues.apache.org/jira/browse/MNG-6584 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Lucas Ludueño >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.6.3 > > > Hi! I noticed that version 3.6.0 does not show the ReasonPhrase anymore (for > example when you run mvn deploy to a custom Maven service). > With version 3.5.0 the ReasonPhrase is shown in a message like: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project mule-module-tooling-service: Failed to deploy artifacts: Could not > transfer artifact > 2b34662a-6937-4581-b954-71ba35a53519:mule-module-tooling-service:jar:mule-plugin:2.1.3 > from/to exchange-repository > (http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven): Failed to > transfer file: > http://maven:8088/2b34662a-6937-4581-b954-71ba35a53519/maven/2b34662a-6937-4581-b954-71ba35a53519/mule-module-tooling-service/2.1.3/mule-module-tooling-service-2.1.3-mule-plugin.jar. > Return code is: 400, ReasonPhrase: my-custom-ReasonPhrase. -> [Help 1] > I am not completely sure if the ReasonPhrase has been removed intentionally. > If the answer is no, can you fix it? If the answer is yes, how can I simulate > the behavior to indicate to someone what was happening? > > Thanks!! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MWRAPPER-46) Simplify use of Maven Wrapper in different environments (basic auth required)
[ https://issues.apache.org/jira/browse/MWRAPPER-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464068#comment-17464068 ] Michael Osipov commented on MWRAPPER-46: The Maven password encryption is moot and gives you a false sense of security. You still must retain a plaintext password for the system. No gain here. [~cstamas] > Simplify use of Maven Wrapper in different environments (basic auth required) > - > > Key: MWRAPPER-46 > URL: https://issues.apache.org/jira/browse/MWRAPPER-46 > Project: Maven Wrapper > Issue Type: Improvement >Affects Versions: 3.1.0 >Reporter: Jimisola Laursen >Priority: Normal > > I'll describe our use-case as I suspect that we might be alone with this one. > This ticket relates to: > # MVNW_REPOURL being insufficient > # user not being able to set MVNW_USERNAME/PASSWORD in plain text due > security > *Prerequisites:* > * _Self-hosted Maven 2 repo that requires basic auth_ (Nexus with proxy for > Maven Central) > * Environments: > ** Local machine: need to use proxy for Internet, can't set > MVNW_USERNAME/PASSWORD in plain text due security > ** Pipeline/Deployment (k8s): need to use proxy for Internet, > MVNW_USERNAME/PASSWORD are set > * We want to be able to specify wrapper and/or Maven version (hence, use > maven-wrapper.properties) > *Use-case:* all downloads, but local and in cluster/cloud, should go via our > self-hosted Maven 2 repo that requires basic auth > *Setup cases:* > # Setting MVNW_REPOURL in both environments causes two problems: > ## local machine: we would have to set MVNW_USER/PASSWORD (can't due to > security risk) > ## k8s: MVNW_REPOURL environment variable, strangely, doesn't override value > in maven-wrapper.properties, but vice versa. Is this really common practise? > Compare with e.g. [Spring Boot's Externalized > Configuration|https://docs.spring.io/spring-boot/docs/1.2.3.RELEASE/reference/html/boot-features-external-config.html]. > So, we would have to either change the base url in the > maven-wrapper.properties in k8s explicitly since we want to keep the version > information for maven-wrapper and Maven. > # Changing the urls to the self-hosted repo in maven-wrapper.properties: > ## local machine: we would have to set MVNW_USER/PASSWORD (can't due to > security risk) > ## k8s: would work since MVNW_USERNAME/PASSWORD are set > # Having maven-wrapper.jar checked in doesn't solve the issue since Maven > itself has to be downloaded as well and basic auth not set. > *Ideas:* > # be able to use [Password > Encryption|https://maven.apache.org/guides/mini/guide-encryption.html] and > have password encrypted in settings.xml or in MVNW_PASSWORD: issue of course > being that Maven Password Encryption is not available during bootstrapping. > # change the behavior of MVNW_REPOURL so that it has the highest priority > and supersedes defaults in mvnw[.cmd] script as well as in > maven-wrapper.properties: at least then we can keep a correct > maven-wrapper.properties (w/ self-hosted Maven repo) and set MVNW_REPOURL to > Maven Central on local machine for bootstrapping. > *Proposed semi-solution:* > * Change priority of MVNW_REPOURL or, for backwards compatibility, add > another environment variable which supersedes all other settings -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-plugin-tools] rmannibucau commented on pull request #58: [MPLUGIN-386] Exclude maven-archiver and maven-jxr from warning
rmannibucau commented on pull request #58: URL: https://github.com/apache/maven-plugin-tools/pull/58#issuecomment-999870917 @michael-o except maven-plugin-api which is intentionally exposed rest of maven sub-artifacts are random and either internals or public API so none can be assumed being provided so this sounds like a lot of false positive to me. What about not warning for all but the plugin api and maybe maven-core? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSITE-878) Upgrade Doxia to 1.11.1 and Doxia Sitetools to 1.11.1
[ https://issues.apache.org/jira/browse/MSITE-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464041#comment-17464041 ] Michael Osipov commented on MSITE-878: -- [~hboutemy], merci! > Upgrade Doxia to 1.11.1 and Doxia Sitetools to 1.11.1 > - > > Key: MSITE-878 > URL: https://issues.apache.org/jira/browse/MSITE-878 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.10.0 > > > h1. Release Notes - Maven Doxia - Version 1.11.1 > h2. Task > * [DOXIA-620] - Deprecate Doxia Logging API in favor of SLF4J > * [DOXIA-621] - Deprecate doxia-module-confluence > * [DOXIA-622] - Deprecate doxia-module-docbook-simple > * [DOXIA-623] - Deprecate doxia-module-fo > * [DOXIA-624] - Deprecate doxia-module-itext > * [DOXIA-625] - Deprecate doxia-module-latex > * [DOXIA-626] - Deprecate doxia-module-rtf > * [DOXIA-627] - Deprecate doxia-module-twiki > * [DOXIA-628] - Deprecate SsiMacro > * [DOXIA-629] - Deprecate SwfMacro > h1. Release Notes - Maven Doxia Sitetools - Version 1.11.1 > h2. Improvement > * [DOXIASITETOOLS-234] - improve documentation on site.xml inheritance vs > interpolation > h2. Task > * [DOXIASITETOOLS-236] - Deprecate Doxia Sitetools Doc Renderer > h2. Dependency upgrade > * [DOXIASITETOOLS-237] - Upgrade Maven Doxia to 1.11.1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MSITE-875) Upgrade Doxia to 1.10 and Doxia Sitetools to 1.10
[ https://issues.apache.org/jira/browse/MSITE-875 ] Herve Boutemy deleted comment on MSITE-875: - was (Author: hudson): Build succeeded in Jenkins: Maven » Maven TLP » maven-site-plugin » MSITE-829 #31 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/MSITE-829/31/ > Upgrade Doxia to 1.10 and Doxia Sitetools to 1.10 > - > > Key: MSITE-875 > URL: https://issues.apache.org/jira/browse/MSITE-875 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.9.1 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.10.0 > > > h1. Release Notes - Maven Doxia - Version 1.10 > h2. Bug > * [DOXIA-542] - Markdown module converts all apostrophes to quotation > marks > * [DOXIA-588] - The Sink.JUSTIFY_XXX has no effect > h2. Improvement > * [DOXIA-521] - Markdown: Allow using the standard "" for code > blocks > * [DOXIA-606] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIA-607] - Add support for XHTML5 keygen element > * [DOXIA-614] - Support obtaining the source reference in a Doxia Parser > * [DOXIA-616] - Markdown: Properly expose the language specified in > fenced code blocks > h2. Task > * [DOXIA-618] - doxia-module-markdown: Reincorporate maven-site-plugin's > Doxia-specific integration tests > h2. Dependency upgrade > * [DOXIA-610] - Update doxia-module-fo to not use log4j > * [DOXIA-615] - Upgrade HttpClient to 4.5.13 > h1. Release Notes - Maven Doxia Sitetools - Version 1.10 > h2. Bug > * [DOXIASITETOOLS-221] - CLIRR can't find previous version > * [DOXIASITETOOLS-227] - Throwing "new ParseException(message)" shows > message with "line [-1]" > h2. Improvement > * [DOXIASITETOOLS-228] - Remove all in default-site-macros.vm and > replace by a space > h2. Dependency upgrade > * [DOXIASITETOOLS-219] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIASITETOOLS-223] - wrong coordinates for jai_core: hyphen should be > underscore > * [DOXIASITETOOLS-226] - Use latest JUnit version 4.13.2 > * [DOXIASITETOOLS-231] - Upgrade Plexus Utils to 3.3.0 > * [DOXIASITETOOLS-232] - Upgrade Plexus Interpolation to 1.26 > * [DOXIASITETOOLS-233] - Upgrade Maven Doxia to 1.10 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MSITE-875) Upgrade Doxia to 1.10 and Doxia Sitetools to 1.10
[ https://issues.apache.org/jira/browse/MSITE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464037#comment-17464037 ] Herve Boutemy commented on MSITE-875: - done in https://github.com/apache/maven-site-plugin/commit/0f59ef6c85b7b17eb15260da1e282ec98b87ba83 > Upgrade Doxia to 1.10 and Doxia Sitetools to 1.10 > - > > Key: MSITE-875 > URL: https://issues.apache.org/jira/browse/MSITE-875 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.9.1 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.10.0 > > > h1. Release Notes - Maven Doxia - Version 1.10 > h2. Bug > * [DOXIA-542] - Markdown module converts all apostrophes to quotation > marks > * [DOXIA-588] - The Sink.JUSTIFY_XXX has no effect > h2. Improvement > * [DOXIA-521] - Markdown: Allow using the standard "" for code > blocks > * [DOXIA-606] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIA-607] - Add support for XHTML5 keygen element > * [DOXIA-614] - Support obtaining the source reference in a Doxia Parser > * [DOXIA-616] - Markdown: Properly expose the language specified in > fenced code blocks > h2. Task > * [DOXIA-618] - doxia-module-markdown: Reincorporate maven-site-plugin's > Doxia-specific integration tests > h2. Dependency upgrade > * [DOXIA-610] - Update doxia-module-fo to not use log4j > * [DOXIA-615] - Upgrade HttpClient to 4.5.13 > h1. Release Notes - Maven Doxia Sitetools - Version 1.10 > h2. Bug > * [DOXIASITETOOLS-221] - CLIRR can't find previous version > * [DOXIASITETOOLS-227] - Throwing "new ParseException(message)" shows > message with "line [-1]" > h2. Improvement > * [DOXIASITETOOLS-228] - Remove all in default-site-macros.vm and > replace by a space > h2. Dependency upgrade > * [DOXIASITETOOLS-219] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIASITETOOLS-223] - wrong coordinates for jai_core: hyphen should be > underscore > * [DOXIASITETOOLS-226] - Use latest JUnit version 4.13.2 > * [DOXIASITETOOLS-231] - Upgrade Plexus Utils to 3.3.0 > * [DOXIASITETOOLS-232] - Upgrade Plexus Interpolation to 1.26 > * [DOXIASITETOOLS-233] - Upgrade Maven Doxia to 1.10 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MSITE-875) Upgrade Doxia to 1.10 and Doxia Sitetools to 1.10
[ https://issues.apache.org/jira/browse/MSITE-875 ] Herve Boutemy deleted comment on MSITE-875: - was (Author: hudson): Build succeeded in Jenkins: Maven » Maven TLP » maven-site-plugin » master #46 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/46/ > Upgrade Doxia to 1.10 and Doxia Sitetools to 1.10 > - > > Key: MSITE-875 > URL: https://issues.apache.org/jira/browse/MSITE-875 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.9.1 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.10.0 > > > h1. Release Notes - Maven Doxia - Version 1.10 > h2. Bug > * [DOXIA-542] - Markdown module converts all apostrophes to quotation > marks > * [DOXIA-588] - The Sink.JUSTIFY_XXX has no effect > h2. Improvement > * [DOXIA-521] - Markdown: Allow using the standard "" for code > blocks > * [DOXIA-606] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIA-607] - Add support for XHTML5 keygen element > * [DOXIA-614] - Support obtaining the source reference in a Doxia Parser > * [DOXIA-616] - Markdown: Properly expose the language specified in > fenced code blocks > h2. Task > * [DOXIA-618] - doxia-module-markdown: Reincorporate maven-site-plugin's > Doxia-specific integration tests > h2. Dependency upgrade > * [DOXIA-610] - Update doxia-module-fo to not use log4j > * [DOXIA-615] - Upgrade HttpClient to 4.5.13 > h1. Release Notes - Maven Doxia Sitetools - Version 1.10 > h2. Bug > * [DOXIASITETOOLS-221] - CLIRR can't find previous version > * [DOXIASITETOOLS-227] - Throwing "new ParseException(message)" shows > message with "line [-1]" > h2. Improvement > * [DOXIASITETOOLS-228] - Remove all in default-site-macros.vm and > replace by a space > h2. Dependency upgrade > * [DOXIASITETOOLS-219] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIASITETOOLS-223] - wrong coordinates for jai_core: hyphen should be > underscore > * [DOXIASITETOOLS-226] - Use latest JUnit version 4.13.2 > * [DOXIASITETOOLS-231] - Upgrade Plexus Utils to 3.3.0 > * [DOXIASITETOOLS-232] - Upgrade Plexus Interpolation to 1.26 > * [DOXIASITETOOLS-233] - Upgrade Maven Doxia to 1.10 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (MSITE-875) Upgrade Doxia to 1.10 and Doxia Sitetools to 1.10
[ https://issues.apache.org/jira/browse/MSITE-875 ] Herve Boutemy deleted comment on MSITE-875: - was (Author: hudson): Build succeeded in Jenkins: Maven » Maven TLP » maven-site-plugin » master #44 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/44/ > Upgrade Doxia to 1.10 and Doxia Sitetools to 1.10 > - > > Key: MSITE-875 > URL: https://issues.apache.org/jira/browse/MSITE-875 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.9.1 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.10.0 > > > h1. Release Notes - Maven Doxia - Version 1.10 > h2. Bug > * [DOXIA-542] - Markdown module converts all apostrophes to quotation > marks > * [DOXIA-588] - The Sink.JUSTIFY_XXX has no effect > h2. Improvement > * [DOXIA-521] - Markdown: Allow using the standard "" for code > blocks > * [DOXIA-606] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIA-607] - Add support for XHTML5 keygen element > * [DOXIA-614] - Support obtaining the source reference in a Doxia Parser > * [DOXIA-616] - Markdown: Properly expose the language specified in > fenced code blocks > h2. Task > * [DOXIA-618] - doxia-module-markdown: Reincorporate maven-site-plugin's > Doxia-specific integration tests > h2. Dependency upgrade > * [DOXIA-610] - Update doxia-module-fo to not use log4j > * [DOXIA-615] - Upgrade HttpClient to 4.5.13 > h1. Release Notes - Maven Doxia Sitetools - Version 1.10 > h2. Bug > * [DOXIASITETOOLS-221] - CLIRR can't find previous version > * [DOXIASITETOOLS-227] - Throwing "new ParseException(message)" shows > message with "line [-1]" > h2. Improvement > * [DOXIASITETOOLS-228] - Remove all in default-site-macros.vm and > replace by a space > h2. Dependency upgrade > * [DOXIASITETOOLS-219] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIASITETOOLS-223] - wrong coordinates for jai_core: hyphen should be > underscore > * [DOXIASITETOOLS-226] - Use latest JUnit version 4.13.2 > * [DOXIASITETOOLS-231] - Upgrade Plexus Utils to 3.3.0 > * [DOXIASITETOOLS-232] - Upgrade Plexus Interpolation to 1.26 > * [DOXIASITETOOLS-233] - Upgrade Maven Doxia to 1.10 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MSITE-875) Upgrade Doxia to 1.10 and Doxia Tools to 1.10
[ https://issues.apache.org/jira/browse/MSITE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSITE-875: Description: h1. Release Notes - Maven Doxia - Version 1.10 h2. Bug * [DOXIA-542] - Markdown module converts all apostrophes to quotation marks * [DOXIA-588] - The Sink.JUSTIFY_XXX has no effect h2. Improvement * [DOXIA-521] - Markdown: Allow using the standard "" for code blocks * [DOXIA-606] - fix javadoc issues with JDK 8 when generating documentation * [DOXIA-607] - Add support for XHTML5 keygen element * [DOXIA-614] - Support obtaining the source reference in a Doxia Parser * [DOXIA-616] - Markdown: Properly expose the language specified in fenced code blocks h2. Task * [DOXIA-618] - doxia-module-markdown: Reincorporate maven-site-plugin's Doxia-specific integration tests h2. Dependency upgrade * [DOXIA-610] - Update doxia-module-fo to not use log4j * [DOXIA-615] - Upgrade HttpClient to 4.5.13 h1. Release Notes - Maven Doxia Sitetools - Version 1.10 h2. Bug * [DOXIASITETOOLS-221] - CLIRR can't find previous version * [DOXIASITETOOLS-227] - Throwing "new ParseException(message)" shows message with "line [-1]" h2. Improvement * [DOXIASITETOOLS-228] - Remove all in default-site-macros.vm and replace by a space h2. Dependency upgrade * [DOXIASITETOOLS-219] - fix javadoc issues with JDK 8 when generating documentation * [DOXIASITETOOLS-223] - wrong coordinates for jai_core: hyphen should be underscore * [DOXIASITETOOLS-226] - Use latest JUnit version 4.13.2 * [DOXIASITETOOLS-231] - Upgrade Plexus Utils to 3.3.0 * [DOXIASITETOOLS-232] - Upgrade Plexus Interpolation to 1.26 * [DOXIASITETOOLS-233] - Upgrade Maven Doxia to 1.10 > Upgrade Doxia to 1.10 and Doxia Tools to 1.10 > - > > Key: MSITE-875 > URL: https://issues.apache.org/jira/browse/MSITE-875 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.10.0 > > > h1. Release Notes - Maven Doxia - Version 1.10 > h2. Bug > * [DOXIA-542] - Markdown module converts all apostrophes to quotation > marks > * [DOXIA-588] - The Sink.JUSTIFY_XXX has no effect > h2. Improvement > * [DOXIA-521] - Markdown: Allow using the standard "" for code > blocks > * [DOXIA-606] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIA-607] - Add support for XHTML5 keygen element > * [DOXIA-614] - Support obtaining the source reference in a Doxia Parser > * [DOXIA-616] - Markdown: Properly expose the language specified in > fenced code blocks > h2. Task > * [DOXIA-618] - doxia-module-markdown: Reincorporate maven-site-plugin's > Doxia-specific integration tests > h2. Dependency upgrade > * [DOXIA-610] - Update doxia-module-fo to not use log4j > * [DOXIA-615] - Upgrade HttpClient to 4.5.13 > h1. Release Notes - Maven Doxia Sitetools - Version 1.10 > h2. Bug > * [DOXIASITETOOLS-221] - CLIRR can't find previous version > * [DOXIASITETOOLS-227] - Throwing "new ParseException(message)" shows > message with "line [-1]" > h2. Improvement > * [DOXIASITETOOLS-228] - Remove all in default-site-macros.vm and > replace by a space > h2. Dependency upgrade > * [DOXIASITETOOLS-219] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIASITETOOLS-223] - wrong coordinates for jai_core: hyphen should be > underscore > * [DOXIASITETOOLS-226] - Use latest JUnit version 4.13.2 > * [DOXIASITETOOLS-231] - Upgrade Plexus Utils to 3.3.0 > * [DOXIASITETOOLS-232] - Upgrade Plexus Interpolation to 1.26 > * [DOXIASITETOOLS-233] - Upgrade Maven Doxia to 1.10 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MSITE-875) Upgrade Doxia to 1.10 and Doxia Sitetools to 1.10
[ https://issues.apache.org/jira/browse/MSITE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSITE-875: Summary: Upgrade Doxia to 1.10 and Doxia Sitetools to 1.10 (was: Upgrade Doxia to 1.10 and Doxia Tools to 1.10) > Upgrade Doxia to 1.10 and Doxia Sitetools to 1.10 > - > > Key: MSITE-875 > URL: https://issues.apache.org/jira/browse/MSITE-875 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.9.1 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.10.0 > > > h1. Release Notes - Maven Doxia - Version 1.10 > h2. Bug > * [DOXIA-542] - Markdown module converts all apostrophes to quotation > marks > * [DOXIA-588] - The Sink.JUSTIFY_XXX has no effect > h2. Improvement > * [DOXIA-521] - Markdown: Allow using the standard "" for code > blocks > * [DOXIA-606] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIA-607] - Add support for XHTML5 keygen element > * [DOXIA-614] - Support obtaining the source reference in a Doxia Parser > * [DOXIA-616] - Markdown: Properly expose the language specified in > fenced code blocks > h2. Task > * [DOXIA-618] - doxia-module-markdown: Reincorporate maven-site-plugin's > Doxia-specific integration tests > h2. Dependency upgrade > * [DOXIA-610] - Update doxia-module-fo to not use log4j > * [DOXIA-615] - Upgrade HttpClient to 4.5.13 > h1. Release Notes - Maven Doxia Sitetools - Version 1.10 > h2. Bug > * [DOXIASITETOOLS-221] - CLIRR can't find previous version > * [DOXIASITETOOLS-227] - Throwing "new ParseException(message)" shows > message with "line [-1]" > h2. Improvement > * [DOXIASITETOOLS-228] - Remove all in default-site-macros.vm and > replace by a space > h2. Dependency upgrade > * [DOXIASITETOOLS-219] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIASITETOOLS-223] - wrong coordinates for jai_core: hyphen should be > underscore > * [DOXIASITETOOLS-226] - Use latest JUnit version 4.13.2 > * [DOXIASITETOOLS-231] - Upgrade Plexus Utils to 3.3.0 > * [DOXIASITETOOLS-232] - Upgrade Plexus Interpolation to 1.26 > * [DOXIASITETOOLS-233] - Upgrade Maven Doxia to 1.10 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MSITE-875) Upgrade Doxia to 1.10 and Doxia Tools to 1.10
[ https://issues.apache.org/jira/browse/MSITE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSITE-875: Affects Version/s: 3.9.1 > Upgrade Doxia to 1.10 and Doxia Tools to 1.10 > - > > Key: MSITE-875 > URL: https://issues.apache.org/jira/browse/MSITE-875 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.9.1 >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.10.0 > > > h1. Release Notes - Maven Doxia - Version 1.10 > h2. Bug > * [DOXIA-542] - Markdown module converts all apostrophes to quotation > marks > * [DOXIA-588] - The Sink.JUSTIFY_XXX has no effect > h2. Improvement > * [DOXIA-521] - Markdown: Allow using the standard "" for code > blocks > * [DOXIA-606] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIA-607] - Add support for XHTML5 keygen element > * [DOXIA-614] - Support obtaining the source reference in a Doxia Parser > * [DOXIA-616] - Markdown: Properly expose the language specified in > fenced code blocks > h2. Task > * [DOXIA-618] - doxia-module-markdown: Reincorporate maven-site-plugin's > Doxia-specific integration tests > h2. Dependency upgrade > * [DOXIA-610] - Update doxia-module-fo to not use log4j > * [DOXIA-615] - Upgrade HttpClient to 4.5.13 > h1. Release Notes - Maven Doxia Sitetools - Version 1.10 > h2. Bug > * [DOXIASITETOOLS-221] - CLIRR can't find previous version > * [DOXIASITETOOLS-227] - Throwing "new ParseException(message)" shows > message with "line [-1]" > h2. Improvement > * [DOXIASITETOOLS-228] - Remove all in default-site-macros.vm and > replace by a space > h2. Dependency upgrade > * [DOXIASITETOOLS-219] - fix javadoc issues with JDK 8 when generating > documentation > * [DOXIASITETOOLS-223] - wrong coordinates for jai_core: hyphen should be > underscore > * [DOXIASITETOOLS-226] - Use latest JUnit version 4.13.2 > * [DOXIASITETOOLS-231] - Upgrade Plexus Utils to 3.3.0 > * [DOXIASITETOOLS-232] - Upgrade Plexus Interpolation to 1.26 > * [DOXIASITETOOLS-233] - Upgrade Maven Doxia to 1.10 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-release] slawekjaranowski commented on pull request #75: Bump maven-invoker from 2.2 to 3.1.0
slawekjaranowski commented on pull request #75: URL: https://github.com/apache/maven-release/pull/75#issuecomment-999849195 Here is a reason - @khmarbaise https://github.com/apache/maven-invoker/commit/78362d5bfa1be17f81d36533835b4176cf0e43c8 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MSITE-878) Upgrade Doxia to 1.11.1 and Doxia Sitetools to 1.11.1
[ https://issues.apache.org/jira/browse/MSITE-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSITE-878: Description: h1. Release Notes - Maven Doxia - Version 1.11.1 h2. Task * [DOXIA-620] - Deprecate Doxia Logging API in favor of SLF4J * [DOXIA-621] - Deprecate doxia-module-confluence * [DOXIA-622] - Deprecate doxia-module-docbook-simple * [DOXIA-623] - Deprecate doxia-module-fo * [DOXIA-624] - Deprecate doxia-module-itext * [DOXIA-625] - Deprecate doxia-module-latex * [DOXIA-626] - Deprecate doxia-module-rtf * [DOXIA-627] - Deprecate doxia-module-twiki * [DOXIA-628] - Deprecate SsiMacro * [DOXIA-629] - Deprecate SwfMacro h1. Release Notes - Maven Doxia Sitetools - Version 1.11.1 h2. Improvement * [DOXIASITETOOLS-234] - improve documentation on site.xml inheritance vs interpolation h2. Task * [DOXIASITETOOLS-236] - Deprecate Doxia Sitetools Doc Renderer h2. Dependency upgrade * [DOXIASITETOOLS-237] - Upgrade Maven Doxia to 1.11.1 > Upgrade Doxia to 1.11.1 and Doxia Sitetools to 1.11.1 > - > > Key: MSITE-878 > URL: https://issues.apache.org/jira/browse/MSITE-878 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.10.0 > > > h1. Release Notes - Maven Doxia - Version 1.11.1 > h2. Task > * [DOXIA-620] - Deprecate Doxia Logging API in favor of SLF4J > * [DOXIA-621] - Deprecate doxia-module-confluence > * [DOXIA-622] - Deprecate doxia-module-docbook-simple > * [DOXIA-623] - Deprecate doxia-module-fo > * [DOXIA-624] - Deprecate doxia-module-itext > * [DOXIA-625] - Deprecate doxia-module-latex > * [DOXIA-626] - Deprecate doxia-module-rtf > * [DOXIA-627] - Deprecate doxia-module-twiki > * [DOXIA-628] - Deprecate SsiMacro > * [DOXIA-629] - Deprecate SwfMacro > h1. Release Notes - Maven Doxia Sitetools - Version 1.11.1 > h2. Improvement > * [DOXIASITETOOLS-234] - improve documentation on site.xml inheritance vs > interpolation > h2. Task > * [DOXIASITETOOLS-236] - Deprecate Doxia Sitetools Doc Renderer > h2. Dependency upgrade > * [DOXIASITETOOLS-237] - Upgrade Maven Doxia to 1.11.1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MSITE-878) Upgrade Doxia to 1.11.1 and Doxia Sitetools to 1.11.1
[ https://issues.apache.org/jira/browse/MSITE-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSITE-878: Summary: Upgrade Doxia to 1.11.1 and Doxia Sitetools to 1.11.1 (was: Upgrade Doxia to 1.11.1 and Doxia Tools to 1.11.1) > Upgrade Doxia to 1.11.1 and Doxia Sitetools to 1.11.1 > - > > Key: MSITE-878 > URL: https://issues.apache.org/jira/browse/MSITE-878 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.10.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-plugin-tools] michael-o commented on pull request #58: [MPLUGIN-386] Exclude maven-archiver and maven-jxr from warning
michael-o commented on pull request #58: URL: https://github.com/apache/maven-plugin-tools/pull/58#issuecomment-999835738 > Can we really do it outside maven plugin api subgraph? Dont think so today :( WDYM? -- 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] (MWRAPPER-43) Download of jar must be quiet by default
[
https://issues.apache.org/jira/browse/MWRAPPER-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464026#comment-17464026
]
Herve Boutemy commented on MWRAPPER-43:
---
thanks for the feedback: yes, updating the script was an option I had
imagined...
> Download of jar must be quiet by default
>
>
> Key: MWRAPPER-43
> URL: https://issues.apache.org/jira/browse/MWRAPPER-43
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Scripts
>Affects Versions: 3.1.0
>Reporter: Jorge Solórzano
>Assignee: Herve Boutemy
>Priority: Normal
> Fix For: 3.1.1
>
>
> By default, the wrapper must be quiet, if the _maven-wrapper.jar_ is not
> found the scripts try to download the jar using {*}wget{*}, {*}curl{*}, or
> the {*}MavenWrapperDownloader{*}.java.
> The download process should only print the output when the +*MVNW_VERBOSE*+
> is set to true.
> Current output for *wget* when the maven-wrapper.jar is missing:
> {noformat}
> ./mvnw clean
> --2021-12-21 11:52:43--
> https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.1.0/maven-wrapper-3.1.0.jar
> Resolving repo.maven.apache.org (repo.maven.apache.org)... 151.101.132.215
> Connecting to repo.maven.apache.org
> (repo.maven.apache.org)|151.101.132.215|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 58727 (57K) [application/java-archive]
> Saving to: '/home/wrapper/api/.mvn/wrapper/maven-wrapper.jar'
> /home/jorsol/Trabajo/conf-worksp
> 100%[==>] 57,35K
> --.-KB/sin 0,007s
> 2021-12-21 11:52:44 (8,13 MB/s) -
> '/home/wrapper/api/.mvn/wrapper/maven-wrapper.jar' saved [58727/58727]
> 11:52:45.544 [INFO] Scanning for projects...
> ...
> {noformat}
> Current output for *curl* the maven-wrapper.jar is missing:
> {noformat}
> ./mvnw clean
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft Speed
> 100 58727 100 587270 0 1303k 0 --:--:-- --:--:-- --:--:-- 1303k
> 12:02:23.007 [INFO] Scanning for projects...
> ...
> {noformat}
> Current output for *MavenWrapperDownloader* when the maven-wrapper.jar is
> missing:
> {noformat}
> ./mvnw clean
> - Downloader started
> - Using base directory: /home/wrapper/api
> - Downloading from:
> https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.1.0/maven-wrapper-3.1.0.jar
> - Downloading to: /home/wrapper/api/.mvn/wrapper/maven-wrapper.jar
> Done
> 11:50:21.599 [INFO] Scanning for projects...
> ...
> {noformat}
> Everything between the _./mvnw_ and the first _INFO_ is just unwanted
> verbosity.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (MWRAPPER-43) Download of jar must be quiet by default
[
https://issues.apache.org/jira/browse/MWRAPPER-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464026#comment-17464026
]
Herve Boutemy edited comment on MWRAPPER-43 at 12/22/21, 8:03 PM:
--
thanks for the feedback: yes, updating the script was an option I had
imagined...
we can do it in ITs, then no need to restore after the run
was (Author: hboutemy):
thanks for the feedback: yes, updating the script was an option I had
imagined...
> Download of jar must be quiet by default
>
>
> Key: MWRAPPER-43
> URL: https://issues.apache.org/jira/browse/MWRAPPER-43
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Scripts
>Affects Versions: 3.1.0
>Reporter: Jorge Solórzano
>Assignee: Herve Boutemy
>Priority: Normal
> Fix For: 3.1.1
>
>
> By default, the wrapper must be quiet, if the _maven-wrapper.jar_ is not
> found the scripts try to download the jar using {*}wget{*}, {*}curl{*}, or
> the {*}MavenWrapperDownloader{*}.java.
> The download process should only print the output when the +*MVNW_VERBOSE*+
> is set to true.
> Current output for *wget* when the maven-wrapper.jar is missing:
> {noformat}
> ./mvnw clean
> --2021-12-21 11:52:43--
> https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.1.0/maven-wrapper-3.1.0.jar
> Resolving repo.maven.apache.org (repo.maven.apache.org)... 151.101.132.215
> Connecting to repo.maven.apache.org
> (repo.maven.apache.org)|151.101.132.215|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 58727 (57K) [application/java-archive]
> Saving to: '/home/wrapper/api/.mvn/wrapper/maven-wrapper.jar'
> /home/jorsol/Trabajo/conf-worksp
> 100%[==>] 57,35K
> --.-KB/sin 0,007s
> 2021-12-21 11:52:44 (8,13 MB/s) -
> '/home/wrapper/api/.mvn/wrapper/maven-wrapper.jar' saved [58727/58727]
> 11:52:45.544 [INFO] Scanning for projects...
> ...
> {noformat}
> Current output for *curl* the maven-wrapper.jar is missing:
> {noformat}
> ./mvnw clean
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft Speed
> 100 58727 100 587270 0 1303k 0 --:--:-- --:--:-- --:--:-- 1303k
> 12:02:23.007 [INFO] Scanning for projects...
> ...
> {noformat}
> Current output for *MavenWrapperDownloader* when the maven-wrapper.jar is
> missing:
> {noformat}
> ./mvnw clean
> - Downloader started
> - Using base directory: /home/wrapper/api
> - Downloading from:
> https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.1.0/maven-wrapper-3.1.0.jar
> - Downloading to: /home/wrapper/api/.mvn/wrapper/maven-wrapper.jar
> Done
> 11:50:21.599 [INFO] Scanning for projects...
> ...
> {noformat}
> Everything between the _./mvnw_ and the first _INFO_ is just unwanted
> verbosity.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MSHARED-966) Resources are not copied to ${project.build.outputDirectory}
[
https://issues.apache.org/jira/browse/MSHARED-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MSHARED-966:
-
Affects Version/s: maven-filtering-3.3.0
> Resources are not copied to ${project.build.outputDirectory}
>
>
> Key: MSHARED-966
> URL: https://issues.apache.org/jira/browse/MSHARED-966
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
>Affects Versions: maven-filtering-3.2.0, maven-filtering-3.3.0
> Environment: Maven 3.6.3, Java 11, macOS
>Reporter: Ralf Taugerbeck
>Priority: Major
> Attachments: maven-example.tgz, maven.log
>
>
> Hi,
> after upgrading from 3.1.0 to 3.2.0 I get this weird issue. My build fails
> with a java.nio.file.NoSuchFileException for a file, that actually exists in
> the resources directory.
> What's special about the file is that it was extracted from a dependency
> artifact. I know this is a strange use case, but for us it is the only way to
> supply a common Velocity macro library file to other modules for Velocity
> template development with IntelliJ (only relative paths supported).
> File content and encoding do not seem to have an impact. Could it be because
> of an archive flag? If I modify and save the file, the build works fine
> again...
> If necessary, I can provide a stack trace or detailed log.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MSHARED-966) Resources are not copied to ${project.build.outputDirectory}
[
https://issues.apache.org/jira/browse/MSHARED-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464016#comment-17464016
]
Sylwester Lachiewicz commented on MSHARED-966:
--
Changes reverted
> Resources are not copied to ${project.build.outputDirectory}
>
>
> Key: MSHARED-966
> URL: https://issues.apache.org/jira/browse/MSHARED-966
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
>Affects Versions: maven-filtering-3.2.0
> Environment: Maven 3.6.3, Java 11, macOS
>Reporter: Ralf Taugerbeck
>Priority: Major
> Attachments: maven-example.tgz, maven.log
>
>
> Hi,
> after upgrading from 3.1.0 to 3.2.0 I get this weird issue. My build fails
> with a java.nio.file.NoSuchFileException for a file, that actually exists in
> the resources directory.
> What's special about the file is that it was extracted from a dependency
> artifact. I know this is a strange use case, but for us it is the only way to
> supply a common Velocity macro library file to other modules for Velocity
> template development with IntelliJ (only relative paths supported).
> File content and encoding do not seem to have an impact. Could it be because
> of an archive flag? If I modify and save the file, the build works fine
> again...
> If necessary, I can provide a stack trace or detailed log.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (MSHARED-966) Resources are not copied to ${project.build.outputDirectory}
[
https://issues.apache.org/jira/browse/MSHARED-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned MSHARED-966:
Assignee: (was: Sylwester Lachiewicz)
> Resources are not copied to ${project.build.outputDirectory}
>
>
> Key: MSHARED-966
> URL: https://issues.apache.org/jira/browse/MSHARED-966
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
>Affects Versions: maven-filtering-3.2.0
> Environment: Maven 3.6.3, Java 11, macOS
>Reporter: Ralf Taugerbeck
>Priority: Major
> Attachments: maven-example.tgz, maven.log
>
>
> Hi,
> after upgrading from 3.1.0 to 3.2.0 I get this weird issue. My build fails
> with a java.nio.file.NoSuchFileException for a file, that actually exists in
> the resources directory.
> What's special about the file is that it was extracted from a dependency
> artifact. I know this is a strange use case, but for us it is the only way to
> supply a common Velocity macro library file to other modules for Velocity
> template development with IntelliJ (only relative paths supported).
> File content and encoding do not seem to have an impact. Could it be because
> of an archive flag? If I modify and save the file, the build works fine
> again...
> If necessary, I can provide a stack trace or detailed log.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MSHARED-966) Resources are not copied to ${project.build.outputDirectory}
[
https://issues.apache.org/jira/browse/MSHARED-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MSHARED-966:
-
Fix Version/s: (was: maven-filtering-3.3.0)
> Resources are not copied to ${project.build.outputDirectory}
>
>
> Key: MSHARED-966
> URL: https://issues.apache.org/jira/browse/MSHARED-966
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
>Affects Versions: maven-filtering-3.2.0
> Environment: Maven 3.6.3, Java 11, macOS
>Reporter: Ralf Taugerbeck
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Attachments: maven-example.tgz, maven.log
>
>
> Hi,
> after upgrading from 3.1.0 to 3.2.0 I get this weird issue. My build fails
> with a java.nio.file.NoSuchFileException for a file, that actually exists in
> the resources directory.
> What's special about the file is that it was extracted from a dependency
> artifact. I know this is a strange use case, but for us it is the only way to
> supply a common Velocity macro library file to other modules for Velocity
> template development with IntelliJ (only relative paths supported).
> File content and encoding do not seem to have an impact. Could it be because
> of an archive flag? If I modify and save the file, the build works fine
> again...
> If necessary, I can provide a stack trace or detailed log.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MSHARED-1002) Require Java 8
[ https://issues.apache.org/jira/browse/MSHARED-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSHARED-1002: -- Component/s: maven-filtering > Require Java 8 > -- > > Key: MSHARED-1002 > URL: https://issues.apache.org/jira/browse/MSHARED-1002 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-common-artifact-filters, maven-filtering >Reporter: Sylwester Lachiewicz >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MSHARED-1003) Require Maven 3.2.5+
[ https://issues.apache.org/jira/browse/MSHARED-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSHARED-1003: -- Description: Grouping all shared components > Require Maven 3.2.5+ > > > Key: MSHARED-1003 > URL: https://issues.apache.org/jira/browse/MSHARED-1003 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-dependency-analyzer, maven-filtering >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: maven-filtering-3.3.0 > > > Grouping all shared components -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-filtering] dependabot[bot] commented on pull request #25: Bump plexus-utils from 3.3.0 to 3.4.1
dependabot[bot] commented on pull request #25: URL: https://github.com/apache/maven-filtering/pull/25#issuecomment-999798349 Looks like this PR is already up-to-date with master! If you'd still like to recreate it from scratch, overwriting any edits, you can request `@dependabot recreate`. -- 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] slachiewicz commented on pull request #25: Bump plexus-utils from 3.3.0 to 3.4.1
slachiewicz commented on pull request #25: URL: https://github.com/apache/maven-filtering/pull/25#issuecomment-999798334 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-release] slachiewicz closed pull request #65: update aether-util
slachiewicz closed pull request #65: URL: https://github.com/apache/maven-release/pull/65 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-release] slachiewicz commented on pull request #75: Bump maven-invoker from 2.2 to 3.1.0
slachiewicz commented on pull request #75: URL: https://github.com/apache/maven-release/pull/75#issuecomment-999746354 @slawekjaranowski can you check what is happening here? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-release] slachiewicz commented on pull request #75: Bump maven-invoker from 2.2 to 3.1.0
slachiewicz commented on pull request #75: URL: https://github.com/apache/maven-release/pull/75#issuecomment-999746050 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-release] slachiewicz commented on pull request #79: Bump scmVersion from 1.11.3 to 1.12.0
slachiewicz commented on pull request #79: URL: https://github.com/apache/maven-release/pull/79#issuecomment-999745922 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-release] slachiewicz commented on pull request #81: Bump maven-scm-manager-plexus from 1.8 to 1.12.0
slachiewicz commented on pull request #81: URL: https://github.com/apache/maven-release/pull/81#issuecomment-999745692 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-enforcer] slachiewicz commented on pull request #129: Bump mrm-maven-plugin from 1.2.0 to 1.3.0
slachiewicz commented on pull request #129: URL: https://github.com/apache/maven-enforcer/pull/129#issuecomment-999745273 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MWRAPPER-46) Simplify use of Maven Wrapper in different environments (basic auth required)
[ https://issues.apache.org/jira/browse/MWRAPPER-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimisola Laursen updated MWRAPPER-46: - Description: I'll describe our use-case as I suspect that we might be alone with this one. This ticket relates to: # MVNW_REPOURL being insufficient # user not being able to set MVNW_USERNAME/PASSWORD in plain text due security *Prerequisites:* * _Self-hosted Maven 2 repo that requires basic auth_ (Nexus with proxy for Maven Central) * Environments: ** Local machine: need to use proxy for Internet, can't set MVNW_USERNAME/PASSWORD in plain text due security ** Pipeline/Deployment (k8s): need to use proxy for Internet, MVNW_USERNAME/PASSWORD are set * We want to be able to specify wrapper and/or Maven version (hence, use maven-wrapper.properties) *Use-case:* all downloads, but local and in cluster/cloud, should go via our self-hosted Maven 2 repo that requires basic auth *Setup cases:* # Setting MVNW_REPOURL in both environments causes two problems: ## local machine: we would have to set MVNW_USER/PASSWORD (can't due to security risk) ## k8s: MVNW_REPOURL environment variable, strangely, doesn't override value in maven-wrapper.properties, but vice versa. Is this really common practise? Compare with e.g. [Spring Boot's Externalized Configuration|https://docs.spring.io/spring-boot/docs/1.2.3.RELEASE/reference/html/boot-features-external-config.html]. So, we would have to either change the base url in the maven-wrapper.properties in k8s explicitly since we want to keep the version information for maven-wrapper and Maven. # Changing the urls to the self-hosted repo in maven-wrapper.properties: ## local machine: we would have to set MVNW_USER/PASSWORD (can't due to security risk) ## k8s: would work since MVNW_USERNAME/PASSWORD are set # Having maven-wrapper.jar checked in doesn't solve the issue since Maven itself has to be downloaded as well and basic auth not set. *Ideas:* # be able to use [Password Encryption|https://maven.apache.org/guides/mini/guide-encryption.html] and have password encrypted in settings.xml or in MVNW_PASSWORD: issue of course being that Maven Password Encryption is not available during bootstrapping. # change the behavior of MVNW_REPOURL so that it has the highest priority and supersedes defaults in mvnw[.cmd] script as well as in maven-wrapper.properties: at least then we can keep a correct maven-wrapper.properties (w/ self-hosted Maven repo) and set MVNW_REPOURL to Maven Central on local machine for bootstrapping. *Proposed semi-solution:* * Change priority of MVNW_REPOURL or, for backwards compatibility, add another environment variable which supersedes all other settings was: I'll describe our use-case as I suspect that we might not be alone with this one. This ticket relates to: # MVNW_REPOURL being insufficient # user not being able to set MVNW_USERNAME/PASSWORD in plain text due security *Prerequisites:* * _Self-hosted Maven 2 repo that requires basic auth_ (Nexus with proxy for Maven Central) * Environments: ** Local machine: need to use proxy for Internet, can't set MVNW_USERNAME/PASSWORD in plain text due security ** Pipeline/Deployment (k8s): need to use proxy for Internet, MVNW_USERNAME/PASSWORD are set * We want to be able to specify wrapper and/or Maven version (hence, use maven-wrapper.properties) *Use-case:* all downloads, but local and in cluster/cloud, should go via our self-hosted Maven 2 repo that requires basic auth *Setup cases:* # Setting MVNW_REPOURL in both environments causes two problems: ## local machine: we would have to set MVNW_USER/PASSWORD (can't due to security risk) ## k8s: MVNW_REPOURL environment variable, strangely, doesn't override value in maven-wrapper.properties, but vice versa. Is this really common practise? Compare with e.g. [Spring Boot's Externalized Configuration|https://docs.spring.io/spring-boot/docs/1.2.3.RELEASE/reference/html/boot-features-external-config.html]. So, we would have to either change the base url in the maven-wrapper.properties in k8s explicitly since we want to keep the version information for maven-wrapper and Maven. # Changing the urls to the self-hosted repo in maven-wrapper.properties: ## local machine: we would have to set MVNW_USER/PASSWORD (can't due to security risk) ## k8s: would work since MVNW_USERNAME/PASSWORD are set # Having maven-wrapper.jar checked in doesn't solve the issue since Maven itself has to be downloaded as well and basic auth not set. *Ideas:* # be able to use [Password Encryption|https://maven.apache.org/guides/mini/guide-encryption.html] and have password encrypted in settings.xml or in MVNW_PASSWORD: issue of course being that Maven Password Encryption is not available during bootstrapping. # change the behavior of MVNW_REPOURL so that it has the highest priority and supersedes defaults in mvnw[
[jira] [Updated] (MWRAPPER-46) Simplify use of Maven Wrapper in different environments (basic auth required)
[ https://issues.apache.org/jira/browse/MWRAPPER-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimisola Laursen updated MWRAPPER-46: - Summary: Simplify use of Maven Wrapper in different environments (basic auth required) (was: Simplify use of Maven Wrapper project in different environments (basic auth required)) > Simplify use of Maven Wrapper in different environments (basic auth required) > - > > Key: MWRAPPER-46 > URL: https://issues.apache.org/jira/browse/MWRAPPER-46 > Project: Maven Wrapper > Issue Type: Improvement >Affects Versions: 3.1.0 >Reporter: Jimisola Laursen >Priority: Normal > > I'll describe our use-case as I suspect that we might not be alone with this > one. > This ticket relates to: > # MVNW_REPOURL being insufficient > # user not being able to set MVNW_USERNAME/PASSWORD in plain text due > security > *Prerequisites:* > * _Self-hosted Maven 2 repo that requires basic auth_ (Nexus with proxy for > Maven Central) > * Environments: > ** Local machine: need to use proxy for Internet, can't set > MVNW_USERNAME/PASSWORD in plain text due security > ** Pipeline/Deployment (k8s): need to use proxy for Internet, > MVNW_USERNAME/PASSWORD are set > * We want to be able to specify wrapper and/or Maven version (hence, use > maven-wrapper.properties) > *Use-case:* all downloads, but local and in cluster/cloud, should go via our > self-hosted Maven 2 repo that requires basic auth > *Setup cases:* > # Setting MVNW_REPOURL in both environments causes two problems: > ## local machine: we would have to set MVNW_USER/PASSWORD (can't due to > security risk) > ## k8s: MVNW_REPOURL environment variable, strangely, doesn't override value > in maven-wrapper.properties, but vice versa. Is this really common practise? > Compare with e.g. [Spring Boot's Externalized > Configuration|https://docs.spring.io/spring-boot/docs/1.2.3.RELEASE/reference/html/boot-features-external-config.html]. > So, we would have to either change the base url in the > maven-wrapper.properties in k8s explicitly since we want to keep the version > information for maven-wrapper and Maven. > # Changing the urls to the self-hosted repo in maven-wrapper.properties: > ## local machine: we would have to set MVNW_USER/PASSWORD (can't due to > security risk) > ## k8s: would work since MVNW_USERNAME/PASSWORD are set > # Having maven-wrapper.jar checked in doesn't solve the issue since Maven > itself has to be downloaded as well and basic auth not set. > *Ideas:* > # be able to use [Password > Encryption|https://maven.apache.org/guides/mini/guide-encryption.html] and > have password encrypted in settings.xml or in MVNW_PASSWORD: issue of course > being that Maven Password Encryption is not available during bootstrapping. > # change the behavior of MVNW_REPOURL so that it has the highest priority > and supersedes defaults in mvnw[.cmd] script as well as in > maven-wrapper.properties: at least then we can keep a correct > maven-wrapper.properties (w/ self-hosted Maven repo) and set MVNW_REPOURL to > Maven Central on local machine for bootstrapping. > *Proposed semi-solution:* > * Change priority of MVNW_REPOURL or, for backwards compatibility, add > another environment variable which supersedes all other settings -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-plugin-tools] rmannibucau commented on pull request #58: [MPLUGIN-386] Exclude maven-archiver and maven-jxr from warning
rmannibucau commented on pull request #58: URL: https://github.com/apache/maven-plugin-tools/pull/58#issuecomment-999733523 Can we really do it outside maven plugin api subgraph? Dont think so today :( -- 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] (MPLUGIN-385) Clarify usage of scope "provided" for Maven artifacts with group id "org.apache.maven"
[
https://issues.apache.org/jira/browse/MPLUGIN-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463963#comment-17463963
]
Konrad Windszus edited comment on MPLUGIN-385 at 12/22/21, 4:53 PM:
FTR: My issue would be solved with
https://issues.apache.org/jira/browse/MPLUGIN-386 and
https://github.com/apache/maven-plugin-tools/pull/58. Feel free though to reuse
this issue to come up with a proper API definition and to ease referencing the
right version.
was (Author: kwin):
FTR: My issue would be solved with
https://issues.apache.org/jira/browse/MPLUGIN-386 and
https://github.com/apache/maven-plugin-tools/pull/58.
> Clarify usage of scope "provided" for Maven artifacts with group id
> "org.apache.maven"
> --
>
> Key: MPLUGIN-385
> URL: https://issues.apache.org/jira/browse/MPLUGIN-385
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
>Affects Versions: 3.6.2
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.7.0
>
>
> Since m-plugin-p 3.6.2 (MPLUGIN-370) all dependencies with group id
> {{org.apache.maven}} are supposed to be referenced with scope {{provided}}.
> But once turning dependency {{org.apache.maven:maven-archiver:3.5.1}} to
> scope provided my ITs based on
> {{org.apache.maven.shared:maven-verifier:1.7.2}} are starting to fail with
> NCDF errors
> {code}
> java.lang.NoClassDefFoundError:
> Lorg/apache/maven/archiver/MavenArchiveConfiguration;
> {code}
> Is that a bug in the classloader with maven-verifier? What if I want to use a
> newer version than shipped with Maven like "maven-archiver 3.5.1"?
> What about group ids starting with "org.apache.maven" like
> "org.apache.maven.shared"?
> You can reproduce with
> https://github.com/apache/jackrabbit-filevault-package-maven-plugin.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MPLUGIN-385) Clarify usage of scope "provided" for Maven artifacts with group id "org.apache.maven"
[
https://issues.apache.org/jira/browse/MPLUGIN-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463963#comment-17463963
]
Konrad Windszus commented on MPLUGIN-385:
-
FTR: My issue would be solved with
https://issues.apache.org/jira/browse/MPLUGIN-386 and
https://github.com/apache/maven-plugin-tools/pull/58.
> Clarify usage of scope "provided" for Maven artifacts with group id
> "org.apache.maven"
> --
>
> Key: MPLUGIN-385
> URL: https://issues.apache.org/jira/browse/MPLUGIN-385
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
>Affects Versions: 3.6.2
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.7.0
>
>
> Since m-plugin-p 3.6.2 (MPLUGIN-370) all dependencies with group id
> {{org.apache.maven}} are supposed to be referenced with scope {{provided}}.
> But once turning dependency {{org.apache.maven:maven-archiver:3.5.1}} to
> scope provided my ITs based on
> {{org.apache.maven.shared:maven-verifier:1.7.2}} are starting to fail with
> NCDF errors
> {code}
> java.lang.NoClassDefFoundError:
> Lorg/apache/maven/archiver/MavenArchiveConfiguration;
> {code}
> Is that a bug in the classloader with maven-verifier? What if I want to use a
> newer version than shipped with Maven like "maven-archiver 3.5.1"?
> What about group ids starting with "org.apache.maven" like
> "org.apache.maven.shared"?
> You can reproduce with
> https://github.com/apache/jackrabbit-filevault-package-maven-plugin.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (MWRAPPER-47) Use name wrapperUrl consistently in Maven Wrapper files/scripts
Jimisola Laursen created MWRAPPER-47: Summary: Use name wrapperUrl consistently in Maven Wrapper files/scripts Key: MWRAPPER-47 URL: https://issues.apache.org/jira/browse/MWRAPPER-47 Project: Maven Wrapper Issue Type: Improvement Components: Maven Wrapper Scripts Reporter: Jimisola Laursen maven-wrapper.properties has two properties: *wrapperUrl* and distributionUrl However, in the mvnw script the wrapperUrl is stored as jarUrl (no need for confusion) and after download it is referred to as wrapperJarPath. Rename jarUrl to wrapperUrl in mvn[.cmd] for consistency. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MWRAPPER-46) Simplify use of Maven Wrapper project in different environments (basic auth required)
[ https://issues.apache.org/jira/browse/MWRAPPER-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimisola Laursen updated MWRAPPER-46: - Summary: Simplify use of Maven Wrapper project in different environments (basic auth required) (was: Simplify use of Maven Wrapper project in different environments) > Simplify use of Maven Wrapper project in different environments (basic auth > required) > - > > Key: MWRAPPER-46 > URL: https://issues.apache.org/jira/browse/MWRAPPER-46 > Project: Maven Wrapper > Issue Type: Improvement >Affects Versions: 3.1.0 >Reporter: Jimisola Laursen >Priority: Normal > > I'll describe our use-case as I suspect that we might not be alone with this > one. > This ticket relates to: > # MVNW_REPOURL being insufficient > # user not being able to set MVNW_USERNAME/PASSWORD in plain text due > security > *Prerequisites:* > * _Self-hosted Maven 2 repo that requires basic auth_ (Nexus with proxy for > Maven Central) > * Environments: > ** Local machine: need to use proxy for Internet, can't set > MVNW_USERNAME/PASSWORD in plain text due security > ** Pipeline/Deployment (k8s): need to use proxy for Internet, > MVNW_USERNAME/PASSWORD are set > * We want to be able to specify wrapper and/or Maven version (hence, use > maven-wrapper.properties) > *Use-case:* all downloads, but local and in cluster/cloud, should go via our > self-hosted Maven 2 repo that requires basic auth > *Setup cases:* > # Setting MVNW_REPOURL in both environments causes two problems: > ## local machine: we would have to set MVNW_USER/PASSWORD (can't due to > security risk) > ## k8s: MVNW_REPOURL environment variable, strangely, doesn't override value > in maven-wrapper.properties, but vice versa. Is this really common practise? > Compare with e.g. [Spring Boot's Externalized > Configuration|https://docs.spring.io/spring-boot/docs/1.2.3.RELEASE/reference/html/boot-features-external-config.html]. > So, we would have to either change the base url in the > maven-wrapper.properties in k8s explicitly since we want to keep the version > information for maven-wrapper and Maven. > # Changing the urls to the self-hosted repo in maven-wrapper.properties: > ## local machine: we would have to set MVNW_USER/PASSWORD (can't due to > security risk) > ## k8s: would work since MVNW_USERNAME/PASSWORD are set > # Having maven-wrapper.jar checked in doesn't solve the issue since Maven > itself has to be downloaded as well and basic auth not set. > *Ideas:* > # be able to use [Password > Encryption|https://maven.apache.org/guides/mini/guide-encryption.html] and > have password encrypted in settings.xml or in MVNW_PASSWORD: issue of course > being that Maven Password Encryption is not available during bootstrapping. > # change the behavior of MVNW_REPOURL so that it has the highest priority > and supersedes defaults in mvnw[.cmd] script as well as in > maven-wrapper.properties: at least then we can keep a correct > maven-wrapper.properties (w/ self-hosted Maven repo) and set MVNW_REPOURL to > Maven Central on local machine for bootstrapping. > *Proposed semi-solution:* > * Change priority of MVNW_REPOURL or, for backwards compatibility, add > another environment variable which supersedes all other settings -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MWRAPPER-46) Simplify use of Maven Wrapper project in different environments
Jimisola Laursen created MWRAPPER-46: Summary: Simplify use of Maven Wrapper project in different environments Key: MWRAPPER-46 URL: https://issues.apache.org/jira/browse/MWRAPPER-46 Project: Maven Wrapper Issue Type: Improvement Affects Versions: 3.1.0 Reporter: Jimisola Laursen I'll describe our use-case as I suspect that we might not be alone with this one. This ticket relates to: # MVNW_REPOURL being insufficient # user not being able to set MVNW_USERNAME/PASSWORD in plain text due security *Prerequisites:* * _Self-hosted Maven 2 repo that requires basic auth_ (Nexus with proxy for Maven Central) * Environments: ** Local machine: need to use proxy for Internet, can't set MVNW_USERNAME/PASSWORD in plain text due security ** Pipeline/Deployment (k8s): need to use proxy for Internet, MVNW_USERNAME/PASSWORD are set * We want to be able to specify wrapper and/or Maven version (hence, use maven-wrapper.properties) *Use-case:* all downloads, but local and in cluster/cloud, should go via our self-hosted Maven 2 repo that requires basic auth *Setup cases:* # Setting MVNW_REPOURL in both environments causes two problems: ## local machine: we would have to set MVNW_USER/PASSWORD (can't due to security risk) ## k8s: MVNW_REPOURL environment variable, strangely, doesn't override value in maven-wrapper.properties, but vice versa. Is this really common practise? Compare with e.g. [Spring Boot's Externalized Configuration|https://docs.spring.io/spring-boot/docs/1.2.3.RELEASE/reference/html/boot-features-external-config.html]. So, we would have to either change the base url in the maven-wrapper.properties in k8s explicitly since we want to keep the version information for maven-wrapper and Maven. # Changing the urls to the self-hosted repo in maven-wrapper.properties: ## local machine: we would have to set MVNW_USER/PASSWORD (can't due to security risk) ## k8s: would work since MVNW_USERNAME/PASSWORD are set # Having maven-wrapper.jar checked in doesn't solve the issue since Maven itself has to be downloaded as well and basic auth not set. *Ideas:* # be able to use [Password Encryption|https://maven.apache.org/guides/mini/guide-encryption.html] and have password encrypted in settings.xml or in MVNW_PASSWORD: issue of course being that Maven Password Encryption is not available during bootstrapping. # change the behavior of MVNW_REPOURL so that it has the highest priority and supersedes defaults in mvnw[.cmd] script as well as in maven-wrapper.properties: at least then we can keep a correct maven-wrapper.properties (w/ self-hosted Maven repo) and set MVNW_REPOURL to Maven Central on local machine for bootstrapping. *Proposed semi-solution:* * Change priority of MVNW_REPOURL or, for backwards compatibility, add another environment variable which supersedes all other settings -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-7335) [Regression] Parallel build fails due to missing JAR artifacts in compilePath
[
https://issues.apache.org/jira/browse/MNG-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463938#comment-17463938
]
Hudson commented on MNG-7335:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #296
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/296/
> [Regression] Parallel build fails due to missing JAR artifacts in compilePath
> -
>
> Key: MNG-7335
> URL: https://issues.apache.org/jira/browse/MNG-7335
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.4, 4.0.0-alpha-1
> Environment: - Linux (tested Docker using maven:3-jdk-8 tag): happens
> most times.
> - Windows 10: happens sometimes.
>Reporter: Falko Modler
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.8.5
>
>
> *The following was cloned from MNG-6843 which was fixed in 3.8.2 and 3.8.3,
> but came back in 3.8.4 due to MNG-7312:*
> Build of our multi module (57) Java maven project is failing phase when
> running it as parallel in 4 threads (mvn -T 4 clean install). The failure
> happens during compilation because packages/classes from compile dependencies
> cannot be found:
> {noformat}
> [main] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile
> (default-compile) on project common: Compilation failure: Compilation
> failure:
> [main] [ERROR]
> /home/common/src/main/java/com/foo/ZonedDateTimeParser.java:[6,32] package
> org.apache.commons.lang3 does not exist{noformat}
> After enabling debug logging (with thread names) I have found out that a
> compile path of the failing module is empty (besides target/classes):
> When running in 4 threads (-T 4):
> {noformat}
> [BuilderThread 2] [DEBUG] (f) compilePath = [/home/common/target/classes]
> ...
> [BuilderThread 2] [DEBUG] Command line options:
> [BuilderThread 2] [DEBUG] -d /home/common/target/classes -classpath
> /home/common/target/classes: -sourcepath
> /home/common/src/main/java:/home/common/target/generated-sources/annotations:
> -s /home/common/target/generated-sources/annotations -g -nowarn -target 1.8
> -source 1.8 -encoding UTF-8{noformat}
> When running in a single thread (-T 1):
> {noformat}
> [BuilderThread 0] [DEBUG] (f) compilePath = [/home/common/target/classes,
> /root/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar,
>
> /root/.m2/repository/commons-collections/commons-collections/3.2.2/commons-collections-3.2.2.jar,
>
> /root/.m2/repository/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar,
>
> /root/.m2/repository/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.jar,
> /root/.m2/repository/org/jooq/jool-java-8/0.9.14/jool-java-8-0.9.14.jar,
> /root/.m2/repository/org/slf4j/slf4j-api/1.7.26/slf4j-api-1.7.26.jar,
> /root/.m2/repository/org/springframework/spring-beans/5.1.8.RELEASE/spring-beans-5.1.8.RELEASE.jar,
>
> /root/.m2/repository/org/springframework/spring-core/5.1.8.RELEASE/spring-core-5.1.8.RELEASE.jar,
>
> /root/.m2/repository/org/springframework/spring-context/5.1.8.RELEASE/spring-context-5.1.8.RELEASE.jar]
> ...
> [BuilderThread 0] [DEBUG] Command line options:
> [BuilderThread 0] [DEBUG] -d /home/common/target/classes -classpath
> /home/common/target/classes:/root/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar:/root/.m2/repository/commons-collections/commons-collections/3.2.2/commons-collections-3.2.2.jar:/root/.m2/repository/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar:/root/.m2/repository/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.jar:/root/.m2/repository/org/jooq/jool-java-8/0.9.14/jool-java-8-0.9.14.jar:/root/.m2/repository/org/slf4j/slf4j-api/1.7.26/slf4j-api-1.7.26.jar:/root/.m2/repository/org/springframework/spring-beans/5.1.8.RELEASE/spring-beans-5.1.8.RELEASE.jar:/root/.m2/repository/org/springframework/spring-core/5.1.8.RELEASE/spring-core-5.1.8.RELEASE.jar:/root/.m2/repository/org/springframework/spring-context/5.1.8.RELEASE/spring-context-5.1.8.RELEASE.jar:
> -sourcepath
> /home/common/src/main/java:/home/common/target/generated-sources/annotations:
> -s /home/common/target/generated-sources/annotations -g -nowarn -target 1.8
> -source 1.8 -encoding UTF-8{noformat}
> After adding custom log messages I have found out that the root cause is that
> org.apache.maven.project.MavenProject.setArtifactFilter() is called with null
> artifactFilter parameter. The call happens for the failing module from a
> thread that is building another module. The call stack is:
> {code:java}
> "BuilderThread 0@2513" prio=5 tid=0xe nid=NA runnable
> java.lang.Thread.State: RUNNA
[jira] [Assigned] (MSHARED-997) Failed / error test DefaultProjectDependencyAnalyzerTest in maven-dependency-analyzer
[
https://issues.apache.org/jira/browse/MSHARED-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski reassigned MSHARED-997:
---
Assignee: Slawomir Jaranowski
> Failed / error test DefaultProjectDependencyAnalyzerTest in
> maven-dependency-analyzer
> -
>
> Key: MSHARED-997
> URL: https://issues.apache.org/jira/browse/MSHARED-997
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-analyzer
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Critical
>
> There is no possibility to build project by:
> {code:java}
> mvn clean verify
> {code}
> Tested last commit: {{b6adba0bcda5036a9bc59e23be2976672b729198}}
> Maven and java versin:
> {code:java}
> Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
> Maven home: /usr/local/Cellar/maven/3.8.2/libexec
> Java version: 1.8.0_302, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@8/1.8.0+302/libexec/openjdk.jdk/Contents/Home/jre
> {code}
> I have many logs like:
> {code:java}
> 37) No implementation for
> java.util.Set
> was bound.
> while locating
> java.util.Set
> for parameter 0 at
> org.eclipse.aether.internal.impl.DefaultLocalRepositoryProvider.(Unknown
> Source)
> while locating
> org.eclipse.aether.internal.impl.DefaultLocalRepositoryProvider
> at ClassRealm[plexus.core, parent: null]
> at ClassRealm[plexus.core, parent: null]
> while locating org.eclipse.aether.impl.LocalRepositoryProvider
> for parameter 8 at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.(Unknown
> Source)
> while locating org.eclipse.aether.internal.impl.DefaultRepositorySystem
> at ClassRealm[plexus.core, parent: null]
> at ClassRealm[plexus.core, parent: null]
> while locating org.eclipse.aether.RepositorySystem
> while locating org.apache.maven.artifact.resolver.DefaultArtifactResolver
> at ClassRealm[plexus.core, parent: null]
> at ClassRealm[plexus.core, parent: null]
> {code}
> and test result:
> {code:java}
> INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [ERROR]
> DefaultProjectDependencyAnalyzerTest.setUp:81->PlexusTestCase.lookup:199 »
> ComponentLookup
> [INFO]
> [ERROR] Tests run: 101, Failures: 0, Errors: 15, Skipped: 0
> {code}
> h3. Build on Apache Jenkins
> There is also strange behavior that {{jenkins}} build also has similar errors
> - but failed tests aren't reported.
> [https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dependency-analyzer/job/master/]
> h3. Build on GitHub
> There is also the same problem on GitHub:
> https://github.com/apache/maven-dependency-analyzer/actions
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (SUREFIRE-1969) Support for Java 17 LTS
Casper Roubos created SUREFIRE-1969: --- Summary: Support for Java 17 LTS Key: SUREFIRE-1969 URL: https://issues.apache.org/jira/browse/SUREFIRE-1969 Project: Maven Surefire Issue Type: Improvement Components: Maven Surefire Plugin Reporter: Casper Roubos Hi, Will there be a version of surefire that supports java 17? Thanks in advance. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-dependency-analyzer] johnlinp commented on pull request #7: [MDEP-679] mvn dependency:analyze detected wrong transitive dependency
johnlinp commented on pull request #7: URL: https://github.com/apache/maven-dependency-analyzer/pull/7#issuecomment-999680776 Thank you for integrating my commits into `master`. -- 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] (MSHARED-1003) Require Maven 3.2.5+
[ https://issues.apache.org/jira/browse/MSHARED-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463897#comment-17463897 ] Slawomir Jaranowski commented on MSHARED-1003: -- Is this issue for both components? - maven-dependency-analyzer - maven-filtering > Require Maven 3.2.5+ > > > Key: MSHARED-1003 > URL: https://issues.apache.org/jira/browse/MSHARED-1003 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-dependency-analyzer, maven-filtering >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: maven-filtering-3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-shade-plugin] slachiewicz closed pull request #107: Bump maven-dependency-tree from 3.0.1 to 3.1.0
slachiewicz closed pull request #107: URL: https://github.com/apache/maven-shade-plugin/pull/107 -- 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-shade-plugin] dependabot[bot] commented on pull request #107: Bump maven-dependency-tree from 3.0.1 to 3.1.0
dependabot[bot] commented on pull request #107: URL: https://github.com/apache/maven-shade-plugin/pull/107#issuecomment-999642012 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
[jira] [Commented] (SUREFIRE-1517) Getting ClassNotFoundException when filtering tests from a dependency jar
[
https://issues.apache.org/jira/browse/SUREFIRE-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463859#comment-17463859
]
Slawomir Jaranowski commented on SUREFIRE-1517:
---
Can you try with the latest version 3.0.0-M5?
> Getting ClassNotFoundException when filtering tests from a dependency jar
> -
>
> Key: SUREFIRE-1517
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1517
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.21.0
> Environment: Windows
>Reporter: simon cierniak
>Priority: Minor
> Attachments: 2018-04-19T12-07-18_153-jvmRun1.dump
>
>
> The issue happens only when I am using tests from a test jar (using option
> dependenciesToScan) and when tests are not into a final package meaning
> having sub-package. FYI, I am executing Spock tests.
> To create my test jar, I followed doc
> [https://maven.apache.org/plugins/maven-jar-plugin/examples/create-test-jar.html]
>
> *+Structure+*
> {noformat}
> com.bug.package1.ASpec
> com.bug.package1.BSpec
> com.bug.package2.CSpec
> com.bug.package2.DSpec
> com.bug.package2.subpackage.C1Spec
> com.bug.package2.subpackage.C2Spec
> {noformat}
>
> +*Commands:*+
> mvn test -Dtest=***/*Spec* works : execute ASpec, BSpec, CSpec,
> DSpec, C1Spec and C2Spec
> mvn test -Dtest=ASpec works : execute ASpec
> mvn test -Dtest=***/package1/** works : execute ASpec and BSpec
> mvn test -Dtest=C1Spec works : execute C1Spec
> mvn test -Dtest=***/package2/subpackage/** works : execute C1Spec and C2Spec
> mvn test -Dtest=CSpec works : execute CSpec
> {color:#ff}mvn test -Dtest=***/package2/** fails with error:
> RuntimeException: Unable to create test class 'com.bug.package2.subpackage.'
> ... caused by: java.lang.ClassNotFoundException:
> com.bug.package2.subpackage.{color}
> {color:#ff}The tests executed should be CSpec and DSpec{color}
> same error when filtering by com/bug/***/**
>
> +*Pom.xml*+
> {noformat}
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.bug
> demo-execution
> 1.0-SNAPSHOT
> jar
> Test Bug
>
> UTF-8
> 2.4.5
> 1.0-groovy-2.4
> false
> **/*Spec.java
>
>
>
>
> 4.11
> 1.1.1
> 2.21.0
>
>
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> ${surefire.version}
>
>
> org.apache.maven.surefire
> surefire-junit47
> ${surefire.version}
>
>
>
> ${skipTests}
> true
> false
> true
> true
>
> com.bug:demo-tests
>
>
>
> ${SpockTests}
>
>
>
>
> ${junit.groups}
> ${junit.excludedGroups}
>
>
>
>
>
>
> com.bug
> demo-tests
> 1.0
>
>
>
> {noformat}
>
> I tested also with version 2.20.1 and 2.19.1 and got same errors.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SUREFIRE-1517) Getting ClassNotFoundException when filtering tests from a dependency jar
[
https://issues.apache.org/jira/browse/SUREFIRE-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated SUREFIRE-1517:
--
Labels: waiting-for-feedback (was: )
> Getting ClassNotFoundException when filtering tests from a dependency jar
> -
>
> Key: SUREFIRE-1517
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1517
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.21.0
> Environment: Windows
>Reporter: simon cierniak
>Priority: Minor
> Labels: waiting-for-feedback
> Attachments: 2018-04-19T12-07-18_153-jvmRun1.dump
>
>
> The issue happens only when I am using tests from a test jar (using option
> dependenciesToScan) and when tests are not into a final package meaning
> having sub-package. FYI, I am executing Spock tests.
> To create my test jar, I followed doc
> [https://maven.apache.org/plugins/maven-jar-plugin/examples/create-test-jar.html]
>
> *+Structure+*
> {noformat}
> com.bug.package1.ASpec
> com.bug.package1.BSpec
> com.bug.package2.CSpec
> com.bug.package2.DSpec
> com.bug.package2.subpackage.C1Spec
> com.bug.package2.subpackage.C2Spec
> {noformat}
>
> +*Commands:*+
> mvn test -Dtest=***/*Spec* works : execute ASpec, BSpec, CSpec,
> DSpec, C1Spec and C2Spec
> mvn test -Dtest=ASpec works : execute ASpec
> mvn test -Dtest=***/package1/** works : execute ASpec and BSpec
> mvn test -Dtest=C1Spec works : execute C1Spec
> mvn test -Dtest=***/package2/subpackage/** works : execute C1Spec and C2Spec
> mvn test -Dtest=CSpec works : execute CSpec
> {color:#ff}mvn test -Dtest=***/package2/** fails with error:
> RuntimeException: Unable to create test class 'com.bug.package2.subpackage.'
> ... caused by: java.lang.ClassNotFoundException:
> com.bug.package2.subpackage.{color}
> {color:#ff}The tests executed should be CSpec and DSpec{color}
> same error when filtering by com/bug/***/**
>
> +*Pom.xml*+
> {noformat}
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.bug
> demo-execution
> 1.0-SNAPSHOT
> jar
> Test Bug
>
> UTF-8
> 2.4.5
> 1.0-groovy-2.4
> false
> **/*Spec.java
>
>
>
>
> 4.11
> 1.1.1
> 2.21.0
>
>
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> ${surefire.version}
>
>
> org.apache.maven.surefire
> surefire-junit47
> ${surefire.version}
>
>
>
> ${skipTests}
> true
> false
> true
> true
>
> com.bug:demo-tests
>
>
>
> ${SpockTests}
>
>
>
>
> ${junit.groups}
> ${junit.excludedGroups}
>
>
>
>
>
>
> com.bug
> demo-tests
> 1.0
>
>
>
> {noformat}
>
> I tested also with version 2.20.1 and 2.19.1 and got same errors.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-integration-testing] asfgit closed pull request #130: [MNG-7335] Make IT compatible with Java 7
asfgit closed pull request #130: URL: https://github.com/apache/maven-integration-testing/pull/130 -- 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-6795) define a replacement for ReasonPhrase to display details about transfert failures
[ https://issues.apache.org/jira/browse/MNG-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-6795: --- Description: as documented in WAGON-541 [372aa52c80c2f7b458c095d837e15ebeafbdf0b7|https://gitbox.apache.org/repos/asf?p=maven-wagon.git&a=commit&h=372aa52c80c2f7b458c095d837e15ebeafbdf0b7], ReasonPhrase has been removed from HTTP/2 and deprecated (optional) in HTTP/1.1 for more than five years. It is useful to give detailed error messages on artifact transfert errors with a repository manager. A replacement has to be found was: as documented in WAGON-541 [372aa52c80c2f7b458c095d837e15ebeafbdf0b7|https://gitbox.apache.org/repos/asf?p=maven-wagon.git&a=commit&h=372aa52c80c2f7b458c095d837e15ebeafbdf0b7], ReasonPhrase has been removed from HTTP/2 and deprecated (optional) in HTTP/1.1 for more than five years. It is useful to give detailed error messages on artifact transfert errors with a repository manager. A replacement has to be found > define a replacement for ReasonPhrase to display details about transfert > failures > - > > Key: MNG-6795 > URL: https://issues.apache.org/jira/browse/MNG-6795 > Project: Maven > Issue Type: Task > Components: Artifacts and Repositories >Affects Versions: 3.3.9, 3.6.3 >Reporter: Herve Boutemy >Priority: Major > Fix For: 4.0.x-candidate > > > as documented in WAGON-541 > [372aa52c80c2f7b458c095d837e15ebeafbdf0b7|https://gitbox.apache.org/repos/asf?p=maven-wagon.git&a=commit&h=372aa52c80c2f7b458c095d837e15ebeafbdf0b7], > ReasonPhrase has been removed from HTTP/2 and deprecated (optional) in > HTTP/1.1 for more than five years. > It is useful to give detailed error messages on artifact transfert errors > with a repository manager. > A replacement has to be found -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven] michael-o commented on a change in pull request #621: [MNG-7347] SessionScoped beans should be singletons for a given session
michael-o commented on a change in pull request #621:
URL: https://github.com/apache/maven/pull/621#discussion_r773804726
##
File path:
maven-core/src/main/java/org/apache/maven/lifecycle/internal/LifecycleModuleBuilder.java
##
@@ -89,8 +89,12 @@ public void buildProject( MavenSession session, MavenSession
rootSession, Reacto
// session may be different from rootSession seeded in DefaultMaven
// explicitly seed the right session here to make sure it is used by
Guice
-sessionScope.enter( reactorContext.getSessionScopeMemento() );
Review comment:
I have no idea what `getSessionScopeMemento()`, but can you explain why
it is not required anymore?
##
File path:
maven-core/src/main/java/org/apache/maven/lifecycle/internal/ReactorContext.java
##
@@ -73,11 +68,4 @@ public ClassLoader getOriginalContextClassLoader()
return originalContextClassLoader;
}
-/**
- * @since 3.3.0
- */
-public SessionScope.Memento getSessionScopeMemento()
Review comment:
This should rather be deprecated in 3.9.0 and removed in 4.0, no?
##
File path:
maven-core/src/main/java/org/apache/maven/lifecycle/internal/LifecycleModuleBuilder.java
##
@@ -89,8 +89,12 @@ public void buildProject( MavenSession session, MavenSession
rootSession, Reacto
// session may be different from rootSession seeded in DefaultMaven
// explicitly seed the right session here to make sure it is used by
Guice
-sessionScope.enter( reactorContext.getSessionScopeMemento() );
-sessionScope.seed( MavenSession.class, session );
+final boolean scoped = session != rootSession;
Review comment:
Is reference comparison acceptable here?
##
File path:
maven-core/src/main/java/org/apache/maven/session/scope/internal/SessionScope.java
##
@@ -19,35 +19,23 @@
* under the License.
*/
-import java.util.Collections;
-import java.util.HashMap;
-import java.util.LinkedList;
+import java.util.Collection;
+import java.util.List;
import java.util.Map;
+import java.util.concurrent.ConcurrentHashMap;
+import java.util.concurrent.CopyOnWriteArrayList;
import com.google.inject.Key;
import com.google.inject.OutOfScopeException;
import com.google.inject.Provider;
import com.google.inject.Scope;
-import com.google.inject.util.Providers;
/**
* SessionScope
*/
public class SessionScope
-implements Scope
+implements Scope
{
-/**
- * @since 3.3.0
- */
-public static class Memento
Review comment:
Same here
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (MWRAPPER-43) Download of jar must be quiet by default
[
https://issues.apache.org/jira/browse/MWRAPPER-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463733#comment-17463733
]
Jorge Solórzano commented on MWRAPPER-43:
-
Well, the little trick I do is to make the _if command -v..._ that check wget
and curl to intentionally fail:
This disables the wget check:
{noformat}
sed -i 's/command -v wget/command -v wgets/' mvnw{noformat}
This disables the curl check:
{noformat}
sed -i 's/command -v curl/command -v curls/' mvnw{noformat}
Then to restore is simply swap back the correct commands:
{noformat}
sed -i 's/command -v wgets/command -v wget/' mvnw
sed -i 's/command -v curls/command -v curl/' mvnw
{noformat}
A bit hackish but doesn't require to uninstall or root and with the side effect
that you have to modify the script.
Thinking of doing more complete integration tests, those scripts require a bit
of refactoring that allows making such tests more easily and also more
maintainable.
> Download of jar must be quiet by default
>
>
> Key: MWRAPPER-43
> URL: https://issues.apache.org/jira/browse/MWRAPPER-43
> Project: Maven Wrapper
> Issue Type: Improvement
> Components: Maven Wrapper Scripts
>Affects Versions: 3.1.0
>Reporter: Jorge Solórzano
>Assignee: Herve Boutemy
>Priority: Normal
> Fix For: 3.1.1
>
>
> By default, the wrapper must be quiet, if the _maven-wrapper.jar_ is not
> found the scripts try to download the jar using {*}wget{*}, {*}curl{*}, or
> the {*}MavenWrapperDownloader{*}.java.
> The download process should only print the output when the +*MVNW_VERBOSE*+
> is set to true.
> Current output for *wget* when the maven-wrapper.jar is missing:
> {noformat}
> ./mvnw clean
> --2021-12-21 11:52:43--
> https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.1.0/maven-wrapper-3.1.0.jar
> Resolving repo.maven.apache.org (repo.maven.apache.org)... 151.101.132.215
> Connecting to repo.maven.apache.org
> (repo.maven.apache.org)|151.101.132.215|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 58727 (57K) [application/java-archive]
> Saving to: '/home/wrapper/api/.mvn/wrapper/maven-wrapper.jar'
> /home/jorsol/Trabajo/conf-worksp
> 100%[==>] 57,35K
> --.-KB/sin 0,007s
> 2021-12-21 11:52:44 (8,13 MB/s) -
> '/home/wrapper/api/.mvn/wrapper/maven-wrapper.jar' saved [58727/58727]
> 11:52:45.544 [INFO] Scanning for projects...
> ...
> {noformat}
> Current output for *curl* the maven-wrapper.jar is missing:
> {noformat}
> ./mvnw clean
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft Speed
> 100 58727 100 587270 0 1303k 0 --:--:-- --:--:-- --:--:-- 1303k
> 12:02:23.007 [INFO] Scanning for projects...
> ...
> {noformat}
> Current output for *MavenWrapperDownloader* when the maven-wrapper.jar is
> missing:
> {noformat}
> ./mvnw clean
> - Downloader started
> - Using base directory: /home/wrapper/api
> - Downloading from:
> https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.1.0/maven-wrapper-3.1.0.jar
> - Downloading to: /home/wrapper/api/.mvn/wrapper/maven-wrapper.jar
> Done
> 11:50:21.599 [INFO] Scanning for projects...
> ...
> {noformat}
> Everything between the _./mvnw_ and the first _INFO_ is just unwanted
> verbosity.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (MWRAPPER-45) Migrate/Sync startup scripts with Maven 4
[ https://issues.apache.org/jira/browse/MWRAPPER-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463692#comment-17463692 ] Michael Osipov edited comment on MWRAPPER-45 at 12/22/21, 10:22 AM: Please note that improvements to the scripts are not complete in Maven 4. was (Author: michael-o): Please note that improvements to the scripts are not complete. > Migrate/Sync startup scripts with Maven 4 > - > > Key: MWRAPPER-45 > URL: https://issues.apache.org/jira/browse/MWRAPPER-45 > Project: Maven Wrapper > Issue Type: Task > Components: Maven Wrapper Scripts >Affects Versions: 3.1.0 >Reporter: Michael Osipov >Priority: Major > > The scripts are Maven 3 based. Maven 4 has simplified the scripts and > introduced consistency improvements. We should port those over for version 4?! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-invoker-plugin] slachiewicz merged pull request #84: Bump extra-enforcer-rules from 1.4 to 1.5.1
slachiewicz merged pull request #84: URL: https://github.com/apache/maven-invoker-plugin/pull/84 -- 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-checkstyle-plugin] slachiewicz merged pull request #61: Bump doxiaVersion from 1.10 to 1.11.1
slachiewicz merged pull request #61: URL: https://github.com/apache/maven-checkstyle-plugin/pull/61 -- 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
