Thanks for the info, Thomas. Could you please explain the background of this decision? JAX-RS 1.1 was needed because Metrics had to support EAP 6.4 (because of OpenShift), right? So clearly, EAP 6.4 is going away from the list of supported containers, but which particular containers are there in the current/short-term-planned list? There is WF10 and anything else? I am asking this because I am trying to figure out how we could manage artifacts separately for various target containers. We'll have to solve this somehow for product vs. community and the question is if the matrix is going to be even more complicated. Thanks again, -- Peter On 2016-01-28 10:11, Thomas Segismont wrote: > Hi, > > A pull request which removes JAX-RS 1.1 support from Metrics has just > been merged. Future minor and major versions of Metrics will support > JAX-RS 2.0 only. > > For Metrics contributors, it means you should remove the api-diff > precommit hook from your .git/hooks directory. > > Regards, > Thomas > _______________________________________________ > hawkular-dev mailing list > hawkular-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev