From edewit at redhat.com Tue Sep 1 02:44:15 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 1 Sep 2015 08:44:15 +0200 Subject: [aerogear-dev] cordova push plugin release Message-ID: I've create a release branch (release) for your testing pleasure with the cordova push plugin 2.0.3. 2 issues have been resolved there is now windows platform support and a fix in the android lib that broke the categories. If there aren't any issues reported I'll release this version -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150901/a8c8e4f2/attachment.html From edewit at redhat.com Tue Sep 1 05:26:39 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 1 Sep 2015 11:26:39 +0200 Subject: [aerogear-dev] crypto release Message-ID: Prepared a release branch of the crypto plugin it fixes the promise plugin dependency and updated the crypto libs for your testing pleasure if no issues are found I'll create a release -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150901/d0a5eaa8/attachment.html From lholmqui at redhat.com Tue Sep 1 09:22:23 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Tue, 1 Sep 2015 09:22:23 -0400 Subject: [aerogear-dev] UnifiedPush js client In-Reply-To: References: Message-ID: On Mon, Aug 31, 2015 at 12:01 PM, Matthias Wessendorf wrote: > sure, let's do it - makes it obvious something changed > > Yea, before i do the bump, i'll have to see what else we want/need to remove. I know notifier we deprecated. I'll start a separate ML thread for all this 3.0 talk and what the future might look like for the JS Lib > On Mon, Aug 31, 2015 at 5:29 PM, Luke Holmquist > wrote: > >> The new Repo is now here https://github.com/aerogear/aerogear-js-push !! >> >> I'll create some JIRA's to update the Readme, update aerogear.org, >> remove the code from the main repo, etc... >> >> >> Question. Will this require a major version bump once i remove the code? >> i'm thinking yes >> >> On Mon, Aug 31, 2015 at 5:11 AM, Corinne Krych >> wrote: >> >>> +1 >>> This way, we're getting closer to native libs approach with separate libs >>> >>> On 31 August 2015 at 10:55, Luk?? Fry? wrote: >>> >>>> You are right Luke, this start to make more and more sense :-) >>>> >>>> On Mon, Aug 24, 2015 at 7:22 PM, Luke Holmquist >>>> wrote: >>>> >>>>> so i decided to take a gander at the push client lib in the >>>>> aerogear.js project. Currently if someone would like to use it, they >>>>> have a couple options. >>>>> >>>>> 1. download the whole lib, >>>>> 2. download a custom build from the website >>>>> 3. download a custom build from bower >>>>> 4. create a custom build from source >>>>> >>>>> In the past i think i was against breaking out pieces of the JS lib >>>>> into separate repo's since we could just use the AeroGearComponents repo i >>>>> created for custom builds. But i think with the state of the JS lib(not >>>>> sure where it's going), it might make sense to, at least with the push >>>>> lib(perhaps the simplePush polyfill also) to break those out into separate >>>>> repo's similar to the other client projects. >>>>> >>>>> I think the starting vision of the project has changed, so perhaps >>>>> this change is good.(this should probably be a whole separate thread) >>>>> >>>>> Now that Chrome and Safari have push in the browser, FF is getting it >>>>> also very soon, it's possible this part of the library will be used more >>>>> >>>>> >>>>> thoughts? >>>>> >>>>> -Luke >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150901/064171fc/attachment-0001.html From lholmqui at redhat.com Tue Sep 1 15:02:25 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Tue, 1 Sep 2015 15:02:25 -0400 Subject: [aerogear-dev] SimplePush Polyfill work In-Reply-To: <55E4DC35.9020003@gmail.com> References: <55E4DC35.9020003@gmail.com> Message-ID: On Mon, Aug 31, 2015 at 6:59 PM, JR Conlin wrote: > +4 > > (sorry, just had some fun with a bounding issue, and felt like sharing.) > > Just to let y'all know, we're going to be running SimplePush for a while, > mostly for older devices. One thing we discovered is that some clients may > have a LARGE number of old channels registered and sending them as part of > the Hello is a waste. (Our server doesn't pay attention to them.) Newer > clients may have an interim fix that blanks the clientIDs:[] record.) Aside > from that, we're definitely not going to be pushing any changes that should > impact your library. > > We've not stood up a production WebPush server, partly because the data > encryption portion of the standard is still under discussion. For what it's > worth, there are also a few other discussion points that have yet to be > finalized (e.g. should developers register with servers, should clients > specify channels like they did for SimplePush, etc.) but the data bit is > the biggest obstacle. > i see that PushAPI is enabled in FF42, and i've successfully gotten notifications with a test i did, what kind of server are you using then? i noticed that in the"dom.push.serverURL" is wss:// push.services.mozilla.com/ > > As always, thanks so much for the continuing support. > > > On 8/31/2015 12:45 PM, Idel Pivnitskiy wrote: > > +1 > > Best regards, > Idel Pivnitskiy > -- > E-mail: Idel.Pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > > On Mon, Aug 31, 2015 at 7:27 PM, Daniel Bevenius < > daniel.bevenius at gmail.com> wrote: > >> +1 >> >> >> m?ndag 31 augusti 2015 skrev Sebastien Blanc < >> scm.blanc at gmail.com>: >> >>> +1 >>> >>> On Mon, Aug 31, 2015 at 5:12 PM, Luke Holmquist >>> wrote: >>> >>>> so now that WebPush is going to take over SimplePush, i'm thinking of >>>> closing the related JIRA's that we have open for simple push in the AG-JS >>>> instance. >>>> >>>> >>>> Not that we've really done any work on it lately, but it would be good >>>> to clean this up a little. >>>> >>>> >>>> Thoughts? >>>> >>>> >>>> -Luke >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > _______________________________________________ > aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150901/e1d6505b/attachment.html From jrconlin at gmail.com Tue Sep 1 17:03:31 2015 From: jrconlin at gmail.com (JR Conlin) Date: Tue, 1 Sep 2015 14:03:31 -0700 Subject: [aerogear-dev] SimplePush Polyfill work In-Reply-To: References: <55E4DC35.9020003@gmail.com> Message-ID: <55E612A3.9030906@gmail.com> On 9/1/2015 12:02 PM, Luke Holmquist wrote: > > > On Mon, Aug 31, 2015 at 6:59 PM, JR Conlin > wrote: > > +4 > > (sorry, just had some fun with a bounding issue, and felt like > sharing.) > > Just to let y'all know, we're going to be running SimplePush for a > while, mostly for older devices. One thing we discovered is that > some clients may have a LARGE number of old channels registered > and sending them as part of the Hello is a waste. (Our server > doesn't pay attention to them.) Newer clients may have an interim > fix that blanks the clientIDs:[] record.) Aside from that, we're > definitely not going to be pushing any changes that should impact > your library. > > We've not stood up a production WebPush server, partly because the > data encryption portion of the standard is still under discussion. > For what it's worth, there are also a few other discussion points > that have yet to be finalized (e.g. should developers register > with servers, should clients specify channels like they did for > SimplePush, etc.) but the data bit is the biggest obstacle. > > > i see that PushAPI is enabled in FF42, and i've successfully gotten > notifications with a test i did, what kind of server are you using > then? i noticed that in the"dom.push.serverURL" is > wss://push.services.mozilla.com/ The server we're using is still "simplepush". There's some tweaks we've done in prep for WebPush, but it's not running as an HTTP2 service. For the more python inclined, here's a pointer to the source: https://github.com/mozilla-services/autopush/ (Some of you may note that this is python and not Go. Turns out that python currently has more optimal libraries for doing this at larger scale. As you happy Java folk know, sometimes good things come well aged.) Eventually WebPush will come out with mandatory data encryption and HTTP2 connections. Google's WebPush kinda/sorta does that now, except they bury the client side into GCM and expose a portion of the server, but it serves as an example of what's to come. Microsoft has also noted that they'll be supporting WebPush eventually, although they've expressed different concerns they'd like to have addressed. Apple, is Apple, and if they release their version, we hope that it follows the spec. > > > > As always, thanks so much for the continuing support. > > > On 8/31/2015 12:45 PM, Idel Pivnitskiy wrote: >> +1 >> >> Best regards, >> Idel Pivnitskiy >> -- >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> >> On Mon, Aug 31, 2015 at 7:27 PM, Daniel Bevenius >> > wrote: >> >> +1 >> >> >> m?ndag 31 augusti 2015 skrev Sebastien Blanc >> >: >> >> +1 >> >> On Mon, Aug 31, 2015 at 5:12 PM, Luke Holmquist >> > wrote: >> >> so now that WebPush is going to take over SimplePush, >> i'm thinking of closing the related JIRA's that we >> have open for simple push in the AG-JS instance. >> >> >> Not that we've really done any work on it lately, >> but it would be good to clean this up a little. >> >> >> Thoughts? >> >> >> -Luke >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150901/8801fc08/attachment-0001.html From bruno at abstractj.org Tue Sep 1 18:40:27 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 01 Sep 2015 15:40:27 -0700 (PDT) Subject: [aerogear-dev] SimplePush Polyfill work In-Reply-To: <55E4DC35.9020003@gmail.com> References: <55E4DC35.9020003@gmail.com> Message-ID: <1441147226792.c06b7218@Nodemailer> Do you have any reference about the encryption discussion. I'd be interested to read more about it. ? abstractj PGP: 0x84DC9914 On Mon, Aug 31, 2015 at 7:59 PM, JR Conlin wrote: > +4 > (sorry, just had some fun with a bounding issue, and felt like sharing.) > Just to let y'all know, we're going to be running SimplePush for a > while, mostly for older devices. One thing we discovered is that some > clients may have a LARGE number of old channels registered and sending > them as part of the Hello is a waste. (Our server doesn't pay attention > to them.) Newer clients may have an interim fix that blanks the > clientIDs:[] record.) Aside from that, we're definitely not going to be > pushing any changes that should impact your library. > We've not stood up a production WebPush server, partly because the data > encryption portion of the standard is still under discussion. For what > it's worth, there are also a few other discussion points that have yet > to be finalized (e.g. should developers register with servers, should > clients specify channels like they did for SimplePush, etc.) but the > data bit is the biggest obstacle. > As always, thanks so much for the continuing support. > On 8/31/2015 12:45 PM, Idel Pivnitskiy wrote: >> +1 >> >> Best regards, >> Idel Pivnitskiy >> -- >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> >> On Mon, Aug 31, 2015 at 7:27 PM, Daniel Bevenius >> > wrote: >> >> +1 >> >> >> m?ndag 31 augusti 2015 skrev Sebastien Blanc > >: >> >> +1 >> >> On Mon, Aug 31, 2015 at 5:12 PM, Luke Holmquist >> wrote: >> >> so now that WebPush is going to take over SimplePush, i'm >> thinking of closing the related JIRA's that we have open >> for simple push in the AG-JS instance. >> >> >> Not that we've really done any work on it lately, but it >> would be good to clean this up a little. >> >> >> Thoughts? >> >> >> -Luke >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150901/30692ea3/attachment.html From jrconlin at gmail.com Tue Sep 1 19:00:09 2015 From: jrconlin at gmail.com (JR Conlin) Date: Tue, 1 Sep 2015 16:00:09 -0700 Subject: [aerogear-dev] SimplePush Polyfill work In-Reply-To: <1441147226792.c06b7218@Nodemailer> References: <55E4DC35.9020003@gmail.com> <1441147226792.c06b7218@Nodemailer> Message-ID: <55E62DF9.3090405@gmail.com> Right now, the best source is the WebPush IETF discussion. https://mailarchive.ietf.org/arch/search/?email_list=webpush&q=encryption In short, folks are leaning toward AES curve25519, because it's greatly improved security over P-256, and there are enough libraries in the wild that it should be reasonable for App developers to use one. Required encryption is tricky for any number of reasons. In this case, the goal is to secure your message from the intermediary carriers. Notably, it's a lot easier for carriers to avoid adding pen registries or turning over data if it's just a pile of indecipherable crap. The message is decrypted by the handling client which also generates the public key the remote server uses and is passed as part of the remote registration. The theory is also that if you're running on a compromised client, you're kinda dorked. If you're THAT paranoid (and not saying it's a bad), it's just up to you do do your own encryption as well. On 9/1/2015 3:40 PM, Bruno Oliveira wrote: > Do you have any reference about the encryption discussion. I'd be > interested to read more about it. > > ? abstractj PGP: 0x84DC9914 > > > On Mon, Aug 31, 2015 at 7:59 PM, JR Conlin > wrote: > > +4 > > (sorry, just had some fun with a bounding issue, and felt like > sharing.) > > Just to let y'all know, we're going to be running SimplePush for a > while, mostly for older devices. One thing we discovered is that > some clients may have a LARGE number of old channels registered > and sending them as part of the Hello is a waste. (Our server > doesn't pay attention to them.) Newer clients may have an interim > fix that blanks the clientIDs:[] record.) Aside from that, we're > definitely not going to be pushing any changes that should impact > your library. > > We've not stood up a production WebPush server, partly because the > data encryption portion of the standard is still under discussion. > For what it's worth, there are also a few other discussion points > that have yet to be finalized (e.g. should developers register > with servers, should clients specify channels like they did for > SimplePush, etc.) but the data bit is the biggest obstacle. > > As always, thanks so much for the continuing support. > > > On 8/31/2015 12:45 PM, Idel Pivnitskiy wrote: >> +1 >> >> Best regards, >> Idel Pivnitskiy >> -- >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> >> On Mon, Aug 31, 2015 at 7:27 PM, Daniel Bevenius >> > wrote: >> >> +1 >> >> >> m?ndag 31 augusti 2015 skrev Sebastien Blanc >> : >> >> +1 >> >> On Mon, Aug 31, 2015 at 5:12 PM, Luke Holmquist >> wrote: >> >> so now that WebPush is going to take over SimplePush, >> i'm thinking of closing the related JIRA's that we >> have open for simple push in the AG-JS instance. >> >> >> Not that we've really done any work on it lately, >> but it would be good to clean this up a little. >> >> >> Thoughts? >> >> >> -Luke >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150901/429d79f2/attachment-0001.html From supittma at redhat.com Wed Sep 2 15:03:32 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 2 Sep 2015 15:03:32 -0400 Subject: [aerogear-dev] GCM Topics Support Cont. Message-ID: So the current PRs for Topics use them automatically when you subscribe to a category. Google doesn't support delivering messages to a subset of users over a topic. UPS has the ability to deliver messages to subsets of category subscribers (via alias and deviceType). I think that a suitable workaround for this would be if a message is sent to a category, and there is a topic available, AND the message isn't filtered based on alias or deviceType then use the topic. Otherwise the message should be treated "normally" and use registrationId based sending (like we do now). wdyt? And as an aside, can you guys think of other use cases where the all or nothing nature of topics might be a problem? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150902/be56cb5a/attachment.html From edewit at redhat.com Thu Sep 3 02:12:07 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 3 Sep 2015 08:12:07 +0200 Subject: [aerogear-dev] GCM Topics Support Cont. In-Reply-To: References: Message-ID: That sounds very good On Wed, Sep 2, 2015 at 9:03 PM, Summers Pittman wrote: > So the current PRs for Topics use them automatically when you subscribe to > a category. Google doesn't support delivering messages to a subset of > users over a topic. UPS has the ability to deliver messages to subsets of > category subscribers (via alias and deviceType). > > I think that a suitable workaround for this would be if a message is sent > to a category, and there is a topic available, AND the message isn't > filtered based on alias or deviceType then use the topic. Otherwise the > message should be treated "normally" and use registrationId based sending > (like we do now). > > > wdyt? > > And as an aside, can you guys think of other use cases where the all or > nothing nature of topics might be a problem? > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150903/bb5c1518/attachment.html From edewit at redhat.com Thu Sep 3 05:47:29 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 3 Sep 2015 11:47:29 +0200 Subject: [aerogear-dev] Cordova push release 2.0.3 Message-ID: I've pushed the release button, again what has changed this release: Release 2.0.3 Bug AGCORDOVA-118 - Adding unifiedpush plugin to cordova project does not work Feature Request AGCORDOVA-109 - Support windows platform Plus updated the android library to version 2.2.2 where a bug was fixed for categories AGDROID-492 - Categories field not working also known as AGCORDOVA-112 Happy coding! -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150903/8d4f2a12/attachment.html From matzew at apache.org Thu Sep 3 06:34:14 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 3 Sep 2015 12:34:14 +0200 Subject: [aerogear-dev] Cordova push release 2.0.3 In-Reply-To: References: Message-ID: yay! On Thu, Sep 3, 2015 at 11:47 AM, Erik Jan de Wit wrote: > I've pushed the release button, again what has changed this release: > > Release 2.0.3 > > > Bug > > AGCORDOVA-118 - Adding > unifiedpush plugin to cordova project does not work > Feature Request > > AGCORDOVA-109 - Support > windows platform > > Plus updated the android library to version 2.2.2 where a bug was fixed > for categories > AGDROID-492 - Categories > field not working > also known as AGCORDOVA-112 > > > Happy coding! > -- > Cheers, > Erik Jan > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150903/5ce2dd30/attachment.html From lholmqui at redhat.com Thu Sep 3 10:41:30 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Thu, 3 Sep 2015 10:41:30 -0400 Subject: [aerogear-dev] New Node sender release Message-ID: Hello, We've just cut a new release of the Node Sender, 0.9.0, https://github.com/aerogear/aerogear-unifiedpush-nodejs-client/releases/tag/0.9.0 This release adds the ability to specify custom headers. Node on my Friends -Luke -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150903/7f414fe4/attachment.html From edewit at redhat.com Fri Sep 4 03:07:06 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 4 Sep 2015 09:07:06 +0200 Subject: [aerogear-dev] crypto release In-Reply-To: References: Message-ID: I've pushed the release button, again what has been fixed in this release: Bug - AGCORDOVA-117 - Crypto plugin has outdated dependency - AGCORDOVA-119 - promise plugin can not be found On Tue, Sep 1, 2015 at 11:26 AM, Erik Jan de Wit wrote: > Prepared a release branch of the crypto plugin it fixes the promise plugin > dependency and updated the crypto libs for your testing pleasure if no > issues are found I'll create a release > > -- > Cheers, > Erik Jan > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150904/472c015f/attachment-0001.html From lholmqui at redhat.com Fri Sep 4 08:31:01 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Fri, 4 Sep 2015 08:31:01 -0400 Subject: [aerogear-dev] Github Protected Branches Message-ID: https://github.com/blog/2051-protected-branches-and-required-status-checks I think this would be good for us to implement -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150904/e138461f/attachment.html From idel.pivnitskiy at gmail.com Fri Sep 4 08:41:26 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Fri, 4 Sep 2015 15:41:26 +0300 Subject: [aerogear-dev] Netty updates Message-ID: Netty team released new versions this week: 4.0.31.Final [1] and 4.1.0.Beta6 [2] For our WebPush Server we're using 4.1.0.Beta5 now. And beta6 has the important change for us - full support of HTTP/2 as specified by RFC7540. I'm gonna update it after merging of current opened PR [3]. [1] http://netty.io/news/2015/09/02/4-0-31-Final.html [2] http://netty.io/news/2015/09/02/4-1-0-Beta6.html [3] https://github.com/aerogear/aerogear-webpush-server/pull/14 Best, Idel Pivnitskiy -- E-mail: Idel.Pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150904/0e7f5d8c/attachment.html From bruno at abstractj.org Fri Sep 4 12:09:25 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Fri, 4 Sep 2015 13:09:25 -0300 Subject: [aerogear-dev] Github Protected Branches In-Reply-To: References: Message-ID: I feel 50/50 about it, sometimes we have to rebase and fix some mess in the Git tree. On Fri, Sep 4, 2015 at 9:31 AM, Luke Holmquist wrote: > https://github.com/blog/2051-protected-branches-and-required-status-checks > > I think this would be good for us to implement > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- "The measure of a man is what he does with power" - Plato - @abstractj - Volenti Nihil Difficile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150904/91690e52/attachment.html From matzew at apache.org Mon Sep 7 05:21:21 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 7 Sep 2015 11:21:21 +0200 Subject: [aerogear-dev] Github Protected Branches In-Reply-To: References: Message-ID: same here. I think perhaps we "just" protect master? On Fri, Sep 4, 2015 at 6:09 PM, Bruno Oliveira wrote: > I feel 50/50 about it, sometimes we have to rebase and fix some mess in > the Git tree. > > On Fri, Sep 4, 2015 at 9:31 AM, Luke Holmquist > wrote: > >> https://github.com/blog/2051-protected-branches-and-required-status-checks >> >> I think this would be good for us to implement >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > > -- > "The measure of a man is what he does with power" - Plato > - > @abstractj > - > Volenti Nihil Difficile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150907/05554c99/attachment.html From edewit at redhat.com Mon Sep 7 05:51:53 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Mon, 7 Sep 2015 11:51:53 +0200 Subject: [aerogear-dev] Github Protected Branches In-Reply-To: References: Message-ID: +1 makes sense to enable this for master and maintenance brances On Mon, Sep 7, 2015 at 11:21 AM, Matthias Wessendorf wrote: > same here. I think perhaps we "just" protect master? > > On Fri, Sep 4, 2015 at 6:09 PM, Bruno Oliveira > wrote: > >> I feel 50/50 about it, sometimes we have to rebase and fix some mess in >> the Git tree. >> >> On Fri, Sep 4, 2015 at 9:31 AM, Luke Holmquist >> wrote: >> >>> >>> https://github.com/blog/2051-protected-branches-and-required-status-checks >>> >>> I think this would be good for us to implement >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> >> -- >> "The measure of a man is what he does with power" - Plato >> - >> @abstractj >> - >> Volenti Nihil Difficile >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150907/6b1a6558/attachment.html From bruno at abstractj.org Mon Sep 7 06:18:49 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 07 Sep 2015 03:18:49 -0700 (PDT) Subject: [aerogear-dev] Github Protected Branches In-Reply-To: References: Message-ID: <1441621129161.cefaec6c@Nodemailer> I think if we really need this, it's because were doing it wrong. ? abstractj PGP: 0x84DC9914 On Mon, Sep 7, 2015 at 6:52 AM, Erik Jan de Wit wrote: > +1 makes sense to enable this for master and maintenance brances > On Mon, Sep 7, 2015 at 11:21 AM, Matthias Wessendorf > wrote: >> same here. I think perhaps we "just" protect master? >> >> On Fri, Sep 4, 2015 at 6:09 PM, Bruno Oliveira >> wrote: >> >>> I feel 50/50 about it, sometimes we have to rebase and fix some mess in >>> the Git tree. >>> >>> On Fri, Sep 4, 2015 at 9:31 AM, Luke Holmquist >>> wrote: >>> >>>> >>>> https://github.com/blog/2051-protected-branches-and-required-status-checks >>>> >>>> I think this would be good for us to implement >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> >>> -- >>> "The measure of a man is what he does with power" - Plato >>> - >>> @abstractj >>> - >>> Volenti Nihil Difficile >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > -- > Cheers, > Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150907/2eb41964/attachment-0001.html From edewit at redhat.com Mon Sep 7 06:47:16 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Mon, 7 Sep 2015 12:47:16 +0200 Subject: [aerogear-dev] Github Protected Branches In-Reply-To: <1441621129161.cefaec6c@Nodemailer> References: <1441621129161.cefaec6c@Nodemailer> Message-ID: better save then sorry I would say On Mon, Sep 7, 2015 at 12:18 PM, Bruno Oliveira wrote: > I think if we really need this, it's because were doing it wrong. > > ? abstractj PGP: 0x84DC9914 > > > On Mon, Sep 7, 2015 at 6:52 AM, Erik Jan de Wit wrote: > >> +1 makes sense to enable this for master and maintenance brances >> >> On Mon, Sep 7, 2015 at 11:21 AM, Matthias Wessendorf >> wrote: >> >>> same here. I think perhaps we "just" protect master? >>> >>> On Fri, Sep 4, 2015 at 6:09 PM, Bruno Oliveira >>> wrote: >>> >>>> I feel 50/50 about it, sometimes we have to rebase and fix some mess in >>>> the Git tree. >>>> >>>> On Fri, Sep 4, 2015 at 9:31 AM, Luke Holmquist >>>> wrote: >>>> >>>>> >>>>> https://github.com/blog/2051-protected-branches-and-required-status-checks >>>>> >>>>> I think this would be good for us to implement >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> -- >>>> "The measure of a man is what he does with power" - Plato >>>> - >>>> @abstractj >>>> - >>>> Volenti Nihil Difficile >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Cheers, >> Erik Jan >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150907/1d3412ba/attachment.html From scm.blanc at gmail.com Tue Sep 8 05:15:27 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 8 Sep 2015 11:15:27 +0200 Subject: [aerogear-dev] Staging of UPS 1.1.0.Final Message-ID: Hi team, I'm happy to announce that UPS 1.1.0 Final has been staged. Please test the staged release : https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6516 By the end of the week I'd like to press the button to release it to the wild. Sebi ps : the openshift update will follow -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150908/48d95285/attachment.html From matzew at apache.org Tue Sep 8 05:17:16 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 8 Sep 2015 11:17:16 +0200 Subject: [aerogear-dev] Staging of UPS 1.1.0.Final In-Reply-To: References: Message-ID: alright, thanks! I will do the OpenShift updates, based on the git tag On Tue, Sep 8, 2015 at 11:15 AM, Sebastien Blanc wrote: > Hi team, > > I'm happy to announce that UPS 1.1.0 Final has been staged. > > Please test the staged release : > > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6516 > > By the end of the week I'd like to press the button to release it to the > wild. > > Sebi > > ps : the openshift update will follow > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150908/f6cd6b0c/attachment.html From idel.pivnitskiy at gmail.com Tue Sep 8 07:33:35 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Tue, 8 Sep 2015 14:33:35 +0300 Subject: [aerogear-dev] Staging of UPS 1.1.0.Final In-Reply-To: References: Message-ID: I've just checked MireDot API documentation. Everything is ok, but it has some insignificant issues. I uploaded the latest version here [1], see Issues tab. We could hide them [2], before publishing on www.aerogear.org, or fix them and move the git tag. [1] http://condor.pp.ua/aerogear-ups-rest-api-doc/latest/index.html [2] http://miredot.com/docs/manual/output-configuration/hide-issues-tab/ Best regards, Idel Pivnitskiy -- E-mail: Idel.Pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy On Tue, Sep 8, 2015 at 12:17 PM, Matthias Wessendorf wrote: > alright, thanks! > > I will do the OpenShift updates, based on the git tag > > On Tue, Sep 8, 2015 at 11:15 AM, Sebastien Blanc > wrote: > >> Hi team, >> >> I'm happy to announce that UPS 1.1.0 Final has been staged. >> >> Please test the staged release : >> >> >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6516 >> >> By the end of the week I'd like to press the button to release it to the >> wild. >> >> Sebi >> >> ps : the openshift update will follow >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150908/252f9850/attachment-0001.html From matzew at apache.org Tue Sep 8 07:40:51 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 8 Sep 2015 13:40:51 +0200 Subject: [aerogear-dev] Staging of UPS 1.1.0.Final In-Reply-To: References: Message-ID: Wanna send a PR ? I am fine in publishing a tweak version for 1.1.0 and keep the tag "incorrect" -M On Tue, Sep 8, 2015 at 1:33 PM, Idel Pivnitskiy wrote: > I've just checked MireDot API documentation. Everything is ok, but it has > some insignificant issues. I uploaded the latest version here [1], see > Issues tab. > > We could hide them [2], before publishing on www.aerogear.org, or fix > them and move the git tag. > > [1] http://condor.pp.ua/aerogear-ups-rest-api-doc/latest/index.html > [2] http://miredot.com/docs/manual/output-configuration/hide-issues-tab/ > > Best regards, > Idel Pivnitskiy > -- > E-mail: Idel.Pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > > On Tue, Sep 8, 2015 at 12:17 PM, Matthias Wessendorf > wrote: > >> alright, thanks! >> >> I will do the OpenShift updates, based on the git tag >> >> On Tue, Sep 8, 2015 at 11:15 AM, Sebastien Blanc >> wrote: >> >>> Hi team, >>> >>> I'm happy to announce that UPS 1.1.0 Final has been staged. >>> >>> Please test the staged release : >>> >>> >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6516 >>> >>> By the end of the week I'd like to press the button to release it to >>> the wild. >>> >>> Sebi >>> >>> ps : the openshift update will follow >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150908/1df92f04/attachment.html From idel.pivnitskiy at gmail.com Tue Sep 8 07:43:39 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Tue, 8 Sep 2015 14:43:39 +0300 Subject: [aerogear-dev] Staging of UPS 1.1.0.Final In-Reply-To: References: Message-ID: Sure, will send Best regards, Idel Pivnitskiy -- E-mail: Idel.Pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy On Tue, Sep 8, 2015 at 2:40 PM, Matthias Wessendorf wrote: > Wanna send a PR ? I am fine in publishing a tweak version for 1.1.0 and > keep the tag "incorrect" > > -M > > On Tue, Sep 8, 2015 at 1:33 PM, Idel Pivnitskiy > wrote: > >> I've just checked MireDot API documentation. Everything is ok, but it has >> some insignificant issues. I uploaded the latest version here [1], see >> Issues tab. >> >> We could hide them [2], before publishing on www.aerogear.org, or fix >> them and move the git tag. >> >> [1] http://condor.pp.ua/aerogear-ups-rest-api-doc/latest/index.html >> [2] http://miredot.com/docs/manual/output-configuration/hide-issues-tab/ >> >> Best regards, >> Idel Pivnitskiy >> -- >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> >> On Tue, Sep 8, 2015 at 12:17 PM, Matthias Wessendorf >> wrote: >> >>> alright, thanks! >>> >>> I will do the OpenShift updates, based on the git tag >>> >>> On Tue, Sep 8, 2015 at 11:15 AM, Sebastien Blanc >>> wrote: >>> >>>> Hi team, >>>> >>>> I'm happy to announce that UPS 1.1.0 Final has been staged. >>>> >>>> Please test the staged release : >>>> >>>> >>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6516 >>>> >>>> By the end of the week I'd like to press the button to release it to >>>> the wild. >>>> >>>> Sebi >>>> >>>> ps : the openshift update will follow >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150908/7ff5aa80/attachment.html From matzew at apache.org Tue Sep 8 08:11:53 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 8 Sep 2015 14:11:53 +0200 Subject: [aerogear-dev] Staging of UPS 1.1.0.Final In-Reply-To: References: Message-ID: here is the OpenShift PR: https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/22 -Matthias On Tue, Sep 8, 2015 at 11:17 AM, Matthias Wessendorf wrote: > alright, thanks! > > I will do the OpenShift updates, based on the git tag > > On Tue, Sep 8, 2015 at 11:15 AM, Sebastien Blanc > wrote: > >> Hi team, >> >> I'm happy to announce that UPS 1.1.0 Final has been staged. >> >> Please test the staged release : >> >> >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6516 >> >> By the end of the week I'd like to press the button to release it to the >> wild. >> >> Sebi >> >> ps : the openshift update will follow >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150908/f8d3b49d/attachment-0001.html From idel.pivnitskiy at gmail.com Tue Sep 8 08:12:23 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Tue, 8 Sep 2015 15:12:23 +0300 Subject: [aerogear-dev] Staging of UPS 1.1.0.Final In-Reply-To: References: Message-ID: Done: https://github.com/aerogear/aerogear-unifiedpush-server/pull/633 It would be great if someone will check the whole API documentation. Hope it doesn't have typos or other problems. Best regards, Idel Pivnitskiy -- E-mail: Idel.Pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy On Tue, Sep 8, 2015 at 3:11 PM, Matthias Wessendorf wrote: > here is the OpenShift PR: > https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/22 > > -Matthias > > On Tue, Sep 8, 2015 at 11:17 AM, Matthias Wessendorf > wrote: > >> alright, thanks! >> >> I will do the OpenShift updates, based on the git tag >> >> On Tue, Sep 8, 2015 at 11:15 AM, Sebastien Blanc >> wrote: >> >>> Hi team, >>> >>> I'm happy to announce that UPS 1.1.0 Final has been staged. >>> >>> Please test the staged release : >>> >>> >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6516 >>> >>> By the end of the week I'd like to press the button to release it to >>> the wild. >>> >>> Sebi >>> >>> ps : the openshift update will follow >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150908/b49d192a/attachment.html From matzew at apache.org Wed Sep 9 03:12:30 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 9 Sep 2015 09:12:30 +0200 Subject: [aerogear-dev] Netty updates In-Reply-To: References: Message-ID: awesome. thanks for the update, Idel! On Fri, Sep 4, 2015 at 2:41 PM, Idel Pivnitskiy wrote: > Netty team released new versions this week: 4.0.31.Final [1] and > 4.1.0.Beta6 [2] > > For our WebPush Server we're using 4.1.0.Beta5 now. And beta6 has the > important change for us - full support of HTTP/2 as specified by RFC7540. > I'm gonna update it after merging of current opened PR [3]. > > [1] http://netty.io/news/2015/09/02/4-0-31-Final.html > [2] http://netty.io/news/2015/09/02/4-1-0-Beta6.html > [3] https://github.com/aerogear/aerogear-webpush-server/pull/14 > > Best, > Idel Pivnitskiy > -- > E-mail: Idel.Pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150909/6d0a80b3/attachment.html From daniel.bevenius at gmail.com Wed Sep 9 14:29:04 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Wed, 9 Sep 2015 20:29:04 +0200 Subject: [aerogear-dev] Netty updates In-Reply-To: References: Message-ID: I've sent a PR for the Netty upgrade [1] as I needed the upgrade for a demo I'm working on. [1] https://github.com/idelpivnitskiy/aerogear-webpush-server/pull/4 On 9 September 2015 at 09:12, Matthias Wessendorf wrote: > awesome. thanks for the update, Idel! > > On Fri, Sep 4, 2015 at 2:41 PM, Idel Pivnitskiy > wrote: > >> Netty team released new versions this week: 4.0.31.Final [1] and >> 4.1.0.Beta6 [2] >> >> For our WebPush Server we're using 4.1.0.Beta5 now. And beta6 has the >> important change for us - full support of HTTP/2 as specified by RFC7540. >> I'm gonna update it after merging of current opened PR [3]. >> >> [1] http://netty.io/news/2015/09/02/4-0-31-Final.html >> [2] http://netty.io/news/2015/09/02/4-1-0-Beta6.html >> [3] https://github.com/aerogear/aerogear-webpush-server/pull/14 >> >> Best, >> Idel Pivnitskiy >> -- >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150909/0f478b3f/attachment.html From lukas.fryc at gmail.com Thu Sep 10 05:38:31 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Thu, 10 Sep 2015 10:38:31 +0100 Subject: [aerogear-dev] GCM Topics Support Cont. In-Reply-To: References: Message-ID: Hello Summers, late but anyways: sounds good and I don't see personally any other issue in that. Would be nice to get this appropriately documented though to avoid surprises :-) ~ Lukas On Wed, Sep 2, 2015 at 8:03 PM, Summers Pittman wrote: > So the current PRs for Topics use them automatically when you subscribe to > a category. Google doesn't support delivering messages to a subset of > users over a topic. UPS has the ability to deliver messages to subsets of > category subscribers (via alias and deviceType). > > I think that a suitable workaround for this would be if a message is sent > to a category, and there is a topic available, AND the message isn't > filtered based on alias or deviceType then use the topic. Otherwise the > message should be treated "normally" and use registrationId based sending > (like we do now). > > > wdyt? > > And as an aside, can you guys think of other use cases where the all or > nothing nature of topics might be a problem? > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150910/d753754d/attachment-0001.html From ivan.gurtler at ahead-itec.com Thu Sep 17 10:33:31 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Thu, 17 Sep 2015 16:33:31 +0200 Subject: [aerogear-dev] aerogear push on weblogic Message-ID: Hello, we try to deploy auth and agpush .war files on Weblogic server. We have problem with persistence provider. We add org.hibernate.ejb.HibernatePersistence to persistence.xml in model-jpa but also we have problem with auth. It is possible to set explicitly the persistence provider in Auth project? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150917/3fbec080/attachment.html From corinnekrych at gmail.com Tue Sep 22 08:48:33 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 22 Sep 2015 14:48:33 +0200 Subject: [aerogear-dev] Suggestion for some OTP improvements Message-ID: Hello Guys, Revisiting OTP demo for iOS client, I've seen some improvements that could be done in the OTP lib itself. 1. storage of secret is done at cordova- layer [1] and [2]. It would be better to store them in a safe storage (ie: Keychain for iOS, KeyStore for Android etc...) or at least leave the option for end user. 2. extracting secret from URL (read from QRCode) is done on each native client demos or in Corodva layer. See [3] for iOS and [4] for Android and [5] for Cordova. What about moving this code snippet in the library itself. For ex, add a new initialiser of OTP which takes an URL. Thoughts? ++ Corinne [1] https://github.com/aerogear/aerogear-cordova-otp/blob/master/www/aerogear-opt.js#L66 [2] https://github.com/aerogear/aerogear-cordova-otp/blob/master/src/ios/CDVAeroGearPlugin.m#L48 [3] https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-390.otp.demo/Two-Factor/TwoFactorOTP/QRcodeCaptureViewController.swift#L76-L103 [4] https://github.com/aerogear/aerogear-android-cookbook/blob/master/Two-Factor%2Fapp%2Fsrc%2Fmain%2Fjava%2Forg%2Fjboss%2Faerogear%2Fandroid%2Fcookbook%2Ftwofactor%2FOTPDisplay.java#L69-L77 [5] https://github.com/aerogear/aerogear-cordova-otp/blob/master/www/aerogear-opt.js#L106-L110 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150922/c0e39826/attachment.html From edewit at redhat.com Tue Sep 22 09:45:30 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 22 Sep 2015 15:45:30 +0200 Subject: [aerogear-dev] Suggestion for some OTP improvements In-Reply-To: References: Message-ID: +1 on this this is something one will need to do use the lib better to have the lib do it or at least support doing that. On Tue, Sep 22, 2015 at 2:48 PM, Corinne Krych wrote: > Hello Guys, > > Revisiting OTP demo for iOS client, I've seen some improvements that could > be done in the OTP lib itself. > > 1. storage of secret is done at cordova- layer [1] and [2]. It would be > better to store them in a safe storage (ie: Keychain for iOS, KeyStore for > Android etc...) or at least leave the option for end user. > > 2. extracting secret from URL (read from QRCode) is done on each native > client demos or in Corodva layer. See [3] for iOS and [4] for Android and > [5] for Cordova. What about moving this code snippet in the library itself. > For ex, add a new initialiser of OTP which takes an URL. > > Thoughts? > > ++ > Corinne > [1] > https://github.com/aerogear/aerogear-cordova-otp/blob/master/www/aerogear-opt.js#L66 > [2] > https://github.com/aerogear/aerogear-cordova-otp/blob/master/src/ios/CDVAeroGearPlugin.m#L48 > [3] > https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-390.otp.demo/Two-Factor/TwoFactorOTP/QRcodeCaptureViewController.swift#L76-L103 > [4] > https://github.com/aerogear/aerogear-android-cookbook/blob/master/Two-Factor%2Fapp%2Fsrc%2Fmain%2Fjava%2Forg%2Fjboss%2Faerogear%2Fandroid%2Fcookbook%2Ftwofactor%2FOTPDisplay.java#L69-L77 > [5] > https://github.com/aerogear/aerogear-cordova-otp/blob/master/www/aerogear-opt.js#L106-L110 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150922/5d3b0668/attachment.html From bruno at abstractj.org Tue Sep 22 13:12:38 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 22 Sep 2015 14:12:38 -0300 Subject: [aerogear-dev] Moving to Keycloak 1.5 Message-ID: Good morning, today we have our OTP demos pointing to guess what, or good and old AeroGear Controller. I would like to move all the demos and the backend for the cookbooks to Keycloak 1.5. Objections!? -- -- "The measure of a man is what he does with power" - Plato - @abstractj - Volenti Nihil Difficile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150922/1d7735cc/attachment.html From daniel.bevenius at gmail.com Tue Sep 22 13:24:01 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Tue, 22 Sep 2015 18:24:01 +0100 Subject: [aerogear-dev] Moving to Keycloak 1.5 In-Reply-To: References: Message-ID: Sound good, lets do it. On 22 September 2015 at 18:12, Bruno Oliveira wrote: > Good morning, today we have our OTP demos pointing to guess what, or good > and old AeroGear Controller. I would like to move all the demos and the > backend for the cookbooks to Keycloak 1.5. > > Objections!? > > -- > > -- > "The measure of a man is what he does with power" - Plato > - > @abstractj > - > Volenti Nihil Difficile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150922/ffc418e9/attachment.html From dpassos at redhat.com Tue Sep 22 13:37:09 2015 From: dpassos at redhat.com (Daniel Passos) Date: Tue, 22 Sep 2015 14:37:09 -0300 Subject: [aerogear-dev] Moving to Keycloak 1.5 In-Reply-To: References: Message-ID: +9001. On Tue, Sep 22, 2015 at 2:12 PM, Bruno Oliveira wrote: > Good morning, today we have our OTP demos pointing to guess what, or good > and old AeroGear Controller. I would like to move all the demos and the > backend for the cookbooks to Keycloak 1.5. > > Objections!? > > -- > > -- > "The measure of a man is what he does with power" - Plato > - > @abstractj > - > Volenti Nihil Difficile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150922/60909fc4/attachment.html From dpassos at redhat.com Tue Sep 22 15:18:04 2015 From: dpassos at redhat.com (Daniel Passos) Date: Tue, 22 Sep 2015 16:18:04 -0300 Subject: [aerogear-dev] Remove Old Auth Cookbook/Example Message-ID: Hi y'all I was playing with our cookbook backend repo[1] and figured we have an Auth project[2]. Since we don't support HTTP Basic/Digest authentication anymore, should we remove this example from backend repo? [1] https://github.com/aerogear/aerogear-backend-cookbook [2] https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Authentication -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150922/98c7ebcb/attachment-0001.html From edewit at redhat.com Wed Sep 23 04:11:45 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 23 Sep 2015 10:11:45 +0200 Subject: [aerogear-dev] Moving to Keycloak 1.5 In-Reply-To: References: Message-ID: Already created a keycloak static demo that one can use to test OTP with, now that that is merged I'll test to see if that also works on the latest keycloak and then update the docs to use that instead. On Tue, Sep 22, 2015 at 7:37 PM, Daniel Passos wrote: > +9001. > > On Tue, Sep 22, 2015 at 2:12 PM, Bruno Oliveira > wrote: > >> Good morning, today we have our OTP demos pointing to guess what, or good >> and old AeroGear Controller. I would like to move all the demos and the >> backend for the cookbooks to Keycloak 1.5. >> >> Objections!? >> >> -- >> >> -- >> "The measure of a man is what he does with power" - Plato >> - >> @abstractj >> - >> Volenti Nihil Difficile >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > -- Passos > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150923/c2fa5b3a/attachment.html From corinnekrych at gmail.com Wed Sep 23 05:13:37 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 23 Sep 2015 11:13:37 +0200 Subject: [aerogear-dev] Moving to Keycloak 1.5 In-Reply-To: References: Message-ID: Yeap Keycloak 1.5 sound good, let update all existing cookbook demos (Shoot, OTP) to use it ++ Corinne On 23 September 2015 at 10:11, Erik Jan de Wit wrote: > Already created a keycloak static demo that one can use to test OTP with, > now that that is merged I'll test to see if that also works on the latest > keycloak and then update the docs to use that instead. > > On Tue, Sep 22, 2015 at 7:37 PM, Daniel Passos wrote: > >> +9001. >> >> On Tue, Sep 22, 2015 at 2:12 PM, Bruno Oliveira >> wrote: >> >>> Good morning, today we have our OTP demos pointing to guess what, or >>> good and old AeroGear Controller. I would like to move all the demos and >>> the backend for the cookbooks to Keycloak 1.5. >>> >>> Objections!? >>> >>> -- >>> >>> -- >>> "The measure of a man is what he does with power" - Plato >>> - >>> @abstractj >>> - >>> Volenti Nihil Difficile >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> -- Passos >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Cheers, > Erik Jan > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150923/20461d7f/attachment.html From corinnekrych at gmail.com Wed Sep 23 05:26:57 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 23 Sep 2015 11:26:57 +0200 Subject: [aerogear-dev] Remove Old Auth Cookbook/Example In-Reply-To: References: Message-ID: This is a feature present on ag-ios-http lib. But i guess the question is: do we still need to demo it with Picketlink and controller as our server parts are going to be removed/deprecated. Maybe we could move the backend demo to Keycloak. @passos wdyt? On 22 September 2015 at 21:18, Daniel Passos wrote: > Hi y'all > > I was playing with our cookbook backend repo[1] and figured we have an > Auth project[2]. Since we don't support HTTP Basic/Digest authentication > anymore, should we remove this example from backend repo? > > [1] https://github.com/aerogear/aerogear-backend-cookbook > [2] > https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Authentication > > -- > -- Passos > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150923/1d83e315/attachment.html From dpassos at redhat.com Wed Sep 23 09:19:48 2015 From: dpassos at redhat.com (Daniel Passos) Date: Wed, 23 Sep 2015 10:19:48 -0300 Subject: [aerogear-dev] Remove Old Auth Cookbook/Example In-Reply-To: References: Message-ID: On Wed, Sep 23, 2015 at 6:26 AM, Corinne Krych wrote: > This is a feature present on ag-ios-http lib. > Hrm, I thought we dropped support it. We don't have it on Android land anymore. > But i guess the question is: do we still need to demo it with Picketlink > and controller as our server parts are going to be removed/deprecated. > +1 to remove it. > Maybe we could move the backend demo to Keycloak. > -1, since we have others examples using Keycloak > @passos wdyt? > > > On 22 September 2015 at 21:18, Daniel Passos wrote: > >> Hi y'all >> >> I was playing with our cookbook backend repo[1] and figured we have an >> Auth project[2]. Since we don't support HTTP Basic/Digest authentication >> anymore, should we remove this example from backend repo? >> >> [1] https://github.com/aerogear/aerogear-backend-cookbook >> [2] >> https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Authentication >> >> -- >> -- Passos >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150923/fb8c6eac/attachment.html From dpassos at redhat.com Wed Sep 23 09:29:02 2015 From: dpassos at redhat.com (Daniel Passos) Date: Wed, 23 Sep 2015 10:29:02 -0300 Subject: [aerogear-dev] Suggestion for some OTP improvements In-Reply-To: References: Message-ID: On Tue, Sep 22, 2015 at 9:48 AM, Corinne Krych wrote: > Hello Guys, > > Revisiting OTP demo for iOS client, I've seen some improvements that could > be done in the OTP lib itself. > > 1. storage of secret is done at cordova- layer [1] and [2]. It would be > better to store them in a safe storage (ie: Keychain for iOS, KeyStore for > Android etc...) or at least leave the option for end user. > I'm not against to have a complete example and storing the secret in the database, but I'd prefer only scan QRCode and show the code on screen. I think it make the example easily to our community debug/play/understand/focus on OTP > 2. extracting secret from URL (read from QRCode) is done on each native > client demos or in Corodva layer. See [3] for iOS and [4] for Android and > [5] for Cordova. What about moving this code snippet in the library itself. > For ex, add a new initialiser of OTP which takes an URL. > +1 I like it. Thoughts? > > ++ > Corinne > [1] > https://github.com/aerogear/aerogear-cordova-otp/blob/master/www/aerogear-opt.js#L66 > [2] > https://github.com/aerogear/aerogear-cordova-otp/blob/master/src/ios/CDVAeroGearPlugin.m#L48 > [3] > https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-390.otp.demo/Two-Factor/TwoFactorOTP/QRcodeCaptureViewController.swift#L76-L103 > [4] > https://github.com/aerogear/aerogear-android-cookbook/blob/master/Two-Factor%2Fapp%2Fsrc%2Fmain%2Fjava%2Forg%2Fjboss%2Faerogear%2Fandroid%2Fcookbook%2Ftwofactor%2FOTPDisplay.java#L69-L77 > [5] > https://github.com/aerogear/aerogear-cordova-otp/blob/master/www/aerogear-opt.js#L106-L110 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150923/064a1d0b/attachment-0001.html From scm.blanc at gmail.com Wed Sep 23 09:44:30 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 23 Sep 2015 15:44:30 +0200 Subject: [aerogear-dev] Staging of UPS 1.1.0.Final In-Reply-To: References: Message-ID: As anyone done any tests for this really important release, it has been staging now for more than 2 weeks ? On Tue, Sep 8, 2015 at 2:12 PM, Idel Pivnitskiy wrote: > Done: https://github.com/aerogear/aerogear-unifiedpush-server/pull/633 > It would be great if someone will check the whole API documentation. Hope > it doesn't have typos or other problems. > > Best regards, > Idel Pivnitskiy > -- > E-mail: Idel.Pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > > On Tue, Sep 8, 2015 at 3:11 PM, Matthias Wessendorf > wrote: > >> here is the OpenShift PR: >> https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/22 >> >> -Matthias >> >> On Tue, Sep 8, 2015 at 11:17 AM, Matthias Wessendorf >> wrote: >> >>> alright, thanks! >>> >>> I will do the OpenShift updates, based on the git tag >>> >>> On Tue, Sep 8, 2015 at 11:15 AM, Sebastien Blanc >>> wrote: >>> >>>> Hi team, >>>> >>>> I'm happy to announce that UPS 1.1.0 Final has been staged. >>>> >>>> Please test the staged release : >>>> >>>> >>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6516 >>>> >>>> By the end of the week I'd like to press the button to release it to >>>> the wild. >>>> >>>> Sebi >>>> >>>> ps : the openshift update will follow >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150923/438c80ae/attachment.html From corinnekrych at gmail.com Wed Sep 23 10:25:01 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 23 Sep 2015 16:25:01 +0200 Subject: [aerogear-dev] Remove Old Auth Cookbook/Example In-Reply-To: References: Message-ID: On 23 September 2015 at 15:19, Daniel Passos wrote: > On Wed, Sep 23, 2015 at 6:26 AM, Corinne Krych > wrote: > >> This is a feature present on ag-ios-http lib. >> > > Hrm, I thought we dropped support it. We don't have it on Android land > anymore. > > >> But i guess the question is: do we still need to demo it with Picketlink >> and controller as our server parts are going to be removed/deprecated. >> > > +1 to remove it. > > >> Maybe we could move the backend demo to Keycloak. >> > > -1, since we have others examples using Keycloak > I meant demo the HTTP basic/digest with native app and Keycloak. Keycloak has its own demo using JavaScript sdk [1] we could complement it with native sdk example. But off course we need to first agree on keeping the feature on our http/pipes libs. Discussion is opened. Let's see what other thoughts are. ++ Corinne [1] https://github.com/keycloak/keycloak/tree/master/examples/basic-auth > > >> @passos wdyt? >> >> >> On 22 September 2015 at 21:18, Daniel Passos wrote: >> >>> Hi y'all >>> >>> I was playing with our cookbook backend repo[1] and figured we have an >>> Auth project[2]. Since we don't support HTTP Basic/Digest authentication >>> anymore, should we remove this example from backend repo? >>> >>> [1] https://github.com/aerogear/aerogear-backend-cookbook >>> [2] >>> https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Authentication >>> >>> -- >>> -- Passos >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > -- Passos > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150923/27c7a783/attachment.html From lholmqui at redhat.com Mon Sep 28 11:34:58 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Mon, 28 Sep 2015 11:34:58 -0400 Subject: [aerogear-dev] Moving to Keycloak 1.5 In-Reply-To: References: Message-ID: whats a AeroGear Controller :) /me hides On Wed, Sep 23, 2015 at 5:13 AM, Corinne Krych wrote: > Yeap > Keycloak 1.5 sound good, let update all existing cookbook demos (Shoot, > OTP) to use it > ++ > Corinne > > On 23 September 2015 at 10:11, Erik Jan de Wit wrote: > >> Already created a keycloak static demo that one can use to test OTP with, >> now that that is merged I'll test to see if that also works on the latest >> keycloak and then update the docs to use that instead. >> >> On Tue, Sep 22, 2015 at 7:37 PM, Daniel Passos >> wrote: >> >>> +9001. >>> >>> On Tue, Sep 22, 2015 at 2:12 PM, Bruno Oliveira >>> wrote: >>> >>>> Good morning, today we have our OTP demos pointing to guess what, or >>>> good and old AeroGear Controller. I would like to move all the demos and >>>> the backend for the cookbooks to Keycloak 1.5. >>>> >>>> Objections!? >>>> >>>> -- >>>> >>>> -- >>>> "The measure of a man is what he does with power" - Plato >>>> - >>>> @abstractj >>>> - >>>> Volenti Nihil Difficile >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> -- Passos >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Cheers, >> Erik Jan >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150928/dc1975f9/attachment-0001.html From lukas.fryc at gmail.com Tue Sep 29 01:56:45 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 29 Sep 2015 07:56:45 +0200 Subject: [aerogear-dev] Staging of UPS 1.1.0.Final In-Reply-To: References: Message-ID: Don't ship yet, I'm taking look today :-) On Wed, Sep 23, 2015 at 3:44 PM, Sebastien Blanc wrote: > As anyone done any tests for this really important release, it has been > staging now for more than 2 weeks ? > > > On Tue, Sep 8, 2015 at 2:12 PM, Idel Pivnitskiy > wrote: > >> Done: https://github.com/aerogear/aerogear-unifiedpush-server/pull/633 >> It would be great if someone will check the whole API documentation. Hope >> it doesn't have typos or other problems. >> >> Best regards, >> Idel Pivnitskiy >> -- >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> >> On Tue, Sep 8, 2015 at 3:11 PM, Matthias Wessendorf >> wrote: >> >>> here is the OpenShift PR: >>> https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/22 >>> >>> -Matthias >>> >>> On Tue, Sep 8, 2015 at 11:17 AM, Matthias Wessendorf >>> wrote: >>> >>>> alright, thanks! >>>> >>>> I will do the OpenShift updates, based on the git tag >>>> >>>> On Tue, Sep 8, 2015 at 11:15 AM, Sebastien Blanc >>>> wrote: >>>> >>>>> Hi team, >>>>> >>>>> I'm happy to announce that UPS 1.1.0 Final has been staged. >>>>> >>>>> Please test the staged release : >>>>> >>>>> >>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6516 >>>>> >>>>> By the end of the week I'd like to press the button to release it to >>>>> the wild. >>>>> >>>>> Sebi >>>>> >>>>> ps : the openshift update will follow >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150929/d7a7a931/attachment.html