I'll repost what I mentioned in December:

"I noticed that on Openshift we are running Hawkular Metrics on WildFly 10.1.0.  It was upped from 10.0.0 several months ago due to a blocking issue that had been fixed in EAP but not WF 10.0.  I ran into a new issue when trying to deploy Metrics master on OS Origin.  It failed to deploy on WF 10.1.0.   I was able to solve the issue without a major change but it called out the fact that we are building Hawkular against WF 10.0.1 bom and running itests against 10.0.0 server.

Because OS is a primary target platform I'm wondering if we should bump the parent pom deps to the 10.1.0 bom and server (as well as upping a few related deps as well, like ISPN).  As part of my investigation I did this locally for parent pom, commons, alerting and metrics and did not see any issues."

I think I have a branch somewhere that fixed whatever that deployment issue is...
On 2/7/2017 4:28 AM, Lucas Ponce wrote:

----- Mensaje original -----

De: "Heiko W.Rupp" <hrupp@redhat.com>
Para: "Discussions around Hawkular development" <hawkular-dev@lists.jboss.org>
Enviados: Martes, 7 de Febrero 2017 10:21:36
Asunto: Re: [Hawkular-dev] Upgrade to Wildfly 1.1.0.Final

On 7 Feb 2017, at 10:16, Lucas Ponce wrote:


Is there any objection / potential problem if we upgrade from
1.0.0.Final to 1.1.0.Final ?

Do we know if 10.1 is just a bug-fix release or would it
introduce new features, that we are then using?


There are some new features

http://wildfly.org/news/2016/08/19/WildFly10-1-Released/



During investigation of a clustering issue, there are some fixes
related that seems to be packaged on 1.1.0.Final.

If it is bugfixes only, I am all for updating.

I am starting to test it locally, at least for Alerting, to see if it resolves issues I am having.

But if there is some way to test other components it would be good to give it a try.
_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev