Re: [Hawkular-dev] open shift agent - what to call it?
> Personally I would vote for:
> - Renaming the existing "Hawkular Agent" to "Hawkular WildFly
Agent" and
> reduce its scope to the embedded WF scenario (+ remote for domains). Small
> in scope == easier to maintain, document, understand...
For the record, that has been what I've been calling that agent for a while now.
"Hawkular WildFly Agent". The git repo isn't called that, but the internals
are - e.g. https://github.com/hawkular/hawkular-agent/tree/master/hawkular-wildfly-a...
The "hawkular-agent" repo was created and named as such with the naive thought
that all hawkular feeds/agents would go under that one big umbrella repo. But that ended
up being a stupid idea :)