#103 Always initializing properties when initializing PropertiesModul…

…eManager Fixes a bug that surfaced in ml-gradle where after the resource timestamps file was deleted, initialize was called, but since the file didn't exist anymore, the properties object wasn't recreated
marklogic · Nov 6, 2018 · 7ab3412 · 7ab3412
1 parent 00081e1
commit 7ab3412
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 3 deletions.
diff --git a/gradle.properties b/gradle.properties
@@ -1,3 +1,3 @@
 group=com.marklogic
 javadocsDir=../gh-pages-marklogic-java/javadocs
-version=3.9.0
+version=3.10.0
diff --git a/src/main/java/com/marklogic/client/ext/batch/DefaultBatchHandler.java b/src/main/java/com/marklogic/client/ext/batch/DefaultBatchHandler.java
@@ -53,8 +53,8 @@ public void handleBatch(DatabaseClient client, List<? extends DocumentWriteOpera
 		} else {
 			mgr.write(set);
 		}
-		if (logger.isInfoEnabled()) {
-			logger.info("Wrote " + count + " documents to MarkLogic; " + connectionInfo);
+		if (logger.isDebugEnabled()) {
+			logger.debug("Wrote " + count + " documents to MarkLogic; " + connectionInfo);
 		}
 	}
 

diff --git a/src/main/java/com/marklogic/client/ext/modulesloader/impl/PropertiesModuleManager.java b/src/main/java/com/marklogic/client/ext/modulesloader/impl/PropertiesModuleManager.java
@@ -28,6 +28,8 @@ public PropertiesModuleManager(String propertiesFilePath) {
 
     @Override
     public void initialize() {
+    	this.props = new Properties();
+
     	File propertiesFile = new File(propertiesFilePath);
 
     	if (propertiesFile.getParentFile() != null) {