Skip to content

Commit a7ff98d

Browse files
jfdenisejfdenise
authored
Merge pull request #31 from jfdenise/master
Fix for #30, rename jar suffix to -bootable
2 parents 8c893bf + 4d0761d commit a7ff98d

12 files changed

Lines changed: 27 additions & 27 deletions

File tree

‎README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,13 @@ A WildFly bootable jar contains both the server and your packaged application (a
55
Once the application has been built and packaged as a bootable jar, you can start the application using the following command:
66

77
```
8-
java -jar target/myapp-wildfly.jar
8+
java -jar target/myapp-bootable.jar
99
```
1010

1111
To get the list of the startup arguments:
1212

1313
```
14-
java -jar target/myapp-wildfly.jar --help
14+
java -jar target/myapp-bootable.jar --help
1515
```
1616

1717
A WildFly bootable jar behave in a way that is similar to a WildFly server installed on file system:

‎docs/guide/intro/index.adoc‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,13 @@ A WildFly bootable jar contains both the server and your packaged application (a
55
Once the application has been built and packaged as a bootable jar, you can start the application using the following command:
66

77
```
8-
java -jar target/myapp-wildfly.jar
8+
java -jar target/myapp-bootable.jar
99
```
1010

1111
To get the list of the startup arguments:
1212

1313
```
14-
java -jar target/myapp-wildfly.jar --help
14+
java -jar target/myapp-bootable.jar --help
1515
```
1616

1717
A WildFly bootable jar behave in a way that is similar to a WildFly server installed on file system:
@@ -148,7 +148,7 @@ The example https://github.com/wildfly-extras/wildfly-jar-maven-plugin/tree/mast
148148
When starting an hollow jar you can provide the path to a deployment you want to see deployed inside the server. For example:
149149

150150
``
151-
java -jar target/jaxrs-hollow-server-wildfly.jar --deployment=path/to/my-jaxrs-app.war
151+
java -jar target/jaxrs-hollow-server-bootable.jar --deployment=path/to/my-jaxrs-app.war
152152
``
153153

154154
NB: In order to have your deployment be located in the root context, name the war file _ROOT.war_.
@@ -321,7 +321,7 @@ When running a slim bootable jar, the default local maven repository is used to
321321
This can be overriden by using the _-Dmaven.repo.local=<path to repository>_ when launching the server, for example:
322322

323323
```
324-
java -Dmaven.repo.local=/opt/maven/maven-repo -jar jaxrs-wildfly.jar
324+
java -Dmaven.repo.local=/opt/maven/maven-repo -jar jaxrs-bootable.jar
325325
```
326326

327327
#### Generating a maven local repository during packaging

‎examples/byteman/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,6 @@ add -Djboss.modules.system.pkgs=org.jboss.byteman when launching the bootable ja
66
* Download and install byteman
77
* cd jaxrs
88
* mvn clean package
9-
* java -javaagent:${BYTEMAN_HOME}/lib/byteman.jar=script:../byteman/byteman.btm -Djboss.modules.system.pkgs=org.jboss.byteman -jar target/jaxrs-wildfly.jar
9+
* java -javaagent:${BYTEMAN_HOME}/lib/byteman.jar=script:../byteman/byteman.btm -Djboss.modules.system.pkgs=org.jboss.byteman -jar target/jaxrs-bootable.jar
1010
* Access to the application: http://127.0.0.1:8080/hello
1111
* Instrumented class logs are printed.

‎examples/https/README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ Build and run
77
=============
88

99
* mvn package
10-
* java -jar target/https-wildfly.jar
10+
* java -jar target/https-bootable.jar
1111
* https://127.0.0.1:8443/hello
1212

1313
Openshift binary build and deployment
@@ -17,7 +17,7 @@ In this example, the keystore is not packaged in the bootable jar but mounted in
1717

1818
Steps:
1919
* mvn package -Popenshift
20-
* mkdir os && cp target/https-wildfly.jar os/
20+
* mkdir os && cp target/https-bootable.jar os/
2121
* oc new-build --strategy source --binary --image-stream openjdk11 --name https-test
2222
* oc start-build https-test --from-dir ./os/
2323
* oc new-app https-test

‎examples/microprofile-config/README.adoc‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ configure the application
1010
== Run the application locally
1111

1212
* To build: `mvn package`
13-
* To run: `CONFIG1="Value comes from the env" java -jar target/microprofile-config-wildfly.jar`
13+
* To run: `CONFIG1="Value comes from the env" java -jar target/microprofile-config-bootable.jar`
1414
* Access the application: http://localhost:8080/
1515

1616
[source,bash]
@@ -28,7 +28,7 @@ config3 = Default value for config3 comes from my code
2828
[source,bash]
2929
----
3030
$ mvn package -Popenshift
31-
$ mkdir target/openshift && cp target/microprofile-config-wildfly.jar target/openshift
31+
$ mkdir target/openshift && cp target/microprofile-config-bootable.jar target/openshift
3232
# Import the OpenJDK 11 image to run the Java application
3333
$ oc import-image ubi8/openjdk-11 --from=registry.redhat.io/ubi8/openjdk-11 --confirm
3434
$ oc new-build --strategy source --binary --image-stream openjdk-11 --name microprofile-config-app

‎examples/postgresql/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ NB: postgresql server must be deployed in the cluster.
77

88
Steps:
99
* mvn package -Popenshift
10-
* mkdir os && cp target/postgresql-wildfly.jar os/
10+
* mkdir os && cp target/postgresql-bootable.jar os/
1111
* oc new-build --strategy source --binary --image-stream openjdk11 --name wf-postgresql
1212
* oc start-build wf-postgresql --from-dir ./os/
1313
* oc new-app wf-postgresql

‎examples/secmanager/README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,6 @@
33
During packaging the permission to read properties is granted to deployments.
44

55
* To build: mvn package
6-
* Update the file ./mypolicy codebase URL with absolute path to target/sec-manager-wildfly.jar
7-
* To run: java -Djava.security.manager -Djava.security.policy=mypolicy -jar target/sec-manager-wildfly.jar
6+
* Update the file ./mypolicy codebase URL with absolute path to target/sec-manager-bootable.jar
7+
* To run: java -Djava.security.manager -Djava.security.policy=mypolicy -jar target/sec-manager-bootable.jar
88
* Access the application: http://127.0.0.1:8080/hello

‎examples/secmanager/mypolicy‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
1-
grant codeBase "file:<path>/wildfly-jar-maven-plugin/examples/secmanager/target/sec-manager-wildfly.jar" {
1+
grant codeBase "file:<path>/wildfly-jar-maven-plugin/examples/secmanager/target/sec-manager-bootable.jar" {
22
permission java.security.AllPermission;
33
};

‎examples/slim/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# WildFly slim bootable jar and local maven repository generation Example
22

33
* To build: mvn package
4-
* To run: java -Dmaven.repo.local=\<absolute path to wildfly jar maven project\>/examples/slim/my-maven-repo -jar target/slim-wildfly.jar
4+
* To run: java -Dmaven.repo.local=\<absolute path to wildfly jar maven project\>/examples/slim/my-maven-repo -jar target/slim-bootable.jar
55
* Access the application: http://127.0.0.1:8080/hello

‎examples/web-clustering/README.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
# Web session sharing between multiple bootable JAR instances example
22

33
* To build: mvn package
4-
* To run first instance: java -jar target/web-clustering-wildfly.jar -Djboss.socket.binding.port-offset=10 -Djboss.node.name=node1
5-
* To run second instance: java -jar target/web-clustering-wildfly.jar -Djboss.node.name=node2
4+
* To run first instance: java -jar target/web-clustering-bootable.jar -Djboss.socket.binding.port-offset=10 -Djboss.node.name=node1
5+
* To run second instance: java -jar target/web-clustering-bootable.jar -Djboss.node.name=node2
66
* Access the application running in the first instance: http://127.0.0.1:8080
77
* Note sessionID and user creation time.
88
* Kill first instance
@@ -20,7 +20,7 @@ Openshift binary build and deployment
2020

2121
Steps:
2222
* mvn package -Popenshift
23-
* mkdir os && cp target/web-clustering-wildfly.jar os/
23+
* mkdir os && cp target/web-clustering-bootable.jar os/
2424
* oc policy add-role-to-user view system:serviceaccount:$(oc project -q):default
2525
* oc new-build --strategy source --binary --image-stream openjdk11 --name web-clustering
2626
* oc start-build web-clustering --from-dir ./os/

0 commit comments

Comments
 (0)