Downgrade de.cronn:reflection-util for java 11

Signed-off-by: Gopal S Akshintala <[email protected]>

Author: overfullstack

.gitignore

@@ -281,3 +281,4 @@ fabric.properties
 .idea/caches/build_file_checksums.ser
 
 .vscode/
+.kotlin

.idea/git_toolbox_blame.xml

@@ -73,7 +73,7 @@ link:{docsdir}/requirements.adoc[Requirements that led to the birth of Vador]
 ====
 
 Validations are a problem almost as old as programming itself, but why a new library or Framework for Validations?
-Validations are predominantly done with `if-else-try-catch` pyramids, similar to https://github.com/overfullstack/railway-oriented-validation/blob/master/src/main/java/app/imperative/ImperativeValidation.java[this].
+Validations are predominantly done with `if-else-try-catch` pyramids, similar to https://github.com/overfullstack/fcwfp-root/blob/95ab9896f1f5f1122555ff94310111e7e7fe64e7/railway-oriented-validation/src/main/java/ga/overfullstack/app/imperative/ImperativeValidation.java#L31-L31[this].
 A domain may have many validations across its batch & non-batch services.
 Having validations as loose functions and using exceptions to halt the validation flow for the above requirements, can create a mess of function calls and execution flow.
 

.idea/kotlinc.xml

@@ -9,7 +9,7 @@ hamcrest-date = "2.0.8"
 typeTools = "0.6.3"
 spotbugs = "6.0.1"
 assertj-vavr = "0.4.3"
-reflection-util = "2.14.0"
+reflection-util = "2.15.0" # 2.15.0 is Compatable with Java 11
 nexus-publish = "2.0.0-rc-1"
 apache-common-text-version = "1.11.0"
 

README.adoc

@@ -16,6 +16,12 @@
       ],
       "groupName" : "all dependencies",
       "groupSlug" : "all"
+    },
+    {
+      "matchPackageNames": [
+        "de.cronn:reflection-util"
+      ],
+      "enabled": false
     }
   ]
 }