summaryrefslogtreecommitdiffstats
path: root/policy-core
diff options
context:
space:
mode:
authorJorge Hernandez <jh1730@att.com>2017-08-31 00:09:45 -0500
committerJorge Hernandez <jh1730@att.com>2017-08-31 00:13:16 -0500
commitfb79f7aa356ef2e4507cac5d5a328f789617cd5a (patch)
treea9eb0cf53de98d8ba6b617e1c6e373fdc13ff194 /policy-core
parentca5aaf029408e83498adc342023397fb1cbc9271 (diff)
Support Utils Libraries for CL Lab Integration
There is a companion review in the drools-applications repo. This also includes workarounds to the recent oparent dependency introduction that breaks runtime (with the version-check-maven-plugin). It manifested by loading control loops and failing to load some classes due to different versions (in a lab environment). The issue was that underlying drools libraries use 3.2.5 and oparent has included a had dependency with transitive dependencies for some maven libraries in 3.2.3 and lower version xml parsers. Bottomoline, the classpath at runtime was formed by the union of both, with some libraries being resolved to the oparent one, and others to the drools one. These errors are very obscured to debug. Additional clean up of dependencies versions and order of build was introduced to avoid issues loading dependencies at runtime in a lab environment (non-junit).. Change-Id: If4f4201e08f7e6e1f3619f557434c1b2e23e47a5 Issue-ID: POLICY-162 Signed-off-by: Jorge Hernandez <jh1730@att.com>
Diffstat (limited to 'policy-core')
-rw-r--r--policy-core/pom.xml2
1 files changed, 0 insertions, 2 deletions
diff --git a/policy-core/pom.xml b/policy-core/pom.xml
index 8fdfaa36..076a4bf2 100644
--- a/policy-core/pom.xml
+++ b/policy-core/pom.xml
@@ -40,13 +40,11 @@
<groupId>org.kie</groupId>
<artifactId>kie-ci</artifactId>
<version>6.5.0.Final</version>
- <scope>runtime</scope>
</dependency>
<dependency>
<groupId>org.drools</groupId>
<artifactId>drools-core</artifactId>
<version>6.5.0.Final</version>
- <scope>runtime</scope>
</dependency>
<dependency>
<groupId>org.drools</groupId>