[GitHub] [maven-dependency-plugin] ian-lavallee commented on pull request #80: [MDEP-708] dependency:analyze should recommend test scope where possible

ian-lavallee commented on pull request #80: URL: https://github.com/apache/maven-dependency-plugin/pull/80#issuecomment-669277156 @elharo can you trigger a CI build for this branch? This is an automated message from the

[GitHub] [maven-dependency-plugin] ian-lavallee commented on pull request #80: [MDEP-708] dependency:analyze should recommend test scope where possible

ian-lavallee commented on pull request #80: URL: https://github.com/apache/maven-dependency-plugin/pull/80#issuecomment-665743730 This PR needs a 1.11.3-SNAPSHOT dependency-analyzer so that the test for compileScopedTestDependencies passes. Currently it fails because in 1.11.2 the

[GitHub] [maven-dependency-plugin] ian-lavallee commented on pull request #80: [MDEP-708] dependency:analyze should recommend test scope where possible

ian-lavallee commented on pull request #80: URL: https://github.com/apache/maven-dependency-plugin/pull/80#issuecomment-662583514 Should I change it to depend on 1.12.0 even though that's not released now then? This is an

[GitHub] [maven-dependency-plugin] ian-lavallee commented on pull request #80: [MDEP-708] dependency:analyze should recommend test scope where possible

ian-lavallee commented on pull request #80: URL: https://github.com/apache/maven-dependency-plugin/pull/80#issuecomment-662560710 Not because of the last commit relying on the new dependency-analyzer we need 1.11.3-SNAPSHOT for the analyzer now.