<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<font face="Calibri">This relates to the "[Hawkular-dev] Future
Packaging of Hawkular" thread. I started this thread to discuss a
specific scenario that I don't know how to handle.<br>
<br>
In addition to the components listed in that e-mail, there are a
few other things in the Hawkular repo that weren't mentioned. For
example, we have pinger and we have the inventory-event bus
listener. I point out those two because I think they now exist
solely to support the community UI. URL monitoring and Alert
Center do not carry over to MIQ. With respect to the alert center
we have out-of-box trigger definitions that are currently still
active and are defined specifically to support the UI Alert center
in Hawkular classic. And so we have a situation where code I
would otherwise remove may need to exist to support the UI in the
community distribution. Do we really want to keep a
community-edition UI and the server-code that *only* supports what
it does? If we remove it it will severely cripple the UI. But I
fear that the UI will anyway quickly deteriorate unless we make
concerted efforts to maintain compatible server code. Even today
I think the UI is starting to falter. I'm not sure but when I
tried to use the master version today to perform a deployment, it
just hung.<br>
<br>
So in line with Juca's questioning, what sort of effort do we put
into the community UI? A lot, and keep it working as best as we
can and ensure we mark server code that is relevant to community
UI support? None, and just make the server code be the headless
provider it needs to be to support MIQ, or something in the middle
(which usually ends up being a waste of time).<br>
</font>
</body>
</html>