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
{{ message }}
This repository was archived by the owner on Feb 27, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,18 +53,30 @@ The gradlew (or gradlew.bat on Windows) command is a Java program called the [Gr
53
53
54
54
Check the following properties file to see if there is any conflicts with your existing system.
55
55
56
-
$PROJET_ROOT/core/gradle.properties
56
+
$PROJECT_ROOT/core/gradle.properties
57
+
58
+
The gradle.properties file indicates where to deploy a test database to test the core unit test. The job.properties are used for testing the examples.
57
59
58
60
From the project root, run the following command. This will create a test database that is configured as a MarkLogic Job Repository.
59
61
60
62
gradlew :core:mlDeploy
61
63
62
-
Run the automated unit tests from the project root
64
+
## Set your environment variables for running the examples
65
+
66
+
Every example under the examples project relies on a properties file called job.properties that indicates the connection information for your MarkLogic database. The default job.properties can be found for the project in the following location.
67
+
68
+
$PROJECT_ROOT/examples/job.properties
69
+
70
+
The directory location for the job.properties is indicated in the environment variable _job.home_. Make sure that this environment variable (job.home) is set before running any of the example tests.
71
+
72
+
To execute all of the automated unit tests, from the project root, run the following command.
63
73
64
74
```
65
75
gradlew test
66
76
```
67
77
78
+
This will execute all the core and examples testing.
79
+
68
80
The policy is the dev branch tests are 100% passing. If all tests run to completion and 100% passing then you are ready to start commiting code.
Copy file name to clipboardExpand all lines: examples/base/build.gradle
+3-7Lines changed: 3 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,21 @@
1
1
/*
2
-
This base gradle file imports the latest MarkLogic Spring Batch Core and Test libraries that are published to jCenter.
2
+
This base gradle file imports the latest MarkLogic Spring Batch Core and Test libraries that are published to jCenter. Make sure that the job.home environment variable is set.
Copy file name to clipboardExpand all lines: examples/build.gradle
+5-3Lines changed: 5 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -2,19 +2,21 @@ subprojects {
2
2
apply plugin: "java"
3
3
apply plugin: "application"
4
4
5
+
/*
6
+
// The job.home environment variable is assumed to be predefined. Otherwise, you can uncomment this section and set the examplesDir variable in the gradle.properties file.
0 commit comments