@@ -63,19 +63,6 @@ cf install-plugin https://github.com/SAP/cf-cli-java-plugin/releases/download/sn
63
63
cf install-plugin https://github.com/SAP/cf-cli-java-plugin/releases/download/snapshot/cf-cli-java-plugin-linux-amd64
64
64
```
65
65
66
- ### Updating from version 1.x to 2.x
67
-
68
- With release 2.0 we aligned the convention of the plugin having the same name as the command it contributes (in our
69
- case, ` java ` ). This change mostly affects you in the way you update your plugin. If you have the version 1.x installed,
70
- you will need to uninstall the old version first by using the command: ` cf uninstall-plugin JavaPlugin ` . You know you
71
- have the version 1.x installed if ` JavaPlugin ` appears in the output of ` cf plugins ` .
72
-
73
- ### Permission Issues
74
-
75
- On Linux and macOS, if you get a permission error, run ` chmod +x [cf-cli-java-plugin] ` (replace ` [cf-cli-java-plugin] `
76
- with the actual binary name you will use, which depends on the OS you are running) on the plugin binary. On Windows, the
77
- plugin will refuse to install unless the binary has the ` .exe ` file extension.
78
-
79
66
## Usage
80
67
81
68
### Prerequisites
@@ -288,6 +275,13 @@ USAGE:
288
275
Get the status of async-profiler on a running Java application
289
276
290
277
OPTIONS :
278
+ -dry-run -n, just output to command line what would be executed
279
+ -keep -k, keep the heap dump in the container; by default the heap dump/JFR/... will
280
+ be deleted from the container's filesystem after being downloaded
281
+ -local-dir -ld, the local directory path that the dump/JFR/... file will be saved to,
282
+ defaults to the current directory
283
+ -no-download -nd, don't download the heap dump/JFR/... file to local, only keep it in the
284
+ container, implies '--keep'
291
285
-verbose -v, enable verbose output for the plugin
292
286
-app-instance-index -i [index], select to which instance of the app to connect
293
287
-args -a, Miscellaneous arguments to pass to the command (if supported) in the
@@ -298,13 +292,6 @@ OPTIONS:
298
292
application name, and generated file name respectively.
299
293
-container-dir -cd, the directory path in the container that the heap dump/JFR/... file will be
300
294
saved to
301
- -dry-run -n, just output to command line what would be executed
302
- -keep -k, keep the heap dump in the container; by default the heap dump/JFR/... will
303
- be deleted from the container's filesystem after being downloaded
304
- -local-dir -ld, the local directory path that the dump/JFR/... file will be saved to,
305
- defaults to the current directory
306
- -no-download -nd, don't download the heap dump/JFR/... file to local, only keep it in the
307
- container, implies '--keep'
308
295
309
296
</pre>
310
297
0 commit comments