diff options
author | Jorge Hernandez <jh1730@att.com> | 2017-08-31 00:09:45 -0500 |
---|---|---|
committer | Jorge Hernandez <jh1730@att.com> | 2017-08-31 00:13:16 -0500 |
commit | fb79f7aa356ef2e4507cac5d5a328f789617cd5a (patch) | |
tree | a9eb0cf53de98d8ba6b617e1c6e373fdc13ff194 /packages/pom.xml | |
parent | ca5aaf029408e83498adc342023397fb1cbc9271 (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 'packages/pom.xml')
0 files changed, 0 insertions, 0 deletions