You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/docs/asciidoc/gradle-plugin.adoc
+1-57Lines changed: 1 addition & 57 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -249,6 +249,7 @@ graalvmNative {
249
249
250
250
NOTE: For options that can be set using command-line, if both DSL and command-line options are present, command-line options take precedence.
251
251
252
+
[[long_classpath_and_fat_jar_support]]
252
253
==== Long classpath and fat jar support
253
254
254
255
Under Windows, https://github.com/graalvm/native-build-tools/issues/85[it is possible that the length of the classpath exceeds what the operating system supports] when invoking the CLI to build a native image.
@@ -326,60 +327,3 @@ The generated configuration files will be found in the `${buildDir}/native/agent
326
327
== Javadocs
327
328
328
329
In addition, you can consult the link:javadocs/native-gradle-plugin/index.html[Javadocs of the plugin].
329
-
330
-
[[changelog]]
331
-
== Changelog
332
-
333
-
=== Release 0.9.3
334
-
335
-
In preparation for supporting more images:
336
-
337
-
- The `nativeBuild` and `nativeTest` extensions are now deprecated. A top-level container for configuring native images has been introduced. Instead of:
338
-
339
-
```groovy
340
-
nativeBuild {
341
-
verbose = true
342
-
}
343
-
```
344
-
345
-
you need to use:
346
-
347
-
```groovy
348
-
graalvmNative {
349
-
binaries {
350
-
main {
351
-
verbose = true
352
-
}
353
-
}
354
-
}
355
-
```
356
-
357
-
and instead of:
358
-
359
-
```groovy
360
-
nativeTest {
361
-
buildArgs("...")
362
-
}
363
-
```
364
-
365
-
you need to use:
366
-
367
-
```groovy
368
-
graalvmNative {
369
-
binaries {
370
-
test {
371
-
verbose = true
372
-
}
373
-
}
374
-
}
375
-
```
376
-
377
-
- The `nativeBuild` task has been renamed to `nativeCompile`.
378
-
- The `nativeTestBuild` task has been renamed to `nativeTestCompile`.
379
-
380
-
Both `nativeBuild` and `nativeTestBuild` task invocations are still supported but deprecated and will be removed in a future release.
Copy file name to clipboardExpand all lines: docs/src/docs/asciidoc/index.adoc
+148Lines changed: 148 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,3 +11,151 @@ Please refer to the following pages for build tool specific documentation:
11
11
- The <<maven-plugin.adoc#,Maven plugin documentation>>
12
12
13
13
If you are interested in contributing, please refer to our https://github.com/graalvm/native-build-tools[Git repository].
14
+
15
+
[[changelog]]
16
+
== Changelog
17
+
18
+
=== Release 0.9.5
19
+
20
+
This release contains, in preparation for supporting more images in the Gradle plugin:
21
+
22
+
- The `nativeBuild` and `nativeTest` extensions are now deprecated. A top-level container for configuring native images has been introduced. Instead of:
23
+
24
+
[source,groovy]
25
+
----
26
+
nativeBuild {
27
+
verbose = true
28
+
}
29
+
----
30
+
31
+
you need to use:
32
+
33
+
[source,groovy]
34
+
----
35
+
graalvmNative {
36
+
binaries {
37
+
main {
38
+
verbose = true
39
+
}
40
+
}
41
+
}
42
+
----
43
+
44
+
and instead of:
45
+
46
+
[source,groovy]
47
+
----
48
+
nativeTest {
49
+
buildArgs("...")
50
+
}
51
+
----
52
+
53
+
you need to use:
54
+
55
+
[source,groovy]
56
+
----
57
+
graalvmNative {
58
+
binaries {
59
+
test {
60
+
verbose = true
61
+
}
62
+
}
63
+
}
64
+
----
65
+
66
+
- The `nativeBuild` task has been renamed to `nativeCompile`.
67
+
- The `nativeTestBuild` task has been renamed to `nativeTestCompile`.
68
+
69
+
Both `nativeBuild` and `nativeTestBuild` task invocations are still supported but deprecated and will be removed in a future release.
70
+
71
+
=== Release 0.9.4
72
+
73
+
This release works around a limitation for Windows users who encounter an issue with long classpath entries on CLI: the Gradle plugin will now automatically handle this problem by creating a fat jar instead of passing all entries on classpath (this behavior can be <<gradle-plugin.adoc#long_classpath_and_fat_jar_support, disabled>>) if needed).
74
+
Maven users will have to <<maven-plugin.adoc#long_classpath_and_shading_support, configure their build differently>> to use shading.
75
+
76
+
In addition to this, we're now publishing development snapshots of this plugin. For Gradle, you will need to declare this repository in your settings.gradle(.kts) file:
77
+
78
+
[source,groovy]
79
+
----
80
+
pluginManagement {
81
+
plugins {
82
+
id 'org.graalvm.buildtools.native' version '0.9.5-SNAPSHOT'
Copy file name to clipboardExpand all lines: docs/src/docs/asciidoc/maven-plugin.adoc
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,6 +170,7 @@ This step won't be needed as of JUnit 5.8 with a future release of native-maven-
170
170
171
171
Running `mvn -Pnative -Dskip test` will then build and run native tests.
172
172
173
+
[[long_classpath_and_shading_support]]
173
174
== Long classpath and shading support
174
175
175
176
Under Windows, https://github.com/graalvm/native-build-tools/issues/85[it is possible that the length of the classpath exceeds what the operating system supports] when invoking the CLI to build a native image.
0 commit comments