Updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

diff --git a/build.xml b/build.xml
index 694b90b234c16cd495a61ce0dbff01297b156f87..4c0f842b780e5a15c3dab45e2fcc5d8b29559e01 100644 (file)
--- a/build.xml
+++ b/build.xml
@@ -1,73 +1,73 @@
-<?xml version="1.0" encoding="UTF-8"?>\r
-<!-- You may freely edit this file. See commented blocks below for -->\r
-<!-- some examples of how to customize the build. -->\r
-<!-- (If you delete it and reopen the project it will be recreated.) -->\r
-<!-- By default, only the Clean and Build commands use this build script. -->\r
-<!-- Commands such as Run, Debug, and Test only use this build script if -->\r
-<!-- the Compile on Save feature is turned off for the project. -->\r
-<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->\r
-<!-- in the project's Project Properties dialog box.-->\r
-<project name="addressbook-core" default="default" basedir=".">\r
-    <description>Builds, tests, and runs the project addressbook-core.</description>\r
-    <import file="nbproject/build-impl.xml"/>\r
-    <!--\r
-\r
-    There exist several targets which are by default empty and which can be \r
-    used for execution of your tasks. These targets are usually executed \r
-    before and after some main targets. They are: \r
-\r
-      -pre-init:                 called before initialization of project properties\r
-      -post-init:                called after initialization of project properties\r
-      -pre-compile:              called before javac compilation\r
-      -post-compile:             called after javac compilation\r
-      -pre-compile-single:       called before javac compilation of single file\r
-      -post-compile-single:      called after javac compilation of single file\r
-      -pre-compile-test:         called before javac compilation of JUnit tests\r
-      -post-compile-test:        called after javac compilation of JUnit tests\r
-      -pre-compile-test-single:  called before javac compilation of single JUnit test\r
-      -post-compile-test-single: called after javac compilation of single JUunit test\r
-      -pre-jar:                  called before JAR building\r
-      -post-jar:                 called after JAR building\r
-      -post-clean:               called after cleaning build products\r
-\r
-    (Targets beginning with '-' are not intended to be called on their own.)\r
-\r
-    Example of inserting an obfuscator after compilation could look like this:\r
-\r
-        <target name="-post-compile">\r
-            <obfuscate>\r
-                <fileset dir="${build.classes.dir}"/>\r
-            </obfuscate>\r
-        </target>\r
-\r
-    For list of available properties check the imported \r
-    nbproject/build-impl.xml file. \r
-\r
-\r
-    Another way to customize the build is by overriding existing main targets.\r
-    The targets of interest are: \r
-\r
-      -init-macrodef-javac:     defines macro for javac compilation\r
-      -init-macrodef-junit:     defines macro for junit execution\r
-      -init-macrodef-debug:     defines macro for class debugging\r
-      -init-macrodef-java:      defines macro for class execution\r
-      -do-jar:                  JAR building\r
-      run:                      execution of project \r
-      -javadoc-build:           Javadoc generation\r
-      test-report:              JUnit report generation\r
-\r
-    An example of overriding the target for project execution could look like this:\r
-\r
-        <target name="run" depends="addressbook-core-impl.jar">\r
-            <exec dir="bin" executable="launcher.exe">\r
-                <arg file="${dist.jar}"/>\r
-            </exec>\r
-        </target>\r
-\r
-    Notice that the overridden target depends on the jar target and not only on \r
-    the compile target as the regular run target does. Again, for a list of available \r
-    properties which you can use, check the target you are overriding in the\r
-    nbproject/build-impl.xml file. \r
-\r
-    -->\r
-</project>\r
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- You may freely edit this file. See commented blocks below for -->
+<!-- some examples of how to customize the build. -->
+<!-- (If you delete it and reopen the project it will be recreated.) -->
+<!-- By default, only the Clean and Build commands use this build script. -->
+<!-- Commands such as Run, Debug, and Test only use this build script if -->
+<!-- the Compile on Save feature is turned off for the project. -->
+<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
+<!-- in the project's Project Properties dialog box.-->
+<project name="addressbook-core" default="default" basedir=".">
+    <description>Builds, tests, and runs the project addressbook-core.</description>
+    <import file="nbproject/build-impl.xml"/>
+    <!--
+
+    There exist several targets which are by default empty and which can be 
+    used for execution of your tasks. These targets are usually executed 
+    before and after some main targets. They are: 
+
+      -pre-init:                 called before initialization of project properties
+      -post-init:                called after initialization of project properties
+      -pre-compile:              called before javac compilation
+      -post-compile:             called after javac compilation
+      -pre-compile-single:       called before javac compilation of single file
+      -post-compile-single:      called after javac compilation of single file
+      -pre-compile-test:         called before javac compilation of JUnit tests
+      -post-compile-test:        called after javac compilation of JUnit tests
+      -pre-compile-test-single:  called before javac compilation of single JUnit test
+      -post-compile-test-single: called after javac compilation of single JUunit test
+      -pre-jar:                  called before JAR building
+      -post-jar:                 called after JAR building
+      -post-clean:               called after cleaning build products
+
+    (Targets beginning with '-' are not intended to be called on their own.)
+
+    Example of inserting an obfuscator after compilation could look like this:
+
+        <target name="-post-compile">
+            <obfuscate>
+                <fileset dir="${build.classes.dir}"/>
+            </obfuscate>
+        </target>
+
+    For list of available properties check the imported 
+    nbproject/build-impl.xml file. 
+
+
+    Another way to customize the build is by overriding existing main targets.
+    The targets of interest are: 
+
+      -init-macrodef-javac:     defines macro for javac compilation
+      -init-macrodef-junit:     defines macro for junit execution
+      -init-macrodef-debug:     defines macro for class debugging
+      -init-macrodef-java:      defines macro for class execution
+      -do-jar:                  JAR building
+      run:                      execution of project 
+      -javadoc-build:           Javadoc generation
+      test-report:              JUnit report generation
+
+    An example of overriding the target for project execution could look like this:
+
+        <target name="run" depends="addressbook-core-impl.jar">
+            <exec dir="bin" executable="launcher.exe">
+                <arg file="${dist.jar}"/>
+            </exec>
+        </target>
+
+    Notice that the overridden target depends on the jar target and not only on 
+    the compile target as the regular run target does. Again, for a list of available 
+    properties which you can use, check the target you are overriding in the
+    nbproject/build-impl.xml file. 
+
+    -->
+</project>

diff --git a/lib/jcore-logger-lib.jar b/lib/jcore-logger-lib.jar
index 90c19526c0c6b2391cb9891396791bdfad9fdb23..2cef76df14ca4ed4d94b804beaf452dde7f96b8a 100644 (file)
Binary files a/lib/jcore-logger-lib.jar and b/lib/jcore-logger-lib.jar differ