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: README.md
+32-2Lines changed: 32 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,12 +18,34 @@ Minimum Java version compatibility table
18
18
19
19
|| Min. Java version | WM client version(s) |
20
20
|---|--------------|----------------------|
21
-
|| 8 | 2.1.3 |
21
+
|| 8 | 2.1.3 and above|
22
22
|| 7 | 2.1.0 |
23
23
|| 6 | 2.0.0 |
24
24
25
25
Version 2.1.2 (Java 7) and 2.1.3 (Java 8) only differ in their dependencies (see CHANGELOG)
26
26
27
+
### Compiling the client and the example project
28
+
29
+
```
30
+
mvn clean install
31
+
```
32
+
run on the wmclient directory, compiles the client and installs it in your local maven repository. The command also
33
+
runs the unit tests against a running instance of the WURFL Microservice server. Tests fails if no server is running.
34
+
35
+
** Note that from version 2.1.7, client artifact produced by mvn commands have their name aligned with the maven artifact
36
+
naming, changing from wm-client-java-x.y.z.jar to wurfl-microservice-x.y.z.jar.
37
+
38
+
To compile the example project, move to the example directory and run:
39
+
40
+
```
41
+
mvn clean compile package
42
+
```
43
+
44
+
to generate an executable jar file with all the needed dependencies.
45
+
You need to compile the client first, because the example project depends on the it.
46
+
47
+
In order to work, the example project needs a running instance of the WURFL Microservice server to connect to.
48
+
27
49
The Example project contains an example of client api usage for a console application :
28
50
29
51
@@ -221,7 +243,7 @@ Wurfl microservice client java only depends on the servlet API, which must be mo
221
243
</dependencies>
222
244
```
223
245
224
-
Please note that your application may need more dependencies to be updated in order to make it compliant with Jakarta EE 9 on Tomcat 10 (for example JSP and JSTç dependencies).
246
+
Please note that your application may need more dependencies to be updated in order to make it compliant with Jakarta EE 9 on Tomcat 10 (for example JSP and JSTL dependencies).
225
247
226
248
- JDK 16
227
249
- Maven 3.8.1
@@ -233,3 +255,11 @@ If you are migrating your custom project to Jakarta EE9, the project build may f
233
255
### Migrating an already compiled wurfl-microservice-client-java jar file.
234
256
There may be cases in which you don't want or cannot rebuild the client or the application from the source code. In that case you can use a tool called [Eclipse Transformer](https://github.com/eclipse/transformer/blob/main/README.md) which can be executed on the wurfl-microservice-client-java JAR file and return an output JAR file in which the bytecode is made compliant with the new namespace **jakarta.***
235
257
258
+
## Code coverage report
259
+
260
+
In order to generate the code coverage report, you must have a running version of WURFL Microservice Server.
261
+
Code coverage report can be found under `target/site/jacoco/index.html`
0 commit comments