Re: [Apiman-user] Apiman 1.5 released

Builds with fixed date-related metadata (likely non-impactful, but we decided to be cautious) Vert.x (Gateway Only): http://downloads.jboss.org/apiman/1.5.1.Final/apiman-distro-vertx-1.5.1.F... WF10/EAP7.1: http://downloads.jboss.org/apiman/1.5.1.Final/apiman-distro-wildfly10-1.5... WF11: http://downloads.jboss.org/apiman/1.5.1.Final/apiman-distro-wildfly11-1.5... EAP7: http://downloads.jboss.org/apiman/1.5.1.Final/apiman-distro-eap7-1.5.1.Fi... Tomcat 8+: http://downloads.jboss.org/apiman/1.5.1.Final/apiman-distro-tomcat8-1.5.1... On 27 July 2018 at 10:33, Marc Savy <marc.savy(a)redhat.com&gt; wrote: > Yet again we seem to have had a problem with the date on the release > machine (claiming it was still 4th July). So I'll be doing a > 1.5.1.Final release to ensure all metadata is correct. > > Sorry about that. I'll try to add safeguards to ensure it doesn't happen again. > > On 25 July 2018 at 17:11, Marc Savy <marc.savy(a)redhat.com&gt; wrote: >> Hi All, >> >> Apiman 1.5 has been released. >> >> It contains an important new policy feature: the ability to modify >> policy failures before they are returned to users. This means that >> policies such as CORS can add their headers, irrespective of whether >> the request was successful or not (e.g. due to rate limiting). >> >> Blog post soon! >> >> Vert.x (Gateway Only): >> http://downloads.jboss.org/apiman/1.5.0.Final/apiman-distro-vertx-1.5.0.F... >> >> WF10/EAP7.1: >> http://downloads.jboss.org/apiman/1.5.0.Final/apiman-distro-wildfly10-1.5... >> >> WF11: >> http://downloads.jboss.org/apiman/1.5.0.Final/apiman-distro-wildfly11-1.5... >> >> EAP7: >> http://downloads.jboss.org/apiman/1.5.0.Final/apiman-distro-eap7-1.5.0.Fi... >> >> Tomcat 8+: >> http://downloads.jboss.org/apiman/1.5.0.Final/apiman-distro-tomcat8-1.5.0... >> >> Regards, >> Marc