-
Bug
-
Resolution: Done
-
High
-
Amsterdam Release
-
None
-
Policy Sprint 1, Policy Sprint 2 - 7/31-8/4
BRMS GW had trouble resolving dependencies for vFW and vDNS flows.
After some digging I think the problem lies with the controlloop jar not stored in nexus, after the restructuring of the drools-applications repo, and is called events. I think that is the only difference
More specifically, from BMS GW side, the 1.0.0 vFW and vDNS have “controllop” jar dependency:
<dependency>
<groupId>org.onap.policy.drools-applications</groupId>
<artifactId>controlloop</artifactId>
<version>1.1.0</version>
</dependency>
But it has been renamed to “events” as I see. So, Tarun, brms gw has to change dependeny to “events” on your side.
Chenfei, in drools-applications some work should be done:
- Clean up the dependencies in template.demo.v1.0.0 project. I see:
<dependency>
<groupId>org.onap.policy.drools-applications</groupId>
<artifactId>guard</artifactId>
<version>1.1.0-SNAPSHOT</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.onap.policy.drools-applications</groupId>
<artifactId>policy-yaml</artifactId>
<version>1.1.0-SNAPSHOT</version>
<scope>provided</scope>
</dependency>
I believe guard and policy-yaml are unnecessary here. I think we may be ok since they are provided, but need to be tidy on these, to avoid drools fetching unnecessary artifacts, again I think may be ok, but better to be tidy here.
- “events” has a pom.xml dependency to gson that should be marked as provided, similar reasoning, I think will be ok, but we have to be tidy, to avoid any potentail issues in the brms gw side, and runtime.
- archetype-closedloop-demo-rules project should be changed, see pom.xml within there, and dependencies to use “events” projects.
- packages/artifacts/pom.xml – they need to include everything needed for artifact resolution. Since the pom parent structure has been redone, and there are multiple levels, we need to make sure that all the parent poms for all artifacts are packaged for nexus installations, otherwise when the rules jar is loaded from nexus, dependency resolution when going through pom files may fail.
I’ll open 2 tickets, one for PE and another one for drools-applications to track this work.
Note vFW and vDNS won’t work until this is resolved.