Re: [Hawkular-dev] Upgrade to Wildfly 1.1.0.Final
----- Original Message -----
From: "John Mazzitelli" <mazz(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Tuesday, 7 February, 2017 3:55:44 PM
Subject: Re: [Hawkular-dev] Upgrade to Wildfly 1.1.0.Final
> To make sure that we are running with the latest bug fixes and security
> updates, whenever there is a new release of Wildfly we should be moving to
> that as soon as possible.
The problem with that is, it may break us if run in older EAP versions (like
EAP6).
If you are relying on an older version of Wildfly to behave the same way as EAP you are
going to be disappointed. They may share a common ancestor, but the longer that EAP is out
there the more out of sync it gets with Wildfly. EAP will have backported fixes and other
updates that the older Wildfly version its based on will never get.
They are similar but different enough that its probably a wise idea to be supporting them
separately. We have to do this with our metric images for OpenShift.
For the community version we should always be updating, even just to make sure we have the
latest security updates.
But this may not be an issue with server-side components like metrics
and
alerts.
It is an issue with the wildfly agent, though.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev