From marc.savy at redhat.com Mon Jun 4 11:21:35 2018 From: marc.savy at redhat.com (Marc Savy) Date: Mon, 4 Jun 2018 16:21:35 +0100 Subject: [Apiman-user] Help needed: Feedback/testing for Apiman on ES 5.x (and possibly ES 2.x) In-Reply-To: References: Message-ID: Hi, I've not received any negative feedback about this. So I'll be merging in soon. I've split off a branch in case any unexpected 1.3.x releases are needed. Regards, Marc On 22 May 2018 at 11:29, Marc Savy wrote: > Hi, > > After spending the last week or more fiddling with test harness and CI > issues, we finally seem to be (almost) there. > > I'd appreciate anyone who could test the latest an ES 5.x version of > Apiman for me. It still needs some tidying up, but should be > functional. > > Steps: > > git clone git at github.com:msavy/apiman.git > git checkout es5x > mvn clean install > cd distro/{distro of your choice}/target/{distro overlay zip of your choice} > > handle the distro zip as you usually would a release (i.e. extract > overlay onto a server such as wildfly10) > > Please modify apiman.properties to match your particular configuration > and try things out! > > Regards, > Marc From marc.savy at redhat.com Wed Jun 6 12:48:54 2018 From: marc.savy at redhat.com (Marc Savy) Date: Wed, 6 Jun 2018 17:48:54 +0100 Subject: [Apiman-user] Help needed: Feedback/testing for Apiman on ES 5.x (and possibly ES 2.x) In-Reply-To: References: Message-ID: This is now on master. Please try it out! On 4 June 2018 at 16:21, Marc Savy wrote: > Hi, > > I've not received any negative feedback about this. So I'll be merging > in soon. I've split off a branch in case any unexpected 1.3.x releases > are needed. > > Regards, > Marc > > On 22 May 2018 at 11:29, Marc Savy wrote: >> Hi, >> >> After spending the last week or more fiddling with test harness and CI >> issues, we finally seem to be (almost) there. >> >> I'd appreciate anyone who could test the latest an ES 5.x version of >> Apiman for me. It still needs some tidying up, but should be >> functional. >> >> Steps: >> >> git clone git at github.com:msavy/apiman.git >> git checkout es5x >> mvn clean install >> cd distro/{distro of your choice}/target/{distro overlay zip of your choice} >> >> handle the distro zip as you usually would a release (i.e. extract >> overlay onto a server such as wildfly10) >> >> Please modify apiman.properties to match your particular configuration >> and try things out! >> >> Regards, >> Marc From marc.savy at redhat.com Wed Jun 6 12:54:38 2018 From: marc.savy at redhat.com (Marc Savy) Date: Wed, 6 Jun 2018 17:54:38 +0100 Subject: [Apiman-user] Help needed: Feedback/testing for Apiman on ES 5.x (and possibly ES 2.x) In-Reply-To: References: Message-ID: Snapshot builds on DockerHub should be available shortly (and a snapshot is being deployed to Sonatype as I type this). I'm also going to merge some other community fixes relating to export-import soon (thanks for that excellent work!). On 6 June 2018 at 17:48, Marc Savy wrote: > This is now on master. Please try it out! > > On 4 June 2018 at 16:21, Marc Savy wrote: >> Hi, >> >> I've not received any negative feedback about this. So I'll be merging >> in soon. I've split off a branch in case any unexpected 1.3.x releases >> are needed. >> >> Regards, >> Marc >> >> On 22 May 2018 at 11:29, Marc Savy wrote: >>> Hi, >>> >>> After spending the last week or more fiddling with test harness and CI >>> issues, we finally seem to be (almost) there. >>> >>> I'd appreciate anyone who could test the latest an ES 5.x version of >>> Apiman for me. It still needs some tidying up, but should be >>> functional. >>> >>> Steps: >>> >>> git clone git at github.com:msavy/apiman.git >>> git checkout es5x >>> mvn clean install >>> cd distro/{distro of your choice}/target/{distro overlay zip of your choice} >>> >>> handle the distro zip as you usually would a release (i.e. extract >>> overlay onto a server such as wildfly10) >>> >>> Please modify apiman.properties to match your particular configuration >>> and try things out! >>> >>> Regards, >>> Marc From marc.savy at redhat.com Thu Jun 7 10:59:01 2018 From: marc.savy at redhat.com (Marc Savy) Date: Thu, 7 Jun 2018 15:59:01 +0100 Subject: [Apiman-user] Preparing for release 1.4.0 Message-ID: Hi, We're now preparing for the release of 1.4.0.Final. Expect a release in the coming days. The predominant change is the move from Elasticsearch 1.x to Elasticsearch 5.x. Please test out master if you can. Especially if you use ES for the Apiman Manager. There are also a few other bug-fixes and few bits that will make it into this release. Thanks to everyone who has contributed! Regards, Marc From marc.savy at redhat.com Thu Jun 7 10:59:49 2018 From: marc.savy at redhat.com (Marc Savy) Date: Thu, 7 Jun 2018 15:59:49 +0100 Subject: [Apiman-user] Preparing for release 1.4.0 In-Reply-To: References: Message-ID: BTW, we've delayed bundling the Apiman CLI until 1.4.1.Final to ensure it's up to scratch -- I didn't want to delay this release for it. On 7 June 2018 at 15:59, Marc Savy wrote: > Hi, > > We're now preparing for the release of 1.4.0.Final. Expect a release > in the coming days. The predominant change is the move from > Elasticsearch 1.x to Elasticsearch 5.x. > > Please test out master if you can. Especially if you use ES for the > Apiman Manager. > > There are also a few other bug-fixes and few bits that will make it > into this release. > > Thanks to everyone who has contributed! > > Regards, > Marc From marc.savy at redhat.com Tue Jun 12 10:28:42 2018 From: marc.savy at redhat.com (Marc Savy) Date: Tue, 12 Jun 2018 15:28:42 +0100 Subject: [Apiman-user] Is it possible blocking request after request body parsing? In-Reply-To: References: Message-ID: I haven't been able to reproduce this. Could you please provide a bit more information so I can debug this. 1. What is your policy chain 2. Can you provide a skeleton policy that reproduces the issue where you say you are able to get a parsed entity without ticking the appropriate box in the UI? On 30 April 2018 at 02:16, ? ?? wrote: > Thanks for your information. > I'll enable this option for parsing request body. > > ________________________________ > ???: Marc Savy > ????: 2018?4?26? ?? 07:36 > ???: Eric Wittmann > ??: ? ??; apiman-user at lists.jboss.org > > ??: Re: [Apiman-user] Is it possible blocking request after request body > parsing? > > Thanks. I'll check it out and report back. > > On 26 April 2018 at 12:26, Eric Wittmann wrote: >> Yes that is the UI option I was referring to. >> >> If the request payload is being parsed without that option being set, then >> there is a bug in the Apiman gateway. I will write up a bug report for >> that >> so that @marcsavy can have a look. :) >> >> -Eric >> >> >> On Thu, Apr 26, 2018 at 4:36 AM, ? ?? wrote: >>> >>> Dear Eric >>> >>> Thanks for your helpful information. >>> I can get request body with IPolicyContext object. >>> Besides, you also mentioned enable this on a per-API basis in the apiman >>> UI. >>> Is It "Enable stateful request payload insepction" in API implementation >>> tab? >>> I'm wondering because I didn't enable this option but can still get the >>> request body in doApply() with IPolicyContext. >>> What is the difference if I enable this option? >>> Thanks >>> >>> Regards >>> >>> ________________________________ >>> ???: Eric Wittmann >>> ????: 2018?4?25? ?? 08:15 >>> ???: ? ?? >>> ??: apiman-user at lists.jboss.org >>> ??: Re: [Apiman-user] Is it possible blocking request after request body >>> parsing? >>> >>> Yes there is a feature where apiman will parse the request BEFORE >>> applying >>> the policies. This will make the HTTP request body available to all >>> policies in the chain, should they need them. >>> >>> You can enable this on a per-API basis in the apiman UI. >>> >>> When this feature is enabled, your custom policy can access the request >>> body as an object found in the IPolicyContext object. For example: >>> >>> Object payload = context.getAttribute("apiman.request-payload"); >>> >>> The type of thing that you get depends on the API's endpoint type. The >>> endpoint type might be JSON, XML, or SOAP. I think it might be possible >>> to >>> have some other kind of endpoint type, but those three are handled by the >>> request body parser feature. >>> >>> Here is what you'll get as that payload object, depending on endpoint >>> type: >>> >>> JSON - Java Map object as a result of parsing the JSON data using Jackson >>> XML - org.w3c.dom.Document >>> Soap - javax.xml.soap.SOAPEnvelope >>> Anything Else - byte[] >>> >>> So for example, if your endpoint type is XML, then you could do this in >>> your policy implementation (in the doApply() method): >>> >>> org.w3c.dom.Document requestBody = (org.w3c.dom.Document) >>> context.gettAttribute("apiman.request-payload"); >>> >>> And then you could make some decision using the request data and e.g. >>> call >>> doFailure(). >>> >>> Also note - you can *change* the request body at this point as well. For >>> example you could apply a XML Transformation to the w3c Document, >>> resulting >>> in a new w3c Document object, which you could store in the Policy Context >>> (at the same key, obviously). That new document would then get >>> serialized >>> and sent as the request body to the backing API impl. There may be some >>> Content-Length issues if you do that, I can't remember... >>> >>> -Eric >>> >>> >>> On Wed, Apr 25, 2018 at 1:29 AM, ? ?? wrote: >>> >>> Hi all, >>> I would like to customize a policy, which parses the request body and >>> blocks the request in case. >>> in http://www.apiman.io/latest/developer-guide.html 4.2.1.2 IData policy, >>> it describes: >>> The request or response body will not begin streaming before the >>> corresponding doApply has been called, however, it is still possible to >>> interrupt the conversation during the streaming phase by signalling >>> doFailure or doError. >>> When I trace the transformation-policy source code, doApply() executes >>> before getRequestDataHandler() which matches the description. >>> In doApply() I can blocks the request via chain.doFailure() however I >>> have >>> no idea how to interrupt/block request in getRequestDataHandler(). >>> Besides, I found following mail group which is similar to my question. >>> Eric also points it's possible to parse the body before apply in request: >>> >>> On Thu, Feb 2, 2017 at 10:31 PM, Eric Wittmann < >>> eric.wittmann at redhat.com> wrote: >>> >>> The bottom line here is that you cannot return a Policy Failure (or >>> customize it) based on information in the response body. The response >>> is >>> streamed from the back-end to the client, and at the time streaming >>> begins, >>> the response code and HTTP headers have already been sent. >>> >>> It sounds to me like you're asking for a feature where you can parse >>> the response body *before* the policy's "apply" method is invoked. we >>> have >>> such a feature for requests, but not for responses. I suspect core >>> changes >>> to apiman would be required to enable that. It seems like a reasonable >>> request to me, as long as users of the feature understand the >>> performance >>> and memory requirements of enabling it. >>> >>> -Eric >>> >>> Thanks for any comments in advance. >>> Kind Regards >>> BT >>> >>> >>> _______________________________________________ >>> Apiman-user mailing list >>> Apiman-user at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/apiman-user >>> >>> >> >> >> _______________________________________________ >> Apiman-user mailing list >> Apiman-user at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/apiman-user >> From marc.savy at redhat.com Wed Jun 13 04:52:47 2018 From: marc.savy at redhat.com (Marc Savy) Date: Wed, 13 Jun 2018 09:52:47 +0100 Subject: [Apiman-user] Preparing for release 1.4.0 In-Reply-To: References: Message-ID: We're trying to release 1.4.0 (actually started yesterday), but been having some problems with the remote server. Hopefully it'll succeed today, finally! Will provide an update once everything is successfully deployed. On 7 June 2018 at 15:59, Marc Savy wrote: > BTW, we've delayed bundling the Apiman CLI until 1.4.1.Final to ensure > it's up to scratch -- I didn't want to delay this release for it. > > On 7 June 2018 at 15:59, Marc Savy wrote: >> Hi, >> >> We're now preparing for the release of 1.4.0.Final. Expect a release >> in the coming days. The predominant change is the move from >> Elasticsearch 1.x to Elasticsearch 5.x. >> >> Please test out master if you can. Especially if you use ES for the >> Apiman Manager. >> >> There are also a few other bug-fixes and few bits that will make it >> into this release. >> >> Thanks to everyone who has contributed! >> >> Regards, >> Marc From marc.savy at redhat.com Wed Jun 13 07:57:37 2018 From: marc.savy at redhat.com (Marc Savy) Date: Wed, 13 Jun 2018 12:57:37 +0100 Subject: [Apiman-user] Apiman 1.4.0.Final released Message-ID: Very happy to say that 1.4.0.Final has been released. Please try it out and give feedback. The major outward facing changes are: - Upgrade Elasticsearch support to 5.x (from 1.x). - Allow policies to suppress and allow connector headers via policy context - Lots of bug-fixes When upgrading from ES 1.x to 5.x you may need to do an export/import, and/or follow Elasticsearch's own migration procedures if you prefer. Vert.x (Gateway Only): http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-vertx-1.4.0.Final.zip WF10/EAP7.1: http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly10-1.4.0.Final-overlay.zip WF11: http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly11-1.4.0.Final-overlay.zip EAP7: http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-eap7-1.4.0.Final-overlay.zip Tomcat 8+: http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-tomcat8-1.4.0.Final-overlay.zip Regards, Marc From donovan.muller at gmail.com Thu Jun 14 02:33:56 2018 From: donovan.muller at gmail.com (Donovan Muller) Date: Thu, 14 Jun 2018 08:33:56 +0200 Subject: [Apiman-user] Apiman 1.4.0.Final released In-Reply-To: References: Message-ID: Hi, Thanks for the release! When will the 1.4.0 release plugins be published to Maven central (or perhaps another download site)? Thanks On Wed, 13 Jun 2018 at 17:04 Marc Savy wrote: > Very happy to say that 1.4.0.Final has been released. > > Please try it out and give feedback. > > The major outward facing changes are: > - Upgrade Elasticsearch support to 5.x (from 1.x). > - Allow policies to suppress and allow connector headers via policy > context > - Lots of bug-fixes > > When upgrading from ES 1.x to 5.x you may need to do an export/import, > and/or follow Elasticsearch's own migration procedures if you prefer. > > Vert.x (Gateway Only): > > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-vertx-1.4.0.Final.zip > > WF10/EAP7.1: > > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly10-1.4.0.Final-overlay.zip > > WF11: > > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly11-1.4.0.Final-overlay.zip > > EAP7: > > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-eap7-1.4.0.Final-overlay.zip > > Tomcat 8+: > > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-tomcat8-1.4.0.Final-overlay.zip > > Regards, > Marc > _______________________________________________ > Apiman-user mailing list > Apiman-user at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20180614/f92cbdf2/attachment.html From marc.savy at redhat.com Thu Jun 14 03:46:21 2018 From: marc.savy at redhat.com (Marc Savy) Date: Thu, 14 Jun 2018 08:46:21 +0100 Subject: [Apiman-user] Apiman 1.4.0.Final released In-Reply-To: References: Message-ID: Hi, It /should/ be there now. It seems to have hit a technical glitch of some sort. I'll try again right now. There were some technical problems with Sonatype's OSSRH which meant it took 2 days to get the release out (see: https://issues.sonatype.org/browse/OSSRH-40470 and thread https://twitter.com/marcsavy/status/1006606526050598912). On 14 June 2018 at 07:33, Donovan Muller wrote: > Hi, > > Thanks for the release! > When will the 1.4.0 release plugins be published to Maven central (or > perhaps another download site)? > > Thanks > > On Wed, 13 Jun 2018 at 17:04 Marc Savy wrote: >> >> Very happy to say that 1.4.0.Final has been released. >> >> Please try it out and give feedback. >> >> The major outward facing changes are: >> - Upgrade Elasticsearch support to 5.x (from 1.x). >> - Allow policies to suppress and allow connector headers via policy >> context >> - Lots of bug-fixes >> >> When upgrading from ES 1.x to 5.x you may need to do an export/import, >> and/or follow Elasticsearch's own migration procedures if you prefer. >> >> Vert.x (Gateway Only): >> >> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-vertx-1.4.0.Final.zip >> >> WF10/EAP7.1: >> >> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly10-1.4.0.Final-overlay.zip >> >> WF11: >> >> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly11-1.4.0.Final-overlay.zip >> >> EAP7: >> >> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-eap7-1.4.0.Final-overlay.zip >> >> Tomcat 8+: >> >> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-tomcat8-1.4.0.Final-overlay.zip >> >> Regards, >> Marc >> _______________________________________________ >> Apiman-user mailing list >> Apiman-user at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/apiman-user From marc.savy at redhat.com Thu Jun 14 04:46:20 2018 From: marc.savy at redhat.com (Marc Savy) Date: Thu, 14 Jun 2018 09:46:20 +0100 Subject: [Apiman-user] Apiman 1.4.0.Final released In-Reply-To: References: Message-ID: Thanks for bringing this up, Donovan. As a quick update: it looks like something also went wrong during the release scripts for apiman-plugins and some of the version substitutions didn't happen properly (might be my fault, but I'm really not sure -- it's likely a consequence of earlier failures due to the OSSRH glitches interrupting things). I ended up having to do a force push on plugins to bring everything back into sync, so many apologies to anyone who pulled from master in the last 24h. Apiman plugins 1.4.0.Final release /should/ be available now -- I received an error from OSSRH but it seems to have deployed anyway. Please try it out. Regards, Marc On 14 June 2018 at 08:46, Marc Savy wrote: > Hi, > > It /should/ be there now. It seems to have hit a technical glitch of > some sort. I'll try again right now. > > There were some technical problems with Sonatype's OSSRH which meant > it took 2 days to get the release out (see: > https://issues.sonatype.org/browse/OSSRH-40470 and thread > https://twitter.com/marcsavy/status/1006606526050598912). > > On 14 June 2018 at 07:33, Donovan Muller wrote: >> Hi, >> >> Thanks for the release! >> When will the 1.4.0 release plugins be published to Maven central (or >> perhaps another download site)? >> >> Thanks >> >> On Wed, 13 Jun 2018 at 17:04 Marc Savy wrote: >>> >>> Very happy to say that 1.4.0.Final has been released. >>> >>> Please try it out and give feedback. >>> >>> The major outward facing changes are: >>> - Upgrade Elasticsearch support to 5.x (from 1.x). >>> - Allow policies to suppress and allow connector headers via policy >>> context >>> - Lots of bug-fixes >>> >>> When upgrading from ES 1.x to 5.x you may need to do an export/import, >>> and/or follow Elasticsearch's own migration procedures if you prefer. >>> >>> Vert.x (Gateway Only): >>> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-vertx-1.4.0.Final.zip >>> >>> WF10/EAP7.1: >>> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly10-1.4.0.Final-overlay.zip >>> >>> WF11: >>> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly11-1.4.0.Final-overlay.zip >>> >>> EAP7: >>> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-eap7-1.4.0.Final-overlay.zip >>> >>> Tomcat 8+: >>> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-tomcat8-1.4.0.Final-overlay.zip >>> >>> Regards, >>> Marc >>> _______________________________________________ >>> Apiman-user mailing list >>> Apiman-user at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/apiman-user From donovan.muller at gmail.com Thu Jun 14 05:59:42 2018 From: donovan.muller at gmail.com (Donovan Muller) Date: Thu, 14 Jun 2018 11:59:42 +0200 Subject: [Apiman-user] Apiman 1.4.0.Final released In-Reply-To: References: Message-ID: Thanks Marc, Still waiting for the plugins to reflect it seems: https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22io.apiman.plugins%22 Thanks On Thu, 14 Jun 2018 at 10:46 Marc Savy wrote: > Thanks for bringing this up, Donovan. > > As a quick update: it looks like something also went wrong during the > release scripts for apiman-plugins and some of the version > substitutions didn't happen properly (might be my fault, but I'm > really not sure -- it's likely a consequence of earlier failures due > to the OSSRH glitches interrupting things). > > I ended up having to do a force push on plugins to bring everything > back into sync, so many apologies to anyone who pulled from master in > the last 24h. > > Apiman plugins 1.4.0.Final release /should/ be available now -- I > received an error from OSSRH but it seems to have deployed anyway. > > Please try it out. > > Regards, > Marc > > > > On 14 June 2018 at 08:46, Marc Savy wrote: > > Hi, > > > > It /should/ be there now. It seems to have hit a technical glitch of > > some sort. I'll try again right now. > > > > There were some technical problems with Sonatype's OSSRH which meant > > it took 2 days to get the release out (see: > > https://issues.sonatype.org/browse/OSSRH-40470 and thread > > https://twitter.com/marcsavy/status/1006606526050598912). > > > > On 14 June 2018 at 07:33, Donovan Muller > wrote: > >> Hi, > >> > >> Thanks for the release! > >> When will the 1.4.0 release plugins be published to Maven central (or > >> perhaps another download site)? > >> > >> Thanks > >> > >> On Wed, 13 Jun 2018 at 17:04 Marc Savy wrote: > >>> > >>> Very happy to say that 1.4.0.Final has been released. > >>> > >>> Please try it out and give feedback. > >>> > >>> The major outward facing changes are: > >>> - Upgrade Elasticsearch support to 5.x (from 1.x). > >>> - Allow policies to suppress and allow connector headers via policy > >>> context > >>> - Lots of bug-fixes > >>> > >>> When upgrading from ES 1.x to 5.x you may need to do an export/import, > >>> and/or follow Elasticsearch's own migration procedures if you prefer. > >>> > >>> Vert.x (Gateway Only): > >>> > >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-vertx-1.4.0.Final.zip > >>> > >>> WF10/EAP7.1: > >>> > >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly10-1.4.0.Final-overlay.zip > >>> > >>> WF11: > >>> > >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly11-1.4.0.Final-overlay.zip > >>> > >>> EAP7: > >>> > >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-eap7-1.4.0.Final-overlay.zip > >>> > >>> Tomcat 8+: > >>> > >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-tomcat8-1.4.0.Final-overlay.zip > >>> > >>> Regards, > >>> Marc > >>> _______________________________________________ > >>> Apiman-user mailing list > >>> Apiman-user at lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/apiman-user > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20180614/4ba33389/attachment-0001.html From marc.savy at redhat.com Thu Jun 14 06:08:04 2018 From: marc.savy at redhat.com (Marc Savy) Date: Thu, 14 Jun 2018 11:08:04 +0100 Subject: [Apiman-user] Apiman 1.4.0.Final released In-Reply-To: References: Message-ID: search.maven.org tends to lag by several hours in my experience. Try this: mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get -Dartifact='io.apiman.plugins:apiman-plugins-circuit-breaker-policy:1.4.0.Final:war' Any luck? Seems to work on my end, but stuff might still be replicating out. On 14 June 2018 at 10:59, Donovan Muller wrote: > Thanks Marc, > > Still waiting for the plugins to reflect it seems: > https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22io.apiman.plugins%22 > > Thanks > > On Thu, 14 Jun 2018 at 10:46 Marc Savy wrote: >> >> Thanks for bringing this up, Donovan. >> >> As a quick update: it looks like something also went wrong during the >> release scripts for apiman-plugins and some of the version >> substitutions didn't happen properly (might be my fault, but I'm >> really not sure -- it's likely a consequence of earlier failures due >> to the OSSRH glitches interrupting things). >> >> I ended up having to do a force push on plugins to bring everything >> back into sync, so many apologies to anyone who pulled from master in >> the last 24h. >> >> Apiman plugins 1.4.0.Final release /should/ be available now -- I >> received an error from OSSRH but it seems to have deployed anyway. >> >> Please try it out. >> >> Regards, >> Marc >> >> >> >> On 14 June 2018 at 08:46, Marc Savy wrote: >> > Hi, >> > >> > It /should/ be there now. It seems to have hit a technical glitch of >> > some sort. I'll try again right now. >> > >> > There were some technical problems with Sonatype's OSSRH which meant >> > it took 2 days to get the release out (see: >> > https://issues.sonatype.org/browse/OSSRH-40470 and thread >> > https://twitter.com/marcsavy/status/1006606526050598912). >> > >> > On 14 June 2018 at 07:33, Donovan Muller >> > wrote: >> >> Hi, >> >> >> >> Thanks for the release! >> >> When will the 1.4.0 release plugins be published to Maven central (or >> >> perhaps another download site)? >> >> >> >> Thanks >> >> >> >> On Wed, 13 Jun 2018 at 17:04 Marc Savy wrote: >> >>> >> >>> Very happy to say that 1.4.0.Final has been released. >> >>> >> >>> Please try it out and give feedback. >> >>> >> >>> The major outward facing changes are: >> >>> - Upgrade Elasticsearch support to 5.x (from 1.x). >> >>> - Allow policies to suppress and allow connector headers via policy >> >>> context >> >>> - Lots of bug-fixes >> >>> >> >>> When upgrading from ES 1.x to 5.x you may need to do an export/import, >> >>> and/or follow Elasticsearch's own migration procedures if you prefer. >> >>> >> >>> Vert.x (Gateway Only): >> >>> >> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-vertx-1.4.0.Final.zip >> >>> >> >>> WF10/EAP7.1: >> >>> >> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly10-1.4.0.Final-overlay.zip >> >>> >> >>> WF11: >> >>> >> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly11-1.4.0.Final-overlay.zip >> >>> >> >>> EAP7: >> >>> >> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-eap7-1.4.0.Final-overlay.zip >> >>> >> >>> Tomcat 8+: >> >>> >> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-tomcat8-1.4.0.Final-overlay.zip >> >>> >> >>> Regards, >> >>> Marc >> >>> _______________________________________________ >> >>> Apiman-user mailing list >> >>> Apiman-user at lists.jboss.org >> >>> https://lists.jboss.org/mailman/listinfo/apiman-user From donovan.muller at gmail.com Thu Jun 14 06:13:04 2018 From: donovan.muller at gmail.com (Donovan Muller) Date: Thu, 14 Jun 2018 12:13:04 +0200 Subject: [Apiman-user] Apiman 1.4.0.Final released In-Reply-To: References: Message-ID: Not working on my side: mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get \ -Dartifact='io.apiman.plugins:apiman-plugins-circuit-breaker-policy:1.4.0.Final:war' [INFO] Scanning for projects... [INFO] [INFO] ------------------< org.apache.maven:standalone-pom >------------------- [INFO] Building Maven Stub Project (No POM) 1 [INFO] --------------------------------[ pom ]--------------------------------- [INFO] [INFO] --- maven-dependency-plugin:2.8:get (default-cli) @ standalone-pom --- Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom (0 B at 0 B/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom (0 B at 0 B/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom (0 B at 0 B/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.pom (0 B at 0 B/s) Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.pom (0 B at 0 B/s) Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.pom (0 B at 0 B/s) Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.pom (0 B at 0 B/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.pom (0 B at 0 B/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.jar Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.jar Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.jar Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.jar (0 B at 0 B/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.jar (0 B at 0 B/s) Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.jar (0 B at 0 B/s) Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.jar (0 B at 0 B/s) Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar (0 B at 0 B/s) Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.jar (0 B at 0 B/s) [INFO] Resolving io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final with transitive dependencies Downloading from central: https://repo.maven.apache.org/maven2/io/apiman/plugins/apiman-plugins-circuit-breaker-policy/1.4.0.Final/apiman-plugins-circuit-breaker-policy-1.4.0.Final.pom [WARNING] Missing POM for io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final Downloading from central: https://repo.maven.apache.org/maven2/io/apiman/plugins/apiman-plugins-circuit-breaker-policy/1.4.0.Final/apiman-plugins-circuit-breaker-policy-1.4.0.Final.war [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5.775 s [INFO] Finished at: 2018-06-14T12:12:01+02:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:get (default-cli) on project standalone-pom: Couldn't download artifact: Missing: [ERROR] ---------- [ERROR] 1) io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final [ERROR] [ERROR] Try downloading the file manually from the project website. [ERROR] [ERROR] Then, install it using the command: [ERROR] mvn install:install-file -DgroupId=io.apiman.plugins -DartifactId=apiman-plugins-circuit-breaker-policy -Dversion=1.4.0.Final -Dpackaging=war -Dfile=/path/to/file [ERROR] [ERROR] Alternatively, if you host your own repository you can deploy the file there: [ERROR] mvn deploy:deploy-file -DgroupId=io.apiman.plugins -DartifactId=apiman-plugins-circuit-breaker-policy -Dversion=1.4.0.Final -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] [ERROR] [ERROR] Path to dependency: [ERROR] 1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 [ERROR] 2) io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final [ERROR] [ERROR] ---------- [ERROR] 1 required artifact is missing. [ERROR] [ERROR] for artifact: [ERROR] org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 [ERROR] [ERROR] from the specified remote repositories: [ERROR] central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false) [ERROR] [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException On Thu, 14 Jun 2018 at 12:08 Marc Savy wrote: > search.maven.org tends to lag by several hours in my experience. > > Try this: > > mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get > > -Dartifact='io.apiman.plugins:apiman-plugins-circuit-breaker-policy:1.4.0.Final:war' > > Any luck? Seems to work on my end, but stuff might still be replicating > out. > > On 14 June 2018 at 10:59, Donovan Muller wrote: > > Thanks Marc, > > > > Still waiting for the plugins to reflect it seems: > > https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22io.apiman.plugins%22 > > > > Thanks > > > > On Thu, 14 Jun 2018 at 10:46 Marc Savy wrote: > >> > >> Thanks for bringing this up, Donovan. > >> > >> As a quick update: it looks like something also went wrong during the > >> release scripts for apiman-plugins and some of the version > >> substitutions didn't happen properly (might be my fault, but I'm > >> really not sure -- it's likely a consequence of earlier failures due > >> to the OSSRH glitches interrupting things). > >> > >> I ended up having to do a force push on plugins to bring everything > >> back into sync, so many apologies to anyone who pulled from master in > >> the last 24h. > >> > >> Apiman plugins 1.4.0.Final release /should/ be available now -- I > >> received an error from OSSRH but it seems to have deployed anyway. > >> > >> Please try it out. > >> > >> Regards, > >> Marc > >> > >> > >> > >> On 14 June 2018 at 08:46, Marc Savy wrote: > >> > Hi, > >> > > >> > It /should/ be there now. It seems to have hit a technical glitch of > >> > some sort. I'll try again right now. > >> > > >> > There were some technical problems with Sonatype's OSSRH which meant > >> > it took 2 days to get the release out (see: > >> > https://issues.sonatype.org/browse/OSSRH-40470 and thread > >> > https://twitter.com/marcsavy/status/1006606526050598912). > >> > > >> > On 14 June 2018 at 07:33, Donovan Muller > >> > wrote: > >> >> Hi, > >> >> > >> >> Thanks for the release! > >> >> When will the 1.4.0 release plugins be published to Maven central (or > >> >> perhaps another download site)? > >> >> > >> >> Thanks > >> >> > >> >> On Wed, 13 Jun 2018 at 17:04 Marc Savy wrote: > >> >>> > >> >>> Very happy to say that 1.4.0.Final has been released. > >> >>> > >> >>> Please try it out and give feedback. > >> >>> > >> >>> The major outward facing changes are: > >> >>> - Upgrade Elasticsearch support to 5.x (from 1.x). > >> >>> - Allow policies to suppress and allow connector headers via > policy > >> >>> context > >> >>> - Lots of bug-fixes > >> >>> > >> >>> When upgrading from ES 1.x to 5.x you may need to do an > export/import, > >> >>> and/or follow Elasticsearch's own migration procedures if you > prefer. > >> >>> > >> >>> Vert.x (Gateway Only): > >> >>> > >> >>> > >> >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-vertx-1.4.0.Final.zip > >> >>> > >> >>> WF10/EAP7.1: > >> >>> > >> >>> > >> >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly10-1.4.0.Final-overlay.zip > >> >>> > >> >>> WF11: > >> >>> > >> >>> > >> >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly11-1.4.0.Final-overlay.zip > >> >>> > >> >>> EAP7: > >> >>> > >> >>> > >> >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-eap7-1.4.0.Final-overlay.zip > >> >>> > >> >>> Tomcat 8+: > >> >>> > >> >>> > >> >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-tomcat8-1.4.0.Final-overlay.zip > >> >>> > >> >>> Regards, > >> >>> Marc > >> >>> _______________________________________________ > >> >>> Apiman-user mailing list > >> >>> Apiman-user at lists.jboss.org > >> >>> https://lists.jboss.org/mailman/listinfo/apiman-user > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20180614/46b88220/attachment-0001.html From marc.savy at redhat.com Thu Jun 14 06:35:03 2018 From: marc.savy at redhat.com (Marc Savy) Date: Thu, 14 Jun 2018 11:35:03 +0100 Subject: [Apiman-user] Apiman 1.4.0.Final released In-Reply-To: References: Message-ID: How annoying! I'll provide an update when I can verify OSSRH has published the plugins release properly. Due to the issues they're currently facing there's some strange behaviour at the moment. On 14 June 2018 at 11:13, Donovan Muller wrote: > Not working on my side: > > mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get \ > -Dartifact='io.apiman.plugins:apiman-plugins-circuit-breaker-policy:1.4.0.Final:war' > [INFO] Scanning for projects... > [INFO] > [INFO] ------------------< org.apache.maven:standalone-pom >>------------------- > [INFO] Building Maven Stub Project (No POM) 1 > [INFO] --------------------------------[ pom > ]--------------------------------- > [INFO] > [INFO] --- maven-dependency-plugin:2.8:get (default-cli) @ standalone-pom > --- > Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom > Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom > (0 B at 0 B/s) > Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom > Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom > (0 B at 0 B/s) > Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom > Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom > (0 B at 0 B/s) > Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.pom > Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.pom > (0 B at 0 B/s) > Downloading from central: > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.pom > Downloaded from central: > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.pom > (0 B at 0 B/s) > Downloading from central: > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.pom > Downloaded from central: > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.pom > (0 B at 0 B/s) > Downloading from central: > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.pom > Downloaded from central: > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.pom > (0 B at 0 B/s) > Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.pom > Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.pom > (0 B at 0 B/s) > Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.jar > Downloading from central: > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.jar > Downloading from central: > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.jar > Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar > Downloading from central: > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.jar > Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.jar > (0 B at 0 B/s) > Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.jar > Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.jar > (0 B at 0 B/s) > Downloaded from central: > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.jar > (0 B at 0 B/s) > Downloaded from central: > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.jar > (0 B at 0 B/s) > Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar > (0 B at 0 B/s) > Downloaded from central: > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.jar > (0 B at 0 B/s) > [INFO] Resolving > io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final with > transitive dependencies > Downloading from central: > https://repo.maven.apache.org/maven2/io/apiman/plugins/apiman-plugins-circuit-breaker-policy/1.4.0.Final/apiman-plugins-circuit-breaker-policy-1.4.0.Final.pom > [WARNING] Missing POM for > io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final > Downloading from central: > https://repo.maven.apache.org/maven2/io/apiman/plugins/apiman-plugins-circuit-breaker-policy/1.4.0.Final/apiman-plugins-circuit-breaker-policy-1.4.0.Final.war > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 5.775 s > [INFO] Finished at: 2018-06-14T12:12:01+02:00 > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-dependency-plugin:2.8:get (default-cli) on > project standalone-pom: Couldn't download artifact: Missing: > [ERROR] ---------- > [ERROR] 1) > io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final > [ERROR] > [ERROR] Try downloading the file manually from the project website. > [ERROR] > [ERROR] Then, install it using the command: > [ERROR] mvn install:install-file -DgroupId=io.apiman.plugins > -DartifactId=apiman-plugins-circuit-breaker-policy -Dversion=1.4.0.Final > -Dpackaging=war -Dfile=/path/to/file > [ERROR] > [ERROR] Alternatively, if you host your own repository you can deploy the > file there: > [ERROR] mvn deploy:deploy-file -DgroupId=io.apiman.plugins > -DartifactId=apiman-plugins-circuit-breaker-policy -Dversion=1.4.0.Final > -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > [ERROR] > [ERROR] Path to dependency: > [ERROR] 1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 > [ERROR] 2) > io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final > [ERROR] > [ERROR] ---------- > [ERROR] 1 required artifact is missing. > [ERROR] > [ERROR] for artifact: > [ERROR] org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 > [ERROR] > [ERROR] from the specified remote repositories: > [ERROR] central (https://repo.maven.apache.org/maven2, releases=true, > snapshots=false) > [ERROR] > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > > On Thu, 14 Jun 2018 at 12:08 Marc Savy wrote: >> >> search.maven.org tends to lag by several hours in my experience. >> >> Try this: >> >> mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get >> >> -Dartifact='io.apiman.plugins:apiman-plugins-circuit-breaker-policy:1.4.0.Final:war' >> >> Any luck? Seems to work on my end, but stuff might still be replicating >> out. >> >> On 14 June 2018 at 10:59, Donovan Muller wrote: >> > Thanks Marc, >> > >> > Still waiting for the plugins to reflect it seems: >> > https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22io.apiman.plugins%22 >> > >> > Thanks >> > >> > On Thu, 14 Jun 2018 at 10:46 Marc Savy wrote: >> >> >> >> Thanks for bringing this up, Donovan. >> >> >> >> As a quick update: it looks like something also went wrong during the >> >> release scripts for apiman-plugins and some of the version >> >> substitutions didn't happen properly (might be my fault, but I'm >> >> really not sure -- it's likely a consequence of earlier failures due >> >> to the OSSRH glitches interrupting things). >> >> >> >> I ended up having to do a force push on plugins to bring everything >> >> back into sync, so many apologies to anyone who pulled from master in >> >> the last 24h. >> >> >> >> Apiman plugins 1.4.0.Final release /should/ be available now -- I >> >> received an error from OSSRH but it seems to have deployed anyway. >> >> >> >> Please try it out. >> >> >> >> Regards, >> >> Marc >> >> >> >> >> >> >> >> On 14 June 2018 at 08:46, Marc Savy wrote: >> >> > Hi, >> >> > >> >> > It /should/ be there now. It seems to have hit a technical glitch of >> >> > some sort. I'll try again right now. >> >> > >> >> > There were some technical problems with Sonatype's OSSRH which meant >> >> > it took 2 days to get the release out (see: >> >> > https://issues.sonatype.org/browse/OSSRH-40470 and thread >> >> > https://twitter.com/marcsavy/status/1006606526050598912). >> >> > >> >> > On 14 June 2018 at 07:33, Donovan Muller >> >> > wrote: >> >> >> Hi, >> >> >> >> >> >> Thanks for the release! >> >> >> When will the 1.4.0 release plugins be published to Maven central >> >> >> (or >> >> >> perhaps another download site)? >> >> >> >> >> >> Thanks >> >> >> >> >> >> On Wed, 13 Jun 2018 at 17:04 Marc Savy wrote: >> >> >>> >> >> >>> Very happy to say that 1.4.0.Final has been released. >> >> >>> >> >> >>> Please try it out and give feedback. >> >> >>> >> >> >>> The major outward facing changes are: >> >> >>> - Upgrade Elasticsearch support to 5.x (from 1.x). >> >> >>> - Allow policies to suppress and allow connector headers via >> >> >>> policy >> >> >>> context >> >> >>> - Lots of bug-fixes >> >> >>> >> >> >>> When upgrading from ES 1.x to 5.x you may need to do an >> >> >>> export/import, >> >> >>> and/or follow Elasticsearch's own migration procedures if you >> >> >>> prefer. >> >> >>> >> >> >>> Vert.x (Gateway Only): >> >> >>> >> >> >>> >> >> >>> >> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-vertx-1.4.0.Final.zip >> >> >>> >> >> >>> WF10/EAP7.1: >> >> >>> >> >> >>> >> >> >>> >> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly10-1.4.0.Final-overlay.zip >> >> >>> >> >> >>> WF11: >> >> >>> >> >> >>> >> >> >>> >> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly11-1.4.0.Final-overlay.zip >> >> >>> >> >> >>> EAP7: >> >> >>> >> >> >>> >> >> >>> >> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-eap7-1.4.0.Final-overlay.zip >> >> >>> >> >> >>> Tomcat 8+: >> >> >>> >> >> >>> >> >> >>> >> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-tomcat8-1.4.0.Final-overlay.zip >> >> >>> >> >> >>> Regards, >> >> >>> Marc >> >> >>> _______________________________________________ >> >> >>> Apiman-user mailing list >> >> >>> Apiman-user at lists.jboss.org >> >> >>> https://lists.jboss.org/mailman/listinfo/apiman-user From marc.savy at redhat.com Thu Jun 14 07:45:44 2018 From: marc.savy at redhat.com (Marc Savy) Date: Thu, 14 Jun 2018 12:45:44 +0100 Subject: [Apiman-user] Apiman 1.4.0.Final released In-Reply-To: References: Message-ID: Seems to be working consistently for me now. Is it working on your end, too? On 14 June 2018 at 11:35, Marc Savy wrote: > How annoying! I'll provide an update when I can verify OSSRH has > published the plugins release properly. Due to the issues they're > currently facing there's some strange behaviour at the moment. > > On 14 June 2018 at 11:13, Donovan Muller wrote: >> Not working on my side: >> >> mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get \ >> -Dartifact='io.apiman.plugins:apiman-plugins-circuit-breaker-policy:1.4.0.Final:war' >> [INFO] Scanning for projects... >> [INFO] >> [INFO] ------------------< org.apache.maven:standalone-pom >>>------------------- >> [INFO] Building Maven Stub Project (No POM) 1 >> [INFO] --------------------------------[ pom >> ]--------------------------------- >> [INFO] >> [INFO] --- maven-dependency-plugin:2.8:get (default-cli) @ standalone-pom >> --- >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom >> (0 B at 0 B/s) >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom >> (0 B at 0 B/s) >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom >> (0 B at 0 B/s) >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.pom >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.pom >> (0 B at 0 B/s) >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.pom >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.pom >> (0 B at 0 B/s) >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.pom >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.pom >> (0 B at 0 B/s) >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.pom >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.pom >> (0 B at 0 B/s) >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.pom >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.pom >> (0 B at 0 B/s) >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.jar >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.jar >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.jar >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.jar >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.jar >> (0 B at 0 B/s) >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.jar >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.jar >> (0 B at 0 B/s) >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.jar >> (0 B at 0 B/s) >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.jar >> (0 B at 0 B/s) >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar >> (0 B at 0 B/s) >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.jar >> (0 B at 0 B/s) >> [INFO] Resolving >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final with >> transitive dependencies >> Downloading from central: >> https://repo.maven.apache.org/maven2/io/apiman/plugins/apiman-plugins-circuit-breaker-policy/1.4.0.Final/apiman-plugins-circuit-breaker-policy-1.4.0.Final.pom >> [WARNING] Missing POM for >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final >> Downloading from central: >> https://repo.maven.apache.org/maven2/io/apiman/plugins/apiman-plugins-circuit-breaker-policy/1.4.0.Final/apiman-plugins-circuit-breaker-policy-1.4.0.Final.war >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD FAILURE >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 5.775 s >> [INFO] Finished at: 2018-06-14T12:12:01+02:00 >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-dependency-plugin:2.8:get (default-cli) on >> project standalone-pom: Couldn't download artifact: Missing: >> [ERROR] ---------- >> [ERROR] 1) >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final >> [ERROR] >> [ERROR] Try downloading the file manually from the project website. >> [ERROR] >> [ERROR] Then, install it using the command: >> [ERROR] mvn install:install-file -DgroupId=io.apiman.plugins >> -DartifactId=apiman-plugins-circuit-breaker-policy -Dversion=1.4.0.Final >> -Dpackaging=war -Dfile=/path/to/file >> [ERROR] >> [ERROR] Alternatively, if you host your own repository you can deploy the >> file there: >> [ERROR] mvn deploy:deploy-file -DgroupId=io.apiman.plugins >> -DartifactId=apiman-plugins-circuit-breaker-policy -Dversion=1.4.0.Final >> -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] >> [ERROR] >> [ERROR] Path to dependency: >> [ERROR] 1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 >> [ERROR] 2) >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final >> [ERROR] >> [ERROR] ---------- >> [ERROR] 1 required artifact is missing. >> [ERROR] >> [ERROR] for artifact: >> [ERROR] org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 >> [ERROR] >> [ERROR] from the specified remote repositories: >> [ERROR] central (https://repo.maven.apache.org/maven2, releases=true, >> snapshots=false) >> [ERROR] >> [ERROR] -> [Help 1] >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e >> switch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> [ERROR] For more information about the errors and possible solutions, please >> read the following articles: >> [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >> >> On Thu, 14 Jun 2018 at 12:08 Marc Savy wrote: >>> >>> search.maven.org tends to lag by several hours in my experience. >>> >>> Try this: >>> >>> mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get >>> >>> -Dartifact='io.apiman.plugins:apiman-plugins-circuit-breaker-policy:1.4.0.Final:war' >>> >>> Any luck? Seems to work on my end, but stuff might still be replicating >>> out. >>> >>> On 14 June 2018 at 10:59, Donovan Muller wrote: >>> > Thanks Marc, >>> > >>> > Still waiting for the plugins to reflect it seems: >>> > https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22io.apiman.plugins%22 >>> > >>> > Thanks >>> > >>> > On Thu, 14 Jun 2018 at 10:46 Marc Savy wrote: >>> >> >>> >> Thanks for bringing this up, Donovan. >>> >> >>> >> As a quick update: it looks like something also went wrong during the >>> >> release scripts for apiman-plugins and some of the version >>> >> substitutions didn't happen properly (might be my fault, but I'm >>> >> really not sure -- it's likely a consequence of earlier failures due >>> >> to the OSSRH glitches interrupting things). >>> >> >>> >> I ended up having to do a force push on plugins to bring everything >>> >> back into sync, so many apologies to anyone who pulled from master in >>> >> the last 24h. >>> >> >>> >> Apiman plugins 1.4.0.Final release /should/ be available now -- I >>> >> received an error from OSSRH but it seems to have deployed anyway. >>> >> >>> >> Please try it out. >>> >> >>> >> Regards, >>> >> Marc >>> >> >>> >> >>> >> >>> >> On 14 June 2018 at 08:46, Marc Savy wrote: >>> >> > Hi, >>> >> > >>> >> > It /should/ be there now. It seems to have hit a technical glitch of >>> >> > some sort. I'll try again right now. >>> >> > >>> >> > There were some technical problems with Sonatype's OSSRH which meant >>> >> > it took 2 days to get the release out (see: >>> >> > https://issues.sonatype.org/browse/OSSRH-40470 and thread >>> >> > https://twitter.com/marcsavy/status/1006606526050598912). >>> >> > >>> >> > On 14 June 2018 at 07:33, Donovan Muller >>> >> > wrote: >>> >> >> Hi, >>> >> >> >>> >> >> Thanks for the release! >>> >> >> When will the 1.4.0 release plugins be published to Maven central >>> >> >> (or >>> >> >> perhaps another download site)? >>> >> >> >>> >> >> Thanks >>> >> >> >>> >> >> On Wed, 13 Jun 2018 at 17:04 Marc Savy wrote: >>> >> >>> >>> >> >>> Very happy to say that 1.4.0.Final has been released. >>> >> >>> >>> >> >>> Please try it out and give feedback. >>> >> >>> >>> >> >>> The major outward facing changes are: >>> >> >>> - Upgrade Elasticsearch support to 5.x (from 1.x). >>> >> >>> - Allow policies to suppress and allow connector headers via >>> >> >>> policy >>> >> >>> context >>> >> >>> - Lots of bug-fixes >>> >> >>> >>> >> >>> When upgrading from ES 1.x to 5.x you may need to do an >>> >> >>> export/import, >>> >> >>> and/or follow Elasticsearch's own migration procedures if you >>> >> >>> prefer. >>> >> >>> >>> >> >>> Vert.x (Gateway Only): >>> >> >>> >>> >> >>> >>> >> >>> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-vertx-1.4.0.Final.zip >>> >> >>> >>> >> >>> WF10/EAP7.1: >>> >> >>> >>> >> >>> >>> >> >>> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly10-1.4.0.Final-overlay.zip >>> >> >>> >>> >> >>> WF11: >>> >> >>> >>> >> >>> >>> >> >>> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly11-1.4.0.Final-overlay.zip >>> >> >>> >>> >> >>> EAP7: >>> >> >>> >>> >> >>> >>> >> >>> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-eap7-1.4.0.Final-overlay.zip >>> >> >>> >>> >> >>> Tomcat 8+: >>> >> >>> >>> >> >>> >>> >> >>> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-tomcat8-1.4.0.Final-overlay.zip >>> >> >>> >>> >> >>> Regards, >>> >> >>> Marc >>> >> >>> _______________________________________________ >>> >> >>> Apiman-user mailing list >>> >> >>> Apiman-user at lists.jboss.org >>> >> >>> https://lists.jboss.org/mailman/listinfo/apiman-user From donovan.muller at gmail.com Thu Jun 14 10:14:29 2018 From: donovan.muller at gmail.com (Donovan Muller) Date: Thu, 14 Jun 2018 16:14:29 +0200 Subject: [Apiman-user] Apiman 1.4.0.Final released In-Reply-To: References: Message-ID: Working now. Thanks On Thu, 14 Jun 2018 at 13:46 Marc Savy wrote: > Seems to be working consistently for me now. Is it working on your end, > too? > > On 14 June 2018 at 11:35, Marc Savy wrote: > > How annoying! I'll provide an update when I can verify OSSRH has > > published the plugins release properly. Due to the issues they're > > currently facing there's some strange behaviour at the moment. > > > > On 14 June 2018 at 11:13, Donovan Muller > wrote: > >> Not working on my side: > >> > >> mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get \ > >> > -Dartifact='io.apiman.plugins:apiman-plugins-circuit-breaker-policy:1.4.0.Final:war' > >> [INFO] Scanning for projects... > >> [INFO] > >> [INFO] ------------------< org.apache.maven:standalone-pom > >>>------------------- > >> [INFO] Building Maven Stub Project (No POM) 1 > >> [INFO] --------------------------------[ pom > >> ]--------------------------------- > >> [INFO] > >> [INFO] --- maven-dependency-plugin:2.8:get (default-cli) @ > standalone-pom > >> --- > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom > >> (0 B at 0 B/s) > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom > >> (0 B at 0 B/s) > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom > >> (0 B at 0 B/s) > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.pom > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.pom > >> (0 B at 0 B/s) > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.pom > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.pom > >> (0 B at 0 B/s) > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.pom > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.pom > >> (0 B at 0 B/s) > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.pom > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.pom > >> (0 B at 0 B/s) > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.pom > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.pom > >> (0 B at 0 B/s) > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.jar > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.jar > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.jar > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.jar > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.jar > >> (0 B at 0 B/s) > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.jar > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.jar > >> (0 B at 0 B/s) > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.jar > >> (0 B at 0 B/s) > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.jar > >> (0 B at 0 B/s) > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar > >> (0 B at 0 B/s) > >> Downloaded from central: > >> > https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.jar > >> (0 B at 0 B/s) > >> [INFO] Resolving > >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final > with > >> transitive dependencies > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/io/apiman/plugins/apiman-plugins-circuit-breaker-policy/1.4.0.Final/apiman-plugins-circuit-breaker-policy-1.4.0.Final.pom > >> [WARNING] Missing POM for > >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final > >> Downloading from central: > >> > https://repo.maven.apache.org/maven2/io/apiman/plugins/apiman-plugins-circuit-breaker-policy/1.4.0.Final/apiman-plugins-circuit-breaker-policy-1.4.0.Final.war > >> [INFO] > >> ------------------------------------------------------------------------ > >> [INFO] BUILD FAILURE > >> [INFO] > >> ------------------------------------------------------------------------ > >> [INFO] Total time: 5.775 s > >> [INFO] Finished at: 2018-06-14T12:12:01+02:00 > >> [INFO] > >> ------------------------------------------------------------------------ > >> [ERROR] Failed to execute goal > >> org.apache.maven.plugins:maven-dependency-plugin:2.8:get (default-cli) > on > >> project standalone-pom: Couldn't download artifact: Missing: > >> [ERROR] ---------- > >> [ERROR] 1) > >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final > >> [ERROR] > >> [ERROR] Try downloading the file manually from the project website. > >> [ERROR] > >> [ERROR] Then, install it using the command: > >> [ERROR] mvn install:install-file -DgroupId=io.apiman.plugins > >> -DartifactId=apiman-plugins-circuit-breaker-policy -Dversion=1.4.0.Final > >> -Dpackaging=war -Dfile=/path/to/file > >> [ERROR] > >> [ERROR] Alternatively, if you host your own repository you can deploy > the > >> file there: > >> [ERROR] mvn deploy:deploy-file -DgroupId=io.apiman.plugins > >> -DartifactId=apiman-plugins-circuit-breaker-policy -Dversion=1.4.0.Final > >> -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > >> [ERROR] > >> [ERROR] Path to dependency: > >> [ERROR] 1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 > >> [ERROR] 2) > >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final > >> [ERROR] > >> [ERROR] ---------- > >> [ERROR] 1 required artifact is missing. > >> [ERROR] > >> [ERROR] for artifact: > >> [ERROR] org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 > >> [ERROR] > >> [ERROR] from the specified remote repositories: > >> [ERROR] central (https://repo.maven.apache.org/maven2, releases=true, > >> snapshots=false) > >> [ERROR] > >> [ERROR] -> [Help 1] > >> [ERROR] > >> [ERROR] To see the full stack trace of the errors, re-run Maven with > the -e > >> switch. > >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. > >> [ERROR] > >> [ERROR] For more information about the errors and possible solutions, > please > >> read the following articles: > >> [ERROR] [Help 1] > >> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > >> > >> On Thu, 14 Jun 2018 at 12:08 Marc Savy wrote: > >>> > >>> search.maven.org tends to lag by several hours in my experience. > >>> > >>> Try this: > >>> > >>> mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get > >>> > >>> > -Dartifact='io.apiman.plugins:apiman-plugins-circuit-breaker-policy:1.4.0.Final:war' > >>> > >>> Any luck? Seems to work on my end, but stuff might still be replicating > >>> out. > >>> > >>> On 14 June 2018 at 10:59, Donovan Muller > wrote: > >>> > Thanks Marc, > >>> > > >>> > Still waiting for the plugins to reflect it seems: > >>> > > https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22io.apiman.plugins%22 > >>> > > >>> > Thanks > >>> > > >>> > On Thu, 14 Jun 2018 at 10:46 Marc Savy wrote: > >>> >> > >>> >> Thanks for bringing this up, Donovan. > >>> >> > >>> >> As a quick update: it looks like something also went wrong during > the > >>> >> release scripts for apiman-plugins and some of the version > >>> >> substitutions didn't happen properly (might be my fault, but I'm > >>> >> really not sure -- it's likely a consequence of earlier failures due > >>> >> to the OSSRH glitches interrupting things). > >>> >> > >>> >> I ended up having to do a force push on plugins to bring everything > >>> >> back into sync, so many apologies to anyone who pulled from master > in > >>> >> the last 24h. > >>> >> > >>> >> Apiman plugins 1.4.0.Final release /should/ be available now -- I > >>> >> received an error from OSSRH but it seems to have deployed anyway. > >>> >> > >>> >> Please try it out. > >>> >> > >>> >> Regards, > >>> >> Marc > >>> >> > >>> >> > >>> >> > >>> >> On 14 June 2018 at 08:46, Marc Savy wrote: > >>> >> > Hi, > >>> >> > > >>> >> > It /should/ be there now. It seems to have hit a technical glitch > of > >>> >> > some sort. I'll try again right now. > >>> >> > > >>> >> > There were some technical problems with Sonatype's OSSRH which > meant > >>> >> > it took 2 days to get the release out (see: > >>> >> > https://issues.sonatype.org/browse/OSSRH-40470 and thread > >>> >> > https://twitter.com/marcsavy/status/1006606526050598912). > >>> >> > > >>> >> > On 14 June 2018 at 07:33, Donovan Muller < > donovan.muller at gmail.com> > >>> >> > wrote: > >>> >> >> Hi, > >>> >> >> > >>> >> >> Thanks for the release! > >>> >> >> When will the 1.4.0 release plugins be published to Maven central > >>> >> >> (or > >>> >> >> perhaps another download site)? > >>> >> >> > >>> >> >> Thanks > >>> >> >> > >>> >> >> On Wed, 13 Jun 2018 at 17:04 Marc Savy > wrote: > >>> >> >>> > >>> >> >>> Very happy to say that 1.4.0.Final has been released. > >>> >> >>> > >>> >> >>> Please try it out and give feedback. > >>> >> >>> > >>> >> >>> The major outward facing changes are: > >>> >> >>> - Upgrade Elasticsearch support to 5.x (from 1.x). > >>> >> >>> - Allow policies to suppress and allow connector headers via > >>> >> >>> policy > >>> >> >>> context > >>> >> >>> - Lots of bug-fixes > >>> >> >>> > >>> >> >>> When upgrading from ES 1.x to 5.x you may need to do an > >>> >> >>> export/import, > >>> >> >>> and/or follow Elasticsearch's own migration procedures if you > >>> >> >>> prefer. > >>> >> >>> > >>> >> >>> Vert.x (Gateway Only): > >>> >> >>> > >>> >> >>> > >>> >> >>> > >>> >> >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-vertx-1.4.0.Final.zip > >>> >> >>> > >>> >> >>> WF10/EAP7.1: > >>> >> >>> > >>> >> >>> > >>> >> >>> > >>> >> >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly10-1.4.0.Final-overlay.zip > >>> >> >>> > >>> >> >>> WF11: > >>> >> >>> > >>> >> >>> > >>> >> >>> > >>> >> >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly11-1.4.0.Final-overlay.zip > >>> >> >>> > >>> >> >>> EAP7: > >>> >> >>> > >>> >> >>> > >>> >> >>> > >>> >> >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-eap7-1.4.0.Final-overlay.zip > >>> >> >>> > >>> >> >>> Tomcat 8+: > >>> >> >>> > >>> >> >>> > >>> >> >>> > >>> >> >>> > http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-tomcat8-1.4.0.Final-overlay.zip > >>> >> >>> > >>> >> >>> Regards, > >>> >> >>> Marc > >>> >> >>> _______________________________________________ > >>> >> >>> Apiman-user mailing list > >>> >> >>> Apiman-user at lists.jboss.org > >>> >> >>> https://lists.jboss.org/mailman/listinfo/apiman-user > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20180614/c0b6572c/attachment-0001.html From btlin1025 at hotmail.com Fri Jun 15 05:13:06 2018 From: btlin1025 at hotmail.com (=?big5?B?qkwgrGanyg==?=) Date: Fri, 15 Jun 2018 09:13:06 +0000 Subject: [Apiman-user] =?big5?b?pl7C0DogIElzIGl0IHBvc3NpYmxlIGJsb2NraW5n?= =?big5?b?IHJlcXVlc3QgYWZ0ZXIgcmVxdWVzdCBib2R5IHBhcnNpbmc/?= In-Reply-To: References: , Message-ID: Dear Marc Sorry that I tried to reproduce the issue in my local test environment however I can't get body content anymore without ticking the stateful payload introspection option. Besides I just enable 1 policy in order to simplify the test. If you need more information, please let me know. Thanks for your help. ________________________________ ???: Marc Savy ????: 2018?6?12? ?? 10:28 ???: ? ?? ??: Eric Wittmann; apiman-user at lists.jboss.org ??: Re: [Apiman-user] Is it possible blocking request after request body parsing? I haven't been able to reproduce this. Could you please provide a bit more information so I can debug this. 1. What is your policy chain 2. Can you provide a skeleton policy that reproduces the issue where you say you are able to get a parsed entity without ticking the appropriate box in the UI? On 30 April 2018 at 02:16, ? ?? wrote: > Thanks for your information. > I'll enable this option for parsing request body. > > ________________________________ > ???: Marc Savy > ????: 2018?4?26? ?? 07:36 > ???: Eric Wittmann > ??: ? ??; apiman-user at lists.jboss.org > > ??: Re: [Apiman-user] Is it possible blocking request after request body > parsing? > > Thanks. I'll check it out and report back. > > On 26 April 2018 at 12:26, Eric Wittmann wrote: >> Yes that is the UI option I was referring to. >> >> If the request payload is being parsed without that option being set, then >> there is a bug in the Apiman gateway. I will write up a bug report for >> that >> so that @marcsavy can have a look. :) >> >> -Eric >> >> >> On Thu, Apr 26, 2018 at 4:36 AM, ? ?? wrote: >>> >>> Dear Eric >>> >>> Thanks for your helpful information. >>> I can get request body with IPolicyContext object. >>> Besides, you also mentioned enable this on a per-API basis in the apiman >>> UI. >>> Is It "Enable stateful request payload insepction" in API implementation >>> tab? >>> I'm wondering because I didn't enable this option but can still get the >>> request body in doApply() with IPolicyContext. >>> What is the difference if I enable this option? >>> Thanks >>> >>> Regards >>> >>> ________________________________ >>> ???: Eric Wittmann >>> ????: 2018?4?25? ?? 08:15 >>> ???: ? ?? >>> ??: apiman-user at lists.jboss.org >>> ??: Re: [Apiman-user] Is it possible blocking request after request body >>> parsing? >>> >>> Yes there is a feature where apiman will parse the request BEFORE >>> applying >>> the policies. This will make the HTTP request body available to all >>> policies in the chain, should they need them. >>> >>> You can enable this on a per-API basis in the apiman UI. >>> >>> When this feature is enabled, your custom policy can access the request >>> body as an object found in the IPolicyContext object. For example: >>> >>> Object payload = context.getAttribute("apiman.request-payload"); >>> >>> The type of thing that you get depends on the API's endpoint type. The >>> endpoint type might be JSON, XML, or SOAP. I think it might be possible >>> to >>> have some other kind of endpoint type, but those three are handled by the >>> request body parser feature. >>> >>> Here is what you'll get as that payload object, depending on endpoint >>> type: >>> >>> JSON - Java Map object as a result of parsing the JSON data using Jackson >>> XML - org.w3c.dom.Document >>> Soap - javax.xml.soap.SOAPEnvelope >>> Anything Else - byte[] >>> >>> So for example, if your endpoint type is XML, then you could do this in >>> your policy implementation (in the doApply() method): >>> >>> org.w3c.dom.Document requestBody = (org.w3c.dom.Document) >>> context.gettAttribute("apiman.request-payload"); >>> >>> And then you could make some decision using the request data and e.g. >>> call >>> doFailure(). >>> >>> Also note - you can *change* the request body at this point as well. For >>> example you could apply a XML Transformation to the w3c Document, >>> resulting >>> in a new w3c Document object, which you could store in the Policy Context >>> (at the same key, obviously). That new document would then get >>> serialized >>> and sent as the request body to the backing API impl. There may be some >>> Content-Length issues if you do that, I can't remember... >>> >>> -Eric >>> >>> >>> On Wed, Apr 25, 2018 at 1:29 AM, ? ?? wrote: >>> >>> Hi all, >>> I would like to customize a policy, which parses the request body and >>> blocks the request in case. >>> in http://www.apiman.io/latest/developer-guide.html 4.2.1.2 IData policy, >>> it describes: >>> The request or response body will not begin streaming before the >>> corresponding doApply has been called, however, it is still possible to >>> interrupt the conversation during the streaming phase by signalling >>> doFailure or doError. >>> When I trace the transformation-policy source code, doApply() executes >>> before getRequestDataHandler() which matches the description. >>> In doApply() I can blocks the request via chain.doFailure() however I >>> have >>> no idea how to interrupt/block request in getRequestDataHandler(). >>> Besides, I found following mail group which is similar to my question. >>> Eric also points it's possible to parse the body before apply in request: >>> >>> On Thu, Feb 2, 2017 at 10:31 PM, Eric Wittmann < >>> eric.wittmann at redhat.com> wrote: >>> >>> The bottom line here is that you cannot return a Policy Failure (or >>> customize it) based on information in the response body. The response >>> is >>> streamed from the back-end to the client, and at the time streaming >>> begins, >>> the response code and HTTP headers have already been sent. >>> >>> It sounds to me like you're asking for a feature where you can parse >>> the response body *before* the policy's "apply" method is invoked. we >>> have >>> such a feature for requests, but not for responses. I suspect core >>> changes >>> to apiman would be required to enable that. It seems like a reasonable >>> request to me, as long as users of the feature understand the >>> performance >>> and memory requirements of enabling it. >>> >>> -Eric >>> >>> Thanks for any comments in advance. >>> Kind Regards >>> BT >>> >>> >>> _______________________________________________ >>> Apiman-user mailing list >>> Apiman-user at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/apiman-user >>> >>> >> >> >> _______________________________________________ >> Apiman-user mailing list >> Apiman-user at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/apiman-user >> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20180615/1d3c8919/attachment.html From donovan.muller at gmail.com Tue Jun 19 12:17:52 2018 From: donovan.muller at gmail.com (Donovan Muller) Date: Tue, 19 Jun 2018 18:17:52 +0200 Subject: [Apiman-user] Apiman 1.4.0.Final released In-Reply-To: References: Message-ID: Hi Marc, Do you have a eta on a 1.4.1 release? On Thu, 14 Jun 2018 at 16:14, Donovan Muller wrote: > Working now. Thanks > > On Thu, 14 Jun 2018 at 13:46 Marc Savy wrote: > >> Seems to be working consistently for me now. Is it working on your end, >> too? >> >> On 14 June 2018 at 11:35, Marc Savy wrote: >> > How annoying! I'll provide an update when I can verify OSSRH has >> > published the plugins release properly. Due to the issues they're >> > currently facing there's some strange behaviour at the moment. >> > >> > On 14 June 2018 at 11:13, Donovan Muller >> wrote: >> >> Not working on my side: >> >> >> >> mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get \ >> >> >> -Dartifact='io.apiman.plugins:apiman-plugins-circuit-breaker-policy:1.4.0.Final:war' >> >> [INFO] Scanning for projects... >> >> [INFO] >> >> [INFO] ------------------< org.apache.maven:standalone-pom >> >>>------------------- >> >> [INFO] Building Maven Stub Project (No POM) 1 >> >> [INFO] --------------------------------[ pom >> >> ]--------------------------------- >> >> [INFO] >> >> [INFO] --- maven-dependency-plugin:2.8:get (default-cli) @ >> standalone-pom >> >> --- >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom >> >> (0 B at 0 B/s) >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom >> >> (0 B at 0 B/s) >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom >> >> (0 B at 0 B/s) >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.pom >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.pom >> >> (0 B at 0 B/s) >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.pom >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.pom >> >> (0 B at 0 B/s) >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.pom >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.pom >> >> (0 B at 0 B/s) >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.pom >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.pom >> >> (0 B at 0 B/s) >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.pom >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.pom >> >> (0 B at 0 B/s) >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.jar >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.jar >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.jar >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.jar >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.jar >> >> (0 B at 0 B/s) >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.jar >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.jar >> >> (0 B at 0 B/s) >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.jar >> >> (0 B at 0 B/s) >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.jar >> >> (0 B at 0 B/s) >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar >> >> (0 B at 0 B/s) >> >> Downloaded from central: >> >> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.jar >> >> (0 B at 0 B/s) >> >> [INFO] Resolving >> >> >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final with >> >> transitive dependencies >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/io/apiman/plugins/apiman-plugins-circuit-breaker-policy/1.4.0.Final/apiman-plugins-circuit-breaker-policy-1.4.0.Final.pom >> >> [WARNING] Missing POM for >> >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final >> >> Downloading from central: >> >> >> https://repo.maven.apache.org/maven2/io/apiman/plugins/apiman-plugins-circuit-breaker-policy/1.4.0.Final/apiman-plugins-circuit-breaker-policy-1.4.0.Final.war >> >> [INFO] >> >> >> ------------------------------------------------------------------------ >> >> [INFO] BUILD FAILURE >> >> [INFO] >> >> >> ------------------------------------------------------------------------ >> >> [INFO] Total time: 5.775 s >> >> [INFO] Finished at: 2018-06-14T12:12:01+02:00 >> >> [INFO] >> >> >> ------------------------------------------------------------------------ >> >> [ERROR] Failed to execute goal >> >> org.apache.maven.plugins:maven-dependency-plugin:2.8:get (default-cli) >> on >> >> project standalone-pom: Couldn't download artifact: Missing: >> >> [ERROR] ---------- >> >> [ERROR] 1) >> >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final >> >> [ERROR] >> >> [ERROR] Try downloading the file manually from the project website. >> >> [ERROR] >> >> [ERROR] Then, install it using the command: >> >> [ERROR] mvn install:install-file -DgroupId=io.apiman.plugins >> >> -DartifactId=apiman-plugins-circuit-breaker-policy >> -Dversion=1.4.0.Final >> >> -Dpackaging=war -Dfile=/path/to/file >> >> [ERROR] >> >> [ERROR] Alternatively, if you host your own repository you can >> deploy the >> >> file there: >> >> [ERROR] mvn deploy:deploy-file -DgroupId=io.apiman.plugins >> >> -DartifactId=apiman-plugins-circuit-breaker-policy >> -Dversion=1.4.0.Final >> >> -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] >> >> [ERROR] >> >> [ERROR] Path to dependency: >> >> [ERROR] 1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 >> >> [ERROR] 2) >> >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final >> >> [ERROR] >> >> [ERROR] ---------- >> >> [ERROR] 1 required artifact is missing. >> >> [ERROR] >> >> [ERROR] for artifact: >> >> [ERROR] org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 >> >> [ERROR] >> >> [ERROR] from the specified remote repositories: >> >> [ERROR] central (https://repo.maven.apache.org/maven2, >> releases=true, >> >> snapshots=false) >> >> [ERROR] >> >> [ERROR] -> [Help 1] >> >> [ERROR] >> >> [ERROR] To see the full stack trace of the errors, re-run Maven with >> the -e >> >> switch. >> >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> >> [ERROR] >> >> [ERROR] For more information about the errors and possible solutions, >> please >> >> read the following articles: >> >> [ERROR] [Help 1] >> >> >> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >> >> >> >> On Thu, 14 Jun 2018 at 12:08 Marc Savy wrote: >> >>> >> >>> search.maven.org tends to lag by several hours in my experience. >> >>> >> >>> Try this: >> >>> >> >>> mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get >> >>> >> >>> >> -Dartifact='io.apiman.plugins:apiman-plugins-circuit-breaker-policy:1.4.0.Final:war' >> >>> >> >>> Any luck? Seems to work on my end, but stuff might still be >> replicating >> >>> out. >> >>> >> >>> On 14 June 2018 at 10:59, Donovan Muller >> wrote: >> >>> > Thanks Marc, >> >>> > >> >>> > Still waiting for the plugins to reflect it seems: >> >>> > >> https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22io.apiman.plugins%22 >> >>> > >> >>> > Thanks >> >>> > >> >>> > On Thu, 14 Jun 2018 at 10:46 Marc Savy >> wrote: >> >>> >> >> >>> >> Thanks for bringing this up, Donovan. >> >>> >> >> >>> >> As a quick update: it looks like something also went wrong during >> the >> >>> >> release scripts for apiman-plugins and some of the version >> >>> >> substitutions didn't happen properly (might be my fault, but I'm >> >>> >> really not sure -- it's likely a consequence of earlier failures >> due >> >>> >> to the OSSRH glitches interrupting things). >> >>> >> >> >>> >> I ended up having to do a force push on plugins to bring everything >> >>> >> back into sync, so many apologies to anyone who pulled from master >> in >> >>> >> the last 24h. >> >>> >> >> >>> >> Apiman plugins 1.4.0.Final release /should/ be available now -- I >> >>> >> received an error from OSSRH but it seems to have deployed anyway. >> >>> >> >> >>> >> Please try it out. >> >>> >> >> >>> >> Regards, >> >>> >> Marc >> >>> >> >> >>> >> >> >>> >> >> >>> >> On 14 June 2018 at 08:46, Marc Savy wrote: >> >>> >> > Hi, >> >>> >> > >> >>> >> > It /should/ be there now. It seems to have hit a technical >> glitch of >> >>> >> > some sort. I'll try again right now. >> >>> >> > >> >>> >> > There were some technical problems with Sonatype's OSSRH which >> meant >> >>> >> > it took 2 days to get the release out (see: >> >>> >> > https://issues.sonatype.org/browse/OSSRH-40470 and thread >> >>> >> > https://twitter.com/marcsavy/status/1006606526050598912). >> >>> >> > >> >>> >> > On 14 June 2018 at 07:33, Donovan Muller < >> donovan.muller at gmail.com> >> >>> >> > wrote: >> >>> >> >> Hi, >> >>> >> >> >> >>> >> >> Thanks for the release! >> >>> >> >> When will the 1.4.0 release plugins be published to Maven >> central >> >>> >> >> (or >> >>> >> >> perhaps another download site)? >> >>> >> >> >> >>> >> >> Thanks >> >>> >> >> >> >>> >> >> On Wed, 13 Jun 2018 at 17:04 Marc Savy >> wrote: >> >>> >> >>> >> >>> >> >>> Very happy to say that 1.4.0.Final has been released. >> >>> >> >>> >> >>> >> >>> Please try it out and give feedback. >> >>> >> >>> >> >>> >> >>> The major outward facing changes are: >> >>> >> >>> - Upgrade Elasticsearch support to 5.x (from 1.x). >> >>> >> >>> - Allow policies to suppress and allow connector headers via >> >>> >> >>> policy >> >>> >> >>> context >> >>> >> >>> - Lots of bug-fixes >> >>> >> >>> >> >>> >> >>> When upgrading from ES 1.x to 5.x you may need to do an >> >>> >> >>> export/import, >> >>> >> >>> and/or follow Elasticsearch's own migration procedures if you >> >>> >> >>> prefer. >> >>> >> >>> >> >>> >> >>> Vert.x (Gateway Only): >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-vertx-1.4.0.Final.zip >> >>> >> >>> >> >>> >> >>> WF10/EAP7.1: >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly10-1.4.0.Final-overlay.zip >> >>> >> >>> >> >>> >> >>> WF11: >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly11-1.4.0.Final-overlay.zip >> >>> >> >>> >> >>> >> >>> EAP7: >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-eap7-1.4.0.Final-overlay.zip >> >>> >> >>> >> >>> >> >>> Tomcat 8+: >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-tomcat8-1.4.0.Final-overlay.zip >> >>> >> >>> >> >>> >> >>> Regards, >> >>> >> >>> Marc >> >>> >> >>> _______________________________________________ >> >>> >> >>> Apiman-user mailing list >> >>> >> >>> Apiman-user at lists.jboss.org >> >>> >> >>> https://lists.jboss.org/mailman/listinfo/apiman-user >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20180619/a986f8c1/attachment-0001.html From marc.savy at redhat.com Tue Jun 19 12:44:18 2018 From: marc.savy at redhat.com (Marc Savy) Date: Tue, 19 Jun 2018 17:44:18 +0100 Subject: [Apiman-user] 1.4.1.Final release in progress Message-ID: Hi All, We've released Apiman 1.4.1.Final with a couple of bug-fixes: * A race condition for ES index initialisation that caused a unimpactful, but annoying, exception message. * Assign IConnectorConfig in IPolicyContext earlier to avoid it being null in Vert.x Vert.x (Gateway Only): http://downloads.jboss.org/apiman/1.4.1.Final/apiman-distro-vertx-1.4.1.Final.zip WF10/EAP7.1: http://downloads.jboss.org/apiman/1.4.1.Final/apiman-distro-wildfly10-1.4.1.Final-overlay.zip WF11: http://downloads.jboss.org/apiman/1.4.1.Final/apiman-distro-wildfly11-1.4.1.Final-overlay.zip EAP7: http://downloads.jboss.org/apiman/1.4.1.Final/apiman-distro-eap7-1.4.1.Final-overlay.zip Tomcat 8+: http://downloads.jboss.org/apiman/1.4.1.Final/apiman-distro-tomcat8-1.4.1.Final-overlay.zip Regards, Marc From marc.savy at redhat.com Tue Jun 19 12:45:58 2018 From: marc.savy at redhat.com (Marc Savy) Date: Tue, 19 Jun 2018 17:45:58 +0100 Subject: [Apiman-user] 1.4.1.Final release in progress In-Reply-To: References: Message-ID: Sorry, subject should have been "1.4.1.Final released"; I decided to wait a while this time before emailing given our previous ORSSH problems - but didn't change my draft title. On 19 June 2018 at 17:44, Marc Savy wrote: > Hi All, > > We've released Apiman 1.4.1.Final with a couple of bug-fixes: > > * A race condition for ES index initialisation that caused a > unimpactful, but annoying, exception message. > * Assign IConnectorConfig in IPolicyContext earlier to avoid it being > null in Vert.x > > Vert.x (Gateway Only): > http://downloads.jboss.org/apiman/1.4.1.Final/apiman-distro-vertx-1.4.1.Final.zip > > WF10/EAP7.1: > http://downloads.jboss.org/apiman/1.4.1.Final/apiman-distro-wildfly10-1.4.1.Final-overlay.zip > > WF11: > http://downloads.jboss.org/apiman/1.4.1.Final/apiman-distro-wildfly11-1.4.1.Final-overlay.zip > > EAP7: > http://downloads.jboss.org/apiman/1.4.1.Final/apiman-distro-eap7-1.4.1.Final-overlay.zip > > Tomcat 8+: > http://downloads.jboss.org/apiman/1.4.1.Final/apiman-distro-tomcat8-1.4.1.Final-overlay.zip > > Regards, > Marc From marc.savy at redhat.com Tue Jun 19 12:46:23 2018 From: marc.savy at redhat.com (Marc Savy) Date: Tue, 19 Jun 2018 17:46:23 +0100 Subject: [Apiman-user] Apiman 1.4.0.Final released In-Reply-To: References: Message-ID: Hi, It /should/ already be available. Regards, Marc On 19 June 2018 at 17:17, Donovan Muller wrote: > Hi Marc, > > Do you have a eta on a 1.4.1 release? > > On Thu, 14 Jun 2018 at 16:14, Donovan Muller > wrote: >> >> Working now. Thanks >> >> On Thu, 14 Jun 2018 at 13:46 Marc Savy wrote: >>> >>> Seems to be working consistently for me now. Is it working on your end, >>> too? >>> >>> On 14 June 2018 at 11:35, Marc Savy wrote: >>> > How annoying! I'll provide an update when I can verify OSSRH has >>> > published the plugins release properly. Due to the issues they're >>> > currently facing there's some strange behaviour at the moment. >>> > >>> > On 14 June 2018 at 11:13, Donovan Muller >>> > wrote: >>> >> Not working on my side: >>> >> >>> >> mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get \ >>> >> >>> >> -Dartifact='io.apiman.plugins:apiman-plugins-circuit-breaker-policy:1.4.0.Final:war' >>> >> [INFO] Scanning for projects... >>> >> [INFO] >>> >> [INFO] ------------------< org.apache.maven:standalone-pom >>> >>>------------------- >>> >> [INFO] Building Maven Stub Project (No POM) 1 >>> >> [INFO] --------------------------------[ pom >>> >> ]--------------------------------- >>> >> [INFO] >>> >> [INFO] --- maven-dependency-plugin:2.8:get (default-cli) @ >>> >> standalone-pom >>> >> --- >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom >>> >> (0 B at 0 B/s) >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom >>> >> (0 B at 0 B/s) >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom >>> >> (0 B at 0 B/s) >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.pom >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.pom >>> >> (0 B at 0 B/s) >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.pom >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.pom >>> >> (0 B at 0 B/s) >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.pom >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.pom >>> >> (0 B at 0 B/s) >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.pom >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.pom >>> >> (0 B at 0 B/s) >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.pom >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.pom >>> >> (0 B at 0 B/s) >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.jar >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.jar >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.jar >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.jar >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.jar >>> >> (0 B at 0 B/s) >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.jar >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.4/maven-dependency-analyzer-1.4.jar >>> >> (0 B at 0 B/s) >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.3/plexus-archiver-2.3.jar >>> >> (0 B at 0 B/s) >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.6/plexus-io-2.0.6.jar >>> >> (0 B at 0 B/s) >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar >>> >> (0 B at 0 B/s) >>> >> Downloaded from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.9/plexus-utils-3.0.9.jar >>> >> (0 B at 0 B/s) >>> >> [INFO] Resolving >>> >> >>> >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final with >>> >> transitive dependencies >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/io/apiman/plugins/apiman-plugins-circuit-breaker-policy/1.4.0.Final/apiman-plugins-circuit-breaker-policy-1.4.0.Final.pom >>> >> [WARNING] Missing POM for >>> >> >>> >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final >>> >> Downloading from central: >>> >> >>> >> https://repo.maven.apache.org/maven2/io/apiman/plugins/apiman-plugins-circuit-breaker-policy/1.4.0.Final/apiman-plugins-circuit-breaker-policy-1.4.0.Final.war >>> >> [INFO] >>> >> >>> >> ------------------------------------------------------------------------ >>> >> [INFO] BUILD FAILURE >>> >> [INFO] >>> >> >>> >> ------------------------------------------------------------------------ >>> >> [INFO] Total time: 5.775 s >>> >> [INFO] Finished at: 2018-06-14T12:12:01+02:00 >>> >> [INFO] >>> >> >>> >> ------------------------------------------------------------------------ >>> >> [ERROR] Failed to execute goal >>> >> org.apache.maven.plugins:maven-dependency-plugin:2.8:get (default-cli) >>> >> on >>> >> project standalone-pom: Couldn't download artifact: Missing: >>> >> [ERROR] ---------- >>> >> [ERROR] 1) >>> >> >>> >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final >>> >> [ERROR] >>> >> [ERROR] Try downloading the file manually from the project website. >>> >> [ERROR] >>> >> [ERROR] Then, install it using the command: >>> >> [ERROR] mvn install:install-file -DgroupId=io.apiman.plugins >>> >> -DartifactId=apiman-plugins-circuit-breaker-policy >>> >> -Dversion=1.4.0.Final >>> >> -Dpackaging=war -Dfile=/path/to/file >>> >> [ERROR] >>> >> [ERROR] Alternatively, if you host your own repository you can >>> >> deploy the >>> >> file there: >>> >> [ERROR] mvn deploy:deploy-file -DgroupId=io.apiman.plugins >>> >> -DartifactId=apiman-plugins-circuit-breaker-policy >>> >> -Dversion=1.4.0.Final >>> >> -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] >>> >> [ERROR] >>> >> [ERROR] Path to dependency: >>> >> [ERROR] 1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 >>> >> [ERROR] 2) >>> >> >>> >> io.apiman.plugins:apiman-plugins-circuit-breaker-policy:war:1.4.0.Final >>> >> [ERROR] >>> >> [ERROR] ---------- >>> >> [ERROR] 1 required artifact is missing. >>> >> [ERROR] >>> >> [ERROR] for artifact: >>> >> [ERROR] org.apache.maven.plugins:maven-downloader-plugin:jar:1.0 >>> >> [ERROR] >>> >> [ERROR] from the specified remote repositories: >>> >> [ERROR] central (https://repo.maven.apache.org/maven2, >>> >> releases=true, >>> >> snapshots=false) >>> >> [ERROR] >>> >> [ERROR] -> [Help 1] >>> >> [ERROR] >>> >> [ERROR] To see the full stack trace of the errors, re-run Maven with >>> >> the -e >>> >> switch. >>> >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>> >> [ERROR] >>> >> [ERROR] For more information about the errors and possible solutions, >>> >> please >>> >> read the following articles: >>> >> [ERROR] [Help 1] >>> >> >>> >> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >>> >> >>> >> On Thu, 14 Jun 2018 at 12:08 Marc Savy wrote: >>> >>> >>> >>> search.maven.org tends to lag by several hours in my experience. >>> >>> >>> >>> Try this: >>> >>> >>> >>> mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get >>> >>> >>> >>> >>> >>> -Dartifact='io.apiman.plugins:apiman-plugins-circuit-breaker-policy:1.4.0.Final:war' >>> >>> >>> >>> Any luck? Seems to work on my end, but stuff might still be >>> >>> replicating >>> >>> out. >>> >>> >>> >>> On 14 June 2018 at 10:59, Donovan Muller >>> >>> wrote: >>> >>> > Thanks Marc, >>> >>> > >>> >>> > Still waiting for the plugins to reflect it seems: >>> >>> > >>> >>> > https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22io.apiman.plugins%22 >>> >>> > >>> >>> > Thanks >>> >>> > >>> >>> > On Thu, 14 Jun 2018 at 10:46 Marc Savy >>> >>> > wrote: >>> >>> >> >>> >>> >> Thanks for bringing this up, Donovan. >>> >>> >> >>> >>> >> As a quick update: it looks like something also went wrong during >>> >>> >> the >>> >>> >> release scripts for apiman-plugins and some of the version >>> >>> >> substitutions didn't happen properly (might be my fault, but I'm >>> >>> >> really not sure -- it's likely a consequence of earlier failures >>> >>> >> due >>> >>> >> to the OSSRH glitches interrupting things). >>> >>> >> >>> >>> >> I ended up having to do a force push on plugins to bring >>> >>> >> everything >>> >>> >> back into sync, so many apologies to anyone who pulled from master >>> >>> >> in >>> >>> >> the last 24h. >>> >>> >> >>> >>> >> Apiman plugins 1.4.0.Final release /should/ be available now -- I >>> >>> >> received an error from OSSRH but it seems to have deployed anyway. >>> >>> >> >>> >>> >> Please try it out. >>> >>> >> >>> >>> >> Regards, >>> >>> >> Marc >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> >> On 14 June 2018 at 08:46, Marc Savy wrote: >>> >>> >> > Hi, >>> >>> >> > >>> >>> >> > It /should/ be there now. It seems to have hit a technical >>> >>> >> > glitch of >>> >>> >> > some sort. I'll try again right now. >>> >>> >> > >>> >>> >> > There were some technical problems with Sonatype's OSSRH which >>> >>> >> > meant >>> >>> >> > it took 2 days to get the release out (see: >>> >>> >> > https://issues.sonatype.org/browse/OSSRH-40470 and thread >>> >>> >> > https://twitter.com/marcsavy/status/1006606526050598912). >>> >>> >> > >>> >>> >> > On 14 June 2018 at 07:33, Donovan Muller >>> >>> >> > >>> >>> >> > wrote: >>> >>> >> >> Hi, >>> >>> >> >> >>> >>> >> >> Thanks for the release! >>> >>> >> >> When will the 1.4.0 release plugins be published to Maven >>> >>> >> >> central >>> >>> >> >> (or >>> >>> >> >> perhaps another download site)? >>> >>> >> >> >>> >>> >> >> Thanks >>> >>> >> >> >>> >>> >> >> On Wed, 13 Jun 2018 at 17:04 Marc Savy >>> >>> >> >> wrote: >>> >>> >> >>> >>> >>> >> >>> Very happy to say that 1.4.0.Final has been released. >>> >>> >> >>> >>> >>> >> >>> Please try it out and give feedback. >>> >>> >> >>> >>> >>> >> >>> The major outward facing changes are: >>> >>> >> >>> - Upgrade Elasticsearch support to 5.x (from 1.x). >>> >>> >> >>> - Allow policies to suppress and allow connector headers >>> >>> >> >>> via >>> >>> >> >>> policy >>> >>> >> >>> context >>> >>> >> >>> - Lots of bug-fixes >>> >>> >> >>> >>> >>> >> >>> When upgrading from ES 1.x to 5.x you may need to do an >>> >>> >> >>> export/import, >>> >>> >> >>> and/or follow Elasticsearch's own migration procedures if you >>> >>> >> >>> prefer. >>> >>> >> >>> >>> >>> >> >>> Vert.x (Gateway Only): >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-vertx-1.4.0.Final.zip >>> >>> >> >>> >>> >>> >> >>> WF10/EAP7.1: >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly10-1.4.0.Final-overlay.zip >>> >>> >> >>> >>> >>> >> >>> WF11: >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-wildfly11-1.4.0.Final-overlay.zip >>> >>> >> >>> >>> >>> >> >>> EAP7: >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-eap7-1.4.0.Final-overlay.zip >>> >>> >> >>> >>> >>> >> >>> Tomcat 8+: >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> >> >>> http://downloads.jboss.org/apiman/1.4.0.Final/apiman-distro-tomcat8-1.4.0.Final-overlay.zip >>> >>> >> >>> >>> >>> >> >>> Regards, >>> >>> >> >>> Marc >>> >>> >> >>> _______________________________________________ >>> >>> >> >>> Apiman-user mailing list >>> >>> >> >>> Apiman-user at lists.jboss.org >>> >>> >> >>> https://lists.jboss.org/mailman/listinfo/apiman-user From marc.savy at redhat.com Fri Jun 22 10:06:43 2018 From: marc.savy at redhat.com (Marc Savy) Date: Fri, 22 Jun 2018 15:06:43 +0100 Subject: [Apiman-user] Apiman 1.4 release blog Message-ID: http://www.apiman.io/blog/apiman/release/2018/06/22/release-1.4.html You guys likely know this already, but just in case :-). From marc.savy at redhat.com Mon Jun 25 11:57:45 2018 From: marc.savy at redhat.com (Marc Savy) Date: Mon, 25 Jun 2018 16:57:45 +0100 Subject: [Apiman-user] Bug in Vert.x Gateway was preventing plugins being loading from static config Message-ID: This might only hit more advanced users, but I discovered that on the Vert.x Gateway that plugins were not being loaded from the static config (conf.json). This is distinct from any policy plugin stuff. For example, if you had your request-parser loaded from a custom plugin: "request-parser": { "class": "plugin:io.apiman.plugins:custom-path-parser-plugin-demo:1.4.2.Final:war/io.apiman.plugins.demo.custompathparser.CustomPathParserImpl", "config": { "defaultOrgName": "Apiman" } } This would fail to work properly. I've fixed it now, and shall do a 1.4.2.Final release shortly unless some problems pop up. Please do try it out on master if this is a feature you use. I have been drafting up a blog post showing how to write your own path parser implementation (so you can have custom URL patterns on your Apiman Gateway). So, watch out for that one! Regards, Marc