Skip to content

Commit f234859

Browse files
committed
Remove grails.util.BuildScope documentation
grails.util.BuildScope was removed in Grails 4
1 parent f1febac commit f234859

File tree

1 file changed

+3
-12
lines changed

1 file changed

+3
-12
lines changed

grails-doc/src/en/guide/plugins/understandingPluginLoadOrder.adoc

Lines changed: 3 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -99,23 +99,14 @@ It's not only plugin load order that you can control. You can also specify which
9999
[source,groovy]
100100
----
101101
def environments = ['development', 'test', 'myCustomEnv']
102-
def scopes = [excludes:'war']
103102
----
104103

105-
In this example, the plugin will only load in the 'development' and 'test' environments. Nor will it be packaged into the WAR file, because it's excluded from the 'war' phase. This allows `development-only` plugins to not be packaged for production use.
104+
In this example, the plugin will only load in the 'development' and 'test' environments.
106105

107-
The full list of available scopes are defined by the enum link:{api}grails/util/BuildScope.html[BuildScope], but here's a summary:
108-
109-
* `test` - when running tests
110-
* `functional-test` - when running functional tests
111-
* `run` - for run-app and run-war
112-
* `war` - when packaging the application as a WAR file
113-
* `all` - plugin applies to all scopes (default)
114-
115-
Both properties can be one of:
106+
The properties can be one of:
116107

117108
* a string - a sole inclusion
118-
* a list - a list of environments or scopes to include
109+
* a list - a list of environments to include
119110
* a map - for full control, with 'includes' and/or 'excludes' keys that can have string or list values
120111

121112
For example,

0 commit comments

Comments
 (0)