Skip to content

Commit 2e99c1d

Browse files
Dropping import scope validity in favour of compile, given import is only applicable for dependencies in dependencyManagement
1 parent 1da321f commit 2e99c1d

2 files changed

Lines changed: 2 additions & 3 deletions

File tree

rewrite-maven/src/main/java/org/openrewrite/maven/AddDependency.java

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -76,9 +76,9 @@ public class AddDependency extends ScanningRecipe<AddDependency.Scanned> {
7676

7777
@Option(displayName = "Scope",
7878
description = "A scope to use when it is not what can be inferred from usage. Most of the time this will be left empty, but " +
79-
"is used when adding a runtime, provided, or import dependency.",
79+
"is used when adding a runtime, provided, or test dependency.",
8080
example = "runtime",
81-
valid = {"import", "runtime", "provided", "test"},
81+
valid = {"compile", "runtime", "provided", "test"},
8282
required = false)
8383
@Nullable
8484
String scope;

rewrite-maven/src/test/java/org/openrewrite/maven/AddDependencyTest.java

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,6 @@
1717

1818
import org.intellij.lang.annotations.Language;
1919
import org.jspecify.annotations.Nullable;
20-
import org.junit.jupiter.api.Disabled;
2120
import org.junit.jupiter.api.Test;
2221
import org.junit.jupiter.params.ParameterizedTest;
2322
import org.junit.jupiter.params.provider.ValueSource;

0 commit comments

Comments
 (0)