Should Jolokia be included in the built jar files?

Description

Tommy was having some trouble with hqlax having multiple copies of the Jolokia classes, this then giving warnings.

The other day I noticed that we include Jolokia in the Cordapp jars generated by some of the sample projects. This doesn't feel right - surely Jolokia is a node concern, and not a Cordapp concern?

I've tested two of the sample apps so far, both using the RC03 enterprise dev pack:

  • reference-states - Jolokia is included in reference-states-0.1.jar

  • negotiation Cordapp has 3 jars, only the root jar has Jolokia:

Status

Assignee

Chris Rankin

Reporter

Ben Wyeth

Labels

Priority

Medium

Fix versions

None

Ported to...

None

Feature Team

Select team

CVSS Vector

None

Severity

Medium

Affects versions

Configure