From edewit at redhat.com Wed Jul 1 08:59:50 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 1 Jul 2015 14:59:50 +0200 Subject: [aerogear-dev] windows push lib release Message-ID: After successful beta testing we decided to release a new version of the windows push sdk. The major addition is the ability to send metrics and configure it using a json file you can download a new version from nuget [1]. [1] https://www.nuget.org/packages/aerogear-windows-push/0.0.9 -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150701/929a4f93/attachment.html From matzew at apache.org Wed Jul 1 09:25:23 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 1 Jul 2015 15:25:23 +0200 Subject: [aerogear-dev] windows push lib release In-Reply-To: References: Message-ID: awesome! On Wed, Jul 1, 2015 at 2:59 PM, Erik Jan de Wit wrote: > After successful beta testing we decided to release a new version of the > windows push sdk. The major addition is the ability to send metrics and > configure it using a json file you can download a new version from nuget > [1]. > > [1] https://www.nuget.org/packages/aerogear-windows-push/0.0.9 > -- > 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/20150701/0741fbb2/attachment.html From idel.pivnitskiy at gmail.com Thu Jul 2 15:18:11 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Thu, 2 Jul 2015 22:18:11 +0300 Subject: [aerogear-dev] [webpush] Message Encryption for Web Push Message-ID: Hi all, Today WebPush WG released a new draft of Message Encryption for Web Push [1]. The changes are not significant. This draft clarifies behavior of encryption and decryption for push messages, which are longer then 4096 octets. For more information, see difference of two versions [2]. [1] https://www.ietf.org/id/draft-thomson-webpush-encryption-01.txt [2] https://tools.ietf.org/rfcdiff?url2=draft-thomson-webpush-encryption-01.txt Best regards, 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/20150702/741d6800/attachment-0001.html From matzew at apache.org Fri Jul 3 03:37:11 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 3 Jul 2015 09:37:11 +0200 Subject: [aerogear-dev] [webpush] Message Encryption for Web Push In-Reply-To: References: Message-ID: Hi Idel, thanks for sharing! Just wondering - do you know if there are any updates planed on the Web Push draft itself ? On Thu, Jul 2, 2015 at 9:18 PM, Idel Pivnitskiy wrote: > Hi all, > > Today WebPush WG released a new draft of Message Encryption for Web Push > [1]. The changes are not significant. This draft clarifies behavior of > encryption and decryption for push messages, which are longer then 4096 > octets. For more information, see difference of two versions [2]. > > [1] https://www.ietf.org/id/draft-thomson-webpush-encryption-01.txt > [2] > https://tools.ietf.org/rfcdiff?url2=draft-thomson-webpush-encryption-01.txt > > Best regards, > 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/20150703/a3a8de28/attachment.html From idel.pivnitskiy at gmail.com Fri Jul 3 05:10:58 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Fri, 3 Jul 2015 12:10:58 +0300 Subject: [aerogear-dev] [webpush] Message Encryption for Web Push In-Reply-To: References: Message-ID: Not now. Shida Schubert (one of WG cochairs) announced a poll for adoption of current draft [1] as WG item (as a starting point for working on the only milestone for the WG) until next Wednesday (Jul 10th). For more info, see this thread [2]. Also, Martin Thomson added some small clarifications for the current draft [3]. Btw, Google works on WebPush too. Hope, Chrome will support it soon. [1] https://tools.ietf.org/id/draft-thomson-webpush-protocol-00.txt [2] http://www.ietf.org/mail-archive/web/webpush/current/msg00183.html [3] https://github.com/unicorn-wg/webpush-protocol/commits/master Best regards, Idel Pivnitskiy -- E-mail: Idel.Pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy 2015-07-03 10:37 GMT+03:00 Matthias Wessendorf : > Hi Idel, > > thanks for sharing! > > Just wondering - do you know if there are any updates planed on the Web > Push draft itself ? > > On Thu, Jul 2, 2015 at 9:18 PM, Idel Pivnitskiy > wrote: > >> Hi all, >> >> Today WebPush WG released a new draft of Message Encryption for Web Push >> [1]. The changes are not significant. This draft clarifies behavior of >> encryption and decryption for push messages, which are longer then 4096 >> octets. For more information, see difference of two versions [2]. >> >> [1] https://www.ietf.org/id/draft-thomson-webpush-encryption-01.txt >> [2] >> https://tools.ietf.org/rfcdiff?url2=draft-thomson-webpush-encryption-01.txt >> >> Best regards, >> 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/20150703/8ddd2076/attachment.html From scm.blanc at gmail.com Fri Jul 3 06:02:25 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 3 Jul 2015 12:02:25 +0200 Subject: [aerogear-dev] [UPS] Create Push Application & variants in the same rest service Message-ID: Hi peeps, We recently added some documentation around integration : https://staging.aerogear.org/docs/unifiedpush/ups_userguide/index/#integration (still on the staging site but will be released soon) and also some scripts that shows how this integration can work : https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/node.js And that made me think of the following use case : A third party should be able to create in one call the Push App and its variants. That would not be too much work on the server side, so wdyt ? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150703/f935c2f2/attachment.html From matzew at apache.org Fri Jul 3 06:34:32 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 3 Jul 2015 12:34:32 +0200 Subject: [aerogear-dev] [webpush] Message Encryption for Web Push In-Reply-To: References: Message-ID: On Fri, Jul 3, 2015 at 11:10 AM, Idel Pivnitskiy wrote: > Not now. > > Shida Schubert (one of WG cochairs) announced a poll for adoption of > current draft [1] as WG item (as a starting point for working on the only > milestone for the WG) until next Wednesday (Jul 10th). For more info, see > this thread [2]. > Also, Martin Thomson added some small clarifications for the current draft > [3]. > > Btw, Google works on WebPush too. Hope, Chrome will support it soon. > Are they working on the actual wire-protocol? Or are they just on the client side, meaning the JS APIs for WebPush? I think their current focus is using GCM behind the WebPush standard APIs (some more context [1]). [1] https://developers.google.com/web/updates/2015/03/push-notificatons-on-the-open-web > > [1] https://tools.ietf.org/id/draft-thomson-webpush-protocol-00.txt > [2] http://www.ietf.org/mail-archive/web/webpush/current/msg00183.html > [3] https://github.com/unicorn-wg/webpush-protocol/commits/master > > Best regards, > Idel Pivnitskiy > -- > E-mail: Idel.Pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > > 2015-07-03 10:37 GMT+03:00 Matthias Wessendorf : > >> Hi Idel, >> >> thanks for sharing! >> >> Just wondering - do you know if there are any updates planed on the Web >> Push draft itself ? >> >> On Thu, Jul 2, 2015 at 9:18 PM, Idel Pivnitskiy < >> idel.pivnitskiy at gmail.com> wrote: >> >>> Hi all, >>> >>> Today WebPush WG released a new draft of Message Encryption for Web Push >>> [1]. The changes are not significant. This draft clarifies behavior of >>> encryption and decryption for push messages, which are longer then 4096 >>> octets. For more information, see difference of two versions [2]. >>> >>> [1] https://www.ietf.org/id/draft-thomson-webpush-encryption-01.txt >>> [2] >>> https://tools.ietf.org/rfcdiff?url2=draft-thomson-webpush-encryption-01.txt >>> >>> Best regards, >>> 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 >> > > > > > _______________________________________________ > 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/20150703/6e14c3d3/attachment-0001.html From idel.pivnitskiy at gmail.com Fri Jul 3 07:12:27 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Fri, 3 Jul 2015 14:12:27 +0300 Subject: [aerogear-dev] [webpush] Message Encryption for Web Push In-Reply-To: References: Message-ID: I heard it from Chromium team, so I think that they are working on client side for web browser. Will ask them for more information. Best regards, Idel Pivnitskiy -- E-mail: Idel.Pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy 2015-07-03 13:34 GMT+03:00 Matthias Wessendorf : > > > On Fri, Jul 3, 2015 at 11:10 AM, Idel Pivnitskiy < > idel.pivnitskiy at gmail.com> wrote: > >> Not now. >> >> Shida Schubert (one of WG cochairs) announced a poll for adoption of >> current draft [1] as WG item (as a starting point for working on the only >> milestone for the WG) until next Wednesday (Jul 10th). For more info, see >> this thread [2]. >> Also, Martin Thomson added some small clarifications for the current >> draft [3]. >> >> Btw, Google works on WebPush too. Hope, Chrome will support it soon. >> > > Are they working on the actual wire-protocol? Or are they just on the > client side, meaning the JS APIs for WebPush? > > I think their current focus is using GCM behind the WebPush standard APIs > (some more context [1]). > > > [1] > https://developers.google.com/web/updates/2015/03/push-notificatons-on-the-open-web > > >> >> [1] https://tools.ietf.org/id/draft-thomson-webpush-protocol-00.txt >> [2] http://www.ietf.org/mail-archive/web/webpush/current/msg00183.html >> [3] https://github.com/unicorn-wg/webpush-protocol/commits/master >> >> Best regards, >> Idel Pivnitskiy >> -- >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> >> 2015-07-03 10:37 GMT+03:00 Matthias Wessendorf : >> >>> Hi Idel, >>> >>> thanks for sharing! >>> >>> Just wondering - do you know if there are any updates planed on the Web >>> Push draft itself ? >>> >>> On Thu, Jul 2, 2015 at 9:18 PM, Idel Pivnitskiy < >>> idel.pivnitskiy at gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> Today WebPush WG released a new draft of Message Encryption for Web >>>> Push [1]. The changes are not significant. This draft clarifies behavior of >>>> encryption and decryption for push messages, which are longer then 4096 >>>> octets. For more information, see difference of two versions [2]. >>>> >>>> [1] https://www.ietf.org/id/draft-thomson-webpush-encryption-01.txt >>>> [2] >>>> https://tools.ietf.org/rfcdiff?url2=draft-thomson-webpush-encryption-01.txt >>>> >>>> Best regards, >>>> 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 >>> >> >> >> >> >> _______________________________________________ >> 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/20150703/d24b033c/attachment.html From dpassos at redhat.com Fri Jul 3 08:10:56 2015 From: dpassos at redhat.com (Daniel Passos) Date: Fri, 3 Jul 2015 09:10:56 -0300 Subject: [aerogear-dev] AeroGear Android Pipe 2.1.1 In-Reply-To: References: Message-ID: I've just click the button to release it. It'll (probably) be available in maven central next monday. On Tue, Jun 30, 2015 at 5:50 PM, Artur Dryomov wrote: > As far as I can tell, the 2.2.1 version works great for my use case. > > 2.2.1 for 204 HTTP response returns valid empty list, i. e. > Arrays.asList() or new ArrayList<>(). > 2.2.0 for 204 HTTP response returns weird list with a single null element, > i. e. Arrays.asList(null). > > _______________________________________________ > 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/20150703/bf65aba6/attachment.html From scm.blanc at gmail.com Fri Jul 3 08:33:46 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 3 Jul 2015 14:33:46 +0200 Subject: [aerogear-dev] [UPS] Create Push Application & variants in the same rest service In-Reply-To: References: Message-ID: I just realized that the iOS Variant endpoint still expects an mutlipartform :/ that will make it a bit more difficult (mostly because of the certificate) On Fri, Jul 3, 2015 at 12:02 PM, Sebastien Blanc wrote: > Hi peeps, > > We recently added some documentation around integration : > https://staging.aerogear.org/docs/unifiedpush/ups_userguide/index/#integration > (still on the staging site but will be released soon) > and also some scripts that shows how this integration can work : > https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/node.js > > And that made me think of the following use case : > > A third party should be able to create in one call the Push App and its > variants. That would not be too much work on the server side, so wdyt ? > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150703/729579e5/attachment.html From matzew at apache.org Fri Jul 3 08:38:44 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 3 Jul 2015 14:38:44 +0200 Subject: [aerogear-dev] [UPS] Create Push Application & variants in the same rest service In-Reply-To: References: Message-ID: Doh - damn Apple. We could do some a check on a (future) "/createAllInOne" :) endpoint to see if multipart is around (just for iOS) or not (for 'normal') On Fri, Jul 3, 2015 at 2:33 PM, Sebastien Blanc wrote: > I just realized that the iOS Variant endpoint still expects an > mutlipartform :/ that will make it a bit more difficult (mostly because of > the certificate) > > > On Fri, Jul 3, 2015 at 12:02 PM, Sebastien Blanc > wrote: > >> Hi peeps, >> >> We recently added some documentation around integration : >> https://staging.aerogear.org/docs/unifiedpush/ups_userguide/index/#integration >> (still on the staging site but will be released soon) >> and also some scripts that shows how this integration can work : >> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/node.js >> >> And that made me think of the following use case : >> >> A third party should be able to create in one call the Push App and its >> variants. That would not be too much work on the server side, so wdyt ? >> >> >> > > _______________________________________________ > 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/20150703/cd47faa1/attachment-0001.html From matzew at apache.org Fri Jul 3 13:20:44 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 3 Jul 2015 19:20:44 +0200 Subject: [aerogear-dev] UPS 1.1.0.Final: Code freeze later this week In-Reply-To: References: Message-ID: Hi, just a heads up - the code freeze has not yet happened, and will therefore happen next week. Any thoughts? On Mon, Jun 29, 2015 at 8:50 PM, Matthias Wessendorf wrote: > Hi folks, > > a few items left on our 1.1.0.Final (see [1]) and hopefully later this > week (ideally on Thursday) we will a code-freeze, to have the release out > next week. > > If you have any suggestions or questions, please let us know! > > -Matthias > > [1] https://issues.jboss.org/browse/AGPUSH/fixforversion/12326301/ > > -- > 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/20150703/42e68727/attachment.html From corinnekrych at gmail.com Mon Jul 6 05:51:47 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 6 Jul 2015 11:51:47 +0200 Subject: [aerogear-dev] iOS 2.4 release: change of scope Message-ID: Hello iOS lovers, 2.4 release initially scheduled end of June which main goal was to clean up cookbook demos (removing 1.6.x branch) and add support for iOS7 for our Swift libs will be rescheduled for September. Moving the release in September will allow us to include Swift2 and iOS9 support, extending AeroGear libs platform support from iOS7 to iOS9. If you want to know more about what's included have a look to our JIRA [1]. To delve into Swift and iOS7 support, read my blog post[2] ;) To learn more about iOS9, stay tuned, I'll tell you more in following weeks... ++ Corinne [1] https://issues.jboss.org/browse/AGIOS/fixforversion/12326644 [2] http://corinnekrych.blogspot.fr/2015/04/how-well-does-swift-plays-on-ios7.html -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150706/2bf97929/attachment.html From matzew at apache.org Mon Jul 6 05:58:47 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 6 Jul 2015 11:58:47 +0200 Subject: [aerogear-dev] iOS 2.4 release: change of scope In-Reply-To: References: Message-ID: In spirit of semver - wouldn't this be a 3.0.0 instead of 2.4 ? On Mon, Jul 6, 2015 at 11:51 AM, Corinne Krych wrote: > Hello iOS lovers, > > 2.4 release initially scheduled end of June which main goal was to clean > up cookbook demos (removing 1.6.x branch) and add support for iOS7 for our > Swift libs will be rescheduled for September. > > Moving the release in September will allow us to include Swift2 and iOS9 > support, extending AeroGear libs platform support from iOS7 to iOS9. > > If you want to know more about what's included have a look to our JIRA > [1]. To delve into Swift and iOS7 support, read my blog post[2] ;) > To learn more about iOS9, stay tuned, I'll tell you more in following > weeks... > > ++ > Corinne > [1] https://issues.jboss.org/browse/AGIOS/fixforversion/12326644 > [2] > http://corinnekrych.blogspot.fr/2015/04/how-well-does-swift-plays-on-ios7.html > > _______________________________________________ > 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/20150706/373031d2/attachment.html From corinnekrych at gmail.com Mon Jul 6 06:05:40 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 6 Jul 2015 12:05:40 +0200 Subject: [aerogear-dev] iOS 2.4 release: change of scope In-Reply-To: References: Message-ID: Good point! Let's call it 3.0.0 and embrace Swift2 syntax. ++ Corinne On 6 July 2015 at 11:58, Matthias Wessendorf wrote: > In spirit of semver - wouldn't this be a 3.0.0 instead of 2.4 ? > > On Mon, Jul 6, 2015 at 11:51 AM, Corinne Krych > wrote: > >> Hello iOS lovers, >> >> 2.4 release initially scheduled end of June which main goal was to clean >> up cookbook demos (removing 1.6.x branch) and add support for iOS7 for our >> Swift libs will be rescheduled for September. >> >> Moving the release in September will allow us to include Swift2 and iOS9 >> support, extending AeroGear libs platform support from iOS7 to iOS9. >> >> If you want to know more about what's included have a look to our JIRA >> [1]. To delve into Swift and iOS7 support, read my blog post[2] ;) >> To learn more about iOS9, stay tuned, I'll tell you more in following >> weeks... >> >> ++ >> Corinne >> [1] https://issues.jboss.org/browse/AGIOS/fixforversion/12326644 >> [2] >> http://corinnekrych.blogspot.fr/2015/04/how-well-does-swift-plays-on-ios7.html >> >> _______________________________________________ >> 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/20150706/2e447b40/attachment.html From qmx at qmx.me Mon Jul 6 06:10:12 2015 From: qmx at qmx.me (Douglas Campos) Date: Mon, 6 Jul 2015 07:10:12 -0300 Subject: [aerogear-dev] UPS 1.1.0.Final: Code freeze later this week In-Reply-To: References: Message-ID: howdy! I have one last big item to ship before the freeze, but the outlook is good so far. On Fri, Jul 3, 2015 at 2:20 PM, Matthias Wessendorf wrote: > Hi, > > just a heads up - the code freeze has not yet happened, and will therefore > happen next week. > > Any thoughts? > > On Mon, Jun 29, 2015 at 8:50 PM, Matthias Wessendorf > wrote: > >> Hi folks, >> >> a few items left on our 1.1.0.Final (see [1]) and hopefully later this >> week (ideally on Thursday) we will a code-freeze, to have the release out >> next week. >> >> If you have any suggestions or questions, please let us know! >> >> -Matthias >> >> [1] https://issues.jboss.org/browse/AGPUSH/fixforversion/12326301/ >> >> -- >> 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/20150706/037592c6/attachment-0001.html From lholmqui at redhat.com Mon Jul 6 09:12:07 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Mon, 6 Jul 2015 09:12:07 -0400 Subject: [aerogear-dev] [webpush] Message Encryption for Web Push In-Reply-To: References: Message-ID: On Fri, Jul 3, 2015 at 7:12 AM, Idel Pivnitskiy wrote: > I heard it from Chromium team, so I think that they are working on client > side for web browser. > Will ask them for more information. > > Best regards, > Idel Pivnitskiy > -- > E-mail: Idel.Pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > > 2015-07-03 13:34 GMT+03:00 Matthias Wessendorf : > >> >> >> On Fri, Jul 3, 2015 at 11:10 AM, Idel Pivnitskiy < >> idel.pivnitskiy at gmail.com> wrote: >> >>> Not now. >>> >>> Shida Schubert (one of WG cochairs) announced a poll for adoption of >>> current draft [1] as WG item (as a starting point for working on the only >>> milestone for the WG) until next Wednesday (Jul 10th). For more info, see >>> this thread [2]. >>> Also, Martin Thomson added some small clarifications for the current >>> draft [3]. >>> >>> Btw, Google works on WebPush too. Hope, Chrome will support it soon. >>> >> >> Are they working on the actual wire-protocol? Or are they just on the >> client side, meaning the JS APIs for WebPush? >> >> I think their current focus is using GCM behind the WebPush standard APIs >> (some more context [1]). >> >> >> [1] >> https://developers.google.com/web/updates/2015/03/push-notificatons-on-the-open-web >> > in this section "Future of Push Messaging on Chrome and the Open Web" they talk about eventually moving to the Web Push Protocol > >> >>> >>> [1] https://tools.ietf.org/id/draft-thomson-webpush-protocol-00.txt >>> [2] http://www.ietf.org/mail-archive/web/webpush/current/msg00183.html >>> [3] https://github.com/unicorn-wg/webpush-protocol/commits/master >>> >>> Best regards, >>> Idel Pivnitskiy >>> -- >>> E-mail: Idel.Pivnitskiy at gmail.com >>> Twitter: @idelpivnitskiy >>> GitHub: @idelpivnitskiy >>> >>> 2015-07-03 10:37 GMT+03:00 Matthias Wessendorf : >>> >>>> Hi Idel, >>>> >>>> thanks for sharing! >>>> >>>> Just wondering - do you know if there are any updates planed on the Web >>>> Push draft itself ? >>>> >>>> On Thu, Jul 2, 2015 at 9:18 PM, Idel Pivnitskiy < >>>> idel.pivnitskiy at gmail.com> wrote: >>>> >>>>> Hi all, >>>>> >>>>> Today WebPush WG released a new draft of Message Encryption for Web >>>>> Push [1]. The changes are not significant. This draft clarifies behavior of >>>>> encryption and decryption for push messages, which are longer then 4096 >>>>> octets. For more information, see difference of two versions [2]. >>>>> >>>>> [1] https://www.ietf.org/id/draft-thomson-webpush-encryption-01.txt >>>>> [2] >>>>> https://tools.ietf.org/rfcdiff?url2=draft-thomson-webpush-encryption-01.txt >>>>> >>>>> Best regards, >>>>> 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 >>>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150706/fb56bc92/attachment.html From edewit at redhat.com Tue Jul 7 09:43:41 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 7 Jul 2015 15:43:41 +0200 Subject: [aerogear-dev] Windows 10 Message-ID: Hi all, As you might now windows 10 is coming, for us developers not a whole lot is changing, but oauth2 is going to be simpler. So I created a branch for windows 10 to remove the *AndContinue API, have a look and maybe even try it out. https://github.com/aerogear/aerogear-windows-oauth2/tree/windows10 -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150707/10c47729/attachment.html From matzew at apache.org Tue Jul 7 10:56:58 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 7 Jul 2015 16:56:58 +0200 Subject: [aerogear-dev] [Aerogear-users] Windows 10 In-Reply-To: References: Message-ID: very cool ! On Tue, Jul 7, 2015 at 3:43 PM, Erik Jan de Wit wrote: > Hi all, > > As you might now windows 10 is coming, for us developers not a whole lot > is changing, but oauth2 is going to be simpler. So I created a branch for > windows 10 to remove the *AndContinue API, have a look and maybe even try > it out. > > https://github.com/aerogear/aerogear-windows-oauth2/tree/windows10 > > -- > Cheers, > Erik Jan > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- 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/20150707/b3fe439c/attachment.html From matzew at apache.org Tue Jul 7 17:51:35 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 7 Jul 2015 23:51:35 +0200 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server Message-ID: Hi team, as we are moving forward w/ the releases, and we are close to have our 1.1.0.Final, I started to think about a proposal for a near-term future roadmap, and I'd like to get feedback, comments (or tomatos) on it. UPS 1.1.x (July/August) - 1.1.0 -> very soon - 1.1.x -> perhaps some needed bug fixes/improvements, in a short interval :-) UPS 1.2.0 (September/October) We have a release version in JIRA already. *Key features* - Keycloak isolation - GCM 3 support (client and server) - Improved docker support (e.g. tests/test suite -> Hopefully Travis supports 'docker run' by than ;-)) One could think that going back to JPA annotations is a key feature as well ;-) UPS 1.2.x (or even 1.3.0) (December 2015) There is no concrete release version for this, but we have a larger ups-future version in JIRA. The ups-future version/label has a few interesting things, that we may have to do right after 1.2.0 *Key features* - APNs goes HTTP2 (a must) - Quiete time for push (aka timezone awareness of devices) - Scheduled pushes - Proxy server support UPS 2.0.0 (March-2016) In October (2015) the WildFly 10 should be released and I'd like to see us adapting this for the 2.0.0 series! Also for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x series! *Note:* We don't have a release version for JIRA here, but heck! this mail is asking for feedback ;-) *Key features / Core changes* - UPS based on (public) APIs that are available in WildFly-10 - looking at using WF feature packs (similar to what Keycloak did, e.g. for layered "product" - looking at getting an UPS sub-system - Java8 only (as well as making sure works w/ Java9) - internal communication fully based on messaging (A-MQ / HornetQ) - WildFly-Swarm launcher (aka fat JARs) - helps with a more modular system: - Modular system (e.g. different ?webapps?, like "sender.war", "registration.war", "UI WAR" etc) - allows us to play with different platforms for the different ?web apps? - e.g. for a 2.x.y we could see/experiment how a vertx microservice (e.g. for the device registration) will behave in the larger system Other new features, e.g. based on needs and/or requests could be weaved into 2.0.0 or 2.0.x, based on timing. Please review this initial draft of a roadmap - once we are all in agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) Greetings, Matthias -- 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/20150707/103afe65/attachment-0001.html From dpassos at redhat.com Tue Jul 7 19:10:51 2015 From: dpassos at redhat.com (Daniel Passos) Date: Tue, 7 Jul 2015 20:10:51 -0300 Subject: [aerogear-dev] What's new in AeroGear? Message-ID: Android We started drop support for Java 6 https://issues.jboss.org/browse/AGDROID-434 We are planning our new release 3.0.0 https://issues.jboss.org/browse/AGDROID/fixforversion/12327585 We started move our tests to JUnit 4 https://issues.jboss.org/browse/AGDROID-420 iOS We?ve been busy this week adding iOS7 support for our Swift libraries: aerogear-ios-http and aerogear-ios-oauth2 Some planning for iOS 3.0.0 release is also going on, visit our JIRA for more details: https://issues.jboss.org/browse/AGIOS/fixforversion/12326644 Enjoy!!! ? -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150707/991304ef/attachment.html From lholmqui at redhat.com Wed Jul 8 09:02:31 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Wed, 8 Jul 2015 09:02:31 -0400 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server In-Reply-To: References: Message-ID: On Tue, Jul 7, 2015 at 5:51 PM, Matthias Wessendorf wrote: > Hi team, > > as we are moving forward w/ the releases, and we are close to have our > 1.1.0.Final, I started to think about a proposal for a near-term future > roadmap, and I'd like to get feedback, comments (or tomatos) on it. > UPS > 1.1.x (July/August) > > - 1.1.0 -> very soon > - 1.1.x -> perhaps some needed bug fixes/improvements, in a short > interval :-) > > > UPS > 1.2.0 (September/October) > > We have a release version > in JIRA > already. > > *Key features* > > - Keycloak isolation > - GCM 3 support (client and server) > - Improved docker support (e.g. tests/test suite -> Hopefully Travis > supports 'docker run' by than ;-)) > > One could think that going back to JPA annotations is a key feature as > well ;-) > > UPS > 1.2.x (or even 1.3.0) (December 2015) > > There is no concrete release version for this, but we have a larger > ups-future version > in JIRA. The ups-future version/label has a few interesting things, that we > may have to do right after 1.2.0 > > *Key features* > > - APNs goes HTTP2 (a must) > - Quiete time for push (aka timezone awareness of devices) > - Scheduled pushes > - Proxy server support > > UPS > 2.0.0 (March-2016) > > In October (2015) the WildFly 10 > should > be released and I'd like to see us adapting this for the 2.0.0 series! Also > for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x > series! > > *Note:* We don't have a release version for JIRA here, but heck! this > mail is asking for feedback ;-) > > *Key features / Core changes* > > - UPS based on (public) APIs that are available in WildFly-10 > > while i'm sure that Wildly/EAP is our "Main" target, wouldn't this make it difficult for users to use some other app server container? > > - > - looking at using WF feature packs > (similar to > what Keycloak did, e.g. for layered "product" > - looking at getting an UPS sub-system > - Java8 only (as well as making sure works w/ Java9) > - internal communication fully based on messaging (A-MQ / HornetQ) > - WildFly-Swarm launcher (aka fat JARs) > - helps with a more modular system: > - Modular system (e.g. different ?webapps?, like "sender.war", > "registration.war", "UI WAR" etc) > - allows us to play with different platforms for the different ?web > apps? > - e.g. for a 2.x.y we could see/experiment how a vertx microservice > (e.g. for the device registration) will behave in the larger system > > Other new features, e.g. based on needs and/or requests could be weaved > into 2.0.0 or 2.0.x, based on timing. > > Please review this initial draft of a roadmap - once we are all in > agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) > > Greetings, > Matthias > > -- > 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/20150708/d148f678/attachment.html From matzew at apache.org Wed Jul 8 10:12:10 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 8 Jul 2015 16:12:10 +0200 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server In-Reply-To: References: Message-ID: On Wed, Jul 8, 2015 at 3:02 PM, Luke Holmquist wrote: > > > On Tue, Jul 7, 2015 at 5:51 PM, Matthias Wessendorf > wrote: > >> Hi team, >> >> as we are moving forward w/ the releases, and we are close to have our >> 1.1.0.Final, I started to think about a proposal for a near-term future >> roadmap, and I'd like to get feedback, comments (or tomatos) on it. >> UPS >> 1.1.x (July/August) >> >> - 1.1.0 -> very soon >> - 1.1.x -> perhaps some needed bug fixes/improvements, in a short >> interval :-) >> >> >> UPS >> 1.2.0 (September/October) >> >> We have a release version >> in JIRA >> already. >> >> *Key features* >> >> - Keycloak isolation >> - GCM 3 support (client and server) >> - Improved docker support (e.g. tests/test suite -> Hopefully Travis >> supports 'docker run' by than ;-)) >> >> One could think that going back to JPA annotations is a key feature as >> well ;-) >> >> UPS >> 1.2.x (or even 1.3.0) (December 2015) >> >> There is no concrete release version for this, but we have a larger >> ups-future >> version >> in JIRA. The ups-future version/label has a few interesting things, that we >> may have to do right after 1.2.0 >> >> *Key features* >> >> - APNs goes HTTP2 (a must) >> - Quiete time for push (aka timezone awareness of devices) >> - Scheduled pushes >> - Proxy server support >> >> UPS >> 2.0.0 (March-2016) >> >> In October (2015) the WildFly 10 >> should >> be released and I'd like to see us adapting this for the 2.0.0 series! Also >> for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x >> series! >> >> *Note:* We don't have a release version for JIRA here, but heck! this >> mail is asking for feedback ;-) >> >> *Key features / Core changes* >> >> - UPS based on (public) APIs that are available in WildFly-10 >> >> while i'm sure that Wildly/EAP is our "Main" target, wouldn't this make > it difficult for users to use some other app server container? > I think it's not really possible today anyways. That said, the modular module (e.g. via WF Swarm) means using 'fat jars' or basically running JARs, not deploying into a container. e.g. this also opens options to replace parts of the UPS server w/ others, like vert.x, dropbox etc > >> - >> - looking at using WF feature packs >> (similar to >> what Keycloak did, e.g. for layered "product" >> - looking at getting an UPS sub-system >> - Java8 only (as well as making sure works w/ Java9) >> - internal communication fully based on messaging (A-MQ / HornetQ) >> - WildFly-Swarm launcher (aka fat JARs) >> - helps with a more modular system: >> - Modular system (e.g. different ?webapps?, like "sender.war", >> "registration.war", "UI WAR" etc) >> - allows us to play with different platforms for the different >> ?web apps? >> - e.g. for a 2.x.y we could see/experiment how a vertx >> microservice (e.g. for the device registration) will behave in the larger >> system >> >> Other new features, e.g. based on needs and/or requests could be weaved >> into 2.0.0 or 2.0.x, based on timing. >> >> Please review this initial draft of a roadmap - once we are all in >> agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) >> >> Greetings, >> Matthias >> >> -- >> 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/20150708/420aca6e/attachment-0001.html From matzew at apache.org Wed Jul 8 10:12:18 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 8 Jul 2015 16:12:18 +0200 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server In-Reply-To: References: Message-ID: dropwizard - sorry On Wed, Jul 8, 2015 at 4:12 PM, Matthias Wessendorf wrote: > > > On Wed, Jul 8, 2015 at 3:02 PM, Luke Holmquist > wrote: > >> >> >> On Tue, Jul 7, 2015 at 5:51 PM, Matthias Wessendorf >> wrote: >> >>> Hi team, >>> >>> as we are moving forward w/ the releases, and we are close to have our >>> 1.1.0.Final, I started to think about a proposal for a near-term future >>> roadmap, and I'd like to get feedback, comments (or tomatos) on it. >>> UPS >>> 1.1.x (July/August) >>> >>> - 1.1.0 -> very soon >>> - 1.1.x -> perhaps some needed bug fixes/improvements, in a short >>> interval :-) >>> >>> >>> UPS >>> 1.2.0 (September/October) >>> >>> We have a release version >>> in JIRA >>> already. >>> >>> *Key features* >>> >>> - Keycloak isolation >>> - GCM 3 support (client and server) >>> - Improved docker support (e.g. tests/test suite -> Hopefully Travis >>> supports 'docker run' by than ;-)) >>> >>> One could think that going back to JPA annotations is a key feature as >>> well ;-) >>> >>> UPS >>> 1.2.x (or even 1.3.0) (December 2015) >>> >>> There is no concrete release version for this, but we have a larger >>> ups-future >>> version >>> in JIRA. The ups-future version/label has a few interesting things, that we >>> may have to do right after 1.2.0 >>> >>> *Key features* >>> >>> - APNs goes HTTP2 (a must) >>> - Quiete time for push (aka timezone awareness of devices) >>> - Scheduled pushes >>> - Proxy server support >>> >>> UPS >>> 2.0.0 (March-2016) >>> >>> In October (2015) the WildFly 10 >>> should >>> be released and I'd like to see us adapting this for the 2.0.0 series! Also >>> for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x >>> series! >>> >>> *Note:* We don't have a release version for JIRA here, but heck! this >>> mail is asking for feedback ;-) >>> >>> *Key features / Core changes* >>> >>> - UPS based on (public) APIs that are available in WildFly-10 >>> >>> while i'm sure that Wildly/EAP is our "Main" target, wouldn't this make >> it difficult for users to use some other app server container? >> > > I think it's not really possible today anyways. > > That said, the modular module (e.g. via WF Swarm) means using 'fat jars' > or basically running JARs, not deploying into a container. > > e.g. this also opens options to replace parts of the UPS server w/ others, > like vert.x, dropbox etc > > > >> >>> - >>> - looking at using WF feature packs >>> (similar >>> to what Keycloak did, e.g. for layered "product" >>> - looking at getting an UPS sub-system >>> - Java8 only (as well as making sure works w/ Java9) >>> - internal communication fully based on messaging (A-MQ / HornetQ) >>> - WildFly-Swarm launcher (aka fat JARs) >>> - helps with a more modular system: >>> - Modular system (e.g. different ?webapps?, like "sender.war", >>> "registration.war", "UI WAR" etc) >>> - allows us to play with different platforms for the different >>> ?web apps? >>> - e.g. for a 2.x.y we could see/experiment how a vertx >>> microservice (e.g. for the device registration) will behave in the larger >>> system >>> >>> Other new features, e.g. based on needs and/or requests could be weaved >>> into 2.0.0 or 2.0.x, based on timing. >>> >>> Please review this initial draft of a roadmap - once we are all in >>> agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) >>> >>> Greetings, >>> Matthias >>> >>> -- >>> 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 > -- 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/20150708/3ab437e6/attachment.html From lholmqui at redhat.com Wed Jul 8 10:15:02 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Wed, 8 Jul 2015 10:15:02 -0400 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server In-Reply-To: References: Message-ID: On Wed, Jul 8, 2015 at 10:12 AM, Matthias Wessendorf wrote: > dropwizard - sorry > oh man, but i so wanted to run my UPS instance in my dropbox :) > > On Wed, Jul 8, 2015 at 4:12 PM, Matthias Wessendorf > wrote: > >> >> >> On Wed, Jul 8, 2015 at 3:02 PM, Luke Holmquist >> wrote: >> >>> >>> >>> On Tue, Jul 7, 2015 at 5:51 PM, Matthias Wessendorf >>> wrote: >>> >>>> Hi team, >>>> >>>> as we are moving forward w/ the releases, and we are close to have our >>>> 1.1.0.Final, I started to think about a proposal for a near-term future >>>> roadmap, and I'd like to get feedback, comments (or tomatos) on it. >>>> UPS >>>> 1.1.x (July/August) >>>> >>>> - 1.1.0 -> very soon >>>> - 1.1.x -> perhaps some needed bug fixes/improvements, in a short >>>> interval :-) >>>> >>>> >>>> UPS >>>> 1.2.0 (September/October) >>>> >>>> We have a release version >>>> in >>>> JIRA already. >>>> >>>> *Key features* >>>> >>>> - Keycloak isolation >>>> - GCM 3 support (client and server) >>>> - Improved docker support (e.g. tests/test suite -> Hopefully >>>> Travis supports 'docker run' by than ;-)) >>>> >>>> One could think that going back to JPA annotations is a key feature as >>>> well ;-) >>>> >>>> UPS >>>> 1.2.x (or even 1.3.0) (December 2015) >>>> >>>> There is no concrete release version for this, but we have a larger >>>> ups-future >>>> version >>>> in JIRA. The ups-future version/label has a few interesting things, that we >>>> may have to do right after 1.2.0 >>>> >>>> *Key features* >>>> >>>> - APNs goes HTTP2 (a must) >>>> - Quiete time for push (aka timezone awareness of devices) >>>> - Scheduled pushes >>>> - Proxy server support >>>> >>>> UPS >>>> 2.0.0 (March-2016) >>>> >>>> In October (2015) the WildFly 10 >>>> should >>>> be released and I'd like to see us adapting this for the 2.0.0 series! Also >>>> for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x >>>> series! >>>> >>>> *Note:* We don't have a release version for JIRA here, but heck! this >>>> mail is asking for feedback ;-) >>>> >>>> *Key features / Core changes* >>>> >>>> - UPS based on (public) APIs that are available in WildFly-10 >>>> >>>> while i'm sure that Wildly/EAP is our "Main" target, wouldn't this make >>> it difficult for users to use some other app server container? >>> >> >> I think it's not really possible today anyways. >> >> That said, the modular module (e.g. via WF Swarm) means using 'fat jars' >> or basically running JARs, not deploying into a container. >> >> e.g. this also opens options to replace parts of the UPS server w/ >> others, like vert.x, dropbox etc >> >> >> >>> >>>> - >>>> - looking at using WF feature packs >>>> (similar >>>> to what Keycloak did, e.g. for layered "product" >>>> - looking at getting an UPS sub-system >>>> - Java8 only (as well as making sure works w/ Java9) >>>> - internal communication fully based on messaging (A-MQ / HornetQ) >>>> - WildFly-Swarm launcher (aka fat JARs) >>>> - helps with a more modular system: >>>> - Modular system (e.g. different ?webapps?, like "sender.war", >>>> "registration.war", "UI WAR" etc) >>>> - allows us to play with different platforms for the different >>>> ?web apps? >>>> - e.g. for a 2.x.y we could see/experiment how a vertx >>>> microservice (e.g. for the device registration) will behave in the larger >>>> system >>>> >>>> Other new features, e.g. based on needs and/or requests could be weaved >>>> into 2.0.0 or 2.0.x, based on timing. >>>> >>>> Please review this initial draft of a roadmap - once we are all in >>>> agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) >>>> >>>> Greetings, >>>> Matthias >>>> >>>> -- >>>> 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 >> > > > > -- > 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/20150708/690a9711/attachment-0001.html From matzew at apache.org Wed Jul 8 10:26:16 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 8 Jul 2015 16:26:16 +0200 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server In-Reply-To: References: Message-ID: you could mount it in there :-) On Wed, Jul 8, 2015 at 4:15 PM, Luke Holmquist wrote: > > > On Wed, Jul 8, 2015 at 10:12 AM, Matthias Wessendorf > wrote: > >> dropwizard - sorry >> > > oh man, but i so wanted to run my UPS instance in my dropbox :) > >> >> On Wed, Jul 8, 2015 at 4:12 PM, Matthias Wessendorf >> wrote: >> >>> >>> >>> On Wed, Jul 8, 2015 at 3:02 PM, Luke Holmquist >>> wrote: >>> >>>> >>>> >>>> On Tue, Jul 7, 2015 at 5:51 PM, Matthias Wessendorf >>>> wrote: >>>> >>>>> Hi team, >>>>> >>>>> as we are moving forward w/ the releases, and we are close to have our >>>>> 1.1.0.Final, I started to think about a proposal for a near-term future >>>>> roadmap, and I'd like to get feedback, comments (or tomatos) on it. >>>>> >>>>> UPS >>>>> 1.1.x (July/August) >>>>> >>>>> - 1.1.0 -> very soon >>>>> - 1.1.x -> perhaps some needed bug fixes/improvements, in a short >>>>> interval :-) >>>>> >>>>> >>>>> UPS >>>>> 1.2.0 (September/October) >>>>> >>>>> We have a release version >>>>> in >>>>> JIRA already. >>>>> >>>>> *Key features* >>>>> >>>>> - Keycloak isolation >>>>> - GCM 3 support (client and server) >>>>> - Improved docker support (e.g. tests/test suite -> Hopefully >>>>> Travis supports 'docker run' by than ;-)) >>>>> >>>>> One could think that going back to JPA annotations is a key feature as >>>>> well ;-) >>>>> >>>>> UPS >>>>> 1.2.x (or even 1.3.0) (December 2015) >>>>> >>>>> There is no concrete release version for this, but we have a larger >>>>> ups-future >>>>> version >>>>> in JIRA. The ups-future version/label has a few interesting things, that we >>>>> may have to do right after 1.2.0 >>>>> >>>>> *Key features* >>>>> >>>>> - APNs goes HTTP2 (a must) >>>>> - Quiete time for push (aka timezone awareness of devices) >>>>> - Scheduled pushes >>>>> - Proxy server support >>>>> >>>>> >>>>> UPS >>>>> 2.0.0 (March-2016) >>>>> >>>>> In October (2015) the WildFly 10 >>>>> should >>>>> be released and I'd like to see us adapting this for the 2.0.0 series! Also >>>>> for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x >>>>> series! >>>>> >>>>> *Note:* We don't have a release version for JIRA here, but heck! this >>>>> mail is asking for feedback ;-) >>>>> >>>>> *Key features / Core changes* >>>>> >>>>> - UPS based on (public) APIs that are available in WildFly-10 >>>>> >>>>> while i'm sure that Wildly/EAP is our "Main" target, wouldn't this >>>> make it difficult for users to use some other app server container? >>>> >>> >>> I think it's not really possible today anyways. >>> >>> That said, the modular module (e.g. via WF Swarm) means using 'fat jars' >>> or basically running JARs, not deploying into a container. >>> >>> e.g. this also opens options to replace parts of the UPS server w/ >>> others, like vert.x, dropbox etc >>> >>> >>> >>>> >>>>> - >>>>> - looking at using WF feature packs >>>>> (similar >>>>> to what Keycloak did, e.g. for layered "product" >>>>> - looking at getting an UPS sub-system >>>>> - Java8 only (as well as making sure works w/ Java9) >>>>> - internal communication fully based on messaging (A-MQ / HornetQ) >>>>> - WildFly-Swarm launcher (aka fat JARs) >>>>> - helps with a more modular system: >>>>> - Modular system (e.g. different ?webapps?, like "sender.war", >>>>> "registration.war", "UI WAR" etc) >>>>> - allows us to play with different platforms for the different >>>>> ?web apps? >>>>> - e.g. for a 2.x.y we could see/experiment how a vertx >>>>> microservice (e.g. for the device registration) will behave in the larger >>>>> system >>>>> >>>>> Other new features, e.g. based on needs and/or requests could be >>>>> weaved into 2.0.0 or 2.0.x, based on timing. >>>>> >>>>> Please review this initial draft of a roadmap - once we are all in >>>>> agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) >>>>> >>>>> Greetings, >>>>> Matthias >>>>> >>>>> -- >>>>> 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 >>> >> >> >> >> -- >> 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/20150708/9380e05e/attachment.html From supittma at redhat.com Wed Jul 8 14:50:17 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 8 Jul 2015 14:50:17 -0400 Subject: [aerogear-dev] Push Registration with multiple Senders (Android) Message-ID: Previously GCM allowed multiple senders to be registered with a single registrationId. Now with the new APIs each senderId gets its own registration token. I don't think we ever supported this use case with UPS, we never really documented an example using multiple senders, and the developer can have a different registrar for each sender if she needs this feature with the new (GCM 3.0) APIs. Because we are already using a major version jump for dropping JDK6, I propose we change the push registrar to only accept a single senderId instead of allowing multiple sender Ids. This more accurately reflects what the service (GCM) is doing under the hood now anyway. If someone has an objection let me know and we can discuss it. Otherwise I'll continue down this path. XOXO, Summers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150708/9a9dfef9/attachment.html From scm.blanc at gmail.com Wed Jul 8 15:24:27 2015 From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=) Date: Wed, 8 Jul 2015 21:24:27 +0200 Subject: [aerogear-dev] Push Registration with multiple Senders (Android) In-Reply-To: References: Message-ID: <0FEBD123-BC49-464E-BE81-F4C90E9F6EC9@gmail.com> +1 Envoy? de mon iPhone > Le 8 juil. 2015 ? 20:50, Summers Pittman a ?crit : > > Previously GCM allowed multiple senders to be registered with a single registrationId. Now with the new APIs each senderId gets its own registration token. > > I don't think we ever supported this use case with UPS, we never really documented an example using multiple senders, and the developer can have a different registrar for each sender if she needs this feature with the new (GCM 3.0) APIs. > > Because we are already using a major version jump for dropping JDK6, I propose we change the push registrar to only accept a single senderId instead of allowing multiple sender Ids. This more accurately reflects what the service (GCM) is doing under the hood now anyway. > > If someone has an objection let me know and we can discuss it. Otherwise I'll continue down this path. > > XOXO, > > Summers > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Wed Jul 8 16:43:58 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 8 Jul 2015 22:43:58 +0200 Subject: [aerogear-dev] Push Registration with multiple Senders (Android) In-Reply-To: <0FEBD123-BC49-464E-BE81-F4C90E9F6EC9@gmail.com> References: <0FEBD123-BC49-464E-BE81-F4C90E9F6EC9@gmail.com> Message-ID: +1 On Wednesday, July 8, 2015, S?bastien Blanc wrote: > +1 > > Envoy? de mon iPhone > > > Le 8 juil. 2015 ? 20:50, Summers Pittman > a ?crit : > > > > Previously GCM allowed multiple senders to be registered with a single > registrationId. Now with the new APIs each senderId gets its own > registration token. > > > > I don't think we ever supported this use case with UPS, we never really > documented an example using multiple senders, and the developer can have a > different registrar for each sender if she needs this feature with the new > (GCM 3.0) APIs. > > > > Because we are already using a major version jump for dropping JDK6, I > propose we change the push registrar to only accept a single senderId > instead of allowing multiple sender Ids. This more accurately reflects > what the service (GCM) is doing under the hood now anyway. > > > > If someone has an objection let me know and we can discuss it. > Otherwise I'll continue down this path. > > > > XOXO, > > > > Summers > > _______________________________________________ > > 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 -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150708/a053a286/attachment.html From matzew at apache.org Wed Jul 8 16:47:23 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 8 Jul 2015 22:47:23 +0200 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server In-Reply-To: References: Message-ID: I think that for version 2.x we should deprecate SimplePush, or even remove it (since ups will soon have initial WebPush support) thoughts? On Tuesday, July 7, 2015, Matthias Wessendorf wrote: > Hi team, > > as we are moving forward w/ the releases, and we are close to have our > 1.1.0.Final, I started to think about a proposal for a near-term future > roadmap, and I'd like to get feedback, comments (or tomatos) on it. > UPS > 1.1.x (July/August) > > - 1.1.0 -> very soon > - 1.1.x -> perhaps some needed bug fixes/improvements, in a short > interval :-) > > > UPS > 1.2.0 (September/October) > > We have a release version > in JIRA > already. > > *Key features* > > - Keycloak isolation > - GCM 3 support (client and server) > - Improved docker support (e.g. tests/test suite -> Hopefully Travis > supports 'docker run' by than ;-)) > > One could think that going back to JPA annotations is a key feature as > well ;-) > > UPS > 1.2.x (or even 1.3.0) (December 2015) > > There is no concrete release version for this, but we have a larger > ups-future version > in JIRA. The ups-future version/label has a few interesting things, that we > may have to do right after 1.2.0 > > *Key features* > > - APNs goes HTTP2 (a must) > - Quiete time for push (aka timezone awareness of devices) > - Scheduled pushes > - Proxy server support > > UPS > 2.0.0 (March-2016) > > In October (2015) the WildFly 10 > should > be released and I'd like to see us adapting this for the 2.0.0 series! Also > for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x > series! > > *Note:* We don't have a release version for JIRA here, but heck! this > mail is asking for feedback ;-) > > *Key features / Core changes* > > - UPS based on (public) APIs that are available in WildFly-10 > - looking at using WF feature packs > (similar to > what Keycloak did, e.g. for layered "product" > - looking at getting an UPS sub-system > - Java8 only (as well as making sure works w/ Java9) > - internal communication fully based on messaging (A-MQ / HornetQ) > - WildFly-Swarm launcher (aka fat JARs) > - helps with a more modular system: > - Modular system (e.g. different ?webapps?, like "sender.war", > "registration.war", "UI WAR" etc) > - allows us to play with different platforms for the different ?web > apps? > - e.g. for a 2.x.y we could see/experiment how a vertx microservice > (e.g. for the device registration) will behave in the larger system > > Other new features, e.g. based on needs and/or requests could be weaved > into 2.0.0 or 2.0.x, based on timing. > > Please review this initial draft of a roadmap - once we are all in > agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) > > Greetings, > Matthias > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150708/9dbc7a4e/attachment.html From dpassos at redhat.com Wed Jul 8 20:03:28 2015 From: dpassos at redhat.com (Daniel Passos) Date: Wed, 8 Jul 2015 21:03:28 -0300 Subject: [aerogear-dev] Rename AGDROID Jira components Message-ID: Hi Guys, As you (maybe) know Summers and I started plan and create some Jiras for the next AeroGear Android release (3.0.0)[1]. We also did some organized in Jira, one of that was rename some components do be more close to the name of the GH repos. See the list below OLD NEW Datamanager Store Datasync Sync Pipeline Pipe OAuth2 Authorization UnifiedPush Push Crypto Security [1] https://issues.jboss.org/browse/AGDROID/fixforversion/12327585 ? -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150708/44d3e98f/attachment-0001.html From matzew at apache.org Thu Jul 9 00:27:39 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 9 Jul 2015 06:27:39 +0200 Subject: [aerogear-dev] Rename AGDROID Jira components In-Reply-To: References: Message-ID: I like the name changes On Thu, Jul 9, 2015 at 2:03 AM, Daniel Passos wrote: > Hi Guys, > > As you (maybe) know Summers and I started plan and create some Jiras for > the next AeroGear Android release (3.0.0)[1]. We also did some organized in > Jira, one of that was rename some components do be more close to the name > of the GH repos. See the list below > OLD NEW Datamanager Store Datasync Sync Pipeline Pipe OAuth2 > Authorization UnifiedPush Push Crypto Security > > [1] https://issues.jboss.org/browse/AGDROID/fixforversion/12327585 > ? > -- > -- Passos > > _______________________________________________ > 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/20150709/bef54d69/attachment.html From scm.blanc at gmail.com Thu Jul 9 04:42:48 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 9 Jul 2015 10:42:48 +0200 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server In-Reply-To: References: Message-ID: Looks good ! Some comments inline On Tue, Jul 7, 2015 at 11:51 PM, Matthias Wessendorf wrote: > Hi team, > > as we are moving forward w/ the releases, and we are close to have our > 1.1.0.Final, I started to think about a proposal for a near-term future > roadmap, and I'd like to get feedback, comments (or tomatos) on it. > UPS > 1.1.x (July/August) > > - 1.1.0 -> very soon > - 1.1.x -> perhaps some needed bug fixes/improvements, in a short > interval :-) > > > UPS > 1.2.0 (September/October) > > We have a release version > in JIRA > already. > > *Key features* > > - Keycloak isolation > - GCM 3 support (client and server) > > For server, does that mean using their xmpp connection instead of http ? > > - Improved docker support (e.g. tests/test suite -> Hopefully Travis > supports 'docker run' by than ;-)) > > One could think that going back to JPA annotations is a key feature as > well ;-) > > UPS > 1.2.x (or even 1.3.0) (December 2015) > > There is no concrete release version for this, but we have a larger > ups-future version > in JIRA. The ups-future version/label has a few interesting things, that we > may have to do right after 1.2.0 > > *Key features* > > - APNs goes HTTP2 (a must) > - Quiete time for push (aka timezone awareness of devices) > - Scheduled pushes > - Proxy server support > > Maybe we could consider some new features around metrics/analytics : I'm thinking of A/B testing for instance > UPS > 2.0.0 (March-2016) > > In October (2015) the WildFly 10 > should > be released and I'd like to see us adapting this for the 2.0.0 series! Also > for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x > series! > > *Note:* We don't have a release version for JIRA here, but heck! this > mail is asking for feedback ;-) > > *Key features / Core changes* > > - UPS based on (public) APIs that are available in WildFly-10 > - looking at using WF feature packs > (similar to > what Keycloak did, e.g. for layered "product" > - looking at getting an UPS sub-system > - Java8 only (as well as making sure works w/ Java9) > - internal communication fully based on messaging (A-MQ / HornetQ) > - WildFly-Swarm launcher (aka fat JARs) > - helps with a more modular system: > - Modular system (e.g. different ?webapps?, like "sender.war", > "registration.war", "UI WAR" etc) > - allows us to play with different platforms for the different ?web > apps? > - e.g. for a 2.x.y we could see/experiment how a vertx microservice > (e.g. for the device registration) will behave in the larger system > > I like that :) > Other new features, e.g. based on needs and/or requests could be weaved > into 2.0.0 or 2.0.x, based on timing. > I think we should consider some security features like certificates for registration etc ... But we can maybe discuss that in a different thread. > Please review this initial draft of a roadmap - once we are all in > agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) > > Greetings, > Matthias > > -- > 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/20150709/bdb770e3/attachment.html From scm.blanc at gmail.com Thu Jul 9 04:45:43 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 9 Jul 2015 10:45:43 +0200 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server In-Reply-To: References: Message-ID: On Wed, Jul 8, 2015 at 10:47 PM, Matthias Wessendorf wrote: > I think that for version 2.x we should deprecate SimplePush, or even > remove it (since ups will soon have initial WebPush support) > > thoughts? > I would prefer to mark it as "frozen" (let it go ! Let it go ! ) , not sure that status exist :) but what I mean, even if FirefoxOS switch to WebPush, we have here a stable server and client support and maybe there are still valid use cases (iot) where people want to use SPS. So I think it would be nice to keep it (even if we do not update it anymore) > > > On Tuesday, July 7, 2015, Matthias Wessendorf wrote: > >> Hi team, >> >> as we are moving forward w/ the releases, and we are close to have our >> 1.1.0.Final, I started to think about a proposal for a near-term future >> roadmap, and I'd like to get feedback, comments (or tomatos) on it. >> UPS >> 1.1.x (July/August) >> >> - 1.1.0 -> very soon >> - 1.1.x -> perhaps some needed bug fixes/improvements, in a short >> interval :-) >> >> >> UPS >> 1.2.0 (September/October) >> >> We have a release version >> in JIRA >> already. >> >> *Key features* >> >> - Keycloak isolation >> - GCM 3 support (client and server) >> - Improved docker support (e.g. tests/test suite -> Hopefully Travis >> supports 'docker run' by than ;-)) >> >> One could think that going back to JPA annotations is a key feature as >> well ;-) >> >> UPS >> 1.2.x (or even 1.3.0) (December 2015) >> >> There is no concrete release version for this, but we have a larger >> ups-future >> version >> in JIRA. The ups-future version/label has a few interesting things, that we >> may have to do right after 1.2.0 >> >> *Key features* >> >> - APNs goes HTTP2 (a must) >> - Quiete time for push (aka timezone awareness of devices) >> - Scheduled pushes >> - Proxy server support >> >> UPS >> 2.0.0 (March-2016) >> >> In October (2015) the WildFly 10 >> should >> be released and I'd like to see us adapting this for the 2.0.0 series! Also >> for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x >> series! >> >> *Note:* We don't have a release version for JIRA here, but heck! this >> mail is asking for feedback ;-) >> >> *Key features / Core changes* >> >> - UPS based on (public) APIs that are available in WildFly-10 >> - looking at using WF feature packs >> (similar to >> what Keycloak did, e.g. for layered "product" >> - looking at getting an UPS sub-system >> - Java8 only (as well as making sure works w/ Java9) >> - internal communication fully based on messaging (A-MQ / HornetQ) >> - WildFly-Swarm launcher (aka fat JARs) >> - helps with a more modular system: >> - Modular system (e.g. different ?webapps?, like "sender.war", >> "registration.war", "UI WAR" etc) >> - allows us to play with different platforms for the different >> ?web apps? >> - e.g. for a 2.x.y we could see/experiment how a vertx >> microservice (e.g. for the device registration) will behave in the larger >> system >> >> Other new features, e.g. based on needs and/or requests could be weaved >> into 2.0.0 or 2.0.x, based on timing. >> >> Please review this initial draft of a roadmap - once we are all in >> agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) >> >> Greetings, >> Matthias >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > > -- > Sent from Gmail Mobile > > _______________________________________________ > 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/20150709/329c163c/attachment-0001.html From matzew at apache.org Thu Jul 9 05:28:57 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 9 Jul 2015 11:28:57 +0200 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server In-Reply-To: References: Message-ID: On Thu, Jul 9, 2015 at 10:42 AM, Sebastien Blanc wrote: > Looks good ! > > Some comments inline > > On Tue, Jul 7, 2015 at 11:51 PM, Matthias Wessendorf > wrote: > >> Hi team, >> >> as we are moving forward w/ the releases, and we are close to have our >> 1.1.0.Final, I started to think about a proposal for a near-term future >> roadmap, and I'd like to get feedback, comments (or tomatos) on it. >> UPS >> 1.1.x (July/August) >> >> - 1.1.0 -> very soon >> - 1.1.x -> perhaps some needed bug fixes/improvements, in a short >> interval :-) >> >> >> UPS >> 1.2.0 (September/October) >> >> We have a release version >> in JIRA >> already. >> >> *Key features* >> >> - Keycloak isolation >> - GCM 3 support (client and server) >> >> For server, does that mean using their xmpp connection instead of http ? > GMC 3.0 supports both, actually - but there is a ticket nested for us, to move over to their XMPP based connection approach. > >> - Improved docker support (e.g. tests/test suite -> Hopefully Travis >> supports 'docker run' by than ;-)) >> >> One could think that going back to JPA annotations is a key feature as >> well ;-) >> >> UPS >> 1.2.x (or even 1.3.0) (December 2015) >> >> There is no concrete release version for this, but we have a larger >> ups-future >> version >> in JIRA. The ups-future version/label has a few interesting things, that we >> may have to do right after 1.2.0 >> >> *Key features* >> >> - APNs goes HTTP2 (a must) >> - Quiete time for push (aka timezone awareness of devices) >> - Scheduled pushes >> - Proxy server support >> >> Maybe we could consider some new features around metrics/analytics : I'm > thinking of A/B testing for instance > Good point - But, I think the linked ups-future version already contains that JIRA. > UPS >> 2.0.0 (March-2016) >> >> In October (2015) the WildFly 10 >> should >> be released and I'd like to see us adapting this for the 2.0.0 series! Also >> for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x >> series! >> >> *Note:* We don't have a release version for JIRA here, but heck! this >> mail is asking for feedback ;-) >> >> *Key features / Core changes* >> >> - UPS based on (public) APIs that are available in WildFly-10 >> - looking at using WF feature packs >> (similar to >> what Keycloak did, e.g. for layered "product" >> - looking at getting an UPS sub-system >> - Java8 only (as well as making sure works w/ Java9) >> - internal communication fully based on messaging (A-MQ / HornetQ) >> - WildFly-Swarm launcher (aka fat JARs) >> - helps with a more modular system: >> - Modular system (e.g. different ?webapps?, like "sender.war", >> "registration.war", "UI WAR" etc) >> - allows us to play with different platforms for the different >> ?web apps? >> - e.g. for a 2.x.y we could see/experiment how a vertx >> microservice (e.g. for the device registration) will behave in the larger >> system >> >> I like that :) > >> Other new features, e.g. based on needs and/or requests could be weaved >> into 2.0.0 or 2.0.x, based on timing. >> > I think we should consider some security features like certificates for > registration etc ... But we can maybe discuss that in a different thread. > ah, right - good point, or at least getting rid of HTTP_BASIC and using the KC bearer tokens for the sender and device APIs. > Please review this initial draft of a roadmap - once we are all in >> agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) >> >> Greetings, >> Matthias >> >> -- >> 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/20150709/c82d7c1a/attachment.html From matzew at apache.org Thu Jul 9 05:30:56 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 9 Jul 2015 11:30:56 +0200 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server In-Reply-To: References: Message-ID: On Thu, Jul 9, 2015 at 10:45 AM, Sebastien Blanc wrote: > > > On Wed, Jul 8, 2015 at 10:47 PM, Matthias Wessendorf > wrote: > >> I think that for version 2.x we should deprecate SimplePush, or even >> remove it (since ups will soon have initial WebPush support) >> >> thoughts? >> > I would prefer to mark it as "frozen" (let it go ! Let it go ! ) , not > sure that status exist :) > right - our SimplePush server should be finished, and its 1.0.0 should be the last release - unless we haz major/security issues. Not sure it's up-to-date w/ the latest Moz impl of the server > but what I mean, even if FirefoxOS switch to WebPush, we have here a > stable server and client support and maybe there are still valid use cases > (iot) where people want to use SPS. So I think it would be nice to keep it > (even if we do not update it anymore) > Ok - fair enough - on UPS we can keep the support for SimplePush > > >> >> >> On Tuesday, July 7, 2015, Matthias Wessendorf wrote: >> >>> Hi team, >>> >>> as we are moving forward w/ the releases, and we are close to have our >>> 1.1.0.Final, I started to think about a proposal for a near-term future >>> roadmap, and I'd like to get feedback, comments (or tomatos) on it. >>> UPS >>> 1.1.x (July/August) >>> >>> - 1.1.0 -> very soon >>> - 1.1.x -> perhaps some needed bug fixes/improvements, in a short >>> interval :-) >>> >>> >>> UPS >>> 1.2.0 (September/October) >>> >>> We have a release version >>> in JIRA >>> already. >>> >>> *Key features* >>> >>> - Keycloak isolation >>> - GCM 3 support (client and server) >>> - Improved docker support (e.g. tests/test suite -> Hopefully Travis >>> supports 'docker run' by than ;-)) >>> >>> One could think that going back to JPA annotations is a key feature as >>> well ;-) >>> >>> UPS >>> 1.2.x (or even 1.3.0) (December 2015) >>> >>> There is no concrete release version for this, but we have a larger >>> ups-future >>> version >>> in JIRA. The ups-future version/label has a few interesting things, that we >>> may have to do right after 1.2.0 >>> >>> *Key features* >>> >>> - APNs goes HTTP2 (a must) >>> - Quiete time for push (aka timezone awareness of devices) >>> - Scheduled pushes >>> - Proxy server support >>> >>> UPS >>> 2.0.0 (March-2016) >>> >>> In October (2015) the WildFly 10 >>> should >>> be released and I'd like to see us adapting this for the 2.0.0 series! Also >>> for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x >>> series! >>> >>> *Note:* We don't have a release version for JIRA here, but heck! this >>> mail is asking for feedback ;-) >>> >>> *Key features / Core changes* >>> >>> - UPS based on (public) APIs that are available in WildFly-10 >>> - looking at using WF feature packs >>> (similar >>> to what Keycloak did, e.g. for layered "product" >>> - looking at getting an UPS sub-system >>> - Java8 only (as well as making sure works w/ Java9) >>> - internal communication fully based on messaging (A-MQ / HornetQ) >>> - WildFly-Swarm launcher (aka fat JARs) >>> - helps with a more modular system: >>> - Modular system (e.g. different ?webapps?, like "sender.war", >>> "registration.war", "UI WAR" etc) >>> - allows us to play with different platforms for the different >>> ?web apps? >>> - e.g. for a 2.x.y we could see/experiment how a vertx >>> microservice (e.g. for the device registration) will behave in the larger >>> system >>> >>> Other new features, e.g. based on needs and/or requests could be weaved >>> into 2.0.0 or 2.0.x, based on timing. >>> >>> Please review this initial draft of a roadmap - once we are all in >>> agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) >>> >>> Greetings, >>> Matthias >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >> >> >> -- >> Sent from Gmail Mobile >> >> _______________________________________________ >> 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/20150709/f16afb14/attachment-0001.html From lholmqui at redhat.com Thu Jul 9 08:17:46 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Thu, 9 Jul 2015 08:17:46 -0400 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server In-Reply-To: References: Message-ID: On Thu, Jul 9, 2015 at 5:30 AM, Matthias Wessendorf wrote: > > > On Thu, Jul 9, 2015 at 10:45 AM, Sebastien Blanc > wrote: > >> >> >> On Wed, Jul 8, 2015 at 10:47 PM, Matthias Wessendorf >> wrote: >> >>> I think that for version 2.x we should deprecate SimplePush, or even >>> remove it (since ups will soon have initial WebPush support) >>> >>> thoughts? >>> >> I would prefer to mark it as "frozen" (let it go ! Let it go ! ) , not >> sure that status exist :) >> > > right - our SimplePush server should be finished, and its 1.0.0 should be > the last release - unless we haz major/security issues. > Not sure it's up-to-date w/ the latest Moz impl of the server > > >> but what I mean, even if FirefoxOS switch to WebPush, we have here a >> stable server and client support and maybe there are still valid use cases >> (iot) where people want to use SPS. So I think it would be nice to keep it >> (even if we do not update it anymore) >> > > Ok - fair enough - on UPS we can keep the support for SimplePush > i second this > > >> >> >>> >>> >>> On Tuesday, July 7, 2015, Matthias Wessendorf wrote: >>> >>>> Hi team, >>>> >>>> as we are moving forward w/ the releases, and we are close to have our >>>> 1.1.0.Final, I started to think about a proposal for a near-term future >>>> roadmap, and I'd like to get feedback, comments (or tomatos) on it. >>>> UPS >>>> 1.1.x (July/August) >>>> >>>> - 1.1.0 -> very soon >>>> - 1.1.x -> perhaps some needed bug fixes/improvements, in a short >>>> interval :-) >>>> >>>> >>>> UPS >>>> 1.2.0 (September/October) >>>> >>>> We have a release version >>>> in >>>> JIRA already. >>>> >>>> *Key features* >>>> >>>> - Keycloak isolation >>>> - GCM 3 support (client and server) >>>> - Improved docker support (e.g. tests/test suite -> Hopefully >>>> Travis supports 'docker run' by than ;-)) >>>> >>>> One could think that going back to JPA annotations is a key feature as >>>> well ;-) >>>> >>>> UPS >>>> 1.2.x (or even 1.3.0) (December 2015) >>>> >>>> There is no concrete release version for this, but we have a larger >>>> ups-future >>>> version >>>> in JIRA. The ups-future version/label has a few interesting things, that we >>>> may have to do right after 1.2.0 >>>> >>>> *Key features* >>>> >>>> - APNs goes HTTP2 (a must) >>>> - Quiete time for push (aka timezone awareness of devices) >>>> - Scheduled pushes >>>> - Proxy server support >>>> >>>> UPS >>>> 2.0.0 (March-2016) >>>> >>>> In October (2015) the WildFly 10 >>>> should >>>> be released and I'd like to see us adapting this for the 2.0.0 series! Also >>>> for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x >>>> series! >>>> >>>> *Note:* We don't have a release version for JIRA here, but heck! this >>>> mail is asking for feedback ;-) >>>> >>>> *Key features / Core changes* >>>> >>>> - UPS based on (public) APIs that are available in WildFly-10 >>>> - looking at using WF feature packs >>>> (similar >>>> to what Keycloak did, e.g. for layered "product" >>>> - looking at getting an UPS sub-system >>>> - Java8 only (as well as making sure works w/ Java9) >>>> - internal communication fully based on messaging (A-MQ / HornetQ) >>>> - WildFly-Swarm launcher (aka fat JARs) >>>> - helps with a more modular system: >>>> - Modular system (e.g. different ?webapps?, like "sender.war", >>>> "registration.war", "UI WAR" etc) >>>> - allows us to play with different platforms for the different >>>> ?web apps? >>>> - e.g. for a 2.x.y we could see/experiment how a vertx >>>> microservice (e.g. for the device registration) will behave in the larger >>>> system >>>> >>>> Other new features, e.g. based on needs and/or requests could be weaved >>>> into 2.0.0 or 2.0.x, based on timing. >>>> >>>> Please review this initial draft of a roadmap - once we are all in >>>> agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) >>>> >>>> Greetings, >>>> Matthias >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> >>> >>> >>> -- >>> Sent from Gmail Mobile >>> >>> _______________________________________________ >>> 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/20150709/690a1819/attachment.html From mfink at email.unc.edu Thu Jul 9 13:22:24 2015 From: mfink at email.unc.edu (Fink, Miles) Date: Thu, 9 Jul 2015 17:22:24 +0000 Subject: [aerogear-dev] UPS Node Sender client categories issue? Message-ID: Hi, I?m just starting out with UPS (which is awesome btw!) and the Node.js sender client. One thing I?ve noticed is that a message sent from the dashboard with a particular category is sent to only those installations that have that category listed. This works great and is expected. I?m glad there is a way to target specific notification channels, etc. Sending a notification via the Node Sender client however appears to be sending to everyone?s installation regardless of the categories sent with the message. Here?s a pastie of what my node client call looks like: http://pastie.org/10282358 I?m using: Unifiedpush Node Sender version 0.8.0-beta1 UPS is the setup via the openshift cartridge, from https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push Any pointers would be greatly appreciated. Very well could be me doing it wrong? ;-) Thanks, Miles -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150709/cf8baa04/attachment.html From lholmqui at redhat.com Thu Jul 9 13:28:36 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Thu, 9 Jul 2015 13:28:36 -0400 Subject: [aerogear-dev] UPS Node Sender client categories issue? In-Reply-To: References: Message-ID: hey Miles, Thanks for using the UPS!! so i think what your seeing is probably similar to this issue, https://issues.jboss.org/browse/AGPUSH-1459 The Dashboard uses the Java Client Sender, so something is going on with the node one then thanks for putting your versions you are using, that should help narrow down things -Luke On Thu, Jul 9, 2015 at 1:22 PM, Fink, Miles wrote: > Hi, > > I?m just starting out with UPS (which is awesome btw!) and the Node.js > sender client. One thing I?ve noticed is that a message sent from the > dashboard with a particular category is sent to only those installations > that have that category listed. This works great and is expected. I?m glad > there is a way to target specific notification channels, etc. > > Sending a notification via the Node Sender client however appears to be > sending to everyone?s installation regardless of the categories sent with > the message. Here?s a pastie of what my node client call looks like: > http://pastie.org/10282358 > > I?m using: > Unifiedpush Node Sender version 0.8.0-beta1 > > UPS is the setup via the openshift cartridge, from > https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push > > > Any pointers would be greatly appreciated. Very well could be me doing > it wrong? ;-) > > Thanks, > Miles > > _______________________________________________ > 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/20150709/13d732d6/attachment-0001.html From mfink at email.unc.edu Thu Jul 9 13:32:03 2015 From: mfink at email.unc.edu (Fink, Miles) Date: Thu, 9 Jul 2015 17:32:03 +0000 Subject: [aerogear-dev] UPS Node Sender client categories issue? Message-ID: Hmm, looks like I emailed to soon. It appears I have a version mix match and that my openshift UPS is on the 1.0.x branch and the Node sender release for that branch doesn?t include an options object for including categories? -Miles From: , mfink > Reply-To: AeroGear Developer Mailing List > Date: Thursday, July 9, 2015 at 1:22 PM To: "aerogear-dev at lists.jboss.org" > Subject: [aerogear-dev] UPS Node Sender client categories issue? Hi, I?m just starting out with UPS (which is awesome btw!) and the Node.js sender client. One thing I?ve noticed is that a message sent from the dashboard with a particular category is sent to only those installations that have that category listed. This works great and is expected. I?m glad there is a way to target specific notification channels, etc. Sending a notification via the Node Sender client however appears to be sending to everyone?s installation regardless of the categories sent with the message. Here?s a pastie of what my node client call looks like: http://pastie.org/10282358 I?m using: Unifiedpush Node Sender version 0.8.0-beta1 UPS is the setup via the openshift cartridge, from https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push Any pointers would be greatly appreciated. Very well could be me doing it wrong? ;-) Thanks, Miles -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150709/050b477d/attachment.html From lholmqui at redhat.com Thu Jul 9 13:32:49 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Thu, 9 Jul 2015 13:32:49 -0400 Subject: [aerogear-dev] UPS Node Sender client categories issue? In-Reply-To: References: Message-ID: So i see you are using the 1.0.3 version of the UPS, could you try the 0.7.0 version of the node-sender and see if that works. The 0.8.x series is targeted for the 1.1.x UPS series which has had some message format changes On Thu, Jul 9, 2015 at 1:28 PM, Luke Holmquist wrote: > hey Miles, > > Thanks for using the UPS!! > > so i think what your seeing is probably similar to this issue, > https://issues.jboss.org/browse/AGPUSH-1459 > > > The Dashboard uses the Java Client Sender, so something is going on with > the node one then > > thanks for putting your versions you are using, that should help narrow > down things > > > -Luke > > > On Thu, Jul 9, 2015 at 1:22 PM, Fink, Miles wrote: > >> Hi, >> >> I?m just starting out with UPS (which is awesome btw!) and the Node.js >> sender client. One thing I?ve noticed is that a message sent from the >> dashboard with a particular category is sent to only those installations >> that have that category listed. This works great and is expected. I?m glad >> there is a way to target specific notification channels, etc. >> >> Sending a notification via the Node Sender client however appears to be >> sending to everyone?s installation regardless of the categories sent with >> the message. Here?s a pastie of what my node client call looks like: >> http://pastie.org/10282358 >> >> I?m using: >> Unifiedpush Node Sender version 0.8.0-beta1 >> >> UPS is the setup via the openshift cartridge, from >> https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push >> >> >> Any pointers would be greatly appreciated. Very well could be me doing >> it wrong? ;-) >> >> Thanks, >> Miles >> >> _______________________________________________ >> 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/20150709/01d4d9a7/attachment.html From kpiwko at redhat.com Thu Jul 9 13:34:34 2015 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 9 Jul 2015 19:34:34 +0200 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server In-Reply-To: References: Message-ID: On Tue, Jul 7, 2015 at 11:51 PM, Matthias Wessendorf wrote: > Hi team, > > as we are moving forward w/ the releases, and we are close to have our > 1.1.0.Final, I started to think about a proposal for a near-term future > roadmap, and I'd like to get feedback, comments (or tomatos) on it. > UPS > 1.1.x (July/August) > > - 1.1.0 -> very soon > - 1.1.x -> perhaps some needed bug fixes/improvements, in a short > interval :-) > > > UPS > 1.2.0 (September/October) > > We have a release version > in JIRA > already. > > *Key features* > > - Keycloak isolation > - GCM 3 support (client and server) > - Improved docker support (e.g. tests/test suite -> Hopefully Travis > supports 'docker run' by than ;-)) > > One could think that going back to JPA annotations is a key feature as > well ;-) > > UPS > 1.2.x (or even 1.3.0) (December 2015) > > There is no concrete release version for this, but we have a larger > ups-future version > in JIRA. The ups-future version/label has a few interesting things, that we > may have to do right after 1.2.0 > > *Key features* > > - APNs goes HTTP2 (a must) > - Quiete time for push (aka timezone awareness of devices) > - Scheduled pushes > - Proxy server support > > +9001!!! > UPS > 2.0.0 (March-2016) > > In October (2015) the WildFly 10 > should > be released and I'd like to see us adapting this for the 2.0.0 series! Also > for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x > series! > > Do you plan to have automated migration path from 1.x series? E.g. Windup tool support? > *Note:* We don't have a release version for JIRA here, but heck! this > mail is asking for feedback ;-) > > *Key features / Core changes* > > - UPS based on (public) APIs that are available in WildFly-10 > - looking at using WF feature packs > (similar to > what Keycloak did, e.g. for layered "product" > - looking at getting an UPS sub-system > - Java8 only (as well as making sure works w/ Java9) > - internal communication fully based on messaging (A-MQ / HornetQ) > - WildFly-Swarm launcher (aka fat JARs) > - helps with a more modular system: > - Modular system (e.g. different ?webapps?, like "sender.war", > "registration.war", "UI WAR" etc) > - allows us to play with different platforms for the different ?web > apps? > - e.g. for a 2.x.y we could see/experiment how a vertx microservice > (e.g. for the device registration) will behave in the larger system > > Other new features, e.g. based on needs and/or requests could be weaved > into 2.0.0 or 2.0.x, based on timing. > > Please review this initial draft of a roadmap - once we are all in > agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) > > Greetings, > Matthias > > -- > 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/20150709/06747f1f/attachment-0001.html From kpiwko at redhat.com Thu Jul 9 13:45:55 2015 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 9 Jul 2015 19:45:55 +0200 Subject: [aerogear-dev] New diagrams for UPS clustering and metrics collection improvements In-Reply-To: References: Message-ID: Thanks Lukas, very handy! Karel On Mon, Jun 15, 2015 at 5:53 PM, Luk?? Fry? wrote: > Small correction, here is (3): > https://docs.google.com/drawings/d/1Dt-ANkv7Z0PuyVjdkPrkH0ZAO8VOr8GbZ0dGmL5iXTw/edit?usp=sharing > > On Mon, Jun 15, 2015 at 5:31 PM, Luk?? Fry? wrote: > >> Hi guys, >> >> I'm finishing diagrams for the docs that cover how UPS using JMS works >> (or will work in a near future) internally. >> >> The concepts illustrated in (2) and (3) are not yet implemented, they >> are just proposals, >> >> that's why I would appreciate if you go through them, read callouts, and >> if you have idea how to improve them, let us know! >> >> *1. Overall picture:* >> >> https://docs.google.com/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing >> >> *2. Token loading, dispatching and metrics collection in detail:* >> >> https://docs.google.com/a/fryc.eu/drawings/d/12cUrYf7ACLYEoYsIWul2szN3lmQcYFMjjaZDq2fr9qQ/edit?usp=sharing >> >> *3. Concept of limiting number of push dispatching sessions * >> *(cluster-wide):* >> >> https://docs.google.com/a/fryc.eu/drawings/d/12cUrYf7ACLYEoYsIWul2szN3lmQcYFMjjaZDq2fr9qQ/edit?usp=sharing >> >> >> There are more details coming in form of UPS guide docs / appendix. >> >> Cheers! >> >> ~ Lukas >> > > > _______________________________________________ > 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/20150709/af32a591/attachment.html From mfink at email.unc.edu Thu Jul 9 14:15:50 2015 From: mfink at email.unc.edu (Fink, Miles) Date: Thu, 9 Jul 2015 18:15:50 +0000 Subject: [aerogear-dev] UPS Node Sender client categories issue? In-Reply-To: References: Message-ID: Thanks Luke. Using 0.7.0 version worked. I will note a couple items: 0.8.x uses applicationId (note Id), .0.7.x uses applicationID Also, I was sending empty arrays for the settings.criteria that I wasn?t using (deviceType, alias) which then still sent the notification to all installations regardless of the categories I was sending. After I removed all the empty arrays from criteria and just sent the categories array it worked! Anyway, thanks for the support! Much appreciated! Cheers, Miles From: Luke Holmquist > Reply-To: AeroGear Developer Mailing List > Date: Thursday, July 9, 2015 at 1:32 PM To: AeroGear Developer Mailing List > Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? So i see you are using the 1.0.3 version of the UPS, could you try the 0.7.0 version of the node-sender and see if that works. The 0.8.x series is targeted for the 1.1.x UPS series which has had some message format changes On Thu, Jul 9, 2015 at 1:28 PM, Luke Holmquist > wrote: hey Miles, Thanks for using the UPS!! so i think what your seeing is probably similar to this issue, https://issues.jboss.org/browse/AGPUSH-1459 The Dashboard uses the Java Client Sender, so something is going on with the node one then thanks for putting your versions you are using, that should help narrow down things -Luke On Thu, Jul 9, 2015 at 1:22 PM, Fink, Miles > wrote: Hi, I?m just starting out with UPS (which is awesome btw!) and the Node.js sender client. One thing I?ve noticed is that a message sent from the dashboard with a particular category is sent to only those installations that have that category listed. This works great and is expected. I?m glad there is a way to target specific notification channels, etc. Sending a notification via the Node Sender client however appears to be sending to everyone?s installation regardless of the categories sent with the message. Here?s a pastie of what my node client call looks like: http://pastie.org/10282358 I?m using: Unifiedpush Node Sender version 0.8.0-beta1 UPS is the setup via the openshift cartridge, from https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push Any pointers would be greatly appreciated. Very well could be me doing it wrong? ;-) Thanks, Miles _______________________________________________ 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/20150709/4c51379f/attachment.html From lholmqui at redhat.com Thu Jul 9 14:27:40 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Thu, 9 Jul 2015 14:27:40 -0400 Subject: [aerogear-dev] UPS Node Sender client categories issue? In-Reply-To: References: Message-ID: On Thu, Jul 9, 2015 at 2:15 PM, Fink, Miles wrote: > Thanks Luke. Using 0.7.0 version worked. > > I will note a couple items: > > 0.8.x uses application*Id* (note Id), .0.7.x uses application*ID* > > Also, I was sending empty arrays for the settings.criteria that I wasn?t > using (deviceType, alias) which then still sent the notification to all > installations regardless of the categories I was sending. After I removed > all the empty arrays from criteria and just sent the categories array it > worked! > thanks for that input. sounds like a Bug! > > Anyway, thanks for the support! Much appreciated! > > Cheers, > Miles > > > From: Luke Holmquist > Reply-To: AeroGear Developer Mailing List > Date: Thursday, July 9, 2015 at 1:32 PM > To: AeroGear Developer Mailing List > Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? > > So i see you are using the 1.0.3 version of the UPS, could you try the > 0.7.0 version of the node-sender and see if that works. > > The 0.8.x series is targeted for the 1.1.x UPS series which has had some > message format changes > > On Thu, Jul 9, 2015 at 1:28 PM, Luke Holmquist > wrote: > >> hey Miles, >> >> Thanks for using the UPS!! >> >> so i think what your seeing is probably similar to this issue, >> https://issues.jboss.org/browse/AGPUSH-1459 >> >> >> The Dashboard uses the Java Client Sender, so something is going on >> with the node one then >> >> thanks for putting your versions you are using, that should help narrow >> down things >> >> >> -Luke >> >> >> On Thu, Jul 9, 2015 at 1:22 PM, Fink, Miles wrote: >> >>> Hi, >>> >>> I?m just starting out with UPS (which is awesome btw!) and the Node.js >>> sender client. One thing I?ve noticed is that a message sent from the >>> dashboard with a particular category is sent to only those installations >>> that have that category listed. This works great and is expected. I?m glad >>> there is a way to target specific notification channels, etc. >>> >>> Sending a notification via the Node Sender client however appears to >>> be sending to everyone?s installation regardless of the categories sent >>> with the message. Here?s a pastie of what my node client call looks like: >>> http://pastie.org/10282358 >>> >>> I?m using: >>> Unifiedpush Node Sender version 0.8.0-beta1 >>> >>> UPS is the setup via the openshift cartridge, from >>> https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push >>> >>> >>> Any pointers would be greatly appreciated. Very well could be me doing >>> it wrong? ;-) >>> >>> Thanks, >>> Miles >>> >>> _______________________________________________ >>> 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/20150709/7d26d762/attachment-0001.html From matzew at apache.org Thu Jul 9 15:44:45 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 9 Jul 2015 21:44:45 +0200 Subject: [aerogear-dev] [Tutorial] OAuth 2.0 with Swift Message-ID: Hi! I just noticed that today Corinne's tutorial on "OAuth 2.0 with Swift " got published at the famous 'raywenderlich' site: http://www.raywenderlich.com/99431/oauth-2-with-swift-tutorial Even better her article gives our AeroGear APIs a nice visibility hook :-) Congrats on getting the article published at Ray Wenderlich, Corinne! -Matthias -- 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/20150709/f36f3496/attachment.html From supittma at redhat.com Thu Jul 9 16:04:47 2015 From: supittma at redhat.com (Summers Pittman) Date: Thu, 9 Jul 2015 16:04:47 -0400 Subject: [aerogear-dev] AGDroid 3.0 improvements Message-ID: One of the things passos and I have discussed in the past is using dependency injection (possibly dagger) to reduce a lot of the boiler plate that is in AGDroid projects (think those nasty config blocks in the quickstarts which exist for EVERY pipe, oauthmodule, push module, etc). We decided not to do that in the past because to make it work we would need to use a gradle plugin, extend all the activity and fragment classes to interrupt the normal lifecycle, or require the user to call magic methods. This felt out of touch with the "style" of programming Google was advocating at the time. With Google play services 7.5 Google is preparing a gradle plugin which will consume a services file and provide those values to code via static variables. (Specifically it injects them into the value.xml file which aidl turns into values in the Resources object). So we've decided to revisit the issue. See Epic : https://issues.jboss.org/browse/AGDROID-476 We want to create a Gradle plugin which will parse ups and keycloak json files and provide convenient tools for managing interactions with those objects. These tools right now will consist of providing annotations to inject modules and interaction with the Activity lifecycle. In the Push Issue on the Jira I have a quick sample of how the code might look. You can see there is a LOT less boiler plate. The idea is that all of the values in the PushRegistrar were parsed from json config file automatically and the PushRegistrar was instantiated and managed transparently. wdyt? What are pain points you've had with AGDroid this style of tool could help? Should we also make plugins for maven applications? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150709/f3431108/attachment.html From qmx at qmx.me Thu Jul 9 16:56:44 2015 From: qmx at qmx.me (Douglas Campos) Date: Thu, 9 Jul 2015 17:56:44 -0300 Subject: [aerogear-dev] Index on device tokens Message-ID: Howdy y'all While I was doing the migration work I've noticed there's an index for device tokens on the installation table. The problem is that MySQL InnoDB doesn't support indexes for VARCHAR columns wider than 255 chars. Any ideas on how to fix this? Was this really a point of contention? What motivated the index addition? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150709/0309fa43/attachment.html From matzew at apache.org Fri Jul 10 01:04:00 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 10 Jul 2015 07:04:00 +0200 Subject: [aerogear-dev] Index on device tokens In-Reply-To: References: Message-ID: yep, it's a known issue https://issues.jboss.org/browse/AGPUSH-1370 On Thu, Jul 9, 2015 at 10:56 PM, Douglas Campos wrote: > Howdy y'all > > While I was doing the migration work I've noticed there's an index for > device tokens on the installation table. The problem is that MySQL InnoDB > doesn't support indexes for VARCHAR columns wider than 255 chars. > > Any ideas on how to fix this? Was this really a point of contention? What > motivated the index addition? > > Thanks! > > _______________________________________________ > 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/20150710/48322b37/attachment.html From scm.blanc at gmail.com Fri Jul 10 07:42:23 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 10 Jul 2015 13:42:23 +0200 Subject: [aerogear-dev] AGDroid 3.0 improvements In-Reply-To: References: Message-ID: I like that ! But did I understand that is tied to Google play Services ? I mean I could not use that to inject for instance the Amazon Push Registrar flavor ? On Thu, Jul 9, 2015 at 10:04 PM, Summers Pittman wrote: > One of the things passos and I have discussed in the past is using > dependency injection (possibly dagger) to reduce a lot of the boiler plate > that is in AGDroid projects (think those nasty config blocks in the > quickstarts which exist for EVERY pipe, oauthmodule, push module, etc). We > decided not to do that in the past because to make it work we would need to > use a gradle plugin, extend all the activity and fragment classes to > interrupt the normal lifecycle, or require the user to call magic methods. > This felt out of touch with the "style" of programming Google was > advocating at the time. > > With Google play services 7.5 Google is preparing a gradle plugin which > will consume a services file and provide those values to code via static > variables. (Specifically it injects them into the value.xml file which aidl > turns into values in the Resources object). So we've decided to revisit > the issue. > > See Epic : https://issues.jboss.org/browse/AGDROID-476 > > We want to create a Gradle plugin which will parse ups and keycloak json > files and provide convenient tools for managing interactions with those > objects. These tools right now will consist of providing annotations to > inject modules and interaction with the Activity lifecycle. > > In the Push Issue on the Jira I have a quick sample of how the code might > look. You can see there is a LOT less boiler plate. The idea is that all > of the values in the PushRegistrar were parsed from json config file > automatically and the PushRegistrar was instantiated and managed > transparently. > > wdyt? What are pain points you've had with AGDroid this style of tool > could help? Should we also make plugins for maven applications? > > _______________________________________________ > 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/20150710/73c35c03/attachment.html From supittma at redhat.com Fri Jul 10 09:09:53 2015 From: supittma at redhat.com (Summers Pittman) Date: Fri, 10 Jul 2015 09:09:53 -0400 Subject: [aerogear-dev] AGDroid 3.0 improvements In-Reply-To: References: Message-ID: Currently we don't support Amazon in the -push library at all so no. If we did at a later date, yes. On Fri, Jul 10, 2015 at 7:42 AM, Sebastien Blanc wrote: > I like that ! > But did I understand that is tied to Google play Services ? I mean I could > not use that to inject for instance the Amazon Push Registrar flavor ? > > > On Thu, Jul 9, 2015 at 10:04 PM, Summers Pittman > wrote: > >> One of the things passos and I have discussed in the past is using >> dependency injection (possibly dagger) to reduce a lot of the boiler plate >> that is in AGDroid projects (think those nasty config blocks in the >> quickstarts which exist for EVERY pipe, oauthmodule, push module, etc). We >> decided not to do that in the past because to make it work we would need to >> use a gradle plugin, extend all the activity and fragment classes to >> interrupt the normal lifecycle, or require the user to call magic methods. >> This felt out of touch with the "style" of programming Google was >> advocating at the time. >> >> With Google play services 7.5 Google is preparing a gradle plugin which >> will consume a services file and provide those values to code via static >> variables. (Specifically it injects them into the value.xml file which aidl >> turns into values in the Resources object). So we've decided to revisit >> the issue. >> >> See Epic : https://issues.jboss.org/browse/AGDROID-476 >> >> We want to create a Gradle plugin which will parse ups and keycloak json >> files and provide convenient tools for managing interactions with those >> objects. These tools right now will consist of providing annotations to >> inject modules and interaction with the Activity lifecycle. >> >> In the Push Issue on the Jira I have a quick sample of how the code might >> look. You can see there is a LOT less boiler plate. The idea is that all >> of the values in the PushRegistrar were parsed from json config file >> automatically and the PushRegistrar was instantiated and managed >> transparently. >> >> wdyt? What are pain points you've had with AGDroid this style of tool >> could help? Should we also make plugins for maven applications? >> >> _______________________________________________ >> 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/20150710/7a414e5f/attachment-0001.html From matzew at apache.org Mon Jul 13 04:39:02 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 13 Jul 2015 10:39:02 +0200 Subject: [aerogear-dev] [UPS] Create Push Application & variants in the same rest service In-Reply-To: References: Message-ID: let's give this "create all in one" a shot will send a PR later today On Fri, Jul 3, 2015 at 2:38 PM, Matthias Wessendorf wrote: > Doh - damn Apple. > > We could do some a check on a (future) "/createAllInOne" :) endpoint to > see if multipart is around (just for iOS) or not (for 'normal') > > > > On Fri, Jul 3, 2015 at 2:33 PM, Sebastien Blanc > wrote: > >> I just realized that the iOS Variant endpoint still expects an >> mutlipartform :/ that will make it a bit more difficult (mostly because of >> the certificate) >> >> >> On Fri, Jul 3, 2015 at 12:02 PM, Sebastien Blanc >> wrote: >> >>> Hi peeps, >>> >>> We recently added some documentation around integration : >>> https://staging.aerogear.org/docs/unifiedpush/ups_userguide/index/#integration >>> (still on the staging site but will be released soon) >>> and also some scripts that shows how this integration can work : >>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/node.js >>> >>> And that made me think of the following use case : >>> >>> A third party should be able to create in one call the Push App and its >>> variants. That would not be too much work on the server side, so wdyt ? >>> >>> >>> >> >> _______________________________________________ >> 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/20150713/879d7c31/attachment.html From mmurphy at redhat.com Mon Jul 13 11:59:56 2015 From: mmurphy at redhat.com (Martin Murphy) Date: Mon, 13 Jul 2015 16:59:56 +0100 Subject: [aerogear-dev] Push plugin for Cordova Message-ID: <88157D9E-84C3-4183-A495-2EA947894F9E@redhat.com> Hi folks, we have a Cordova application that?s using Codrova 3.3. The application uses org.jboss.aerogear.cordova.push 1.0.2 When preparing for an android build, there seems to be an problem installing one of the dependencies of the aurora plugin An id has been updated: com.vladstirbu.cordova.promise, now has a different id: es6-promise-plugin. The newer plugin 2.0.2 is in the npm registry. Is it possible to add a fix and deploy to the old cordova registry so that it?s usable in 3.x Is the newer plugin 2.0.2 backward compatible with 1.0.2 I understand that the ideal approach would be to use a more up-to-date version of Cordova, and use the latest aurora plugin, however it will take some time before I will be able to do that. I?m open to other suggestions also. Best Regards, Martin Murphy. From matzew at apache.org Tue Jul 14 04:51:09 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Jul 2015 10:51:09 +0200 Subject: [aerogear-dev] UPS Node Sender client categories issue? In-Reply-To: References: Message-ID: Miles,Luke mind filing a JIRA issue for this ? On Thu, Jul 9, 2015 at 8:27 PM, Luke Holmquist wrote: > > > On Thu, Jul 9, 2015 at 2:15 PM, Fink, Miles wrote: > >> Thanks Luke. Using 0.7.0 version worked. >> >> I will note a couple items: >> >> 0.8.x uses application*Id* (note Id), .0.7.x uses application*ID* >> >> Also, I was sending empty arrays for the settings.criteria that I >> wasn?t using (deviceType, alias) which then still sent the notification to >> all installations regardless of the categories I was sending. After I >> removed all the empty arrays from criteria and just sent the categories >> array it worked! >> > > thanks for that input. sounds like a Bug! > >> >> Anyway, thanks for the support! Much appreciated! >> >> Cheers, >> Miles >> >> >> From: Luke Holmquist >> Reply-To: AeroGear Developer Mailing List >> Date: Thursday, July 9, 2015 at 1:32 PM >> To: AeroGear Developer Mailing List >> Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? >> >> So i see you are using the 1.0.3 version of the UPS, could you try >> the 0.7.0 version of the node-sender and see if that works. >> >> The 0.8.x series is targeted for the 1.1.x UPS series which has had >> some message format changes >> >> On Thu, Jul 9, 2015 at 1:28 PM, Luke Holmquist >> wrote: >> >>> hey Miles, >>> >>> Thanks for using the UPS!! >>> >>> so i think what your seeing is probably similar to this issue, >>> https://issues.jboss.org/browse/AGPUSH-1459 >>> >>> >>> The Dashboard uses the Java Client Sender, so something is going on >>> with the node one then >>> >>> thanks for putting your versions you are using, that should help >>> narrow down things >>> >>> >>> -Luke >>> >>> >>> On Thu, Jul 9, 2015 at 1:22 PM, Fink, Miles >>> wrote: >>> >>>> Hi, >>>> >>>> I?m just starting out with UPS (which is awesome btw!) and the >>>> Node.js sender client. One thing I?ve noticed is that a message sent from >>>> the dashboard with a particular category is sent to only those >>>> installations that have that category listed. This works great and is >>>> expected. I?m glad there is a way to target specific notification channels, >>>> etc. >>>> >>>> Sending a notification via the Node Sender client however appears to >>>> be sending to everyone?s installation regardless of the categories sent >>>> with the message. Here?s a pastie of what my node client call looks like: >>>> http://pastie.org/10282358 >>>> >>>> I?m using: >>>> Unifiedpush Node Sender version 0.8.0-beta1 >>>> >>>> UPS is the setup via the openshift cartridge, from >>>> https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push >>>> >>>> >>>> Any pointers would be greatly appreciated. Very well could be me >>>> doing it wrong? ;-) >>>> >>>> Thanks, >>>> Miles >>>> >>>> _______________________________________________ >>>> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150714/ec279910/attachment.html From matzew at apache.org Tue Jul 14 06:59:35 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Jul 2015 12:59:35 +0200 Subject: [aerogear-dev] Push plugin for Cordova In-Reply-To: <88157D9E-84C3-4183-A495-2EA947894F9E@redhat.com> References: <88157D9E-84C3-4183-A495-2EA947894F9E@redhat.com> Message-ID: Hi Martin, so - it's basically porting this commit over to the 1.0x branch: https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 right ? Mind sending a PR ? On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy wrote: > Hi folks, > we have a Cordova application that?s using Codrova 3.3. > The application uses org.jboss.aerogear.cordova.push 1.0.2 > > When preparing for an android build, there seems to be an problem > installing one of the dependencies of the aurora plugin > An id has been updated: com.vladstirbu.cordova.promise, now has a > different id: es6-promise-plugin. > > The newer plugin 2.0.2 is in the npm registry. > > Is it possible to add a fix and deploy to the old cordova registry so that > it?s usable in 3.x > Is the newer plugin 2.0.2 backward compatible with 1.0.2 > > I understand that the ideal approach would be to use a more up-to-date > version of Cordova, and use the latest aurora plugin, however it will take > some time before I will be able to do that. > I?m open to other suggestions also. > > Best Regards, > Martin Murphy. > > > > _______________________________________________ > 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/20150714/33336331/attachment-0001.html From mmurphy at redhat.com Tue Jul 14 07:11:56 2015 From: mmurphy at redhat.com (Martin Murphy) Date: Tue, 14 Jul 2015 12:11:56 +0100 Subject: [aerogear-dev] Push plugin for Cordova In-Reply-To: References: <88157D9E-84C3-4183-A495-2EA947894F9E@redhat.com> Message-ID: Hi Matthias, That would do, however I was think more of this way: https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477 to avoid the risk of pointing at a changing repo. Can use the one you mentioned, or a combination of them? I can certainly do the PR. Best Regards, Martin Murphy. > On 14 Jul 2015, at 11:59, Matthias Wessendorf wrote: > > Hi Martin, > > so - it's basically porting this commit over to the 1.0x branch: > https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 > > right ? > > Mind sending a PR ? > > On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy > wrote: > Hi folks, > we have a Cordova application that?s using Codrova 3.3. > The application uses org.jboss.aerogear.cordova.push 1.0.2 > > When preparing for an android build, there seems to be an problem installing one of the dependencies of the aurora plugin > An id has been updated: com.vladstirbu.cordova.promise, now has a different id: es6-promise-plugin. > > The newer plugin 2.0.2 is in the npm registry. > > Is it possible to add a fix and deploy to the old cordova registry so that it?s usable in 3.x > Is the newer plugin 2.0.2 backward compatible with 1.0.2 > > I understand that the ideal approach would be to use a more up-to-date version of Cordova, and use the latest aurora plugin, however it will take some time before I will be able to do that. > I?m open to other suggestions also. > > Best Regards, > Martin Murphy. > > > > _______________________________________________ > 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/20150714/cb5521e5/attachment.html From matzew at apache.org Tue Jul 14 07:16:10 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Jul 2015 13:16:10 +0200 Subject: [aerogear-dev] Push plugin for Cordova In-Reply-To: References: <88157D9E-84C3-4183-A495-2EA947894F9E@redhat.com> Message-ID: On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy wrote: > Hi Matthias, > That would do, however I was think more of this way: > > https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477 > to avoid the risk of pointing at a changing repo. > sounds good! > > Can use the one you mentioned, or a combination of them? > > I can certainly do the PR. > that would be awesome > > > Best Regards, > Martin Murphy. > > > On 14 Jul 2015, at 11:59, Matthias Wessendorf wrote: > > Hi Martin, > > so - it's basically porting this commit over to the 1.0x branch: > > https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 > > right ? > > Mind sending a PR ? > > On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy wrote: > >> Hi folks, >> we have a Cordova application that?s using Codrova 3.3. >> The application uses org.jboss.aerogear.cordova.push 1.0.2 >> >> When preparing for an android build, there seems to be an problem >> installing one of the dependencies of the aurora plugin >> An id has been updated: com.vladstirbu.cordova.promise, now has a >> different id: es6-promise-plugin. >> >> The newer plugin 2.0.2 is in the npm registry. >> >> Is it possible to add a fix and deploy to the old cordova registry so >> that it?s usable in 3.x >> Is the newer plugin 2.0.2 backward compatible with 1.0.2 >> >> I understand that the ideal approach would be to use a more up-to-date >> version of Cordova, and use the latest aurora plugin, however it will take >> some time before I will be able to do that. >> I?m open to other suggestions also. >> >> Best Regards, >> Martin Murphy. >> >> >> >> _______________________________________________ >> 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/20150714/8794be0a/attachment.html From mmurphy at redhat.com Tue Jul 14 07:35:59 2015 From: mmurphy at redhat.com (Martin Murphy) Date: Tue, 14 Jul 2015 12:35:59 +0100 Subject: [aerogear-dev] Push plugin for Cordova In-Reply-To: References: <88157D9E-84C3-4183-A495-2EA947894F9E@redhat.com> Message-ID: <8BF0659B-C814-471A-80D8-F6AE2C93F0FE@redhat.com> > On 14 Jul 2015, at 12:16, Matthias Wessendorf wrote: > > > > On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy > wrote: > Hi Matthias, > That would do, however I was think more of this way: > https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477 > to avoid the risk of pointing at a changing repo. > > sounds good! > > > Can use the one you mentioned, or a combination of them? > > I can certainly do the PR. > > that would be awesome Is this sufficient? https://github.com/aerogear/aerogear-cordova-push/pull/74 > > > > Best Regards, > Martin Murphy. > > >> On 14 Jul 2015, at 11:59, Matthias Wessendorf > wrote: >> >> Hi Martin, >> >> so - it's basically porting this commit over to the 1.0x branch: >> https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 >> >> right ? >> >> Mind sending a PR ? >> >> On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy > wrote: >> Hi folks, >> we have a Cordova application that?s using Codrova 3.3. >> The application uses org.jboss.aerogear.cordova.push 1.0.2 >> >> When preparing for an android build, there seems to be an problem installing one of the dependencies of the aurora plugin >> An id has been updated: com.vladstirbu.cordova.promise, now has a different id: es6-promise-plugin. >> >> The newer plugin 2.0.2 is in the npm registry. >> >> Is it possible to add a fix and deploy to the old cordova registry so that it?s usable in 3.x >> Is the newer plugin 2.0.2 backward compatible with 1.0.2 >> >> I understand that the ideal approach would be to use a more up-to-date version of Cordova, and use the latest aurora plugin, however it will take some time before I will be able to do that. >> I?m open to other suggestions also. >> >> Best Regards, >> Martin Murphy. >> >> >> >> _______________________________________________ >> 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/20150714/c5fdd830/attachment-0001.html From matzew at apache.org Tue Jul 14 08:30:47 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Jul 2015 14:30:47 +0200 Subject: [aerogear-dev] Cordova Push - 1.0.3 release (was: Re: Push plugin for Cordova) Message-ID: Hi, now that we merged the PR from Martin, and the given fact that the old plugin registry is read-only, starting tomorrow, I'd like to push a release of the 1.0.3 version, using this branch: https://github.com/aerogear/aerogear-cordova-push/tree/1.0.x Any thoughts? On Tue, Jul 14, 2015 at 1:35 PM, Martin Murphy wrote: > > On 14 Jul 2015, at 12:16, Matthias Wessendorf wrote: > > > > On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy wrote: > >> Hi Matthias, >> That would do, however I was think more of this way: >> >> https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477 >> to avoid the risk of pointing at a changing repo. >> > > sounds good! > > >> >> Can use the one you mentioned, or a combination of them? >> >> I can certainly do the PR. >> > > that would be awesome > > > Is this sufficient? > https://github.com/aerogear/aerogear-cordova-push/pull/74 > > > >> >> >> Best Regards, >> Martin Murphy. >> >> >> On 14 Jul 2015, at 11:59, Matthias Wessendorf wrote: >> >> Hi Martin, >> >> so - it's basically porting this commit over to the 1.0x branch: >> >> https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 >> >> right ? >> >> Mind sending a PR ? >> >> On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy >> wrote: >> >>> Hi folks, >>> we have a Cordova application that?s using Codrova 3.3. >>> The application uses org.jboss.aerogear.cordova.push 1.0.2 >>> >>> When preparing for an android build, there seems to be an problem >>> installing one of the dependencies of the aurora plugin >>> An id has been updated: com.vladstirbu.cordova.promise, now has a >>> different id: es6-promise-plugin. >>> >>> The newer plugin 2.0.2 is in the npm registry. >>> >>> Is it possible to add a fix and deploy to the old cordova registry so >>> that it?s usable in 3.x >>> Is the newer plugin 2.0.2 backward compatible with 1.0.2 >>> >>> I understand that the ideal approach would be to use a more up-to-date >>> version of Cordova, and use the latest aurora plugin, however it will take >>> some time before I will be able to do that. >>> I?m open to other suggestions also. >>> >>> Best Regards, >>> Martin Murphy. >>> >>> >>> >>> _______________________________________________ >>> 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 > > > > _______________________________________________ > 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/20150714/3ce9510c/attachment.html From mfink at email.unc.edu Tue Jul 14 08:56:24 2015 From: mfink at email.unc.edu (Fink, Miles) Date: Tue, 14 Jul 2015 12:56:24 +0000 Subject: [aerogear-dev] UPS Node Sender client categories issue? In-Reply-To: References: Message-ID: I'll see if I can?t get it in JIRA. Just to clarify, the issue I noticed regarding empty arrays was on the 0.7.x branch of Node Sender, so it may not be an issue in the latest branch. -Miles From: Matthias Wessendorf > Reply-To: AeroGear Developer Mailing List > Date: Tuesday, July 14, 2015 at 4:51 AM To: AeroGear Developer Mailing List > Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? Miles,Luke mind filing a JIRA issue for this ? On Thu, Jul 9, 2015 at 8:27 PM, Luke Holmquist > wrote: On Thu, Jul 9, 2015 at 2:15 PM, Fink, Miles > wrote: Thanks Luke. Using 0.7.0 version worked. I will note a couple items: 0.8.x uses applicationId (note Id), .0.7.x uses applicationID Also, I was sending empty arrays for the settings.criteria that I wasn?t using (deviceType, alias) which then still sent the notification to all installations regardless of the categories I was sending. After I removed all the empty arrays from criteria and just sent the categories array it worked! thanks for that input. sounds like a Bug! Anyway, thanks for the support! Much appreciated! Cheers, Miles From: Luke Holmquist > Reply-To: AeroGear Developer Mailing List > Date: Thursday, July 9, 2015 at 1:32 PM To: AeroGear Developer Mailing List > Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? So i see you are using the 1.0.3 version of the UPS, could you try the 0.7.0 version of the node-sender and see if that works. The 0.8.x series is targeted for the 1.1.x UPS series which has had some message format changes On Thu, Jul 9, 2015 at 1:28 PM, Luke Holmquist > wrote: hey Miles, Thanks for using the UPS!! so i think what your seeing is probably similar to this issue, https://issues.jboss.org/browse/AGPUSH-1459 The Dashboard uses the Java Client Sender, so something is going on with the node one then thanks for putting your versions you are using, that should help narrow down things -Luke On Thu, Jul 9, 2015 at 1:22 PM, Fink, Miles > wrote: Hi, I?m just starting out with UPS (which is awesome btw!) and the Node.js sender client. One thing I?ve noticed is that a message sent from the dashboard with a particular category is sent to only those installations that have that category listed. This works great and is expected. I?m glad there is a way to target specific notification channels, etc. Sending a notification via the Node Sender client however appears to be sending to everyone?s installation regardless of the categories sent with the message. Here?s a pastie of what my node client call looks like: http://pastie.org/10282358 I?m using: Unifiedpush Node Sender version 0.8.0-beta1 UPS is the setup via the openshift cartridge, from https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push Any pointers would be greatly appreciated. Very well could be me doing it wrong? ;-) Thanks, Miles _______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150714/776887a4/attachment-0001.html From mmurphy at redhat.com Tue Jul 14 09:10:13 2015 From: mmurphy at redhat.com (Martin Murphy) Date: Tue, 14 Jul 2015 14:10:13 +0100 Subject: [aerogear-dev] Cordova Push - 1.0.3 release (was: Re: Push plugin for Cordova) In-Reply-To: References: Message-ID: <8708342E-7A1A-4EED-B749-8B1E2A25EAD4@redhat.com> > On 14 Jul 2015, at 13:30, Matthias Wessendorf wrote: > > Hi, > > now that we merged the PR from Martin, and the given fact that the old plugin registry is read-only, starting tomorrow, I'd like to push a release of the 1.0.3 version, using this branch: > > https://github.com/aerogear/aerogear-cordova-push/tree/1.0.x > > Any thoughts? Sounds good to me :) Best Regards, Martin Murphy. > > On Tue, Jul 14, 2015 at 1:35 PM, Martin Murphy > wrote: > >> On 14 Jul 2015, at 12:16, Matthias Wessendorf > wrote: >> >> >> >> On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy > wrote: >> Hi Matthias, >> That would do, however I was think more of this way: >> https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477 >> to avoid the risk of pointing at a changing repo. >> >> sounds good! >> >> >> Can use the one you mentioned, or a combination of them? >> >> I can certainly do the PR. >> >> that would be awesome > > Is this sufficient? https://github.com/aerogear/aerogear-cordova-push/pull/74 > >> >> >> >> Best Regards, >> Martin Murphy. >> >> >>> On 14 Jul 2015, at 11:59, Matthias Wessendorf > wrote: >>> >>> Hi Martin, >>> >>> so - it's basically porting this commit over to the 1.0x branch: >>> https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 >>> >>> right ? >>> >>> Mind sending a PR ? >>> >>> On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy > wrote: >>> Hi folks, >>> we have a Cordova application that?s using Codrova 3.3. >>> The application uses org.jboss.aerogear.cordova.push 1.0.2 >>> >>> When preparing for an android build, there seems to be an problem installing one of the dependencies of the aurora plugin >>> An id has been updated: com.vladstirbu.cordova.promise, now has a different id: es6-promise-plugin. >>> >>> The newer plugin 2.0.2 is in the npm registry. >>> >>> Is it possible to add a fix and deploy to the old cordova registry so that it?s usable in 3.x >>> Is the newer plugin 2.0.2 backward compatible with 1.0.2 >>> >>> I understand that the ideal approach would be to use a more up-to-date version of Cordova, and use the latest aurora plugin, however it will take some time before I will be able to do that. >>> I?m open to other suggestions also. >>> >>> Best Regards, >>> Martin Murphy. >>> >>> >>> >>> _______________________________________________ >>> 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 > > _______________________________________________ > 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/20150714/002ec87b/attachment.html From lholmqui at redhat.com Tue Jul 14 09:11:35 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Tue, 14 Jul 2015 09:11:35 -0400 Subject: [aerogear-dev] Cordova Push - 1.0.3 release (was: Re: Push plugin for Cordova) In-Reply-To: References: Message-ID: lets do it On Tue, Jul 14, 2015 at 8:30 AM, Matthias Wessendorf wrote: > Hi, > > now that we merged the PR from Martin, and the given fact that the old > plugin registry is read-only, starting tomorrow, I'd like to push a release > of the 1.0.3 version, using this branch: > > https://github.com/aerogear/aerogear-cordova-push/tree/1.0.x > > Any thoughts? > > On Tue, Jul 14, 2015 at 1:35 PM, Martin Murphy wrote: > >> >> On 14 Jul 2015, at 12:16, Matthias Wessendorf wrote: >> >> >> >> On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy >> wrote: >> >>> Hi Matthias, >>> That would do, however I was think more of this way: >>> >>> https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477 >>> to avoid the risk of pointing at a changing repo. >>> >> >> sounds good! >> >> >>> >>> Can use the one you mentioned, or a combination of them? >>> >>> I can certainly do the PR. >>> >> >> that would be awesome >> >> >> Is this sufficient? >> https://github.com/aerogear/aerogear-cordova-push/pull/74 >> >> >> >>> >>> >>> Best Regards, >>> Martin Murphy. >>> >>> >>> On 14 Jul 2015, at 11:59, Matthias Wessendorf wrote: >>> >>> Hi Martin, >>> >>> so - it's basically porting this commit over to the 1.0x branch: >>> >>> https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 >>> >>> right ? >>> >>> Mind sending a PR ? >>> >>> On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy >>> wrote: >>> >>>> Hi folks, >>>> we have a Cordova application that?s using Codrova 3.3. >>>> The application uses org.jboss.aerogear.cordova.push 1.0.2 >>>> >>>> When preparing for an android build, there seems to be an problem >>>> installing one of the dependencies of the aurora plugin >>>> An id has been updated: com.vladstirbu.cordova.promise, now has a >>>> different id: es6-promise-plugin. >>>> >>>> The newer plugin 2.0.2 is in the npm registry. >>>> >>>> Is it possible to add a fix and deploy to the old cordova registry so >>>> that it?s usable in 3.x >>>> Is the newer plugin 2.0.2 backward compatible with 1.0.2 >>>> >>>> I understand that the ideal approach would be to use a more up-to-date >>>> version of Cordova, and use the latest aurora plugin, however it will take >>>> some time before I will be able to do that. >>>> I?m open to other suggestions also. >>>> >>>> Best Regards, >>>> Martin Murphy. >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >> >> >> >> _______________________________________________ >> 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/20150714/ef017825/attachment-0001.html From dpassos at redhat.com Tue Jul 14 09:18:50 2015 From: dpassos at redhat.com (Daniel Passos) Date: Tue, 14 Jul 2015 10:18:50 -0300 Subject: [aerogear-dev] Cordova Push - 1.0.3 release (was: Re: Push plugin for Cordova) In-Reply-To: References: Message-ID: +1 On Tue, Jul 14, 2015 at 10:11 AM, Luke Holmquist wrote: > lets do it > > On Tue, Jul 14, 2015 at 8:30 AM, Matthias Wessendorf > wrote: > >> Hi, >> >> now that we merged the PR from Martin, and the given fact that the old >> plugin registry is read-only, starting tomorrow, I'd like to push a release >> of the 1.0.3 version, using this branch: >> >> https://github.com/aerogear/aerogear-cordova-push/tree/1.0.x >> >> Any thoughts? >> >> On Tue, Jul 14, 2015 at 1:35 PM, Martin Murphy >> wrote: >> >>> >>> On 14 Jul 2015, at 12:16, Matthias Wessendorf wrote: >>> >>> >>> >>> On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy >>> wrote: >>> >>>> Hi Matthias, >>>> That would do, however I was think more of this way: >>>> >>>> https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477 >>>> to avoid the risk of pointing at a changing repo. >>>> >>> >>> sounds good! >>> >>> >>>> >>>> Can use the one you mentioned, or a combination of them? >>>> >>>> I can certainly do the PR. >>>> >>> >>> that would be awesome >>> >>> >>> Is this sufficient? >>> https://github.com/aerogear/aerogear-cordova-push/pull/74 >>> >>> >>> >>>> >>>> >>>> Best Regards, >>>> Martin Murphy. >>>> >>>> >>>> On 14 Jul 2015, at 11:59, Matthias Wessendorf >>>> wrote: >>>> >>>> Hi Martin, >>>> >>>> so - it's basically porting this commit over to the 1.0x branch: >>>> >>>> https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 >>>> >>>> right ? >>>> >>>> Mind sending a PR ? >>>> >>>> On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy >>>> wrote: >>>> >>>>> Hi folks, >>>>> we have a Cordova application that?s using Codrova 3.3. >>>>> The application uses org.jboss.aerogear.cordova.push 1.0.2 >>>>> >>>>> When preparing for an android build, there seems to be an problem >>>>> installing one of the dependencies of the aurora plugin >>>>> An id has been updated: com.vladstirbu.cordova.promise, now has a >>>>> different id: es6-promise-plugin. >>>>> >>>>> The newer plugin 2.0.2 is in the npm registry. >>>>> >>>>> Is it possible to add a fix and deploy to the old cordova registry so >>>>> that it?s usable in 3.x >>>>> Is the newer plugin 2.0.2 backward compatible with 1.0.2 >>>>> >>>>> I understand that the ideal approach would be to use a more up-to-date >>>>> version of Cordova, and use the latest aurora plugin, however it will take >>>>> some time before I will be able to do that. >>>>> I?m open to other suggestions also. >>>>> >>>>> Best Regards, >>>>> Martin Murphy. >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >>> >>> >>> _______________________________________________ >>> 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 > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150714/6712354d/attachment.html From bruno at abstractj.org Tue Jul 14 09:19:11 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 14 Jul 2015 10:19:11 -0300 Subject: [aerogear-dev] Cordova Push - 1.0.3 release (was: Re: Push plugin for Cordova) In-Reply-To: References: Message-ID: Ship it! On Tue, Jul 14, 2015 at 9:30 AM, Matthias Wessendorf wrote: > Hi, > > now that we merged the PR from Martin, and the given fact that the old > plugin registry is read-only, starting tomorrow, I'd like to push a release > of the 1.0.3 version, using this branch: > > https://github.com/aerogear/aerogear-cordova-push/tree/1.0.x > > Any thoughts? > > On Tue, Jul 14, 2015 at 1:35 PM, Martin Murphy wrote: > >> >> On 14 Jul 2015, at 12:16, Matthias Wessendorf wrote: >> >> >> >> On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy >> wrote: >> >>> Hi Matthias, >>> That would do, however I was think more of this way: >>> >>> https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477 >>> to avoid the risk of pointing at a changing repo. >>> >> >> sounds good! >> >> >>> >>> Can use the one you mentioned, or a combination of them? >>> >>> I can certainly do the PR. >>> >> >> that would be awesome >> >> >> Is this sufficient? >> https://github.com/aerogear/aerogear-cordova-push/pull/74 >> >> >> >>> >>> >>> Best Regards, >>> Martin Murphy. >>> >>> >>> On 14 Jul 2015, at 11:59, Matthias Wessendorf wrote: >>> >>> Hi Martin, >>> >>> so - it's basically porting this commit over to the 1.0x branch: >>> >>> https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 >>> >>> right ? >>> >>> Mind sending a PR ? >>> >>> On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy >>> wrote: >>> >>>> Hi folks, >>>> we have a Cordova application that?s using Codrova 3.3. >>>> The application uses org.jboss.aerogear.cordova.push 1.0.2 >>>> >>>> When preparing for an android build, there seems to be an problem >>>> installing one of the dependencies of the aurora plugin >>>> An id has been updated: com.vladstirbu.cordova.promise, now has a >>>> different id: es6-promise-plugin. >>>> >>>> The newer plugin 2.0.2 is in the npm registry. >>>> >>>> Is it possible to add a fix and deploy to the old cordova registry so >>>> that it?s usable in 3.x >>>> Is the newer plugin 2.0.2 backward compatible with 1.0.2 >>>> >>>> I understand that the ideal approach would be to use a more up-to-date >>>> version of Cordova, and use the latest aurora plugin, however it will take >>>> some time before I will be able to do that. >>>> I?m open to other suggestions also. >>>> >>>> Best Regards, >>>> Martin Murphy. >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >> >> >> >> _______________________________________________ >> 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 > -- -- "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/20150714/63e7322b/attachment-0001.html From dpassos at redhat.com Tue Jul 14 10:08:15 2015 From: dpassos at redhat.com (Daniel Passos) Date: Tue, 14 Jul 2015 11:08:15 -0300 Subject: [aerogear-dev] AeroGear Android 3.0 - Roadmap Message-ID: Hey Guys, As you know Summers and I started work on AGDroid 3.0. Today we revisited what we want to this release. I hope you enjoy it GOALS - Remove Java 6 support - Move to $LATEST android-maven-plugin - GCM 3.0 + Push Tasks - Extra convenience tooling - Memeolist demo app - Update docs - oAuth2 improvements - Experimental Offline Module - Experimental Yubikey Neo support Aerogear Android Push - GCM 3.0 - Instance ID - This is a new lifecycle for keeping the registration ID in sync - Using new services and broadcast receivers or providing equavalent support - XMPP - Using XMPP messaging for receiving messages and sending analytics updates - May be basis for more robust client side diagnostics and/or eventual messaging APIs AeroGear Android plugin (new) - Previously we shot this idea down because it adds work on developer which isn?t standard - Google is moving to including more plugins in Gradle so that isn?t a concern - Goals - Linting push and authz - Confirm services in manifest - Confirm appropriate licecycle on Message Listeners - Annotation Processing - Automate boring lifecycle tasks around Push (attaching/detaching listeners from activity) - Manifest processing - Inject Required services for push and authz if libraries are present - Automatically configure these services with values from keycloak.json and push-service.json AeroGear Android Cookbook - Memeolist Demo App - Show off Material design skills - Show off integration with other Red Hat/JBoss technologies - Increase profile of AeroGear inside of Red Hat - Dogfooding AeroGear Android Pipe - Logging support - Easier injection of HTTPProviders - Document adding custom headers under pipe AeroGear Android Store - Decide between - Async operation - Content Provider - With the plugin we could also engage in automatic contract object generation - For an example of what I am thinking see Contracts and ContentProvider AeroGear Android Offline - Cache : Configurable storage mechanism - Location : Where the CaceItem will be stored - Memory : in Memory store. - OnDevice : the internal permanent storage of the device - Media : removable media based storage. SD Cards, USB Sticks, etc - Eviction Policy : How long CacheItems can stay around - Permanent : Cache items must be removed manually - LRU : When the cache is full the least recently accessed will be removed - Fifo : The oldest object in the cache will be removed. - Size : The max number of items a cache may hold. - Age : The max age of any item AeroGear Android Authz - Revisit oAuth2 opened jiras AeroGear Android Security - Experimental Yubikey Neo support PS: Jiras are comming soon ? -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150714/dafd32af/attachment.html From dpassos at redhat.com Tue Jul 14 10:13:14 2015 From: dpassos at redhat.com (Daniel Passos) Date: Tue, 14 Jul 2015 11:13:14 -0300 Subject: [aerogear-dev] What's new in AeroGear? Message-ID: Hi all, Here is a community update: Android AeroGear Android 3.0 - Roadmap http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Android-3-0-Roadmap-td11933.html Summers is working in a gradle plugin for AeroGear Android. It is part of the annotations stuff, mostly experimenting on things while we wait for GCM 3.0 https://github.com/secondsun/aerogear-android-plugin ? -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150714/0ee5213b/attachment.html From lholmqui at redhat.com Tue Jul 14 10:28:23 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Tue, 14 Jul 2015 10:28:23 -0400 Subject: [aerogear-dev] UPS Node Sender client categories issue? In-Reply-To: References: Message-ID: JIRA'd https://issues.jboss.org/browse/AGPUSH-1468 Matzew, so for versioning of the node-sender, i wonder if we should add that "component" in the versions for JIRA similar to how sps has it's own versioning scheme. something like node-sender-0.7.0 , node-sender-0.8.0 ? something like that, would be easier to keep track of those releases. as i was writing this, i'm also thinking if these issues should be part of AG-JS and i can do the versions there? hmmm On Tue, Jul 14, 2015 at 8:56 AM, Fink, Miles wrote: > I'll see if I can?t get it in JIRA. Just to clarify, the issue I > noticed regarding empty arrays was on the 0.7.x branch of Node Sender, so > it may not be an issue in the latest branch. > > -Miles > > From: Matthias Wessendorf > Reply-To: AeroGear Developer Mailing List > Date: Tuesday, July 14, 2015 at 4:51 AM > > To: AeroGear Developer Mailing List > Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? > > Miles,Luke > > mind filing a JIRA issue for this ? > > On Thu, Jul 9, 2015 at 8:27 PM, Luke Holmquist > wrote: > >> >> >> On Thu, Jul 9, 2015 at 2:15 PM, Fink, Miles wrote: >> >>> Thanks Luke. Using 0.7.0 version worked. >>> >>> I will note a couple items: >>> >>> 0.8.x uses application*Id* (note Id), .0.7.x uses application*ID* >>> >>> Also, I was sending empty arrays for the settings.criteria that I >>> wasn?t using (deviceType, alias) which then still sent the notification to >>> all installations regardless of the categories I was sending. After I >>> removed all the empty arrays from criteria and just sent the categories >>> array it worked! >>> >> >> thanks for that input. sounds like a Bug! >> >>> >>> Anyway, thanks for the support! Much appreciated! >>> >>> Cheers, >>> Miles >>> >>> >>> From: Luke Holmquist >>> Reply-To: AeroGear Developer Mailing List >>> Date: Thursday, July 9, 2015 at 1:32 PM >>> To: AeroGear Developer Mailing List >>> Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? >>> >>> So i see you are using the 1.0.3 version of the UPS, could you try >>> the 0.7.0 version of the node-sender and see if that works. >>> >>> The 0.8.x series is targeted for the 1.1.x UPS series which has had >>> some message format changes >>> >>> On Thu, Jul 9, 2015 at 1:28 PM, Luke Holmquist >>> wrote: >>> >>>> hey Miles, >>>> >>>> Thanks for using the UPS!! >>>> >>>> so i think what your seeing is probably similar to this issue, >>>> https://issues.jboss.org/browse/AGPUSH-1459 >>>> >>>> >>>> The Dashboard uses the Java Client Sender, so something is going on >>>> with the node one then >>>> >>>> thanks for putting your versions you are using, that should help >>>> narrow down things >>>> >>>> >>>> -Luke >>>> >>>> >>>> On Thu, Jul 9, 2015 at 1:22 PM, Fink, Miles >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I?m just starting out with UPS (which is awesome btw!) and the >>>>> Node.js sender client. One thing I?ve noticed is that a message sent from >>>>> the dashboard with a particular category is sent to only those >>>>> installations that have that category listed. This works great and is >>>>> expected. I?m glad there is a way to target specific notification channels, >>>>> etc. >>>>> >>>>> Sending a notification via the Node Sender client however appears to >>>>> be sending to everyone?s installation regardless of the categories sent >>>>> with the message. Here?s a pastie of what my node client call looks like: >>>>> http://pastie.org/10282358 >>>>> >>>>> I?m using: >>>>> Unifiedpush Node Sender version 0.8.0-beta1 >>>>> >>>>> UPS is the setup via the openshift cartridge, from >>>>> https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push >>>>> >>>>> >>>>> Any pointers would be greatly appreciated. Very well could be me >>>>> doing it wrong? ;-) >>>>> >>>>> Thanks, >>>>> Miles >>>>> >>>>> _______________________________________________ >>>>> 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/20150714/2e94299b/attachment-0001.html From matzew at apache.org Tue Jul 14 11:01:44 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Jul 2015 17:01:44 +0200 Subject: [aerogear-dev] Help! (was: Re: Cordova Push - 1.0.3 release (was: Re: Push plugin for Cordova)) Message-ID: I need help :-) a few 'problems' * there is already a 1.0.3 TAG - but was not published (not a big deal - we will just do 1.0.4 instead) * I can not publish the 1.0.4 stuff - this is a real problem/blocker :-( here is my > plugman publish . I am getting this error: attempting to publish plugin to registry npm ERR! publish Failed PUT response undefined Error Code: undefined login error Unfortunately the current published 1.0.2 is broken and does not work..., another pity is the 'old' registry (where our 1.0.x stuff is located) is read-only by tomorrow: http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html So... we can only update it today :-) If one of you, that did push some plugins in the past (Erik in on vacation), could help out here and push the 1.0.4 TAG to the registry? It's highly appreciated. thanks, Matthias On Tue, Jul 14, 2015 at 2:30 PM, Matthias Wessendorf wrote: > Hi, > > now that we merged the PR from Martin, and the given fact that the old > plugin registry is read-only, starting tomorrow, I'd like to push a release > of the 1.0.3 version, using this branch: > > https://github.com/aerogear/aerogear-cordova-push/tree/1.0.x > > Any thoughts? > > On Tue, Jul 14, 2015 at 1:35 PM, Martin Murphy wrote: > >> >> On 14 Jul 2015, at 12:16, Matthias Wessendorf wrote: >> >> >> >> On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy >> wrote: >> >>> Hi Matthias, >>> That would do, however I was think more of this way: >>> >>> https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477 >>> to avoid the risk of pointing at a changing repo. >>> >> >> sounds good! >> >> >>> >>> Can use the one you mentioned, or a combination of them? >>> >>> I can certainly do the PR. >>> >> >> that would be awesome >> >> >> Is this sufficient? >> https://github.com/aerogear/aerogear-cordova-push/pull/74 >> >> >> >>> >>> >>> Best Regards, >>> Martin Murphy. >>> >>> >>> On 14 Jul 2015, at 11:59, Matthias Wessendorf wrote: >>> >>> Hi Martin, >>> >>> so - it's basically porting this commit over to the 1.0x branch: >>> >>> https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 >>> >>> right ? >>> >>> Mind sending a PR ? >>> >>> On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy >>> wrote: >>> >>>> Hi folks, >>>> we have a Cordova application that?s using Codrova 3.3. >>>> The application uses org.jboss.aerogear.cordova.push 1.0.2 >>>> >>>> When preparing for an android build, there seems to be an problem >>>> installing one of the dependencies of the aurora plugin >>>> An id has been updated: com.vladstirbu.cordova.promise, now has a >>>> different id: es6-promise-plugin. >>>> >>>> The newer plugin 2.0.2 is in the npm registry. >>>> >>>> Is it possible to add a fix and deploy to the old cordova registry so >>>> that it?s usable in 3.x >>>> Is the newer plugin 2.0.2 backward compatible with 1.0.2 >>>> >>>> I understand that the ideal approach would be to use a more up-to-date >>>> version of Cordova, and use the latest aurora plugin, however it will take >>>> some time before I will be able to do that. >>>> I?m open to other suggestions also. >>>> >>>> Best Regards, >>>> Martin Murphy. >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >> >> >> >> _______________________________________________ >> 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/20150714/6d4540de/attachment.html From matzew at apache.org Tue Jul 14 11:05:53 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Jul 2015 17:05:53 +0200 Subject: [aerogear-dev] UPS Node Sender client categories issue? In-Reply-To: References: Message-ID: On Tue, Jul 14, 2015 at 4:28 PM, Luke Holmquist wrote: > JIRA'd https://issues.jboss.org/browse/AGPUSH-1468 > > > Matzew, so for versioning of the node-sender, i wonder if we should add > that "component" in the versions for JIRA similar to how sps has it's own > versioning scheme. something like node-sender-0.7.0 , node-sender-0.8.0 ? > something like that, would be easier to keep track of those releases. > > as i was writing this, i'm also thinking if these issues should be part > of AG-JS and i can do the versions there? hmmm > yeah - actually, I think you are right. I am absolutely fine w/ having the node-js-sender on AGJS. It's been a) a fairly stable component (lholmquist++) and b) our APIs are mostly JSON payload to a well-known endpoint - so not much to 'plan' from a AGPUSH / UPS perspective -M > > > On Tue, Jul 14, 2015 at 8:56 AM, Fink, Miles wrote: > >> I'll see if I can?t get it in JIRA. Just to clarify, the issue I >> noticed regarding empty arrays was on the 0.7.x branch of Node Sender, so >> it may not be an issue in the latest branch. >> >> -Miles >> >> From: Matthias Wessendorf >> Reply-To: AeroGear Developer Mailing List >> Date: Tuesday, July 14, 2015 at 4:51 AM >> >> To: AeroGear Developer Mailing List >> Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? >> >> Miles,Luke >> >> mind filing a JIRA issue for this ? >> >> On Thu, Jul 9, 2015 at 8:27 PM, Luke Holmquist >> wrote: >> >>> >>> >>> On Thu, Jul 9, 2015 at 2:15 PM, Fink, Miles wrote: >>> >>>> Thanks Luke. Using 0.7.0 version worked. >>>> >>>> I will note a couple items: >>>> >>>> 0.8.x uses application*Id* (note Id), .0.7.x uses application*ID* >>>> >>>> Also, I was sending empty arrays for the settings.criteria that I >>>> wasn?t using (deviceType, alias) which then still sent the notification to >>>> all installations regardless of the categories I was sending. After I >>>> removed all the empty arrays from criteria and just sent the categories >>>> array it worked! >>>> >>> >>> thanks for that input. sounds like a Bug! >>> >>>> >>>> Anyway, thanks for the support! Much appreciated! >>>> >>>> Cheers, >>>> Miles >>>> >>>> >>>> From: Luke Holmquist >>>> Reply-To: AeroGear Developer Mailing List >>> > >>>> Date: Thursday, July 9, 2015 at 1:32 PM >>>> To: AeroGear Developer Mailing List >>>> Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? >>>> >>>> So i see you are using the 1.0.3 version of the UPS, could you try >>>> the 0.7.0 version of the node-sender and see if that works. >>>> >>>> The 0.8.x series is targeted for the 1.1.x UPS series which has had >>>> some message format changes >>>> >>>> On Thu, Jul 9, 2015 at 1:28 PM, Luke Holmquist >>>> wrote: >>>> >>>>> hey Miles, >>>>> >>>>> Thanks for using the UPS!! >>>>> >>>>> so i think what your seeing is probably similar to this issue, >>>>> https://issues.jboss.org/browse/AGPUSH-1459 >>>>> >>>>> >>>>> The Dashboard uses the Java Client Sender, so something is going on >>>>> with the node one then >>>>> >>>>> thanks for putting your versions you are using, that should help >>>>> narrow down things >>>>> >>>>> >>>>> -Luke >>>>> >>>>> >>>>> On Thu, Jul 9, 2015 at 1:22 PM, Fink, Miles >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I?m just starting out with UPS (which is awesome btw!) and the >>>>>> Node.js sender client. One thing I?ve noticed is that a message sent from >>>>>> the dashboard with a particular category is sent to only those >>>>>> installations that have that category listed. This works great and is >>>>>> expected. I?m glad there is a way to target specific notification channels, >>>>>> etc. >>>>>> >>>>>> Sending a notification via the Node Sender client however appears >>>>>> to be sending to everyone?s installation regardless of the categories sent >>>>>> with the message. Here?s a pastie of what my node client call looks like: >>>>>> http://pastie.org/10282358 >>>>>> >>>>>> I?m using: >>>>>> Unifiedpush Node Sender version 0.8.0-beta1 >>>>>> >>>>>> UPS is the setup via the openshift cartridge, from >>>>>> https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push >>>>>> >>>>>> >>>>>> Any pointers would be greatly appreciated. Very well could be me >>>>>> doing it wrong? ;-) >>>>>> >>>>>> Thanks, >>>>>> Miles >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >> > > > _______________________________________________ > 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/20150714/79eb9f59/attachment-0001.html From supittma at redhat.com Tue Jul 14 11:17:21 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 14 Jul 2015 11:17:21 -0400 Subject: [aerogear-dev] AeroGear Android 3.0 - Roadmap In-Reply-To: References: Message-ID: On Tue, Jul 14, 2015 at 10:08 AM, Daniel Passos wrote: > Hey Guys, > > As you know Summers and I started work on AGDroid 3.0. Today we revisited > what we want to this release. I hope you enjoy it > GOALS > > - Remove Java 6 support > - Move to $LATEST android-maven-plugin > - GCM 3.0 + Push Tasks > - Extra convenience tooling > - Memeolist demo app > - Update docs > - oAuth2 improvements > - Experimental Offline Module > - Experimental Yubikey Neo support > > Aerogear Android Push > > - GCM 3.0 > - Instance ID > - This is a new lifecycle for keeping the registration ID in sync > - Using new services and broadcast receivers or providing > equavalent support > - XMPP > - Using XMPP messaging for receiving messages and sending analytics > updates > - May be basis for more robust client side diagnostics and/or > eventual messaging APIs > > AeroGear Android plugin (new) > > - Previously we shot this idea down because it adds work on developer > which isn?t standard > - Google is moving to including more plugins in Gradle so that isn?t a > concern > - Goals > - Linting push and authz > - Confirm services in manifest > - Confirm appropriate licecycle on Message Listeners > - Annotation Processing > - Automate boring lifecycle tasks around Push > (attaching/detaching listeners from activity) > - Manifest processing > - Inject Required services for push and authz if libraries are > present > - Automatically configure these services with values from > keycloak.json and push-service.json > > AeroGear Android Cookbook > > - Memeolist Demo App > - Show off Material design skills > - Show off integration with other Red Hat/JBoss technologies > - Increase profile of AeroGear inside of Red Hat > - Dogfooding > > AeroGear Android Pipe > > - Logging support > - Easier injection of HTTPProviders > - Document adding custom headers under pipe > > AeroGear Android Store > > - Decide between > - Async operation > - Content Provider > - With the plugin we could also engage in automatic contract > object generation > - For an example of what I am thinking see Contracts > > and ContentProvider > > > AeroGear Android Offline > > - Cache : Configurable storage mechanism > - Location : Where the CaceItem will be stored > - Memory : in Memory store. > - OnDevice : the internal permanent storage of the device > - Media : removable media based storage. SD Cards, USB Sticks, > etc > - Eviction Policy : How long CacheItems can stay around > - Permanent : Cache items must be removed manually > - LRU : When the cache is full the least recently accessed will > be removed > - Fifo : The oldest object in the cache will be removed. > - Size : The max number of items a cache may hold. > - Age : The max age of any item > > AeroGear Android Authz > > - Revisit oAuth2 opened jiras > > AeroGear Android Security > > - Experimental Yubikey Neo > support > > PS: Jiras are comming soon > PPS Feel free to yell at us with thoughts, ideas, comments, etc. > ? > -- > -- 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/20150714/09ed6f4e/attachment.html From lholmqui at redhat.com Tue Jul 14 11:22:13 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Tue, 14 Jul 2015 11:22:13 -0400 Subject: [aerogear-dev] Help! (was: Re: Cordova Push - 1.0.3 release (was: Re: Push plugin for Cordova)) In-Reply-To: References: Message-ID: it looks like erik is the only owner of the plugin: https://gist.github.com/lholmquist/06161cfde8c0a25c61e5 i have a user in the registry, lholmquist , but i cannot add it to the plugin using 'plugman owner add lholmquist' i think erik might need to add me On Tue, Jul 14, 2015 at 11:01 AM, Matthias Wessendorf wrote: > I need help :-) > > a few 'problems' > > * there is already a 1.0.3 TAG - but was not published (not a big deal - > we will just do 1.0.4 instead) > * I can not publish the 1.0.4 stuff - this is a real problem/blocker :-( > > here is my > > plugman publish . > > I am getting this error: > > attempting to publish plugin to registry > npm ERR! publish Failed PUT response undefined > Error Code: undefined > login error > > > Unfortunately the current published 1.0.2 is broken and does not work..., > another pity is the 'old' registry (where our 1.0.x stuff is located) is > read-only by tomorrow: > > http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html > > So... we can only update it today :-) > > > If one of you, that did push some plugins in the past (Erik in on > vacation), could help out here and push the 1.0.4 TAG to the registry? It's > highly appreciated. > > thanks, > Matthias > > > > On Tue, Jul 14, 2015 at 2:30 PM, Matthias Wessendorf > wrote: > >> Hi, >> >> now that we merged the PR from Martin, and the given fact that the old >> plugin registry is read-only, starting tomorrow, I'd like to push a release >> of the 1.0.3 version, using this branch: >> >> https://github.com/aerogear/aerogear-cordova-push/tree/1.0.x >> >> Any thoughts? >> >> On Tue, Jul 14, 2015 at 1:35 PM, Martin Murphy >> wrote: >> >>> >>> On 14 Jul 2015, at 12:16, Matthias Wessendorf wrote: >>> >>> >>> >>> On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy >>> wrote: >>> >>>> Hi Matthias, >>>> That would do, however I was think more of this way: >>>> >>>> https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477 >>>> to avoid the risk of pointing at a changing repo. >>>> >>> >>> sounds good! >>> >>> >>>> >>>> Can use the one you mentioned, or a combination of them? >>>> >>>> I can certainly do the PR. >>>> >>> >>> that would be awesome >>> >>> >>> Is this sufficient? >>> https://github.com/aerogear/aerogear-cordova-push/pull/74 >>> >>> >>> >>>> >>>> >>>> Best Regards, >>>> Martin Murphy. >>>> >>>> >>>> On 14 Jul 2015, at 11:59, Matthias Wessendorf >>>> wrote: >>>> >>>> Hi Martin, >>>> >>>> so - it's basically porting this commit over to the 1.0x branch: >>>> >>>> https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 >>>> >>>> right ? >>>> >>>> Mind sending a PR ? >>>> >>>> On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy >>>> wrote: >>>> >>>>> Hi folks, >>>>> we have a Cordova application that?s using Codrova 3.3. >>>>> The application uses org.jboss.aerogear.cordova.push 1.0.2 >>>>> >>>>> When preparing for an android build, there seems to be an problem >>>>> installing one of the dependencies of the aurora plugin >>>>> An id has been updated: com.vladstirbu.cordova.promise, now has a >>>>> different id: es6-promise-plugin. >>>>> >>>>> The newer plugin 2.0.2 is in the npm registry. >>>>> >>>>> Is it possible to add a fix and deploy to the old cordova registry so >>>>> that it?s usable in 3.x >>>>> Is the newer plugin 2.0.2 backward compatible with 1.0.2 >>>>> >>>>> I understand that the ideal approach would be to use a more up-to-date >>>>> version of Cordova, and use the latest aurora plugin, however it will take >>>>> some time before I will be able to do that. >>>>> I?m open to other suggestions also. >>>>> >>>>> Best Regards, >>>>> Martin Murphy. >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >>> >>> >>> _______________________________________________ >>> 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/20150714/6695ce91/attachment-0001.html From lholmqui at redhat.com Tue Jul 14 11:23:59 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Tue, 14 Jul 2015 11:23:59 -0400 Subject: [aerogear-dev] UPS Node Sender client categories issue? In-Reply-To: References: Message-ID: On Tue, Jul 14, 2015 at 11:05 AM, Matthias Wessendorf wrote: > > > On Tue, Jul 14, 2015 at 4:28 PM, Luke Holmquist > wrote: > >> JIRA'd https://issues.jboss.org/browse/AGPUSH-1468 >> >> >> Matzew, so for versioning of the node-sender, i wonder if we should add >> that "component" in the versions for JIRA similar to how sps has it's own >> versioning scheme. something like node-sender-0.7.0 , node-sender-0.8.0 ? >> something like that, would be easier to keep track of those releases. >> >> as i was writing this, i'm also thinking if these issues should be part >> of AG-JS and i can do the versions there? hmmm >> > > yeah - actually, I think you are right. I am absolutely fine w/ having the > node-js-sender on AGJS. > > It's been a) a fairly stable component (lholmquist++) and b) our APIs are > mostly JSON payload to a well-known endpoint - so not much to 'plan' from a > AGPUSH / UPS perspective > ok, sounds good. I will start adding things over there > > -M > > >> >> >> On Tue, Jul 14, 2015 at 8:56 AM, Fink, Miles wrote: >> >>> I'll see if I can?t get it in JIRA. Just to clarify, the issue I >>> noticed regarding empty arrays was on the 0.7.x branch of Node Sender, so >>> it may not be an issue in the latest branch. >>> >>> -Miles >>> >>> From: Matthias Wessendorf >>> Reply-To: AeroGear Developer Mailing List >>> Date: Tuesday, July 14, 2015 at 4:51 AM >>> >>> To: AeroGear Developer Mailing List >>> Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? >>> >>> Miles,Luke >>> >>> mind filing a JIRA issue for this ? >>> >>> On Thu, Jul 9, 2015 at 8:27 PM, Luke Holmquist >>> wrote: >>> >>>> >>>> >>>> On Thu, Jul 9, 2015 at 2:15 PM, Fink, Miles >>>> wrote: >>>> >>>>> Thanks Luke. Using 0.7.0 version worked. >>>>> >>>>> I will note a couple items: >>>>> >>>>> 0.8.x uses application*Id* (note Id), .0.7.x uses application*ID* >>>>> >>>>> Also, I was sending empty arrays for the settings.criteria that I >>>>> wasn?t using (deviceType, alias) which then still sent the notification to >>>>> all installations regardless of the categories I was sending. After I >>>>> removed all the empty arrays from criteria and just sent the categories >>>>> array it worked! >>>>> >>>> >>>> thanks for that input. sounds like a Bug! >>>> >>>>> >>>>> Anyway, thanks for the support! Much appreciated! >>>>> >>>>> Cheers, >>>>> Miles >>>>> >>>>> >>>>> From: Luke Holmquist >>>>> Reply-To: AeroGear Developer Mailing List < >>>>> aerogear-dev at lists.jboss.org> >>>>> Date: Thursday, July 9, 2015 at 1:32 PM >>>>> To: AeroGear Developer Mailing List >>>>> Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? >>>>> >>>>> So i see you are using the 1.0.3 version of the UPS, could you try >>>>> the 0.7.0 version of the node-sender and see if that works. >>>>> >>>>> The 0.8.x series is targeted for the 1.1.x UPS series which has had >>>>> some message format changes >>>>> >>>>> On Thu, Jul 9, 2015 at 1:28 PM, Luke Holmquist >>>>> wrote: >>>>> >>>>>> hey Miles, >>>>>> >>>>>> Thanks for using the UPS!! >>>>>> >>>>>> so i think what your seeing is probably similar to this issue, >>>>>> https://issues.jboss.org/browse/AGPUSH-1459 >>>>>> >>>>>> >>>>>> The Dashboard uses the Java Client Sender, so something is going on >>>>>> with the node one then >>>>>> >>>>>> thanks for putting your versions you are using, that should help >>>>>> narrow down things >>>>>> >>>>>> >>>>>> -Luke >>>>>> >>>>>> >>>>>> On Thu, Jul 9, 2015 at 1:22 PM, Fink, Miles >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I?m just starting out with UPS (which is awesome btw!) and the >>>>>>> Node.js sender client. One thing I?ve noticed is that a message sent from >>>>>>> the dashboard with a particular category is sent to only those >>>>>>> installations that have that category listed. This works great and is >>>>>>> expected. I?m glad there is a way to target specific notification channels, >>>>>>> etc. >>>>>>> >>>>>>> Sending a notification via the Node Sender client however appears >>>>>>> to be sending to everyone?s installation regardless of the categories sent >>>>>>> with the message. Here?s a pastie of what my node client call looks like: >>>>>>> http://pastie.org/10282358 >>>>>>> >>>>>>> I?m using: >>>>>>> Unifiedpush Node Sender version 0.8.0-beta1 >>>>>>> >>>>>>> UPS is the setup via the openshift cartridge, from >>>>>>> https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push >>>>>>> >>>>>>> >>>>>>> Any pointers would be greatly appreciated. Very well could be me >>>>>>> doing it wrong? ;-) >>>>>>> >>>>>>> Thanks, >>>>>>> Miles >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>> >> >> >> _______________________________________________ >> 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/20150714/12f9013e/attachment.html From matzew at apache.org Tue Jul 14 11:25:38 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Jul 2015 17:25:38 +0200 Subject: [aerogear-dev] AeroGear Android 3.0 - Roadmap In-Reply-To: References: Message-ID: This looks like a lot of items for a 3.0.0 - this feels more like a roadmap for a 3.x. Why not break it down ? E.g. given the fact that for push, it would be nice to have GCM_3 in early, so, that could be released w/o "waiting" for stuff like offline, or store related work -Matthias On Tue, Jul 14, 2015 at 5:17 PM, Summers Pittman wrote: > > > On Tue, Jul 14, 2015 at 10:08 AM, Daniel Passos > wrote: > >> Hey Guys, >> >> As you know Summers and I started work on AGDroid 3.0. Today we revisited >> what we want to this release. I hope you enjoy it >> GOALS >> >> - Remove Java 6 support >> - Move to $LATEST android-maven-plugin >> - GCM 3.0 + Push Tasks >> - Extra convenience tooling >> - Memeolist demo app >> - Update docs >> - oAuth2 improvements >> - Experimental Offline Module >> - Experimental Yubikey Neo support >> >> Aerogear Android Push >> >> - GCM 3.0 >> - Instance ID >> - This is a new lifecycle for keeping the registration ID in >> sync >> - Using new services and broadcast receivers or providing >> equavalent support >> - XMPP >> - Using XMPP messaging for receiving messages and sending >> analytics updates >> - May be basis for more robust client side diagnostics and/or >> eventual messaging APIs >> >> AeroGear Android plugin (new) >> >> - Previously we shot this idea down because it adds work on developer >> which isn?t standard >> - Google is moving to including more plugins in Gradle so that isn?t >> a concern >> - Goals >> - Linting push and authz >> - Confirm services in manifest >> - Confirm appropriate licecycle on Message Listeners >> - Annotation Processing >> - Automate boring lifecycle tasks around Push >> (attaching/detaching listeners from activity) >> - Manifest processing >> - Inject Required services for push and authz if libraries are >> present >> - Automatically configure these services with values from >> keycloak.json and push-service.json >> >> AeroGear Android Cookbook >> >> - Memeolist Demo App >> - Show off Material design skills >> - Show off integration with other Red Hat/JBoss technologies >> - Increase profile of AeroGear inside of Red Hat >> - Dogfooding >> >> AeroGear Android Pipe >> >> - Logging support >> - Easier injection of HTTPProviders >> - Document adding custom headers under pipe >> >> AeroGear Android Store >> >> - Decide between >> - Async operation >> - Content Provider >> - With the plugin we could also engage in automatic contract >> object generation >> - For an example of what I am thinking see Contracts >> >> and ContentProvider >> >> >> AeroGear Android Offline >> >> - Cache : Configurable storage mechanism >> - Location : Where the CaceItem will be stored >> - Memory : in Memory store. >> - OnDevice : the internal permanent storage of the device >> - Media : removable media based storage. SD Cards, USB Sticks, >> etc >> - Eviction Policy : How long CacheItems can stay around >> - Permanent : Cache items must be removed manually >> - LRU : When the cache is full the least recently accessed will >> be removed >> - Fifo : The oldest object in the cache will be removed. >> - Size : The max number of items a cache may hold. >> - Age : The max age of any item >> >> AeroGear Android Authz >> >> - Revisit oAuth2 opened jiras >> >> AeroGear Android Security >> >> - Experimental Yubikey Neo >> >> support >> >> PS: Jiras are comming soon >> > PPS Feel free to yell at us with thoughts, ideas, comments, etc. > >> ? >> -- >> -- 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 > -- 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/20150714/3da8c899/attachment-0001.html From matzew at apache.org Tue Jul 14 11:27:14 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Jul 2015 17:27:14 +0200 Subject: [aerogear-dev] AeroGear Android 3.0 - Roadmap In-Reply-To: References: Message-ID: On Tue, Jul 14, 2015 at 4:08 PM, Daniel Passos wrote: > Hey Guys, > > As you know Summers and I started work on AGDroid 3.0. Today we revisited > what we want to this release. I hope you enjoy it > GOALS > > - Remove Java 6 support > - Move to $LATEST android-maven-plugin > - GCM 3.0 + Push Tasks > - Extra convenience tooling > - Memeolist demo app > - Update docs > - oAuth2 improvements > - Experimental Offline Module > - Experimental Yubikey Neo support > > Aerogear Android Push > > - GCM 3.0 > - Instance ID > - This is a new lifecycle for keeping the registration ID in sync > - Using new services and broadcast receivers or providing > equavalent support > > What about Topics ? I'd like to see our SDK mapping the categories to GCM topics > > - XMPP > - Using XMPP messaging for receiving messages and sending analytics > updates > > for sending analytic updates? To the UPS? I would not think that the push server needs (for analytics) to expose XMPP > > - > - May be basis for more robust client side diagnostics and/or > eventual messaging APIs > > > > - > > AeroGear Android plugin (new) > > - Previously we shot this idea down because it adds work on developer > which isn?t standard > - Google is moving to including more plugins in Gradle so that isn?t a > concern > - Goals > - Linting push and authz > - Confirm services in manifest > - Confirm appropriate licecycle on Message Listeners > - Annotation Processing > - Automate boring lifecycle tasks around Push > (attaching/detaching listeners from activity) > - Manifest processing > - Inject Required services for push and authz if libraries are > present > - Automatically configure these services with values from > keycloak.json and push-service.json > > AeroGear Android Cookbook > > - Memeolist Demo App > - Show off Material design skills > - Show off integration with other Red Hat/JBoss technologies > - Increase profile of AeroGear inside of Red Hat > - Dogfooding > > AeroGear Android Pipe > > - Logging support > - Easier injection of HTTPProviders > - Document adding custom headers under pipe > > AeroGear Android Store > > - Decide between > - Async operation > - Content Provider > - With the plugin we could also engage in automatic contract > object generation > - For an example of what I am thinking see Contracts > > and ContentProvider > > > AeroGear Android Offline > > - Cache : Configurable storage mechanism > - Location : Where the CaceItem will be stored > - Memory : in Memory store. > - OnDevice : the internal permanent storage of the device > - Media : removable media based storage. SD Cards, USB Sticks, > etc > - Eviction Policy : How long CacheItems can stay around > - Permanent : Cache items must be removed manually > - LRU : When the cache is full the least recently accessed will > be removed > - Fifo : The oldest object in the cache will be removed. > - Size : The max number of items a cache may hold. > - Age : The max age of any item > > AeroGear Android Authz > > - Revisit oAuth2 opened jiras > > AeroGear Android Security > > - Experimental Yubikey Neo > support > > PS: Jiras are comming soon > ? > -- > -- Passos > > _______________________________________________ > 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/20150714/2901fb07/attachment.html From matzew at apache.org Tue Jul 14 11:28:36 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Jul 2015 17:28:36 +0200 Subject: [aerogear-dev] Help! (was: Re: Cordova Push - 1.0.3 release (was: Re: Push plugin for Cordova)) In-Reply-To: References: Message-ID: Nooooooo :-) Ok, than nevermind. For the new NPM registry - abstractj was kindly enough to setup a group - instead of a single person, which is now a bottleneck. Ok. so TL;DR for users interested in 1.0.4 - they would have to pin the branch/tag on their project On Tue, Jul 14, 2015 at 5:22 PM, Luke Holmquist wrote: > it looks like erik is the only owner of the plugin: > > > https://gist.github.com/lholmquist/06161cfde8c0a25c61e5 > > > i have a user in the registry, lholmquist , but i cannot add it to the > plugin using 'plugman owner add lholmquist' i think erik might need to > add me > > On Tue, Jul 14, 2015 at 11:01 AM, Matthias Wessendorf > wrote: > >> I need help :-) >> >> a few 'problems' >> >> * there is already a 1.0.3 TAG - but was not published (not a big deal - >> we will just do 1.0.4 instead) >> * I can not publish the 1.0.4 stuff - this is a real problem/blocker :-( >> >> here is my >> > plugman publish . >> >> I am getting this error: >> >> attempting to publish plugin to registry >> npm ERR! publish Failed PUT response undefined >> Error Code: undefined >> login error >> >> >> Unfortunately the current published 1.0.2 is broken and does not work..., >> another pity is the 'old' registry (where our 1.0.x stuff is located) is >> read-only by tomorrow: >> >> http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html >> >> So... we can only update it today :-) >> >> >> If one of you, that did push some plugins in the past (Erik in on >> vacation), could help out here and push the 1.0.4 TAG to the registry? It's >> highly appreciated. >> >> thanks, >> Matthias >> >> >> >> On Tue, Jul 14, 2015 at 2:30 PM, Matthias Wessendorf >> wrote: >> >>> Hi, >>> >>> now that we merged the PR from Martin, and the given fact that the old >>> plugin registry is read-only, starting tomorrow, I'd like to push a release >>> of the 1.0.3 version, using this branch: >>> >>> https://github.com/aerogear/aerogear-cordova-push/tree/1.0.x >>> >>> Any thoughts? >>> >>> On Tue, Jul 14, 2015 at 1:35 PM, Martin Murphy >>> wrote: >>> >>>> >>>> On 14 Jul 2015, at 12:16, Matthias Wessendorf >>>> wrote: >>>> >>>> >>>> >>>> On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy >>>> wrote: >>>> >>>>> Hi Matthias, >>>>> That would do, however I was think more of this way: >>>>> >>>>> https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477 >>>>> to avoid the risk of pointing at a changing repo. >>>>> >>>> >>>> sounds good! >>>> >>>> >>>>> >>>>> Can use the one you mentioned, or a combination of them? >>>>> >>>>> I can certainly do the PR. >>>>> >>>> >>>> that would be awesome >>>> >>>> >>>> Is this sufficient? >>>> https://github.com/aerogear/aerogear-cordova-push/pull/74 >>>> >>>> >>>> >>>>> >>>>> >>>>> Best Regards, >>>>> Martin Murphy. >>>>> >>>>> >>>>> On 14 Jul 2015, at 11:59, Matthias Wessendorf >>>>> wrote: >>>>> >>>>> Hi Martin, >>>>> >>>>> so - it's basically porting this commit over to the 1.0x branch: >>>>> >>>>> https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 >>>>> >>>>> right ? >>>>> >>>>> Mind sending a PR ? >>>>> >>>>> On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy >>>>> wrote: >>>>> >>>>>> Hi folks, >>>>>> we have a Cordova application that?s using Codrova 3.3. >>>>>> The application uses org.jboss.aerogear.cordova.push 1.0.2 >>>>>> >>>>>> When preparing for an android build, there seems to be an problem >>>>>> installing one of the dependencies of the aurora plugin >>>>>> An id has been updated: com.vladstirbu.cordova.promise, now has a >>>>>> different id: es6-promise-plugin. >>>>>> >>>>>> The newer plugin 2.0.2 is in the npm registry. >>>>>> >>>>>> Is it possible to add a fix and deploy to the old cordova registry so >>>>>> that it?s usable in 3.x >>>>>> Is the newer plugin 2.0.2 backward compatible with 1.0.2 >>>>>> >>>>>> I understand that the ideal approach would be to use a more >>>>>> up-to-date version of Cordova, and use the latest aurora plugin, however it >>>>>> will take some time before I will be able to do that. >>>>>> I?m open to other suggestions also. >>>>>> >>>>>> Best Regards, >>>>>> Martin Murphy. >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 > -- 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/20150714/736f3b36/attachment-0001.html From supittma at redhat.com Tue Jul 14 11:36:00 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 14 Jul 2015 11:36:00 -0400 Subject: [aerogear-dev] AeroGear Android 3.0 - Roadmap In-Reply-To: References: Message-ID: On Tue, Jul 14, 2015 at 11:27 AM, Matthias Wessendorf wrote: > > > On Tue, Jul 14, 2015 at 4:08 PM, Daniel Passos wrote: > >> Hey Guys, >> >> As you know Summers and I started work on AGDroid 3.0. Today we revisited >> what we want to this release. I hope you enjoy it >> GOALS >> >> - Remove Java 6 support >> - Move to $LATEST android-maven-plugin >> - GCM 3.0 + Push Tasks >> - Extra convenience tooling >> - Memeolist demo app >> - Update docs >> - oAuth2 improvements >> - Experimental Offline Module >> - Experimental Yubikey Neo support >> >> Aerogear Android Push >> >> - GCM 3.0 >> - Instance ID >> - This is a new lifecycle for keeping the registration ID in >> sync >> - Using new services and broadcast receivers or providing >> equavalent support >> >> > What about Topics ? I'd like to see our SDK mapping the categories to GCM > topics > Oh right, those got left off this email but are scheduled in JIRA. https://issues.jboss.org/browse/AGDROID-470 > > >> >> - XMPP >> - Using XMPP messaging for receiving messages and sending >> analytics updates >> >> for sending analytic updates? To the UPS? I would not think that the push > server needs (for analytics) to expose XMPP > Expose no. It just needs to connect to Google's XMPP messaging services. See : https://issues.jboss.org/browse/AGPUSH-36 and : https://issues.jboss.org/browse/AGDROID-472 we had an old demo implementation with the sync-server. I can dig up those old bits of code if you would like. > > >> >> - >> - May be basis for more robust client side diagnostics and/or >> eventual messaging APIs >> >> > > > >> >> - >> >> AeroGear Android plugin (new) >> >> - Previously we shot this idea down because it adds work on developer >> which isn?t standard >> - Google is moving to including more plugins in Gradle so that isn?t >> a concern >> - Goals >> - Linting push and authz >> - Confirm services in manifest >> - Confirm appropriate licecycle on Message Listeners >> - Annotation Processing >> - Automate boring lifecycle tasks around Push >> (attaching/detaching listeners from activity) >> - Manifest processing >> - Inject Required services for push and authz if libraries are >> present >> - Automatically configure these services with values from >> keycloak.json and push-service.json >> >> AeroGear Android Cookbook >> >> - Memeolist Demo App >> - Show off Material design skills >> - Show off integration with other Red Hat/JBoss technologies >> - Increase profile of AeroGear inside of Red Hat >> - Dogfooding >> >> AeroGear Android Pipe >> >> - Logging support >> - Easier injection of HTTPProviders >> - Document adding custom headers under pipe >> >> AeroGear Android Store >> >> - Decide between >> - Async operation >> - Content Provider >> - With the plugin we could also engage in automatic contract >> object generation >> - For an example of what I am thinking see Contracts >> >> and ContentProvider >> >> >> AeroGear Android Offline >> >> - Cache : Configurable storage mechanism >> - Location : Where the CaceItem will be stored >> - Memory : in Memory store. >> - OnDevice : the internal permanent storage of the device >> - Media : removable media based storage. SD Cards, USB Sticks, >> etc >> - Eviction Policy : How long CacheItems can stay around >> - Permanent : Cache items must be removed manually >> - LRU : When the cache is full the least recently accessed will >> be removed >> - Fifo : The oldest object in the cache will be removed. >> - Size : The max number of items a cache may hold. >> - Age : The max age of any item >> >> AeroGear Android Authz >> >> - Revisit oAuth2 opened jiras >> >> AeroGear Android Security >> >> - Experimental Yubikey Neo >> >> support >> >> PS: Jiras are comming soon >> ? >> -- >> -- Passos >> >> _______________________________________________ >> 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/20150714/76712c4f/attachment.html From supittma at redhat.com Tue Jul 14 11:37:46 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 14 Jul 2015 11:37:46 -0400 Subject: [aerogear-dev] AeroGear Android 3.0 - Roadmap In-Reply-To: References: Message-ID: On Tue, Jul 14, 2015 at 11:25 AM, Matthias Wessendorf wrote: > This looks like a lot of items for a 3.0.0 - this feels more like a > roadmap for a 3.x. > > Why not break it down ? E.g. given the fact that for push, it would be > nice to have GCM_3 in early, so, that could be released w/o "waiting" for > stuff like offline, or store related work > Keep in mind that AGDroid is not a monolithic project any more. There is no reason that -push 3.0.0 and -store 3.0.0 have to be released at the same time (other than dependency mgmt). But yes this is very ambitious. > > -Matthias > > > On Tue, Jul 14, 2015 at 5:17 PM, Summers Pittman > wrote: > >> >> >> On Tue, Jul 14, 2015 at 10:08 AM, Daniel Passos >> wrote: >> >>> Hey Guys, >>> >>> As you know Summers and I started work on AGDroid 3.0. Today we >>> revisited what we want to this release. I hope you enjoy it >>> GOALS >>> >>> - Remove Java 6 support >>> - Move to $LATEST android-maven-plugin >>> - GCM 3.0 + Push Tasks >>> - Extra convenience tooling >>> - Memeolist demo app >>> - Update docs >>> - oAuth2 improvements >>> - Experimental Offline Module >>> - Experimental Yubikey Neo support >>> >>> Aerogear Android Push >>> >>> - GCM 3.0 >>> - Instance ID >>> - This is a new lifecycle for keeping the registration ID in >>> sync >>> - Using new services and broadcast receivers or providing >>> equavalent support >>> - XMPP >>> - Using XMPP messaging for receiving messages and sending >>> analytics updates >>> - May be basis for more robust client side diagnostics and/or >>> eventual messaging APIs >>> >>> AeroGear Android plugin (new) >>> >>> - Previously we shot this idea down because it adds work on >>> developer which isn?t standard >>> - Google is moving to including more plugins in Gradle so that isn?t >>> a concern >>> - Goals >>> - Linting push and authz >>> - Confirm services in manifest >>> - Confirm appropriate licecycle on Message Listeners >>> - Annotation Processing >>> - Automate boring lifecycle tasks around Push >>> (attaching/detaching listeners from activity) >>> - Manifest processing >>> - Inject Required services for push and authz if libraries are >>> present >>> - Automatically configure these services with values from >>> keycloak.json and push-service.json >>> >>> AeroGear Android Cookbook >>> >>> - Memeolist Demo App >>> - Show off Material design skills >>> - Show off integration with other Red Hat/JBoss technologies >>> - Increase profile of AeroGear inside of Red Hat >>> - Dogfooding >>> >>> AeroGear Android Pipe >>> >>> - Logging support >>> - Easier injection of HTTPProviders >>> - Document adding custom headers under pipe >>> >>> AeroGear Android Store >>> >>> - Decide between >>> - Async operation >>> - Content Provider >>> - With the plugin we could also engage in automatic contract >>> object generation >>> - For an example of what I am thinking see Contracts >>> >>> and ContentProvider >>> >>> >>> AeroGear Android Offline >>> >>> - Cache : Configurable storage mechanism >>> - Location : Where the CaceItem will be stored >>> - Memory : in Memory store. >>> - OnDevice : the internal permanent storage of the device >>> - Media : removable media based storage. SD Cards, USB Sticks, >>> etc >>> - Eviction Policy : How long CacheItems can stay around >>> - Permanent : Cache items must be removed manually >>> - LRU : When the cache is full the least recently accessed >>> will be removed >>> - Fifo : The oldest object in the cache will be removed. >>> - Size : The max number of items a cache may hold. >>> - Age : The max age of any item >>> >>> AeroGear Android Authz >>> >>> - Revisit oAuth2 opened jiras >>> >>> AeroGear Android Security >>> >>> - Experimental Yubikey Neo >>> >>> support >>> >>> PS: Jiras are comming soon >>> >> PPS Feel free to yell at us with thoughts, ideas, comments, etc. >> >>> ? >>> -- >>> -- 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 >> > > > > -- > 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/20150714/5444275c/attachment-0001.html From roos at symentis.com Tue Jul 14 12:25:38 2015 From: roos at symentis.com (Robert Oschwald) Date: Tue, 14 Jul 2015 18:25:38 +0200 Subject: [aerogear-dev] aerogear-ios-push Carthage support Message-ID: <7871F45C-CAEC-472C-B4C1-184B14DC9AE7@symentis.com> is it planned to add Carthage support to the library? We moved away from Cocoapods since a while and love Carthage for beeing non-intrusive. Thanks, Robert From matzew at apache.org Tue Jul 14 13:17:32 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Jul 2015 19:17:32 +0200 Subject: [aerogear-dev] AeroGear Android 3.0 - Roadmap In-Reply-To: References: Message-ID: On Tue, Jul 14, 2015 at 5:36 PM, Summers Pittman wrote: > > > On Tue, Jul 14, 2015 at 11:27 AM, Matthias Wessendorf > wrote: > >> >> >> On Tue, Jul 14, 2015 at 4:08 PM, Daniel Passos >> wrote: >> >>> Hey Guys, >>> >>> As you know Summers and I started work on AGDroid 3.0. Today we >>> revisited what we want to this release. I hope you enjoy it >>> GOALS >>> >>> - Remove Java 6 support >>> - Move to $LATEST android-maven-plugin >>> - GCM 3.0 + Push Tasks >>> - Extra convenience tooling >>> - Memeolist demo app >>> - Update docs >>> - oAuth2 improvements >>> - Experimental Offline Module >>> - Experimental Yubikey Neo support >>> >>> Aerogear Android Push >>> >>> - GCM 3.0 >>> - Instance ID >>> - This is a new lifecycle for keeping the registration ID in >>> sync >>> - Using new services and broadcast receivers or providing >>> equavalent support >>> >>> >> What about Topics ? I'd like to see our SDK mapping the categories to GCM >> topics >> > Oh right, those got left off this email but are scheduled in JIRA. > https://issues.jboss.org/browse/AGDROID-470 > >> >> >>> >>> - XMPP >>> - Using XMPP messaging for receiving messages and sending >>> analytics updates >>> >>> for sending analytic updates? To the UPS? I would not think that the >> push server needs (for analytics) to expose XMPP >> > Expose no. It just needs to connect to Google's XMPP messaging services. > > See : https://issues.jboss.org/browse/AGPUSH-36 > and : https://issues.jboss.org/browse/AGDROID-472 > > ok - I was just wondering since it said _and_ :-) we had an old demo implementation with the sync-server. I can dig up those old bits of code if you would like. nah - we can revisit that once needed > > >> >> - >> - May be basis for more robust client side diagnostics and/or >> eventual messaging APIs >> >> > > > >> >> - >> >> AeroGear Android plugin (new) >> >> - Previously we shot this idea down because it adds work on developer >> which isn?t standard >> - Google is moving to including more plugins in Gradle so that isn?t >> a concern >> - Goals >> - Linting push and authz >> - Confirm services in manifest >> - Confirm appropriate licecycle on Message Listeners >> - Annotation Processing >> - Automate boring lifecycle tasks around Push >> (attaching/detaching listeners from activity) >> - Manifest processing >> - Inject Required services for push and authz if libraries are >> present >> - Automatically configure these services with values from >> keycloak.json and push-service.json >> >> AeroGear Android Cookbook >> >> - Memeolist Demo App >> - Show off Material design skills >> - Show off integration with other Red Hat/JBoss technologies >> - Increase profile of AeroGear inside of Red Hat >> - Dogfooding >> >> AeroGear Android Pipe >> >> - Logging support >> - Easier injection of HTTPProviders >> - Document adding custom headers under pipe >> >> AeroGear Android Store >> >> - Decide between >> - Async operation >> - Content Provider >> - With the plugin we could also engage in automatic contract >> object generation >> - For an example of what I am thinking see Contracts >> >> and ContentProvider >> >> >> AeroGear Android Offline >> >> - Cache : Configurable storage mechanism >> - Location : Where the CaceItem will be stored >> - Memory : in Memory store. >> - OnDevice : the internal permanent storage of the device >> - Media : removable media based storage. SD Cards, USB Sticks, >> etc >> - Eviction Policy : How long CacheItems can stay around >> - Permanent : Cache items must be removed manually >> - LRU : When the cache is full the least recently accessed will >> be removed >> - Fifo : The oldest object in the cache will be removed. >> - Size : The max number of items a cache may hold. >> - Age : The max age of any item >> >> AeroGear Android Authz >> >> - Revisit oAuth2 opened jiras >> >> AeroGear Android Security >> >> - Experimental Yubikey Neo >> >> support >> >> PS: Jiras are comming soon >> ? >> -- >> -- Passos >> >> _______________________________________________ >> 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/20150714/4ef89159/attachment-0001.html From matzew at apache.org Tue Jul 14 13:18:55 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Jul 2015 19:18:55 +0200 Subject: [aerogear-dev] AeroGear Android 3.0 - Roadmap In-Reply-To: References: Message-ID: On Tue, Jul 14, 2015 at 5:37 PM, Summers Pittman wrote: > > > On Tue, Jul 14, 2015 at 11:25 AM, Matthias Wessendorf > wrote: > >> This looks like a lot of items for a 3.0.0 - this feels more like a >> roadmap for a 3.x. >> >> Why not break it down ? E.g. given the fact that for push, it would be >> nice to have GCM_3 in early, so, that could be released w/o "waiting" for >> stuff like offline, or store related work >> > Keep in mind that AGDroid is not a monolithic project any more. There is > no reason that -push 3.0.0 and -store 3.0.0 have to be released at the same > time (other than dependency mgmt). > true, and getting -push-3.0.0 (and -core-3.0.0 + -pipe-3.0.0) out, does also not mean a few weeks later there is just a 3.1.0 that for instance contains the above discussed PIPE changes/features -M > But yes this is very ambitious. > >> >> -Matthias >> >> >> On Tue, Jul 14, 2015 at 5:17 PM, Summers Pittman >> wrote: >> >>> >>> >>> On Tue, Jul 14, 2015 at 10:08 AM, Daniel Passos >>> wrote: >>> >>>> Hey Guys, >>>> >>>> As you know Summers and I started work on AGDroid 3.0. Today we >>>> revisited what we want to this release. I hope you enjoy it >>>> GOALS >>>> >>>> - Remove Java 6 support >>>> - Move to $LATEST android-maven-plugin >>>> - GCM 3.0 + Push Tasks >>>> - Extra convenience tooling >>>> - Memeolist demo app >>>> - Update docs >>>> - oAuth2 improvements >>>> - Experimental Offline Module >>>> - Experimental Yubikey Neo support >>>> >>>> Aerogear Android Push >>>> >>>> - GCM 3.0 >>>> - Instance ID >>>> - This is a new lifecycle for keeping the registration ID in >>>> sync >>>> - Using new services and broadcast receivers or providing >>>> equavalent support >>>> - XMPP >>>> - Using XMPP messaging for receiving messages and sending >>>> analytics updates >>>> - May be basis for more robust client side diagnostics and/or >>>> eventual messaging APIs >>>> >>>> AeroGear Android plugin (new) >>>> >>>> - Previously we shot this idea down because it adds work on >>>> developer which isn?t standard >>>> - Google is moving to including more plugins in Gradle so that >>>> isn?t a concern >>>> - Goals >>>> - Linting push and authz >>>> - Confirm services in manifest >>>> - Confirm appropriate licecycle on Message Listeners >>>> - Annotation Processing >>>> - Automate boring lifecycle tasks around Push >>>> (attaching/detaching listeners from activity) >>>> - Manifest processing >>>> - Inject Required services for push and authz if libraries >>>> are present >>>> - Automatically configure these services with values from >>>> keycloak.json and push-service.json >>>> >>>> AeroGear Android Cookbook >>>> >>>> - Memeolist Demo App >>>> - Show off Material design skills >>>> - Show off integration with other Red Hat/JBoss technologies >>>> - Increase profile of AeroGear inside of Red Hat >>>> - Dogfooding >>>> >>>> AeroGear Android Pipe >>>> >>>> - Logging support >>>> - Easier injection of HTTPProviders >>>> - Document adding custom headers under pipe >>>> >>>> AeroGear Android Store >>>> >>>> - Decide between >>>> - Async operation >>>> - Content Provider >>>> - With the plugin we could also engage in automatic contract >>>> object generation >>>> - For an example of what I am thinking see Contracts >>>> >>>> and ContentProvider >>>> >>>> >>>> AeroGear Android Offline >>>> >>>> - Cache : Configurable storage mechanism >>>> - Location : Where the CaceItem will be stored >>>> - Memory : in Memory store. >>>> - OnDevice : the internal permanent storage of the device >>>> - Media : removable media based storage. SD Cards, USB >>>> Sticks, etc >>>> - Eviction Policy : How long CacheItems can stay around >>>> - Permanent : Cache items must be removed manually >>>> - LRU : When the cache is full the least recently accessed >>>> will be removed >>>> - Fifo : The oldest object in the cache will be removed. >>>> - Size : The max number of items a cache may hold. >>>> - Age : The max age of any item >>>> >>>> AeroGear Android Authz >>>> >>>> - Revisit oAuth2 opened jiras >>>> >>>> AeroGear Android Security >>>> >>>> - Experimental Yubikey Neo >>>> >>>> support >>>> >>>> PS: Jiras are comming soon >>>> >>> PPS Feel free to yell at us with thoughts, ideas, comments, etc. >>> >>>> ? >>>> -- >>>> -- 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 >>> >> >> >> >> -- >> 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/20150714/e311e291/attachment.html From supittma at redhat.com Tue Jul 14 13:38:52 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 14 Jul 2015 13:38:52 -0400 Subject: [aerogear-dev] AeroGear Android 3.0 - Roadmap In-Reply-To: References: Message-ID: On Tue, Jul 14, 2015 at 1:18 PM, Matthias Wessendorf wrote: > > > On Tue, Jul 14, 2015 at 5:37 PM, Summers Pittman > wrote: > >> >> >> On Tue, Jul 14, 2015 at 11:25 AM, Matthias Wessendorf >> wrote: >> >>> This looks like a lot of items for a 3.0.0 - this feels more like a >>> roadmap for a 3.x. >>> >>> Why not break it down ? E.g. given the fact that for push, it would be >>> nice to have GCM_3 in early, so, that could be released w/o "waiting" for >>> stuff like offline, or store related work >>> >> Keep in mind that AGDroid is not a monolithic project any more. There is >> no reason that -push 3.0.0 and -store 3.0.0 have to be released at the same >> time (other than dependency mgmt). >> > > true, and getting -push-3.0.0 (and -core-3.0.0 + -pipe-3.0.0) out, does > also not mean a few weeks later there is just a 3.1.0 that for instance > contains the above discussed PIPE changes/features > True. So with dropping JDK 6[Done], moving to JUnit 4[Done], updating to android-maven-plugin 4.3.0[Done], the GCM updates [in progress], doc updates [JIRA'd] and probably a couple of small fixes here and there (pipe and store bugs that should be easy to accomplish) we have enough to put into a 3.0.0 by September's UPS 1.2.0. I guess what I am saying is I do agree there is no reason this can't been seen as a 3.x roadmap as well. > > -M > > >> But yes this is very ambitious. >> >>> >>> -Matthias >>> >>> >>> On Tue, Jul 14, 2015 at 5:17 PM, Summers Pittman >>> wrote: >>> >>>> >>>> >>>> On Tue, Jul 14, 2015 at 10:08 AM, Daniel Passos >>>> wrote: >>>> >>>>> Hey Guys, >>>>> >>>>> As you know Summers and I started work on AGDroid 3.0. Today we >>>>> revisited what we want to this release. I hope you enjoy it >>>>> GOALS >>>>> >>>>> - Remove Java 6 support >>>>> - Move to $LATEST android-maven-plugin >>>>> - GCM 3.0 + Push Tasks >>>>> - Extra convenience tooling >>>>> - Memeolist demo app >>>>> - Update docs >>>>> - oAuth2 improvements >>>>> - Experimental Offline Module >>>>> - Experimental Yubikey Neo support >>>>> >>>>> Aerogear Android Push >>>>> >>>>> - GCM 3.0 >>>>> - Instance ID >>>>> - This is a new lifecycle for keeping the registration ID in >>>>> sync >>>>> - Using new services and broadcast receivers or providing >>>>> equavalent support >>>>> - XMPP >>>>> - Using XMPP messaging for receiving messages and sending >>>>> analytics updates >>>>> - May be basis for more robust client side diagnostics and/or >>>>> eventual messaging APIs >>>>> >>>>> AeroGear Android plugin (new) >>>>> >>>>> - Previously we shot this idea down because it adds work on >>>>> developer which isn?t standard >>>>> - Google is moving to including more plugins in Gradle so that >>>>> isn?t a concern >>>>> - Goals >>>>> - Linting push and authz >>>>> - Confirm services in manifest >>>>> - Confirm appropriate licecycle on Message Listeners >>>>> - Annotation Processing >>>>> - Automate boring lifecycle tasks around Push >>>>> (attaching/detaching listeners from activity) >>>>> - Manifest processing >>>>> - Inject Required services for push and authz if libraries >>>>> are present >>>>> - Automatically configure these services with values from >>>>> keycloak.json and push-service.json >>>>> >>>>> AeroGear Android Cookbook >>>>> >>>>> - Memeolist Demo App >>>>> - Show off Material design skills >>>>> - Show off integration with other Red Hat/JBoss technologies >>>>> - Increase profile of AeroGear inside of Red Hat >>>>> - Dogfooding >>>>> >>>>> AeroGear Android Pipe >>>>> >>>>> - Logging support >>>>> - Easier injection of HTTPProviders >>>>> - Document adding custom headers under pipe >>>>> >>>>> AeroGear Android Store >>>>> >>>>> - Decide between >>>>> - Async operation >>>>> - Content Provider >>>>> - With the plugin we could also engage in automatic contract >>>>> object generation >>>>> - For an example of what I am thinking see Contracts >>>>> >>>>> and ContentProvider >>>>> >>>>> >>>>> AeroGear Android Offline >>>>> >>>>> - Cache : Configurable storage mechanism >>>>> - Location : Where the CaceItem will be stored >>>>> - Memory : in Memory store. >>>>> - OnDevice : the internal permanent storage of the device >>>>> - Media : removable media based storage. SD Cards, USB >>>>> Sticks, etc >>>>> - Eviction Policy : How long CacheItems can stay around >>>>> - Permanent : Cache items must be removed manually >>>>> - LRU : When the cache is full the least recently accessed >>>>> will be removed >>>>> - Fifo : The oldest object in the cache will be removed. >>>>> - Size : The max number of items a cache may hold. >>>>> - Age : The max age of any item >>>>> >>>>> AeroGear Android Authz >>>>> >>>>> - Revisit oAuth2 opened jiras >>>>> >>>>> AeroGear Android Security >>>>> >>>>> - Experimental Yubikey Neo >>>>> >>>>> support >>>>> >>>>> PS: Jiras are comming soon >>>>> >>>> PPS Feel free to yell at us with thoughts, ideas, comments, etc. >>>> >>>>> ? >>>>> -- >>>>> -- 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 >>>> >>> >>> >>> >>> -- >>> 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/20150714/715877a2/attachment-0001.html From matzew at apache.org Tue Jul 14 13:50:04 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Jul 2015 19:50:04 +0200 Subject: [aerogear-dev] AeroGear Android 3.0 - Roadmap In-Reply-To: References: Message-ID: On Tue, Jul 14, 2015 at 7:38 PM, Summers Pittman wrote: > > > On Tue, Jul 14, 2015 at 1:18 PM, Matthias Wessendorf > wrote: > >> >> >> On Tue, Jul 14, 2015 at 5:37 PM, Summers Pittman >> wrote: >> >>> >>> >>> On Tue, Jul 14, 2015 at 11:25 AM, Matthias Wessendorf >> > wrote: >>> >>>> This looks like a lot of items for a 3.0.0 - this feels more like a >>>> roadmap for a 3.x. >>>> >>>> Why not break it down ? E.g. given the fact that for push, it would be >>>> nice to have GCM_3 in early, so, that could be released w/o "waiting" for >>>> stuff like offline, or store related work >>>> >>> Keep in mind that AGDroid is not a monolithic project any more. There >>> is no reason that -push 3.0.0 and -store 3.0.0 have to be released at the >>> same time (other than dependency mgmt). >>> >> >> true, and getting -push-3.0.0 (and -core-3.0.0 + -pipe-3.0.0) out, does >> also not mean a few weeks later there is just a 3.1.0 that for instance >> contains the above discussed PIPE changes/features >> > > True. > > So with dropping JDK 6[Done], moving to JUnit 4[Done], updating to > android-maven-plugin 4.3.0[Done], the GCM updates [in progress], doc > updates [JIRA'd] and probably a couple of small fixes here and there (pipe > and store bugs that should be easy to accomplish) we have enough to put > into a 3.0.0 by September's UPS 1.2.0. > \o/ > > I guess what I am saying is I do agree there is no reason this can't been > seen as a 3.x roadmap as well. > fair point! :) Thanks for the infos > > >> >> -M >> >> >>> But yes this is very ambitious. >>> >>>> >>>> -Matthias >>>> >>>> >>>> On Tue, Jul 14, 2015 at 5:17 PM, Summers Pittman >>>> wrote: >>>> >>>>> >>>>> >>>>> On Tue, Jul 14, 2015 at 10:08 AM, Daniel Passos >>>>> wrote: >>>>> >>>>>> Hey Guys, >>>>>> >>>>>> As you know Summers and I started work on AGDroid 3.0. Today we >>>>>> revisited what we want to this release. I hope you enjoy it >>>>>> GOALS >>>>>> >>>>>> - Remove Java 6 support >>>>>> - Move to $LATEST android-maven-plugin >>>>>> - GCM 3.0 + Push Tasks >>>>>> - Extra convenience tooling >>>>>> - Memeolist demo app >>>>>> - Update docs >>>>>> - oAuth2 improvements >>>>>> - Experimental Offline Module >>>>>> - Experimental Yubikey Neo support >>>>>> >>>>>> Aerogear Android Push >>>>>> >>>>>> - GCM 3.0 >>>>>> - Instance ID >>>>>> - This is a new lifecycle for keeping the registration ID >>>>>> in sync >>>>>> - Using new services and broadcast receivers or providing >>>>>> equavalent support >>>>>> - XMPP >>>>>> - Using XMPP messaging for receiving messages and sending >>>>>> analytics updates >>>>>> - May be basis for more robust client side diagnostics and/or >>>>>> eventual messaging APIs >>>>>> >>>>>> AeroGear Android plugin (new) >>>>>> >>>>>> - Previously we shot this idea down because it adds work on >>>>>> developer which isn?t standard >>>>>> - Google is moving to including more plugins in Gradle so that >>>>>> isn?t a concern >>>>>> - Goals >>>>>> - Linting push and authz >>>>>> - Confirm services in manifest >>>>>> - Confirm appropriate licecycle on Message Listeners >>>>>> - Annotation Processing >>>>>> - Automate boring lifecycle tasks around Push >>>>>> (attaching/detaching listeners from activity) >>>>>> - Manifest processing >>>>>> - Inject Required services for push and authz if libraries >>>>>> are present >>>>>> - Automatically configure these services with values from >>>>>> keycloak.json and push-service.json >>>>>> >>>>>> AeroGear Android Cookbook >>>>>> >>>>>> - Memeolist Demo App >>>>>> - Show off Material design skills >>>>>> - Show off integration with other Red Hat/JBoss technologies >>>>>> - Increase profile of AeroGear inside of Red Hat >>>>>> - Dogfooding >>>>>> >>>>>> AeroGear Android Pipe >>>>>> >>>>>> - Logging support >>>>>> - Easier injection of HTTPProviders >>>>>> - Document adding custom headers under pipe >>>>>> >>>>>> AeroGear Android Store >>>>>> >>>>>> - Decide between >>>>>> - Async operation >>>>>> - Content Provider >>>>>> - With the plugin we could also engage in automatic >>>>>> contract object generation >>>>>> - For an example of what I am thinking see Contracts >>>>>> >>>>>> and ContentProvider >>>>>> >>>>>> >>>>>> AeroGear Android Offline >>>>>> >>>>>> - Cache : Configurable storage mechanism >>>>>> - Location : Where the CaceItem will be stored >>>>>> - Memory : in Memory store. >>>>>> - OnDevice : the internal permanent storage of the device >>>>>> - Media : removable media based storage. SD Cards, USB >>>>>> Sticks, etc >>>>>> - Eviction Policy : How long CacheItems can stay around >>>>>> - Permanent : Cache items must be removed manually >>>>>> - LRU : When the cache is full the least recently accessed >>>>>> will be removed >>>>>> - Fifo : The oldest object in the cache will be removed. >>>>>> - Size : The max number of items a cache may hold. >>>>>> - Age : The max age of any item >>>>>> >>>>>> AeroGear Android Authz >>>>>> >>>>>> - Revisit oAuth2 opened jiras >>>>>> >>>>>> AeroGear Android Security >>>>>> >>>>>> - Experimental Yubikey Neo >>>>>> >>>>>> support >>>>>> >>>>>> PS: Jiras are comming soon >>>>>> >>>>> PPS Feel free to yell at us with thoughts, ideas, comments, etc. >>>>> >>>>>> ? >>>>>> -- >>>>>> -- 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> 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 >> > > > _______________________________________________ > 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/20150714/cce53699/attachment-0001.html From lholmqui at redhat.com Tue Jul 14 15:38:19 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Tue, 14 Jul 2015 15:38:19 -0400 Subject: [aerogear-dev] Help! (was: Re: Cordova Push - 1.0.3 release (was: Re: Push plugin for Cordova)) In-Reply-To: References: Message-ID: On Tue, Jul 14, 2015 at 11:28 AM, Matthias Wessendorf wrote: > Nooooooo :-) > > Ok, than nevermind. > > For the new NPM registry - abstractj was kindly enough to setup a group - > instead of a single person, which is now a bottleneck. > > Ok. so TL;DR for users interested in 1.0.4 - they would have to pin the > branch/tag on their project > So i think is probably a sane root, > > > > On Tue, Jul 14, 2015 at 5:22 PM, Luke Holmquist > wrote: > >> it looks like erik is the only owner of the plugin: >> >> >> https://gist.github.com/lholmquist/06161cfde8c0a25c61e5 >> >> >> i have a user in the registry, lholmquist , but i cannot add it to the >> plugin using 'plugman owner add lholmquist' i think erik might need to >> add me >> >> On Tue, Jul 14, 2015 at 11:01 AM, Matthias Wessendorf >> wrote: >> >>> I need help :-) >>> >>> a few 'problems' >>> >>> * there is already a 1.0.3 TAG - but was not published (not a big deal - >>> we will just do 1.0.4 instead) >>> * I can not publish the 1.0.4 stuff - this is a real problem/blocker :-( >>> >>> here is my >>> > plugman publish . >>> >>> I am getting this error: >>> >>> attempting to publish plugin to registry >>> npm ERR! publish Failed PUT response undefined >>> Error Code: undefined >>> login error >>> >>> >>> Unfortunately the current published 1.0.2 is broken and does not >>> work..., another pity is the 'old' registry (where our 1.0.x stuff is >>> located) is read-only by tomorrow: >>> >>> http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html >>> >>> So... we can only update it today :-) >>> >>> >>> If one of you, that did push some plugins in the past (Erik in on >>> vacation), could help out here and push the 1.0.4 TAG to the registry? It's >>> highly appreciated. >>> >>> thanks, >>> Matthias >>> >>> >>> >>> On Tue, Jul 14, 2015 at 2:30 PM, Matthias Wessendorf >>> wrote: >>> >>>> Hi, >>>> >>>> now that we merged the PR from Martin, and the given fact that the old >>>> plugin registry is read-only, starting tomorrow, I'd like to push a release >>>> of the 1.0.3 version, using this branch: >>>> >>>> https://github.com/aerogear/aerogear-cordova-push/tree/1.0.x >>>> >>>> Any thoughts? >>>> >>>> On Tue, Jul 14, 2015 at 1:35 PM, Martin Murphy >>>> wrote: >>>> >>>>> >>>>> On 14 Jul 2015, at 12:16, Matthias Wessendorf >>>>> wrote: >>>>> >>>>> >>>>> >>>>> On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy >>>>> wrote: >>>>> >>>>>> Hi Matthias, >>>>>> That would do, however I was think more of this way: >>>>>> >>>>>> https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477 >>>>>> to avoid the risk of pointing at a changing repo. >>>>>> >>>>> >>>>> sounds good! >>>>> >>>>> >>>>>> >>>>>> Can use the one you mentioned, or a combination of them? >>>>>> >>>>>> I can certainly do the PR. >>>>>> >>>>> >>>>> that would be awesome >>>>> >>>>> >>>>> Is this sufficient? >>>>> https://github.com/aerogear/aerogear-cordova-push/pull/74 >>>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>> Best Regards, >>>>>> Martin Murphy. >>>>>> >>>>>> >>>>>> On 14 Jul 2015, at 11:59, Matthias Wessendorf >>>>>> wrote: >>>>>> >>>>>> Hi Martin, >>>>>> >>>>>> so - it's basically porting this commit over to the 1.0x branch: >>>>>> >>>>>> https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 >>>>>> >>>>>> right ? >>>>>> >>>>>> Mind sending a PR ? >>>>>> >>>>>> On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy >>>>>> wrote: >>>>>> >>>>>>> Hi folks, >>>>>>> we have a Cordova application that?s using Codrova 3.3. >>>>>>> The application uses org.jboss.aerogear.cordova.push 1.0.2 >>>>>>> >>>>>>> When preparing for an android build, there seems to be an problem >>>>>>> installing one of the dependencies of the aurora plugin >>>>>>> An id has been updated: com.vladstirbu.cordova.promise, now has a >>>>>>> different id: es6-promise-plugin. >>>>>>> >>>>>>> The newer plugin 2.0.2 is in the npm registry. >>>>>>> >>>>>>> Is it possible to add a fix and deploy to the old cordova registry >>>>>>> so that it?s usable in 3.x >>>>>>> Is the newer plugin 2.0.2 backward compatible with 1.0.2 >>>>>>> >>>>>>> I understand that the ideal approach would be to use a more >>>>>>> up-to-date version of Cordova, and use the latest aurora plugin, however it >>>>>>> will take some time before I will be able to do that. >>>>>>> I?m open to other suggestions also. >>>>>>> >>>>>>> Best Regards, >>>>>>> Martin Murphy. >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >> > > > > -- > 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/20150714/eb65b44e/attachment.html From matzew at apache.org Tue Jul 14 15:59:20 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Jul 2015 21:59:20 +0200 Subject: [aerogear-dev] Help! (was: Re: Cordova Push - 1.0.3 release (was: Re: Push plugin for Cordova)) In-Reply-To: References: Message-ID: On Tuesday, July 14, 2015, Luke Holmquist wrote: > > > On Tue, Jul 14, 2015 at 11:28 AM, Matthias Wessendorf > wrote: > >> Nooooooo :-) >> >> Ok, than nevermind. >> >> For the new NPM registry - abstractj was kindly enough to setup a group - >> instead of a single person, which is now a bottleneck. >> >> Ok. so TL;DR for users interested in 1.0.4 - they would have to pin the >> branch/tag on their project >> > > So i think is probably a sane root, > word up ? > >> >> >> On Tue, Jul 14, 2015 at 5:22 PM, Luke Holmquist > > wrote: >> >>> it looks like erik is the only owner of the plugin: >>> >>> >>> https://gist.github.com/lholmquist/06161cfde8c0a25c61e5 >>> >>> >>> i have a user in the registry, lholmquist , but i cannot add it to the >>> plugin using 'plugman owner add lholmquist' i think erik might need to >>> add me >>> >>> On Tue, Jul 14, 2015 at 11:01 AM, Matthias Wessendorf >> > wrote: >>> >>>> I need help :-) >>>> >>>> a few 'problems' >>>> >>>> * there is already a 1.0.3 TAG - but was not published (not a big deal >>>> - we will just do 1.0.4 instead) >>>> * I can not publish the 1.0.4 stuff - this is a real problem/blocker :-( >>>> >>>> here is my >>>> > plugman publish . >>>> >>>> I am getting this error: >>>> >>>> attempting to publish plugin to registry >>>> npm ERR! publish Failed PUT response undefined >>>> Error Code: undefined >>>> login error >>>> >>>> >>>> Unfortunately the current published 1.0.2 is broken and does not >>>> work..., another pity is the 'old' registry (where our 1.0.x stuff is >>>> located) is read-only by tomorrow: >>>> >>>> http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html >>>> >>>> So... we can only update it today :-) >>>> >>>> >>>> If one of you, that did push some plugins in the past (Erik in on >>>> vacation), could help out here and push the 1.0.4 TAG to the registry? It's >>>> highly appreciated. >>>> >>>> thanks, >>>> Matthias >>>> >>>> >>>> >>>> On Tue, Jul 14, 2015 at 2:30 PM, Matthias Wessendorf >>> > wrote: >>>> >>>>> Hi, >>>>> >>>>> now that we merged the PR from Martin, and the given fact that the old >>>>> plugin registry is read-only, starting tomorrow, I'd like to push a release >>>>> of the 1.0.3 version, using this branch: >>>>> >>>>> https://github.com/aerogear/aerogear-cordova-push/tree/1.0.x >>>>> >>>>> Any thoughts? >>>>> >>>>> On Tue, Jul 14, 2015 at 1:35 PM, Martin Murphy >>>> > wrote: >>>>> >>>>>> >>>>>> On 14 Jul 2015, at 12:16, Matthias Wessendorf >>>>> > wrote: >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy >>>>> > wrote: >>>>>> >>>>>>> Hi Matthias, >>>>>>> That would do, however I was think more of this way: >>>>>>> >>>>>>> https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477 >>>>>>> to avoid the risk of pointing at a changing repo. >>>>>>> >>>>>> >>>>>> sounds good! >>>>>> >>>>>> >>>>>>> >>>>>>> Can use the one you mentioned, or a combination of them? >>>>>>> >>>>>>> I can certainly do the PR. >>>>>>> >>>>>> >>>>>> that would be awesome >>>>>> >>>>>> >>>>>> Is this sufficient? >>>>>> https://github.com/aerogear/aerogear-cordova-push/pull/74 >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>> Best Regards, >>>>>>> Martin Murphy. >>>>>>> >>>>>>> >>>>>>> On 14 Jul 2015, at 11:59, Matthias Wessendorf >>>>>> > wrote: >>>>>>> >>>>>>> Hi Martin, >>>>>>> >>>>>>> so - it's basically porting this commit over to the 1.0x branch: >>>>>>> >>>>>>> https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3 >>>>>>> >>>>>>> right ? >>>>>>> >>>>>>> Mind sending a PR ? >>>>>>> >>>>>>> On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy >>>>>> > wrote: >>>>>>> >>>>>>>> Hi folks, >>>>>>>> we have a Cordova application that?s using Codrova 3.3. >>>>>>>> The application uses org.jboss.aerogear.cordova.push 1.0.2 >>>>>>>> >>>>>>>> When preparing for an android build, there seems to be an problem >>>>>>>> installing one of the dependencies of the aurora plugin >>>>>>>> An id has been updated: com.vladstirbu.cordova.promise, now has a >>>>>>>> different id: es6-promise-plugin. >>>>>>>> >>>>>>>> The newer plugin 2.0.2 is in the npm registry. >>>>>>>> >>>>>>>> Is it possible to add a fix and deploy to the old cordova registry >>>>>>>> so that it?s usable in 3.x >>>>>>>> Is the newer plugin 2.0.2 backward compatible with 1.0.2 >>>>>>>> >>>>>>>> I understand that the ideal approach would be to use a more >>>>>>>> up-to-date version of Cordova, and use the latest aurora plugin, however it >>>>>>>> will take some time before I will be able to do that. >>>>>>>> I?m open to other suggestions also. >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> Martin Murphy. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>> >> >> >> >> -- >> 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 >> > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150714/41f1ccf6/attachment-0001.html From lholmqui at redhat.com Wed Jul 15 14:29:53 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Wed, 15 Jul 2015 14:29:53 -0400 Subject: [aerogear-dev] AG JS JIRA Message-ID: Hello all, we've decided that it would probably be a good idea to move JIRA's related to the node-sender to the AG-JS JIRA instead of having them on the AGUSH JIRA. i think this makes a bit more sense since this a javascript component. I've started to move open JIRA's over. i think i'll probably just leave the existing JIRA's where they are, unless someone feels strongly. I've also started to create some "component" versions similar to the other projects. the main JS lib will still be just numbers, like 2.3.0, and for the node-sender we will now have node-sender-0.8.0, for example -Luke -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150715/bd7f9a11/attachment.html From lholmqui at redhat.com Wed Jul 15 15:16:24 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Wed, 15 Jul 2015 15:16:24 -0400 Subject: [aerogear-dev] UPS Node Sender client categories issue? In-Reply-To: References: Message-ID: So i've sent PR's for this now, https://github.com/aerogear/aerogear-unifiedpush-nodejs-client/pull/21 and https://github.com/aerogear/aerogear-unifiedpush-nodejs-client/pull/20 first link is for the 0.7.x release and second is for master On Tue, Jul 14, 2015 at 11:23 AM, Luke Holmquist wrote: > > > On Tue, Jul 14, 2015 at 11:05 AM, Matthias Wessendorf > wrote: > >> >> >> On Tue, Jul 14, 2015 at 4:28 PM, Luke Holmquist >> wrote: >> >>> JIRA'd https://issues.jboss.org/browse/AGPUSH-1468 >>> >>> >>> Matzew, so for versioning of the node-sender, i wonder if we should >>> add that "component" in the versions for JIRA similar to how sps has it's >>> own versioning scheme. something like node-sender-0.7.0 , >>> node-sender-0.8.0 ? something like that, would be easier to keep track of >>> those releases. >>> >>> as i was writing this, i'm also thinking if these issues should be part >>> of AG-JS and i can do the versions there? hmmm >>> >> >> yeah - actually, I think you are right. I am absolutely fine w/ having >> the node-js-sender on AGJS. >> >> It's been a) a fairly stable component (lholmquist++) and b) our APIs are >> mostly JSON payload to a well-known endpoint - so not much to 'plan' from a >> AGPUSH / UPS perspective >> > > ok, sounds good. I will start adding things over there > >> >> -M >> >> >>> >>> >>> On Tue, Jul 14, 2015 at 8:56 AM, Fink, Miles >>> wrote: >>> >>>> I'll see if I can?t get it in JIRA. Just to clarify, the issue I >>>> noticed regarding empty arrays was on the 0.7.x branch of Node Sender, so >>>> it may not be an issue in the latest branch. >>>> >>>> -Miles >>>> >>>> From: Matthias Wessendorf >>>> Reply-To: AeroGear Developer Mailing List >>> > >>>> Date: Tuesday, July 14, 2015 at 4:51 AM >>>> >>>> To: AeroGear Developer Mailing List >>>> Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? >>>> >>>> Miles,Luke >>>> >>>> mind filing a JIRA issue for this ? >>>> >>>> On Thu, Jul 9, 2015 at 8:27 PM, Luke Holmquist >>>> wrote: >>>> >>>>> >>>>> >>>>> On Thu, Jul 9, 2015 at 2:15 PM, Fink, Miles >>>>> wrote: >>>>> >>>>>> Thanks Luke. Using 0.7.0 version worked. >>>>>> >>>>>> I will note a couple items: >>>>>> >>>>>> 0.8.x uses application*Id* (note Id), .0.7.x uses application*ID* >>>>>> >>>>>> Also, I was sending empty arrays for the settings.criteria that I >>>>>> wasn?t using (deviceType, alias) which then still sent the notification to >>>>>> all installations regardless of the categories I was sending. After I >>>>>> removed all the empty arrays from criteria and just sent the categories >>>>>> array it worked! >>>>>> >>>>> >>>>> thanks for that input. sounds like a Bug! >>>>> >>>>>> >>>>>> Anyway, thanks for the support! Much appreciated! >>>>>> >>>>>> Cheers, >>>>>> Miles >>>>>> >>>>>> >>>>>> From: Luke Holmquist >>>>>> Reply-To: AeroGear Developer Mailing List < >>>>>> aerogear-dev at lists.jboss.org> >>>>>> Date: Thursday, July 9, 2015 at 1:32 PM >>>>>> To: AeroGear Developer Mailing List >>>>>> Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? >>>>>> >>>>>> So i see you are using the 1.0.3 version of the UPS, could you >>>>>> try the 0.7.0 version of the node-sender and see if that works. >>>>>> >>>>>> The 0.8.x series is targeted for the 1.1.x UPS series which has had >>>>>> some message format changes >>>>>> >>>>>> On Thu, Jul 9, 2015 at 1:28 PM, Luke Holmquist >>>>>> wrote: >>>>>> >>>>>>> hey Miles, >>>>>>> >>>>>>> Thanks for using the UPS!! >>>>>>> >>>>>>> so i think what your seeing is probably similar to this issue, >>>>>>> https://issues.jboss.org/browse/AGPUSH-1459 >>>>>>> >>>>>>> >>>>>>> The Dashboard uses the Java Client Sender, so something is going >>>>>>> on with the node one then >>>>>>> >>>>>>> thanks for putting your versions you are using, that should help >>>>>>> narrow down things >>>>>>> >>>>>>> >>>>>>> -Luke >>>>>>> >>>>>>> >>>>>>> On Thu, Jul 9, 2015 at 1:22 PM, Fink, Miles >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I?m just starting out with UPS (which is awesome btw!) and the >>>>>>>> Node.js sender client. One thing I?ve noticed is that a message sent from >>>>>>>> the dashboard with a particular category is sent to only those >>>>>>>> installations that have that category listed. This works great and is >>>>>>>> expected. I?m glad there is a way to target specific notification channels, >>>>>>>> etc. >>>>>>>> >>>>>>>> Sending a notification via the Node Sender client however appears >>>>>>>> to be sending to everyone?s installation regardless of the categories sent >>>>>>>> with the message. Here?s a pastie of what my node client call looks like: >>>>>>>> http://pastie.org/10282358 >>>>>>>> >>>>>>>> I?m using: >>>>>>>> Unifiedpush Node Sender version 0.8.0-beta1 >>>>>>>> >>>>>>>> UPS is the setup via the openshift cartridge, from >>>>>>>> https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push >>>>>>>> >>>>>>>> >>>>>>>> Any pointers would be greatly appreciated. Very well could be me >>>>>>>> doing it wrong? ;-) >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Miles >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>> >>> >>> >>> _______________________________________________ >>> 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/20150715/ee199161/attachment.html From bruno at abstractj.org Wed Jul 15 15:21:42 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 15 Jul 2015 16:21:42 -0300 Subject: [aerogear-dev] AG JS JIRA In-Reply-To: References: Message-ID: +1 makes more sense On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist wrote: > Hello all, > > we've decided that it would probably be a good idea to move JIRA's related > to the node-sender to the AG-JS JIRA instead of having them on the AGUSH > JIRA. > > i think this makes a bit more sense since this a javascript component. > > I've started to move open JIRA's over. i think i'll probably just leave > the existing JIRA's where they are, unless someone feels strongly. > > > I've also started to create some "component" versions similar to the other > projects. > > the main JS lib will still be just numbers, like 2.3.0, and for the > node-sender we will now have node-sender-0.8.0, for example > > > -Luke > > _______________________________________________ > 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/20150715/0d80a880/attachment-0001.html From dpassos at redhat.com Wed Jul 15 16:52:17 2015 From: dpassos at redhat.com (Daniel Passos) Date: Wed, 15 Jul 2015 17:52:17 -0300 Subject: [aerogear-dev] AG JS JIRA In-Reply-To: References: Message-ID: +1 On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira wrote: > +1 makes more sense > > On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist > wrote: > >> Hello all, >> >> we've decided that it would probably be a good idea to move JIRA's >> related to the node-sender to the AG-JS JIRA instead of having them on the >> AGUSH JIRA. >> >> i think this makes a bit more sense since this a javascript component. >> >> I've started to move open JIRA's over. i think i'll probably just leave >> the existing JIRA's where they are, unless someone feels strongly. >> >> >> I've also started to create some "component" versions similar to the >> other projects. >> >> the main JS lib will still be just numbers, like 2.3.0, and for the >> node-sender we will now have node-sender-0.8.0, for example >> >> >> -Luke >> >> _______________________________________________ >> 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 > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150715/a9a2751c/attachment.html From daniel.bevenius at gmail.com Thu Jul 16 00:50:45 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Thu, 16 Jul 2015 06:50:45 +0200 Subject: [aerogear-dev] AG JS JIRA In-Reply-To: References: Message-ID: +1 Sounds good On 15 July 2015 at 22:52, Daniel Passos wrote: > +1 > > On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira > wrote: > >> +1 makes more sense >> >> On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist >> wrote: >> >>> Hello all, >>> >>> we've decided that it would probably be a good idea to move JIRA's >>> related to the node-sender to the AG-JS JIRA instead of having them on the >>> AGUSH JIRA. >>> >>> i think this makes a bit more sense since this a javascript component. >>> >>> I've started to move open JIRA's over. i think i'll probably just leave >>> the existing JIRA's where they are, unless someone feels strongly. >>> >>> >>> I've also started to create some "component" versions similar to the >>> other projects. >>> >>> the main JS lib will still be just numbers, like 2.3.0, and for the >>> node-sender we will now have node-sender-0.8.0, for example >>> >>> >>> -Luke >>> >>> _______________________________________________ >>> 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 >> > > > > -- > -- 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/20150716/0b5023ec/attachment.html From matzew at apache.org Thu Jul 16 02:42:47 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 16 Jul 2015 08:42:47 +0200 Subject: [aerogear-dev] AG JS JIRA In-Reply-To: References: Message-ID: word up? On Thursday, July 16, 2015, Daniel Bevenius wrote: > +1 Sounds good > > On 15 July 2015 at 22:52, Daniel Passos > wrote: > >> +1 >> >> On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira > > wrote: >> >>> +1 makes more sense >>> >>> On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist >> > wrote: >>> >>>> Hello all, >>>> >>>> we've decided that it would probably be a good idea to move JIRA's >>>> related to the node-sender to the AG-JS JIRA instead of having them on the >>>> AGUSH JIRA. >>>> >>>> i think this makes a bit more sense since this a javascript component. >>>> >>>> I've started to move open JIRA's over. i think i'll probably just >>>> leave the existing JIRA's where they are, unless someone feels strongly. >>>> >>>> >>>> I've also started to create some "component" versions similar to the >>>> other projects. >>>> >>>> the main JS lib will still be just numbers, like 2.3.0, and for the >>>> node-sender we will now have node-sender-0.8.0, for example >>>> >>>> >>>> -Luke >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> >> >> -- >> -- Passos >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150716/35be7634/attachment.html From corinnekrych at gmail.com Thu Jul 16 03:14:18 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 16 Jul 2015 09:14:18 +0200 Subject: [aerogear-dev] aerogear-ios-push Carthage support In-Reply-To: <7871F45C-CAEC-472C-B4C1-184B14DC9AE7@symentis.com> References: <7871F45C-CAEC-472C-B4C1-184B14DC9AE7@symentis.com> Message-ID: Hello Robert Yes we have an open ticket for carthage support [1]. Contributions are welcome ;) ++ Corinne [1] https://issues.jboss.org/browse/AGIOS-415 On 14 July 2015 at 18:25, Robert Oschwald wrote: > is it planned to add Carthage support to the library? > We moved away from Cocoapods since a while and love Carthage for beeing > non-intrusive. > > Thanks, > Robert > > > _______________________________________________ > 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/20150716/86cb613e/attachment.html From lukas.fryc at gmail.com Thu Jul 16 04:42:52 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Thu, 16 Jul 2015 10:42:52 +0200 Subject: [aerogear-dev] AG JS JIRA In-Reply-To: References: Message-ID: I know there already is strong agreement, but my $0.02: I'm not convinced about AGJS and connection with server-side libraries. I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side libs, AGPUSH, AGSYNC, are trackes for server-side technologies, consider this use case: if we build eventually a new server-side Swift node-sender library, we won't track it under AGIOS because Swift comes from iOS land. On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf wrote: > word up? > > > On Thursday, July 16, 2015, Daniel Bevenius > wrote: > >> +1 Sounds good >> >> On 15 July 2015 at 22:52, Daniel Passos wrote: >> >>> +1 >>> >>> On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira >>> wrote: >>> >>>> +1 makes more sense >>>> >>>> On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist >>>> wrote: >>>> >>>>> Hello all, >>>>> >>>>> we've decided that it would probably be a good idea to move JIRA's >>>>> related to the node-sender to the AG-JS JIRA instead of having them on the >>>>> AGUSH JIRA. >>>>> >>>>> i think this makes a bit more sense since this a javascript component. >>>>> >>>>> I've started to move open JIRA's over. i think i'll probably just >>>>> leave the existing JIRA's where they are, unless someone feels strongly. >>>>> >>>>> >>>>> I've also started to create some "component" versions similar to the >>>>> other projects. >>>>> >>>>> the main JS lib will still be just numbers, like 2.3.0, and for the >>>>> node-sender we will now have node-sender-0.8.0, for example >>>>> >>>>> >>>>> -Luke >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>> >>> >>> >>> -- >>> -- Passos >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > -- > Sent from Gmail Mobile > > _______________________________________________ > 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/20150716/0d52a9ea/attachment-0001.html From matzew at apache.org Thu Jul 16 05:01:26 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 16 Jul 2015 11:01:26 +0200 Subject: [aerogear-dev] AG JS JIRA In-Reply-To: References: Message-ID: well... the use of components makes it easy - and for versions we could even do something like, for instance in AGJS node-1.2.0 store-0.7.0 etc On Thu, Jul 16, 2015 at 10:42 AM, Luk?? Fry? wrote: > I know there already is strong agreement, but my $0.02: > > I'm not convinced about AGJS and connection with server-side libraries. > > > I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side > libs, > > AGPUSH, AGSYNC, are trackes for server-side technologies, > > > consider this use case: if we build eventually a new server-side Swift > node-sender library, we won't track it under AGIOS because Swift comes from > iOS land. > > On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf > wrote: > >> word up? >> >> >> On Thursday, July 16, 2015, Daniel Bevenius >> wrote: >> >>> +1 Sounds good >>> >>> On 15 July 2015 at 22:52, Daniel Passos wrote: >>> >>>> +1 >>>> >>>> On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira >>>> wrote: >>>> >>>>> +1 makes more sense >>>>> >>>>> On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist >>>>> wrote: >>>>> >>>>>> Hello all, >>>>>> >>>>>> we've decided that it would probably be a good idea to move JIRA's >>>>>> related to the node-sender to the AG-JS JIRA instead of having them on the >>>>>> AGUSH JIRA. >>>>>> >>>>>> i think this makes a bit more sense since this a javascript component. >>>>>> >>>>>> I've started to move open JIRA's over. i think i'll probably just >>>>>> leave the existing JIRA's where they are, unless someone feels strongly. >>>>>> >>>>>> >>>>>> I've also started to create some "component" versions similar to the >>>>>> other projects. >>>>>> >>>>>> the main JS lib will still be just numbers, like 2.3.0, and for the >>>>>> node-sender we will now have node-sender-0.8.0, for example >>>>>> >>>>>> >>>>>> -Luke >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> -- Passos >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >> >> -- >> Sent from Gmail Mobile >> >> _______________________________________________ >> 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/20150716/c51f7f66/attachment.html From matzew at apache.org Thu Jul 16 05:03:41 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 16 Jul 2015 11:03:41 +0200 Subject: [aerogear-dev] One JIRA instance to rule them all? (was Re: AG JS JIRA) Message-ID: That brings me to something .... :-) using this approach,e.g * android-oauth-3.0.0 * swift-sender-1.0.0 * ios-swift-push 3.0.0 we could go back and just use one JIRA. That's perhaps less confusion for our users :-) They just enter bugs/issues and we are responsible for the actual 'triage' (e.g. set correct components and versions) :-) On Thu, Jul 16, 2015 at 11:01 AM, Matthias Wessendorf wrote: > well... the use of components makes it easy - and for versions we could > even do something like, for instance in AGJS > > node-1.2.0 > store-0.7.0 > > etc > > > > On Thu, Jul 16, 2015 at 10:42 AM, Luk?? Fry? wrote: > >> I know there already is strong agreement, but my $0.02: >> >> I'm not convinced about AGJS and connection with server-side libraries. >> >> >> I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side >> libs, >> >> AGPUSH, AGSYNC, are trackes for server-side technologies, >> >> >> consider this use case: if we build eventually a new server-side Swift >> node-sender library, we won't track it under AGIOS because Swift comes from >> iOS land. >> >> On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf >> wrote: >> >>> word up? >>> >>> >>> On Thursday, July 16, 2015, Daniel Bevenius >>> wrote: >>> >>>> +1 Sounds good >>>> >>>> On 15 July 2015 at 22:52, Daniel Passos wrote: >>>> >>>>> +1 >>>>> >>>>> On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira >>>>> wrote: >>>>> >>>>>> +1 makes more sense >>>>>> >>>>>> On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist >>>>>> wrote: >>>>>> >>>>>>> Hello all, >>>>>>> >>>>>>> we've decided that it would probably be a good idea to move JIRA's >>>>>>> related to the node-sender to the AG-JS JIRA instead of having them on the >>>>>>> AGUSH JIRA. >>>>>>> >>>>>>> i think this makes a bit more sense since this a javascript >>>>>>> component. >>>>>>> >>>>>>> I've started to move open JIRA's over. i think i'll probably just >>>>>>> leave the existing JIRA's where they are, unless someone feels strongly. >>>>>>> >>>>>>> >>>>>>> I've also started to create some "component" versions similar to the >>>>>>> other projects. >>>>>>> >>>>>>> the main JS lib will still be just numbers, like 2.3.0, and for the >>>>>>> node-sender we will now have node-sender-0.8.0, for example >>>>>>> >>>>>>> >>>>>>> -Luke >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> -- Passos >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>> >>> -- >>> Sent from Gmail Mobile >>> >>> _______________________________________________ >>> 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 > -- 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/20150716/a6fc3569/attachment.html From lukas.fryc at gmail.com Thu Jul 16 05:20:50 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Thu, 16 Jul 2015 11:20:50 +0200 Subject: [aerogear-dev] One JIRA instance to rule them all? (was Re: AG JS JIRA) In-Reply-To: References: Message-ID: Pros: Indeed that is super-simple for users, Cons: it is a bit harder to read or use other JIRA features like roadmap or agile. On Thu, Jul 16, 2015 at 11:03 AM, Matthias Wessendorf wrote: > That brings me to something .... :-) > > > using this approach,e.g > * android-oauth-3.0.0 > * swift-sender-1.0.0 > * ios-swift-push 3.0.0 > > we could go back and just use one JIRA. > > That's perhaps less confusion for our users :-) > > They just enter bugs/issues and we are responsible for the actual 'triage' > (e.g. set correct components and versions) > > :-) > > > On Thu, Jul 16, 2015 at 11:01 AM, Matthias Wessendorf > wrote: > >> well... the use of components makes it easy - and for versions we could >> even do something like, for instance in AGJS >> >> node-1.2.0 >> store-0.7.0 >> >> etc >> >> >> >> On Thu, Jul 16, 2015 at 10:42 AM, Luk?? Fry? >> wrote: >> >>> I know there already is strong agreement, but my $0.02: >>> >>> I'm not convinced about AGJS and connection with server-side libraries. >>> >>> >>> I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side >>> libs, >>> >>> AGPUSH, AGSYNC, are trackes for server-side technologies, >>> >>> >>> consider this use case: if we build eventually a new server-side Swift >>> node-sender library, we won't track it under AGIOS because Swift comes from >>> iOS land. >>> >>> On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf >>> wrote: >>> >>>> word up? >>>> >>>> >>>> On Thursday, July 16, 2015, Daniel Bevenius >>>> wrote: >>>> >>>>> +1 Sounds good >>>>> >>>>> On 15 July 2015 at 22:52, Daniel Passos wrote: >>>>> >>>>>> +1 >>>>>> >>>>>> On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira >>>>>> wrote: >>>>>> >>>>>>> +1 makes more sense >>>>>>> >>>>>>> On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist >>>>>> > wrote: >>>>>>> >>>>>>>> Hello all, >>>>>>>> >>>>>>>> we've decided that it would probably be a good idea to move JIRA's >>>>>>>> related to the node-sender to the AG-JS JIRA instead of having them on the >>>>>>>> AGUSH JIRA. >>>>>>>> >>>>>>>> i think this makes a bit more sense since this a javascript >>>>>>>> component. >>>>>>>> >>>>>>>> I've started to move open JIRA's over. i think i'll probably just >>>>>>>> leave the existing JIRA's where they are, unless someone feels strongly. >>>>>>>> >>>>>>>> >>>>>>>> I've also started to create some "component" versions similar to >>>>>>>> the other projects. >>>>>>>> >>>>>>>> the main JS lib will still be just numbers, like 2.3.0, and for >>>>>>>> the node-sender we will now have node-sender-0.8.0, for example >>>>>>>> >>>>>>>> >>>>>>>> -Luke >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> -- Passos >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>> >>>> -- >>>> Sent from Gmail Mobile >>>> >>>> _______________________________________________ >>>> 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 >> > > > > -- > 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/20150716/731d5c70/attachment-0001.html From matzew at apache.org Thu Jul 16 05:45:07 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 16 Jul 2015 11:45:07 +0200 Subject: [aerogear-dev] One JIRA instance to rule them all? (was Re: AG JS JIRA) In-Reply-To: References: Message-ID: roadmaps is slightly harder to read - because a bunch of different versions are there. BUT! it shows activity better :) On Thu, Jul 16, 2015 at 11:20 AM, Luk?? Fry? wrote: > Pros: Indeed that is super-simple for users, > > Cons: it is a bit harder to read or use other JIRA features like roadmap > or agile. > > On Thu, Jul 16, 2015 at 11:03 AM, Matthias Wessendorf > wrote: > >> That brings me to something .... :-) >> >> >> using this approach,e.g >> * android-oauth-3.0.0 >> * swift-sender-1.0.0 >> * ios-swift-push 3.0.0 >> >> we could go back and just use one JIRA. >> >> That's perhaps less confusion for our users :-) >> >> They just enter bugs/issues and we are responsible for the actual >> 'triage' (e.g. set correct components and versions) >> >> :-) >> >> >> On Thu, Jul 16, 2015 at 11:01 AM, Matthias Wessendorf >> wrote: >> >>> well... the use of components makes it easy - and for versions we could >>> even do something like, for instance in AGJS >>> >>> node-1.2.0 >>> store-0.7.0 >>> >>> etc >>> >>> >>> >>> On Thu, Jul 16, 2015 at 10:42 AM, Luk?? Fry? >>> wrote: >>> >>>> I know there already is strong agreement, but my $0.02: >>>> >>>> I'm not convinced about AGJS and connection with server-side libraries. >>>> >>>> >>>> I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for >>>> client-side libs, >>>> >>>> AGPUSH, AGSYNC, are trackes for server-side technologies, >>>> >>>> >>>> consider this use case: if we build eventually a new server-side Swift >>>> node-sender library, we won't track it under AGIOS because Swift comes from >>>> iOS land. >>>> >>>> On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf >>> > wrote: >>>> >>>>> word up? >>>>> >>>>> >>>>> On Thursday, July 16, 2015, Daniel Bevenius >>>>> wrote: >>>>> >>>>>> +1 Sounds good >>>>>> >>>>>> On 15 July 2015 at 22:52, Daniel Passos wrote: >>>>>> >>>>>>> +1 >>>>>>> >>>>>>> On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira >>>>>> > wrote: >>>>>>> >>>>>>>> +1 makes more sense >>>>>>>> >>>>>>>> On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist < >>>>>>>> lholmqui at redhat.com> wrote: >>>>>>>> >>>>>>>>> Hello all, >>>>>>>>> >>>>>>>>> we've decided that it would probably be a good idea to move JIRA's >>>>>>>>> related to the node-sender to the AG-JS JIRA instead of having them on the >>>>>>>>> AGUSH JIRA. >>>>>>>>> >>>>>>>>> i think this makes a bit more sense since this a javascript >>>>>>>>> component. >>>>>>>>> >>>>>>>>> I've started to move open JIRA's over. i think i'll probably just >>>>>>>>> leave the existing JIRA's where they are, unless someone feels strongly. >>>>>>>>> >>>>>>>>> >>>>>>>>> I've also started to create some "component" versions similar to >>>>>>>>> the other projects. >>>>>>>>> >>>>>>>>> the main JS lib will still be just numbers, like 2.3.0, and for >>>>>>>>> the node-sender we will now have node-sender-0.8.0, for example >>>>>>>>> >>>>>>>>> >>>>>>>>> -Luke >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> -- Passos >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> Sent from Gmail Mobile >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> >> >> -- >> 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/20150716/45f4d051/attachment.html From lholmqui at redhat.com Thu Jul 16 08:09:02 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Thu, 16 Jul 2015 08:09:02 -0400 Subject: [aerogear-dev] AG JS JIRA In-Reply-To: References: Message-ID: On Thu, Jul 16, 2015 at 4:42 AM, Luk?? Fry? wrote: > I know there already is strong agreement, but my $0.02: > > I'm not convinced about AGJS and connection with server-side libraries. > > > I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side > libs, > I agree with you, but i think AGJS has might be evolving from just a client side lib. This is whole topic could be and should be a whole other thread. I think the original goal of the JS lib has changed and doesn't have as clear of a "story" as the other libraries anymore. I think that is one of the reasons for this change. Even though the node-sender is contacting server technologies, it still is Javascript. Perhaps thats what AG-JS will evolve into, all JS related things from AeroGear > > AGPUSH, AGSYNC, are trackes for server-side technologies, > I think for AGSync we have related JIRA's pointing to JIRA's in AG-JS. I thought about doing something like that for the node-sender stuff > > > consider this use case: if we build eventually a new server-side Swift > node-sender library, we won't track it under AGIOS because Swift comes from > iOS land. > > On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf > wrote: > >> word up? >> >> >> On Thursday, July 16, 2015, Daniel Bevenius >> wrote: >> >>> +1 Sounds good >>> >>> On 15 July 2015 at 22:52, Daniel Passos wrote: >>> >>>> +1 >>>> >>>> On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira >>>> wrote: >>>> >>>>> +1 makes more sense >>>>> >>>>> On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist >>>>> wrote: >>>>> >>>>>> Hello all, >>>>>> >>>>>> we've decided that it would probably be a good idea to move JIRA's >>>>>> related to the node-sender to the AG-JS JIRA instead of having them on the >>>>>> AGUSH JIRA. >>>>>> >>>>>> i think this makes a bit more sense since this a javascript component. >>>>>> >>>>>> I've started to move open JIRA's over. i think i'll probably just >>>>>> leave the existing JIRA's where they are, unless someone feels strongly. >>>>>> >>>>>> >>>>>> I've also started to create some "component" versions similar to the >>>>>> other projects. >>>>>> >>>>>> the main JS lib will still be just numbers, like 2.3.0, and for the >>>>>> node-sender we will now have node-sender-0.8.0, for example >>>>>> >>>>>> >>>>>> -Luke >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> -- Passos >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >> >> -- >> Sent from Gmail Mobile >> >> _______________________________________________ >> 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/20150716/4febb522/attachment-0001.html From lholmqui at redhat.com Thu Jul 16 08:11:04 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Thu, 16 Jul 2015 08:11:04 -0400 Subject: [aerogear-dev] AG JS JIRA In-Reply-To: References: Message-ID: On Thu, Jul 16, 2015 at 5:01 AM, Matthias Wessendorf wrote: > well... the use of components makes it easy - and for versions we could > even do something like, for instance in AGJS > > node-1.2.0 > store-0.7.0 > i think for the JS library, we would only version components that lived in there own repo. the node sender makes sense here. but store(and other components of the main lib) probably wouldn't get this type of granularity, and at this point, i don't think it makes sense to split them apart > > etc > > > > On Thu, Jul 16, 2015 at 10:42 AM, Luk?? Fry? wrote: > >> I know there already is strong agreement, but my $0.02: >> >> I'm not convinced about AGJS and connection with server-side libraries. >> >> >> I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side >> libs, >> >> AGPUSH, AGSYNC, are trackes for server-side technologies, >> >> >> consider this use case: if we build eventually a new server-side Swift >> node-sender library, we won't track it under AGIOS because Swift comes from >> iOS land. >> >> On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf >> wrote: >> >>> word up? >>> >>> >>> On Thursday, July 16, 2015, Daniel Bevenius >>> wrote: >>> >>>> +1 Sounds good >>>> >>>> On 15 July 2015 at 22:52, Daniel Passos wrote: >>>> >>>>> +1 >>>>> >>>>> On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira >>>>> wrote: >>>>> >>>>>> +1 makes more sense >>>>>> >>>>>> On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist >>>>>> wrote: >>>>>> >>>>>>> Hello all, >>>>>>> >>>>>>> we've decided that it would probably be a good idea to move JIRA's >>>>>>> related to the node-sender to the AG-JS JIRA instead of having them on the >>>>>>> AGUSH JIRA. >>>>>>> >>>>>>> i think this makes a bit more sense since this a javascript >>>>>>> component. >>>>>>> >>>>>>> I've started to move open JIRA's over. i think i'll probably just >>>>>>> leave the existing JIRA's where they are, unless someone feels strongly. >>>>>>> >>>>>>> >>>>>>> I've also started to create some "component" versions similar to the >>>>>>> other projects. >>>>>>> >>>>>>> the main JS lib will still be just numbers, like 2.3.0, and for the >>>>>>> node-sender we will now have node-sender-0.8.0, for example >>>>>>> >>>>>>> >>>>>>> -Luke >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> -- Passos >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>> >>> -- >>> Sent from Gmail Mobile >>> >>> _______________________________________________ >>> 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/20150716/317ad144/attachment.html From lholmqui at redhat.com Thu Jul 16 09:09:06 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Thu, 16 Jul 2015 09:09:06 -0400 Subject: [aerogear-dev] UPS Node Sender client categories issue? In-Reply-To: References: Message-ID: This should be all set now, i released 0.7.1 on npm and here is the release on GH, https://github.com/aerogear/aerogear-unifiedpush-nodejs-client/releases/tag/0.7.1 On Wed, Jul 15, 2015 at 3:16 PM, Luke Holmquist wrote: > So i've sent PR's for this now, > https://github.com/aerogear/aerogear-unifiedpush-nodejs-client/pull/21 > and https://github.com/aerogear/aerogear-unifiedpush-nodejs-client/pull/20 > > > first link is for the 0.7.x release and second is for master > > On Tue, Jul 14, 2015 at 11:23 AM, Luke Holmquist > wrote: > >> >> >> On Tue, Jul 14, 2015 at 11:05 AM, Matthias Wessendorf >> wrote: >> >>> >>> >>> On Tue, Jul 14, 2015 at 4:28 PM, Luke Holmquist >>> wrote: >>> >>>> JIRA'd https://issues.jboss.org/browse/AGPUSH-1468 >>>> >>>> >>>> Matzew, so for versioning of the node-sender, i wonder if we should >>>> add that "component" in the versions for JIRA similar to how sps has it's >>>> own versioning scheme. something like node-sender-0.7.0 , >>>> node-sender-0.8.0 ? something like that, would be easier to keep track of >>>> those releases. >>>> >>>> as i was writing this, i'm also thinking if these issues should be >>>> part of AG-JS and i can do the versions there? hmmm >>>> >>> >>> yeah - actually, I think you are right. I am absolutely fine w/ having >>> the node-js-sender on AGJS. >>> >>> It's been a) a fairly stable component (lholmquist++) and b) our APIs >>> are mostly JSON payload to a well-known endpoint - so not much to 'plan' >>> from a AGPUSH / UPS perspective >>> >> >> ok, sounds good. I will start adding things over there >> >>> >>> -M >>> >>> >>>> >>>> >>>> On Tue, Jul 14, 2015 at 8:56 AM, Fink, Miles >>>> wrote: >>>> >>>>> I'll see if I can?t get it in JIRA. Just to clarify, the issue I >>>>> noticed regarding empty arrays was on the 0.7.x branch of Node Sender, so >>>>> it may not be an issue in the latest branch. >>>>> >>>>> -Miles >>>>> >>>>> From: Matthias Wessendorf >>>>> Reply-To: AeroGear Developer Mailing List < >>>>> aerogear-dev at lists.jboss.org> >>>>> Date: Tuesday, July 14, 2015 at 4:51 AM >>>>> >>>>> To: AeroGear Developer Mailing List >>>>> Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? >>>>> >>>>> Miles,Luke >>>>> >>>>> mind filing a JIRA issue for this ? >>>>> >>>>> On Thu, Jul 9, 2015 at 8:27 PM, Luke Holmquist >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Thu, Jul 9, 2015 at 2:15 PM, Fink, Miles >>>>>> wrote: >>>>>> >>>>>>> Thanks Luke. Using 0.7.0 version worked. >>>>>>> >>>>>>> I will note a couple items: >>>>>>> >>>>>>> 0.8.x uses application*Id* (note Id), .0.7.x uses application*ID* >>>>>>> >>>>>>> Also, I was sending empty arrays for the settings.criteria that I >>>>>>> wasn?t using (deviceType, alias) which then still sent the notification to >>>>>>> all installations regardless of the categories I was sending. After I >>>>>>> removed all the empty arrays from criteria and just sent the categories >>>>>>> array it worked! >>>>>>> >>>>>> >>>>>> thanks for that input. sounds like a Bug! >>>>>> >>>>>>> >>>>>>> Anyway, thanks for the support! Much appreciated! >>>>>>> >>>>>>> Cheers, >>>>>>> Miles >>>>>>> >>>>>>> >>>>>>> From: Luke Holmquist >>>>>>> Reply-To: AeroGear Developer Mailing List < >>>>>>> aerogear-dev at lists.jboss.org> >>>>>>> Date: Thursday, July 9, 2015 at 1:32 PM >>>>>>> To: AeroGear Developer Mailing List >>>>>>> Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? >>>>>>> >>>>>>> So i see you are using the 1.0.3 version of the UPS, could you >>>>>>> try the 0.7.0 version of the node-sender and see if that works. >>>>>>> >>>>>>> The 0.8.x series is targeted for the 1.1.x UPS series which has >>>>>>> had some message format changes >>>>>>> >>>>>>> On Thu, Jul 9, 2015 at 1:28 PM, Luke Holmquist >>>>>>> wrote: >>>>>>> >>>>>>>> hey Miles, >>>>>>>> >>>>>>>> Thanks for using the UPS!! >>>>>>>> >>>>>>>> so i think what your seeing is probably similar to this issue, >>>>>>>> https://issues.jboss.org/browse/AGPUSH-1459 >>>>>>>> >>>>>>>> >>>>>>>> The Dashboard uses the Java Client Sender, so something is going >>>>>>>> on with the node one then >>>>>>>> >>>>>>>> thanks for putting your versions you are using, that should help >>>>>>>> narrow down things >>>>>>>> >>>>>>>> >>>>>>>> -Luke >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Jul 9, 2015 at 1:22 PM, Fink, Miles >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I?m just starting out with UPS (which is awesome btw!) and the >>>>>>>>> Node.js sender client. One thing I?ve noticed is that a message sent from >>>>>>>>> the dashboard with a particular category is sent to only those >>>>>>>>> installations that have that category listed. This works great and is >>>>>>>>> expected. I?m glad there is a way to target specific notification channels, >>>>>>>>> etc. >>>>>>>>> >>>>>>>>> Sending a notification via the Node Sender client however >>>>>>>>> appears to be sending to everyone?s installation regardless of the >>>>>>>>> categories sent with the message. Here?s a pastie of what my node client >>>>>>>>> call looks like: http://pastie.org/10282358 >>>>>>>>> >>>>>>>>> I?m using: >>>>>>>>> Unifiedpush Node Sender version 0.8.0-beta1 >>>>>>>>> >>>>>>>>> UPS is the setup via the openshift cartridge, from >>>>>>>>> https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push >>>>>>>>> >>>>>>>>> >>>>>>>>> Any pointers would be greatly appreciated. Very well could be me >>>>>>>>> doing it wrong? ;-) >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Miles >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>> >>>> >>>> >>>> _______________________________________________ >>>> 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/20150716/a69116a0/attachment-0001.html From matzew at apache.org Thu Jul 16 10:59:09 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 16 Jul 2015 16:59:09 +0200 Subject: [aerogear-dev] UnifiedPush Server: time for a 1.1.0-beta.3 Message-ID: Hi, we had a few changes since the last beta: https://issues.jboss.org/issues/?jql=project%20%3D%20AGPUSH%20AND%20fixVersion%20%3D%20ups-1.1.0.final%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC I'd like to run another beta. The DB migrator is not yet there, but Dan and QMX are close on this. yay! So, in the spirit of release often / release early I see zero reasons to not do another beta. Any thoughts? -- 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/20150716/efadacf8/attachment.html From scm.blanc at gmail.com Thu Jul 16 11:01:07 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 16 Jul 2015 17:01:07 +0200 Subject: [aerogear-dev] UnifiedPush Server: time for a 1.1.0-beta.3 In-Reply-To: References: Message-ID: Ship it ! On Thu, Jul 16, 2015 at 4:59 PM, Matthias Wessendorf wrote: > Hi, > > we had a few changes since the last beta: > > > https://issues.jboss.org/issues/?jql=project%20%3D%20AGPUSH%20AND%20fixVersion%20%3D%20ups-1.1.0.final%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC > > I'd like to run another beta. > > The DB migrator is not yet there, but Dan and QMX are close on this. yay! > > > So, in the spirit of release often / release early I see zero reasons to > not do another beta. > > > Any thoughts? > > > > > > -- > 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/20150716/9bda19e8/attachment.html From bruno at abstractj.org Thu Jul 16 13:29:40 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 16 Jul 2015 14:29:40 -0300 Subject: [aerogear-dev] One JIRA instance to rule them all? (was Re: AG JS JIRA) In-Reply-To: References: Message-ID: Do we have any complaints about our current Jira instances? Maybe I missed something. Nothing against moving all the Jiras to a single instance. But I think that just moving without a rock solid plan, will turn this into a mess. On Thu, Jul 16, 2015 at 6:03 AM, Matthias Wessendorf wrote: > That brings me to something .... :-) > > > using this approach,e.g > * android-oauth-3.0.0 > * swift-sender-1.0.0 > * ios-swift-push 3.0.0 > > we could go back and just use one JIRA. > > That's perhaps less confusion for our users :-) > > They just enter bugs/issues and we are responsible for the actual 'triage' > (e.g. set correct components and versions) > > :-) > > > On Thu, Jul 16, 2015 at 11:01 AM, Matthias Wessendorf > wrote: > >> well... the use of components makes it easy - and for versions we could >> even do something like, for instance in AGJS >> >> node-1.2.0 >> store-0.7.0 >> >> etc >> >> >> >> On Thu, Jul 16, 2015 at 10:42 AM, Luk?? Fry? >> wrote: >> >>> I know there already is strong agreement, but my $0.02: >>> >>> I'm not convinced about AGJS and connection with server-side libraries. >>> >>> >>> I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side >>> libs, >>> >>> AGPUSH, AGSYNC, are trackes for server-side technologies, >>> >>> >>> consider this use case: if we build eventually a new server-side Swift >>> node-sender library, we won't track it under AGIOS because Swift comes from >>> iOS land. >>> >>> On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf >>> wrote: >>> >>>> word up? >>>> >>>> >>>> On Thursday, July 16, 2015, Daniel Bevenius >>>> wrote: >>>> >>>>> +1 Sounds good >>>>> >>>>> On 15 July 2015 at 22:52, Daniel Passos wrote: >>>>> >>>>>> +1 >>>>>> >>>>>> On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira >>>>>> wrote: >>>>>> >>>>>>> +1 makes more sense >>>>>>> >>>>>>> On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist >>>>>> > wrote: >>>>>>> >>>>>>>> Hello all, >>>>>>>> >>>>>>>> we've decided that it would probably be a good idea to move JIRA's >>>>>>>> related to the node-sender to the AG-JS JIRA instead of having them on the >>>>>>>> AGUSH JIRA. >>>>>>>> >>>>>>>> i think this makes a bit more sense since this a javascript >>>>>>>> component. >>>>>>>> >>>>>>>> I've started to move open JIRA's over. i think i'll probably just >>>>>>>> leave the existing JIRA's where they are, unless someone feels strongly. >>>>>>>> >>>>>>>> >>>>>>>> I've also started to create some "component" versions similar to >>>>>>>> the other projects. >>>>>>>> >>>>>>>> the main JS lib will still be just numbers, like 2.3.0, and for >>>>>>>> the node-sender we will now have node-sender-0.8.0, for example >>>>>>>> >>>>>>>> >>>>>>>> -Luke >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> -- Passos >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>> >>>> -- >>>> Sent from Gmail Mobile >>>> >>>> _______________________________________________ >>>> 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 >> > > > > -- > 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 > -- -- "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/20150716/6cf7a7d9/attachment.html From lholmqui at redhat.com Thu Jul 16 13:39:48 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Thu, 16 Jul 2015 13:39:48 -0400 Subject: [aerogear-dev] One JIRA instance to rule them all? (was Re: AG JS JIRA) In-Reply-To: References: Message-ID: On Thu, Jul 16, 2015 at 1:29 PM, Bruno Oliveira wrote: > Do we have any complaints about our current Jira instances? Maybe I missed > something. > > Nothing against moving all the Jiras to a single instance. > Isn't this what we started with, i'm minus infinity on going back there > But I think that just moving without a rock solid plan, will turn this > into a mess. > > On Thu, Jul 16, 2015 at 6:03 AM, Matthias Wessendorf > wrote: > >> That brings me to something .... :-) >> >> >> using this approach,e.g >> * android-oauth-3.0.0 >> * swift-sender-1.0.0 >> * ios-swift-push 3.0.0 >> >> we could go back and just use one JIRA. >> >> That's perhaps less confusion for our users :-) >> >> They just enter bugs/issues and we are responsible for the actual >> 'triage' (e.g. set correct components and versions) >> >> :-) >> >> >> On Thu, Jul 16, 2015 at 11:01 AM, Matthias Wessendorf >> wrote: >> >>> well... the use of components makes it easy - and for versions we could >>> even do something like, for instance in AGJS >>> >>> node-1.2.0 >>> store-0.7.0 >>> >>> etc >>> >>> >>> >>> On Thu, Jul 16, 2015 at 10:42 AM, Luk?? Fry? >>> wrote: >>> >>>> I know there already is strong agreement, but my $0.02: >>>> >>>> I'm not convinced about AGJS and connection with server-side libraries. >>>> >>>> >>>> I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for >>>> client-side libs, >>>> >>>> AGPUSH, AGSYNC, are trackes for server-side technologies, >>>> >>>> >>>> consider this use case: if we build eventually a new server-side Swift >>>> node-sender library, we won't track it under AGIOS because Swift comes from >>>> iOS land. >>>> >>>> On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf >>> > wrote: >>>> >>>>> word up? >>>>> >>>>> >>>>> On Thursday, July 16, 2015, Daniel Bevenius >>>>> wrote: >>>>> >>>>>> +1 Sounds good >>>>>> >>>>>> On 15 July 2015 at 22:52, Daniel Passos wrote: >>>>>> >>>>>>> +1 >>>>>>> >>>>>>> On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira >>>>>> > wrote: >>>>>>> >>>>>>>> +1 makes more sense >>>>>>>> >>>>>>>> On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist < >>>>>>>> lholmqui at redhat.com> wrote: >>>>>>>> >>>>>>>>> Hello all, >>>>>>>>> >>>>>>>>> we've decided that it would probably be a good idea to move JIRA's >>>>>>>>> related to the node-sender to the AG-JS JIRA instead of having them on the >>>>>>>>> AGUSH JIRA. >>>>>>>>> >>>>>>>>> i think this makes a bit more sense since this a javascript >>>>>>>>> component. >>>>>>>>> >>>>>>>>> I've started to move open JIRA's over. i think i'll probably just >>>>>>>>> leave the existing JIRA's where they are, unless someone feels strongly. >>>>>>>>> >>>>>>>>> >>>>>>>>> I've also started to create some "component" versions similar to >>>>>>>>> the other projects. >>>>>>>>> >>>>>>>>> the main JS lib will still be just numbers, like 2.3.0, and for >>>>>>>>> the node-sender we will now have node-sender-0.8.0, for example >>>>>>>>> >>>>>>>>> >>>>>>>>> -Luke >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> -- Passos >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> Sent from Gmail Mobile >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> >> >> -- >> 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 >> > > > > -- > > -- > "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/20150716/4bfde974/attachment-0001.html From matzew at apache.org Thu Jul 16 13:53:03 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 16 Jul 2015 19:53:03 +0200 Subject: [aerogear-dev] One JIRA instance to rule them all? (was Re: AG JS JIRA) In-Reply-To: References: Message-ID: no, it was just a thought - not more ;-) On Thu, Jul 16, 2015 at 7:29 PM, Bruno Oliveira wrote: > Do we have any complaints about our current Jira instances? Maybe I missed > something. > > Nothing against moving all the Jiras to a single instance. But I think > that just moving without a rock solid plan, will turn this into a mess. > > On Thu, Jul 16, 2015 at 6:03 AM, Matthias Wessendorf > wrote: > >> That brings me to something .... :-) >> >> >> using this approach,e.g >> * android-oauth-3.0.0 >> * swift-sender-1.0.0 >> * ios-swift-push 3.0.0 >> >> we could go back and just use one JIRA. >> >> That's perhaps less confusion for our users :-) >> >> They just enter bugs/issues and we are responsible for the actual >> 'triage' (e.g. set correct components and versions) >> >> :-) >> >> >> On Thu, Jul 16, 2015 at 11:01 AM, Matthias Wessendorf >> wrote: >> >>> well... the use of components makes it easy - and for versions we could >>> even do something like, for instance in AGJS >>> >>> node-1.2.0 >>> store-0.7.0 >>> >>> etc >>> >>> >>> >>> On Thu, Jul 16, 2015 at 10:42 AM, Luk?? Fry? >>> wrote: >>> >>>> I know there already is strong agreement, but my $0.02: >>>> >>>> I'm not convinced about AGJS and connection with server-side libraries. >>>> >>>> >>>> I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for >>>> client-side libs, >>>> >>>> AGPUSH, AGSYNC, are trackes for server-side technologies, >>>> >>>> >>>> consider this use case: if we build eventually a new server-side Swift >>>> node-sender library, we won't track it under AGIOS because Swift comes from >>>> iOS land. >>>> >>>> On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf >>> > wrote: >>>> >>>>> word up? >>>>> >>>>> >>>>> On Thursday, July 16, 2015, Daniel Bevenius >>>>> wrote: >>>>> >>>>>> +1 Sounds good >>>>>> >>>>>> On 15 July 2015 at 22:52, Daniel Passos wrote: >>>>>> >>>>>>> +1 >>>>>>> >>>>>>> On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira >>>>>> > wrote: >>>>>>> >>>>>>>> +1 makes more sense >>>>>>>> >>>>>>>> On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist < >>>>>>>> lholmqui at redhat.com> wrote: >>>>>>>> >>>>>>>>> Hello all, >>>>>>>>> >>>>>>>>> we've decided that it would probably be a good idea to move JIRA's >>>>>>>>> related to the node-sender to the AG-JS JIRA instead of having them on the >>>>>>>>> AGUSH JIRA. >>>>>>>>> >>>>>>>>> i think this makes a bit more sense since this a javascript >>>>>>>>> component. >>>>>>>>> >>>>>>>>> I've started to move open JIRA's over. i think i'll probably just >>>>>>>>> leave the existing JIRA's where they are, unless someone feels strongly. >>>>>>>>> >>>>>>>>> >>>>>>>>> I've also started to create some "component" versions similar to >>>>>>>>> the other projects. >>>>>>>>> >>>>>>>>> the main JS lib will still be just numbers, like 2.3.0, and for >>>>>>>>> the node-sender we will now have node-sender-0.8.0, for example >>>>>>>>> >>>>>>>>> >>>>>>>>> -Luke >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> -- Passos >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> Sent from Gmail Mobile >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> >> >> -- >> 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 >> > > > > -- > > -- > "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/20150716/302589eb/attachment.html From matzew at apache.org Fri Jul 17 03:59:38 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 17 Jul 2015 09:59:38 +0200 Subject: [aerogear-dev] Staging of beta.3 (was: Re: UnifiedPush Server: time for a 1.1.0-beta.3) Message-ID: Hi team, here is another beta release for the UPS 1.1.0, to stablize before we will hit our final: Details about the containing fixes and enhancements are in JIRA: https://issues.jboss.org/browse/AGPUSH/fixforversion/12326301/ Please test the staged release: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6061/ Like w/ the previous beta, please make sure you use a FULL profile WildFly or EAP server for tests, since we now have JMS hooks ;-) (See README for details) On Tuesday next week I'd like to press the button to release it to the wild. PS: I will be working on updating our Openshift cartridge later today... -M On Thu, Jul 16, 2015 at 5:01 PM, Sebastien Blanc wrote: > Ship it ! > > On Thu, Jul 16, 2015 at 4:59 PM, Matthias Wessendorf > wrote: > >> Hi, >> >> we had a few changes since the last beta: >> >> >> https://issues.jboss.org/issues/?jql=project%20%3D%20AGPUSH%20AND%20fixVersion%20%3D%20ups-1.1.0.final%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC >> >> I'd like to run another beta. >> >> The DB migrator is not yet there, but Dan and QMX are close on this. yay! >> >> >> So, in the spirit of release often / release early I see zero reasons to >> not do another beta. >> >> >> Any thoughts? >> >> >> >> >> >> -- >> 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/20150717/8b975840/attachment.html From matzew at apache.org Fri Jul 17 04:02:53 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 17 Jul 2015 10:02:53 +0200 Subject: [aerogear-dev] Staging of beta.3 (was: Re: UnifiedPush Server: time for a 1.1.0-beta.3) In-Reply-To: References: Message-ID: ... and the DIST is on GH marked as a pre-release https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.0-beta.3 -M On Fri, Jul 17, 2015 at 9:59 AM, Matthias Wessendorf wrote: > Hi team, > > here is another beta release for the UPS 1.1.0, to stablize before we will > hit our final: > Details about the containing fixes and enhancements are in JIRA: > https://issues.jboss.org/browse/AGPUSH/fixforversion/12326301/ > > Please test the staged release: > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6061/ > > Like w/ the previous beta, please make sure you use a FULL profile WildFly > or EAP server for tests, since we now have JMS hooks ;-) > (See README for details) > > On Tuesday next week I'd like to press the button to release it to the > wild. > > PS: I will be working on updating our Openshift cartridge later today... > > -M > > > > > On Thu, Jul 16, 2015 at 5:01 PM, Sebastien Blanc > wrote: > >> Ship it ! >> >> On Thu, Jul 16, 2015 at 4:59 PM, Matthias Wessendorf >> wrote: >> >>> Hi, >>> >>> we had a few changes since the last beta: >>> >>> >>> https://issues.jboss.org/issues/?jql=project%20%3D%20AGPUSH%20AND%20fixVersion%20%3D%20ups-1.1.0.final%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC >>> >>> I'd like to run another beta. >>> >>> The DB migrator is not yet there, but Dan and QMX are close on this. yay! >>> >>> >>> So, in the spirit of release often / release early I see zero reasons to >>> not do another beta. >>> >>> >>> Any thoughts? >>> >>> >>> >>> >>> >>> -- >>> 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 > -- 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/20150717/be85aede/attachment-0001.html From mfink at email.unc.edu Fri Jul 17 09:15:33 2015 From: mfink at email.unc.edu (Fink, Miles) Date: Fri, 17 Jul 2015 13:15:33 +0000 Subject: [aerogear-dev] UPS Node Sender client categories issue? In-Reply-To: References: Message-ID: Thanks Luke! You guys are awesome! -Miles From: Luke Holmquist > Reply-To: AeroGear Developer Mailing List > Date: Thursday, July 16, 2015 at 9:09 AM To: AeroGear Developer Mailing List > Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? This should be all set now, i released 0.7.1 on npm and here is the release on GH, https://github.com/aerogear/aerogear-unifiedpush-nodejs-client/releases/tag/0.7.1 On Wed, Jul 15, 2015 at 3:16 PM, Luke Holmquist > wrote: So i've sent PR's for this now, https://github.com/aerogear/aerogear-unifiedpush-nodejs-client/pull/21 and https://github.com/aerogear/aerogear-unifiedpush-nodejs-client/pull/20 first link is for the 0.7.x release and second is for master On Tue, Jul 14, 2015 at 11:23 AM, Luke Holmquist > wrote: On Tue, Jul 14, 2015 at 11:05 AM, Matthias Wessendorf > wrote: On Tue, Jul 14, 2015 at 4:28 PM, Luke Holmquist > wrote: JIRA'd https://issues.jboss.org/browse/AGPUSH-1468 Matzew, so for versioning of the node-sender, i wonder if we should add that "component" in the versions for JIRA similar to how sps has it's own versioning scheme. something like node-sender-0.7.0 , node-sender-0.8.0 ? something like that, would be easier to keep track of those releases. as i was writing this, i'm also thinking if these issues should be part of AG-JS and i can do the versions there? hmmm yeah - actually, I think you are right. I am absolutely fine w/ having the node-js-sender on AGJS. It's been a) a fairly stable component (lholmquist++) and b) our APIs are mostly JSON payload to a well-known endpoint - so not much to 'plan' from a AGPUSH / UPS perspective ok, sounds good. I will start adding things over there -M On Tue, Jul 14, 2015 at 8:56 AM, Fink, Miles > wrote: I'll see if I can?t get it in JIRA. Just to clarify, the issue I noticed regarding empty arrays was on the 0.7.x branch of Node Sender, so it may not be an issue in the latest branch. -Miles From: Matthias Wessendorf > Reply-To: AeroGear Developer Mailing List > Date: Tuesday, July 14, 2015 at 4:51 AM To: AeroGear Developer Mailing List > Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? Miles,Luke mind filing a JIRA issue for this ? On Thu, Jul 9, 2015 at 8:27 PM, Luke Holmquist > wrote: On Thu, Jul 9, 2015 at 2:15 PM, Fink, Miles > wrote: Thanks Luke. Using 0.7.0 version worked. I will note a couple items: 0.8.x uses applicationId (note Id), .0.7.x uses applicationID Also, I was sending empty arrays for the settings.criteria that I wasn?t using (deviceType, alias) which then still sent the notification to all installations regardless of the categories I was sending. After I removed all the empty arrays from criteria and just sent the categories array it worked! thanks for that input. sounds like a Bug! Anyway, thanks for the support! Much appreciated! Cheers, Miles From: Luke Holmquist > Reply-To: AeroGear Developer Mailing List > Date: Thursday, July 9, 2015 at 1:32 PM To: AeroGear Developer Mailing List > Subject: Re: [aerogear-dev] UPS Node Sender client categories issue? So i see you are using the 1.0.3 version of the UPS, could you try the 0.7.0 version of the node-sender and see if that works. The 0.8.x series is targeted for the 1.1.x UPS series which has had some message format changes On Thu, Jul 9, 2015 at 1:28 PM, Luke Holmquist > wrote: hey Miles, Thanks for using the UPS!! so i think what your seeing is probably similar to this issue, https://issues.jboss.org/browse/AGPUSH-1459 The Dashboard uses the Java Client Sender, so something is going on with the node one then thanks for putting your versions you are using, that should help narrow down things -Luke On Thu, Jul 9, 2015 at 1:22 PM, Fink, Miles > wrote: Hi, I?m just starting out with UPS (which is awesome btw!) and the Node.js sender client. One thing I?ve noticed is that a message sent from the dashboard with a particular category is sent to only those installations that have that category listed. This works great and is expected. I?m glad there is a way to target specific notification channels, etc. Sending a notification via the Node Sender client however appears to be sending to everyone?s installation regardless of the categories sent with the message. Here?s a pastie of what my node client call looks like: http://pastie.org/10282358 I?m using: Unifiedpush Node Sender version 0.8.0-beta1 UPS is the setup via the openshift cartridge, from https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push Any pointers would be greatly appreciated. Very well could be me doing it wrong? ;-) Thanks, Miles _______________________________________________ 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 _______________________________________________ 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/20150717/14ac1e65/attachment.html From matzew at apache.org Fri Jul 17 10:18:54 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 17 Jul 2015 16:18:54 +0200 Subject: [aerogear-dev] Staging of beta.3 (was: Re: UnifiedPush Server: time for a 1.1.0-beta.3) In-Reply-To: References: Message-ID: Hi guys, as promissed, here are some updates on Openshift for 1.1.0-beta.3: rhc create-app --gear-size medium --no-git YOUR_NAME " https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshift-origin-cartridge-aerogear-push&commit=653439039d69cd84b05dbc12506cf7fe2b146351 " PR: https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/20/files -Matthias On Fri, Jul 17, 2015 at 9:59 AM, Matthias Wessendorf wrote: > Hi team, > > here is another beta release for the UPS 1.1.0, to stablize before we will > hit our final: > Details about the containing fixes and enhancements are in JIRA: > https://issues.jboss.org/browse/AGPUSH/fixforversion/12326301/ > > Please test the staged release: > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6061/ > > Like w/ the previous beta, please make sure you use a FULL profile WildFly > or EAP server for tests, since we now have JMS hooks ;-) > (See README for details) > > On Tuesday next week I'd like to press the button to release it to the > wild. > > PS: I will be working on updating our Openshift cartridge later today... > > -M > > > > > On Thu, Jul 16, 2015 at 5:01 PM, Sebastien Blanc > wrote: > >> Ship it ! >> >> On Thu, Jul 16, 2015 at 4:59 PM, Matthias Wessendorf >> wrote: >> >>> Hi, >>> >>> we had a few changes since the last beta: >>> >>> >>> https://issues.jboss.org/issues/?jql=project%20%3D%20AGPUSH%20AND%20fixVersion%20%3D%20ups-1.1.0.final%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC >>> >>> I'd like to run another beta. >>> >>> The DB migrator is not yet there, but Dan and QMX are close on this. yay! >>> >>> >>> So, in the spirit of release often / release early I see zero reasons to >>> not do another beta. >>> >>> >>> Any thoughts? >>> >>> >>> >>> >>> >>> -- >>> 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 > -- 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/20150717/96942520/attachment-0001.html From matzew at apache.org Mon Jul 20 02:58:13 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 20 Jul 2015 08:58:13 +0200 Subject: [aerogear-dev] Parent: next release should be 0.3.0 ? Message-ID: Hi, current release is 0.2.16 - but we recently changed the JDK settings underneath: https://github.com/aerogear/aerogear-parent/pull/51 I'd like to release that, but was wondering if it would be better to release it as "0.3.0" - instead of 0.2.17. Any thoughts ? -- 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/20150720/ba1b32f8/attachment.html From matzew at apache.org Mon Jul 20 04:24:48 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 20 Jul 2015 10:24:48 +0200 Subject: [aerogear-dev] [RFC] future Roadmap for Unified Push Server In-Reply-To: References: Message-ID: On Thu, Jul 9, 2015 at 7:34 PM, Karel Piwko wrote: > > On Tue, Jul 7, 2015 at 11:51 PM, Matthias Wessendorf > wrote: > >> Hi team, >> >> as we are moving forward w/ the releases, and we are close to have our >> 1.1.0.Final, I started to think about a proposal for a near-term future >> roadmap, and I'd like to get feedback, comments (or tomatos) on it. >> UPS >> 1.1.x (July/August) >> >> - 1.1.0 -> very soon >> - 1.1.x -> perhaps some needed bug fixes/improvements, in a short >> interval :-) >> >> >> UPS >> 1.2.0 (September/October) >> >> We have a release version >> in JIRA >> already. >> >> *Key features* >> >> - Keycloak isolation >> - GCM 3 support (client and server) >> - Improved docker support (e.g. tests/test suite -> Hopefully Travis >> supports 'docker run' by than ;-)) >> >> One could think that going back to JPA annotations is a key feature as >> well ;-) >> >> UPS >> 1.2.x (or even 1.3.0) (December 2015) >> >> There is no concrete release version for this, but we have a larger >> ups-future >> version >> in JIRA. The ups-future version/label has a few interesting things, that we >> may have to do right after 1.2.0 >> >> *Key features* >> >> - APNs goes HTTP2 (a must) >> - Quiete time for push (aka timezone awareness of devices) >> - Scheduled pushes >> - Proxy server support >> >> +9001!!! > > >> UPS >> 2.0.0 (March-2016) >> >> In October (2015) the WildFly 10 >> should >> be released and I'd like to see us adapting this for the 2.0.0 series! Also >> for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x >> series! >> >> Do you plan to have automated migration path from 1.x series? E.g. Windup > tool support? > hrm - I have not thought about that. What will be the scope here? And how different would it be from the DB migrator work that QMX started ? > > >> *Note:* We don't have a release version for JIRA here, but heck! this >> mail is asking for feedback ;-) >> >> *Key features / Core changes* >> >> - UPS based on (public) APIs that are available in WildFly-10 >> - looking at using WF feature packs >> (similar to >> what Keycloak did, e.g. for layered "product" >> - looking at getting an UPS sub-system >> - Java8 only (as well as making sure works w/ Java9) >> - internal communication fully based on messaging (A-MQ / HornetQ) >> - WildFly-Swarm launcher (aka fat JARs) >> - helps with a more modular system: >> - Modular system (e.g. different ?webapps?, like "sender.war", >> "registration.war", "UI WAR" etc) >> - allows us to play with different platforms for the different >> ?web apps? >> - e.g. for a 2.x.y we could see/experiment how a vertx >> microservice (e.g. for the device registration) will behave in the larger >> system >> >> Other new features, e.g. based on needs and/or requests could be weaved >> into 2.0.0 or 2.0.x, based on timing. >> >> Please review this initial draft of a roadmap - once we are all in >> agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) >> >> Greetings, >> Matthias >> >> -- >> 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/20150720/ac1c3976/attachment.html From scm.blanc at gmail.com Mon Jul 20 04:48:42 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 20 Jul 2015 10:48:42 +0200 Subject: [aerogear-dev] Parent: next release should be 0.3.0 ? In-Reply-To: References: Message-ID: +1 JDK upgrade seems to be a good reason to bump to 0.3.0 On Mon, Jul 20, 2015 at 8:58 AM, Matthias Wessendorf wrote: > Hi, > > current release is 0.2.16 - but we recently changed the JDK settings > underneath: > https://github.com/aerogear/aerogear-parent/pull/51 > > I'd like to release that, but was wondering if it would be better to > release it as "0.3.0" - instead of 0.2.17. > > Any thoughts ? > > -- > 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/20150720/b4342809/attachment.html From matzew at apache.org Mon Jul 20 06:46:27 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 20 Jul 2015 12:46:27 +0200 Subject: [aerogear-dev] UPS JIRAs for future releases (was: Re: [RFC] future Roadmap for Unified Push Server) Message-ID: Hi guys, thanks for the feedback and the discussions. Here is a list of releases done after 1.1.0.Final (out early August). - 1.1.1 (end of August'15) - JIRA issues - 1.2.0 (end of September'15) - JIRA issues - 1.3.0 (early of December'15) - JIRA issues And moving forward with some more technical changes, we will have a 2.0.0 in 2016 - 2.0.0 (March 2016) - JIRA issues Feel free to comment either here or on the JIRAs, if something needs improvements or suggestions etc. Feedback is more than welcome! -Matthias On Tue, Jul 7, 2015 at 11:51 PM, Matthias Wessendorf wrote: > Hi team, > > as we are moving forward w/ the releases, and we are close to have our > 1.1.0.Final, I started to think about a proposal for a near-term future > roadmap, and I'd like to get feedback, comments (or tomatos) on it. > UPS > 1.1.x (July/August) > > - 1.1.0 -> very soon > - 1.1.x -> perhaps some needed bug fixes/improvements, in a short > interval :-) > > > UPS > 1.2.0 (September/October) > > We have a release version > in JIRA > already. > > *Key features* > > - Keycloak isolation > - GCM 3 support (client and server) > - Improved docker support (e.g. tests/test suite -> Hopefully Travis > supports 'docker run' by than ;-)) > > One could think that going back to JPA annotations is a key feature as > well ;-) > > UPS > 1.2.x (or even 1.3.0) (December 2015) > > There is no concrete release version for this, but we have a larger > ups-future version > in JIRA. The ups-future version/label has a few interesting things, that we > may have to do right after 1.2.0 > > *Key features* > > - APNs goes HTTP2 (a must) > - Quiete time for push (aka timezone awareness of devices) > - Scheduled pushes > - Proxy server support > > UPS > 2.0.0 (March-2016) > > In October (2015) the WildFly 10 > should > be released and I'd like to see us adapting this for the 2.0.0 series! Also > for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x > series! > > *Note:* We don't have a release version for JIRA here, but heck! this > mail is asking for feedback ;-) > > *Key features / Core changes* > > - UPS based on (public) APIs that are available in WildFly-10 > - looking at using WF feature packs > (similar to > what Keycloak did, e.g. for layered "product" > - looking at getting an UPS sub-system > - Java8 only (as well as making sure works w/ Java9) > - internal communication fully based on messaging (A-MQ / HornetQ) > - WildFly-Swarm launcher (aka fat JARs) > - helps with a more modular system: > - Modular system (e.g. different ?webapps?, like "sender.war", > "registration.war", "UI WAR" etc) > - allows us to play with different platforms for the different ?web > apps? > - e.g. for a 2.x.y we could see/experiment how a vertx microservice > (e.g. for the device registration) will behave in the larger system > > Other new features, e.g. based on needs and/or requests could be weaved > into 2.0.0 or 2.0.x, based on timing. > > Please review this initial draft of a roadmap - once we are all in > agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) > > Greetings, > Matthias > > -- > 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/20150720/b285ef50/attachment-0001.html From dpassos at redhat.com Mon Jul 20 08:47:56 2015 From: dpassos at redhat.com (Daniel Passos) Date: Mon, 20 Jul 2015 09:47:56 -0300 Subject: [aerogear-dev] Parent: next release should be 0.3.0 ? In-Reply-To: References: Message-ID: +1 for 0.3.0 On Mon, Jul 20, 2015 at 5:48 AM, Sebastien Blanc wrote: > +1 JDK upgrade seems to be a good reason to bump to 0.3.0 > > On Mon, Jul 20, 2015 at 8:58 AM, Matthias Wessendorf > wrote: > >> Hi, >> >> current release is 0.2.16 - but we recently changed the JDK settings >> underneath: >> https://github.com/aerogear/aerogear-parent/pull/51 >> >> I'd like to release that, but was wondering if it would be better to >> release it as "0.3.0" - instead of 0.2.17. >> >> Any thoughts ? >> >> -- >> 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 > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150720/755fe124/attachment.html From dpassos at redhat.com Mon Jul 20 16:13:50 2015 From: dpassos at redhat.com (Daniel Passos) Date: Mon, 20 Jul 2015 17:13:50 -0300 Subject: [aerogear-dev] What's new in AeroGear? Message-ID: iOS AeroGear Swift libs are progressing towards more platforms support. Last week, aerogear-ios-jsonsz has lower its minimal target deployment to iOS7 and a new swift-2.0 branch is available for iOS9 (beta3) support. What?s coming next? All AeroGear Swift libs will have a swift-2.0 branch (regularly rebased) until iOS9 is offically released, and will be finally merged in master. Android - 3.x roadmap proposal/discussion - http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Android-3-0-Roadmap-td11933.html - aerogear-android-plugin discussion - http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AGDroid-3-0-improvements-td11915.html - secondsun?s test repo : https://github.com/secondsun/aerogear-android-plugin - Push improvments - MERGED Migrating to InstanceID ( https://github.com/aerogear/aerogear-android-push/pull/43) - PR issued for Implementing InstanceIDListenerService ( https://github.com/aerogear/aerogear-android-push/pull/44) - GCM 3.0 JIRA should be done in time for UPS 1.2 ( https://issues.jboss.org/browse/AGDROID-433) UnifiedPush - Beta-3 release to help stabilization: http://lists.jboss.org/pipermail/aerogear-dev/2015-July/011874.html - Openshift update, using 1.1.0: https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/20 - Migrator work in progress Javascript - Small bug resolved in the Unified Push node sender - https://issues.jboss.org/browse/AGJS-293 - 0.7.1 released on npm ? -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150720/9cab6865/attachment.html From scm.blanc at gmail.com Tue Jul 21 03:24:29 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 21 Jul 2015 09:24:29 +0200 Subject: [aerogear-dev] UPS JIRAs for future releases (was: Re: [RFC] future Roadmap for Unified Push Server) In-Reply-To: References: Message-ID: On Mon, Jul 20, 2015 at 12:46 PM, Matthias Wessendorf wrote: > Hi guys, > > thanks for the feedback and the discussions. Here is a list of releases > done after 1.1.0.Final (out early August). > > - 1.1.1 (end of August'15) - JIRA issues > > - 1.2.0 (end of September'15) - JIRA issues > > - 1.3.0 (early of December'15) - JIRA issues > > > Geo stuff is included here, that is great. From the latest discussion and POC (end 2014), we decided that the geolocation should be an independant component/server that could of course "speak" with UPS but could also be used standalone (like I demonstrate in this screencast https://www.youtube.com/watch?v=R-qdLJh4EWQ). Should we relaunch the geo server in a separate thread ? And moving forward with some more technical changes, we will have a 2.0.0 > in 2016 > > - 2.0.0 (March 2016) - JIRA issues > > > Feel free to comment either here or on the JIRAs, if something needs > improvements or suggestions etc. Feedback is more than welcome! > > -Matthias > > On Tue, Jul 7, 2015 at 11:51 PM, Matthias Wessendorf > wrote: > >> Hi team, >> >> as we are moving forward w/ the releases, and we are close to have our >> 1.1.0.Final, I started to think about a proposal for a near-term future >> roadmap, and I'd like to get feedback, comments (or tomatos) on it. >> UPS >> 1.1.x (July/August) >> >> - 1.1.0 -> very soon >> - 1.1.x -> perhaps some needed bug fixes/improvements, in a short >> interval :-) >> >> >> UPS >> 1.2.0 (September/October) >> >> We have a release version >> in JIRA >> already. >> >> *Key features* >> >> - Keycloak isolation >> - GCM 3 support (client and server) >> - Improved docker support (e.g. tests/test suite -> Hopefully Travis >> supports 'docker run' by than ;-)) >> >> One could think that going back to JPA annotations is a key feature as >> well ;-) >> >> UPS >> 1.2.x (or even 1.3.0) (December 2015) >> >> There is no concrete release version for this, but we have a larger >> ups-future >> version >> in JIRA. The ups-future version/label has a few interesting things, that we >> may have to do right after 1.2.0 >> >> *Key features* >> >> - APNs goes HTTP2 (a must) >> - Quiete time for push (aka timezone awareness of devices) >> - Scheduled pushes >> - Proxy server support >> >> UPS >> 2.0.0 (March-2016) >> >> In October (2015) the WildFly 10 >> should >> be released and I'd like to see us adapting this for the 2.0.0 series! Also >> for a possible release of our 2.0.0 in March 2016, I?d like to stop the 1.x >> series! >> >> *Note:* We don't have a release version for JIRA here, but heck! this >> mail is asking for feedback ;-) >> >> *Key features / Core changes* >> >> - UPS based on (public) APIs that are available in WildFly-10 >> - looking at using WF feature packs >> (similar to >> what Keycloak did, e.g. for layered "product" >> - looking at getting an UPS sub-system >> - Java8 only (as well as making sure works w/ Java9) >> - internal communication fully based on messaging (A-MQ / HornetQ) >> - WildFly-Swarm launcher (aka fat JARs) >> - helps with a more modular system: >> - Modular system (e.g. different ?webapps?, like "sender.war", >> "registration.war", "UI WAR" etc) >> - allows us to play with different platforms for the different >> ?web apps? >> - e.g. for a 2.x.y we could see/experiment how a vertx >> microservice (e.g. for the device registration) will behave in the larger >> system >> >> Other new features, e.g. based on needs and/or requests could be weaved >> into 2.0.0 or 2.0.x, based on timing. >> >> Please review this initial draft of a roadmap - once we are all in >> agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-) >> >> Greetings, >> Matthias >> >> -- >> 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/20150721/81e9022c/attachment-0001.html From matzew at apache.org Tue Jul 21 09:25:44 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 21 Jul 2015 15:25:44 +0200 Subject: [aerogear-dev] UPS and Docker Message-ID: Hi, for UPS we have three different images, at: 1) unifiedpush-wildfly 2) unifiedpush-wildfly-dev 3) push-quickstarts-wildfly-dev The first deploys the latest stable (1.0.2) release on WildFly, using HTTPS. The second does a checkout of the UPS master repo, and also deploys it into WildFly, using HTTPS. The third one deploys our 'complex' CRUD quickstart, which we did for xpaas launch. I'd like to remove this, because that's a repo which will eventually go away. I could keep it, if there is really interest in it - but I prefer to remove it.... Now, the other two are currently broken, because there are some changes in the layer above us. The WildFly's parent parent :-) now is Centos7, not Fedora anymore. This is cool, since Centos is closer to RHEL and also used on Openshift-Origin. I have update the two Dockerfiles based on the underlying OS change, and I added deployment for UPS 1.1.0-beta.2 (our last release). Here is my branch: https://github.com/matzew/dockerfiles/tree/Centos7 Moving forward, I added support for MySQL using Docker container linking: https://github.com/matzew/dockerfiles/tree/Centos7_mysql NOTE: this requires two docker containers (named 'unifiedpush' and 'keycloak') being around. Here is a docker-compose.yml file allowing to run the entire shindig: https://gist.github.com/matzew/f99995e7c1d38ff7004c Any thoughts? -- 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/20150721/6fc51954/attachment.html From matzew at apache.org Tue Jul 21 14:50:54 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 21 Jul 2015 20:50:54 +0200 Subject: [aerogear-dev] UPS and Docker In-Reply-To: References: Message-ID: Sent the PR for the container linkage: https://github.com/aerogear/dockerfiles/pull/8 To some degree it also mimics hat openshift itself does, spinning up the different pods via Kubernetes, and using env. variables to access the inbound containers/pods -Matthias On Tue, Jul 21, 2015 at 3:25 PM, Matthias Wessendorf wrote: > Hi, > > for UPS we have three different images, at: > 1) unifiedpush-wildfly > 2) unifiedpush-wildfly-dev > 3) push-quickstarts-wildfly-dev > > The first deploys the latest stable (1.0.2) release on WildFly, using > HTTPS. The second does a checkout of the UPS master repo, and also deploys > it into WildFly, using HTTPS. > > > The third one deploys our 'complex' CRUD quickstart, which we did for > xpaas launch. I'd like to remove this, because that's a repo which will > eventually go away. > > I could keep it, if there is really interest in it - but I prefer to > remove it.... > > > Now, the other two are currently broken, because there are some changes in > the layer above us. The WildFly's parent parent :-) now is Centos7, not > Fedora anymore. This is cool, since Centos is closer to RHEL and also used > on Openshift-Origin. > > I have update the two Dockerfiles based on the underlying OS change, and I > added deployment for UPS 1.1.0-beta.2 (our last release). Here is my branch: > > https://github.com/matzew/dockerfiles/tree/Centos7 > > Moving forward, I added support for MySQL using Docker container linking: > https://github.com/matzew/dockerfiles/tree/Centos7_mysql > > NOTE: this requires two docker containers (named 'unifiedpush' and > 'keycloak') being around. Here is a docker-compose.yml file allowing to run > the entire shindig: > https://gist.github.com/matzew/f99995e7c1d38ff7004c > > > Any thoughts? > > > > -- > 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/20150721/dddd907b/attachment.html From dpassos at redhat.com Tue Jul 21 15:28:12 2015 From: dpassos at redhat.com (Daniel Passos) Date: Tue, 21 Jul 2015 16:28:12 -0300 Subject: [aerogear-dev] Outdate code snippet for Android in UPS Console Message-ID: Hey Guys, I just run UPS (from master) to test the Summers's PR[1] and figure out the Android register code is outdated[2], buuuuuut I remember I've fixed it months ago[3] Maybe I did it in the wrong place or anyone have any idea what happened? [1] https://github.com/aerogear/aerogear-android-push/pull/44 [2] http://take.ms/Yw9DA [3] https://github.com/aerogear/aerogear-unifiedpush-server/pull/524 -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150721/8da92b94/attachment.html From matzew at apache.org Tue Jul 21 15:54:34 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 21 Jul 2015 21:54:34 +0200 Subject: [aerogear-dev] Outdate code snippet for Android in UPS Console In-Reply-To: References: Message-ID: not sure :-( perhaps wanna send a new PR ? I think it has been an accidential override or so, w// the new UI: https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/admin-ui/app/snippets/register-device/android.java On Tue, Jul 21, 2015 at 9:28 PM, Daniel Passos wrote: > Hey Guys, > > I just run UPS (from master) to test the Summers's PR[1] and figure out > the Android register code is outdated[2], buuuuuut I remember I've fixed it > months ago[3] > > Maybe I did it in the wrong place or anyone have any idea what happened? > > [1] https://github.com/aerogear/aerogear-android-push/pull/44 > [2] http://take.ms/Yw9DA > [3] https://github.com/aerogear/aerogear-unifiedpush-server/pull/524 > > -- > -- Passos > > _______________________________________________ > 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/20150721/8c55fe12/attachment.html From dpassos at redhat.com Tue Jul 21 16:12:19 2015 From: dpassos at redhat.com (Daniel Passos) Date: Tue, 21 Jul 2015 17:12:19 -0300 Subject: [aerogear-dev] Outdate code snippet for Android in UPS Console In-Reply-To: References: Message-ID: np at all, just checking. We always can copy and paste PRs :P I'll send it asap On Tue, Jul 21, 2015 at 4:54 PM, Matthias Wessendorf wrote: > not sure :-( > > perhaps wanna send a new PR ? > > I think it has been an accidential override or so, w// the new UI: > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/admin-ui/app/snippets/register-device/android.java > > > > On Tue, Jul 21, 2015 at 9:28 PM, Daniel Passos wrote: > >> Hey Guys, >> >> I just run UPS (from master) to test the Summers's PR[1] and figure out >> the Android register code is outdated[2], buuuuuut I remember I've fixed it >> months ago[3] >> >> Maybe I did it in the wrong place or anyone have any idea what happened? >> >> [1] https://github.com/aerogear/aerogear-android-push/pull/44 >> [2] http://take.ms/Yw9DA >> [3] https://github.com/aerogear/aerogear-unifiedpush-server/pull/524 >> >> -- >> -- Passos >> >> _______________________________________________ >> 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 > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150721/63bfac96/attachment-0001.html From matzew at apache.org Tue Jul 21 16:13:25 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 21 Jul 2015 22:13:25 +0200 Subject: [aerogear-dev] Outdate code snippet for Android in UPS Console In-Reply-To: References: Message-ID: LOL yeah :) sorry for that inconvenience ! On Tue, Jul 21, 2015 at 10:12 PM, Daniel Passos wrote: > np at all, just checking. We always can copy and paste PRs :P > > I'll send it asap > > On Tue, Jul 21, 2015 at 4:54 PM, Matthias Wessendorf > wrote: > >> not sure :-( >> >> perhaps wanna send a new PR ? >> >> I think it has been an accidential override or so, w// the new UI: >> >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/admin-ui/app/snippets/register-device/android.java >> >> >> >> On Tue, Jul 21, 2015 at 9:28 PM, Daniel Passos >> wrote: >> >>> Hey Guys, >>> >>> I just run UPS (from master) to test the Summers's PR[1] and figure out >>> the Android register code is outdated[2], buuuuuut I remember I've fixed it >>> months ago[3] >>> >>> Maybe I did it in the wrong place or anyone have any idea what happened? >>> >>> [1] https://github.com/aerogear/aerogear-android-push/pull/44 >>> [2] http://take.ms/Yw9DA >>> [3] https://github.com/aerogear/aerogear-unifiedpush-server/pull/524 >>> >>> -- >>> -- Passos >>> >>> _______________________________________________ >>> 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 >> > > > > -- > -- Passos > > _______________________________________________ > 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/20150721/0ff3143b/attachment.html From dpassos at redhat.com Wed Jul 22 09:25:57 2015 From: dpassos at redhat.com (Daniel Passos) Date: Wed, 22 Jul 2015 10:25:57 -0300 Subject: [aerogear-dev] Outdate code snippet for Android in UPS Console In-Reply-To: References: Message-ID: PR sent: https://github.com/aerogear/aerogear-unifiedpush-server/pull/620 On Tue, Jul 21, 2015 at 5:13 PM, Matthias Wessendorf wrote: > LOL yeah :) > > sorry for that inconvenience ! > > On Tue, Jul 21, 2015 at 10:12 PM, Daniel Passos > wrote: > >> np at all, just checking. We always can copy and paste PRs :P >> >> I'll send it asap >> >> On Tue, Jul 21, 2015 at 4:54 PM, Matthias Wessendorf >> wrote: >> >>> not sure :-( >>> >>> perhaps wanna send a new PR ? >>> >>> I think it has been an accidential override or so, w// the new UI: >>> >>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/admin-ui/app/snippets/register-device/android.java >>> >>> >>> >>> On Tue, Jul 21, 2015 at 9:28 PM, Daniel Passos >>> wrote: >>> >>>> Hey Guys, >>>> >>>> I just run UPS (from master) to test the Summers's PR[1] and figure out >>>> the Android register code is outdated[2], buuuuuut I remember I've fixed it >>>> months ago[3] >>>> >>>> Maybe I did it in the wrong place or anyone have any idea what happened? >>>> >>>> [1] https://github.com/aerogear/aerogear-android-push/pull/44 >>>> [2] http://take.ms/Yw9DA >>>> [3] https://github.com/aerogear/aerogear-unifiedpush-server/pull/524 >>>> >>>> -- >>>> -- Passos >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> >> >> -- >> -- Passos >> >> _______________________________________________ >> 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 > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150722/c8d55cb5/attachment.html From supittma at redhat.com Wed Jul 22 10:54:33 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 22 Jul 2015 10:54:33 -0400 Subject: [aerogear-dev] AGDroid Gradle plugin Message-ID: So in those awkward moments when I'm waiting on PRs to get reviewed I've been working on a Gradle plugin for AGDroid. https://github.com/secondsun/aerogear-android-plugin Right now it doesn't do much other than fail a couple of unit tests, but my first goal is to have it validate the AndroidManifest file if it detects a push config file. After that I would like it to be able to autoconfigure the manifest if it finds errors. Eventually I would like to be able to do basic annotation processing to simplify lots of rote tasks in Android. What would you guys like to see added? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150722/6e381f78/attachment.html From matzew at apache.org Wed Jul 22 11:00:59 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 22 Jul 2015 17:00:59 +0200 Subject: [aerogear-dev] AGDroid Gradle plugin In-Reply-To: References: Message-ID: Awesome stuff, summers! should we - at somepoint - import it into aerogear org? Or wanna keep it on your GH account? On Wed, Jul 22, 2015 at 4:54 PM, Summers Pittman wrote: > So in those awkward moments when I'm waiting on PRs to get reviewed I've > been working on a Gradle plugin for AGDroid. > > https://github.com/secondsun/aerogear-android-plugin > > Right now it doesn't do much other than fail a couple of unit tests, but > my first goal is to have it validate the AndroidManifest file if it detects > a push config file. After that I would like it to be able to autoconfigure > the manifest if it finds errors. Eventually I would like to be able to do > basic annotation processing to simplify lots of rote tasks in Android. > > What would you guys like to see added? > > _______________________________________________ > 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/20150722/6291841b/attachment-0001.html From edewit at redhat.com Wed Jul 22 11:26:31 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 22 Jul 2015 17:26:31 +0200 Subject: [aerogear-dev] Windows support aerogear push plugin Message-ID: Hi, As Fabio Turizo pointed out [1] it would be nice if the push plugin also supported cordova windows store apps. I'm pleased to announce that there is a PR that enables this functionality [2]. If you feel bold you can try it out. [1] http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Using-Aerogear-PushPlugin-with-Phonegap-Build-td128.html [2] https://github.com/aerogear/aerogear-cordova-push/pull/75 [3] https://www.dropbox.com/s/lr9dfwkbfk907u4/Screenshot%202015-07-22%2016.27.32.png?dl=0 -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150722/cffa0bc1/attachment.html From supittma at redhat.com Wed Jul 22 11:52:08 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 22 Jul 2015 11:52:08 -0400 Subject: [aerogear-dev] AGDroid Gradle plugin In-Reply-To: References: Message-ID: On Wed, Jul 22, 2015 at 11:00 AM, Matthias Wessendorf wrote: > Awesome stuff, summers! > > should we - at somepoint - import it into aerogear org? Or wanna keep it > on your GH account? > If the community finds it useful we should import it. If the community doesn't I will probably wander off from it after a while. > On Wed, Jul 22, 2015 at 4:54 PM, Summers Pittman > wrote: > >> So in those awkward moments when I'm waiting on PRs to get reviewed I've >> been working on a Gradle plugin for AGDroid. >> >> https://github.com/secondsun/aerogear-android-plugin >> >> Right now it doesn't do much other than fail a couple of unit tests, but >> my first goal is to have it validate the AndroidManifest file if it detects >> a push config file. After that I would like it to be able to autoconfigure >> the manifest if it finds errors. Eventually I would like to be able to do >> basic annotation processing to simplify lots of rote tasks in Android. >> >> What would you guys like to see added? >> >> _______________________________________________ >> 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/20150722/e9db4d86/attachment.html From smikloso at redhat.com Thu Jul 23 10:15:26 2015 From: smikloso at redhat.com (Stefan Miklosovic) Date: Thu, 23 Jul 2015 16:15:26 +0200 Subject: [aerogear-dev] Staging of beta.3 (was: Re: UnifiedPush Server: time for a 1.1.0-beta.3) In-Reply-To: References: Message-ID: Hi there, I am mostly tracking the notes for Beta2. I'll comment only on the issues relevant to this release. 1. While sending push notification from the browser, there is "No variants" in variant selection by default. When I do not select any variant, the message is sent to all variants. It should be renamed to "All variants" instead "No variants" or it should be said that when nothing is chosen, by default it will be sent everywhere. - "All variants" label is used, I consider this to be resolved. 2. For some reason there is a lot of space in the bottom and I can scroll away all the content - minor issue. - resolved Bugs: 1. After adding variant for simple push in the wizard, all links on that variant page are dead - they do not do anything. - resolved UI/UX Quirks 1. When hitting the Edit variant button, it shows a dialog where I can change only the name of the variant. However when I click the Change network options button, I am presented with the possibility to change both the name of the variant and the network specific configuration. I would therefore suggest to not show the name field in the Change network options dialog as it is not considered a good practise to have two ways of doing the same thing in UI. - this is repaired and name can be changed only via "edit name" link Setup: I tried it on Wildfly 9.0.0.Final and 8.2.0.Final with MySQL as well as with Postgres. I tried helloworld quickstart on Android tablet, pushes arrived without problems. It was overall smooth experience and I did it at the first shot. I love the UI. I exercised the UI quite a lot and I do not encounter any usability nor performance issue. I am overall satisfied with this release and I do not raise any significant objections which would prevent the release of 1.1.0-beta.3 of UPS. I submitted two additional JIRAs for this release: https://issues.jboss.org/browse/AGPUSH-1484 https://issues.jboss.org/browse/AGPUSH-1485 I focused only on Android. Tomas Hradec should cover iOS. Regards On Fri, Jul 17, 2015 at 9:59 AM, Matthias Wessendorf wrote: > Hi team, > > here is another beta release for the UPS 1.1.0, to stablize before we will > hit our final: > Details about the containing fixes and enhancements are in JIRA: > https://issues.jboss.org/browse/AGPUSH/fixforversion/12326301/ > > Please test the staged release: > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6061/ > > Like w/ the previous beta, please make sure you use a FULL profile WildFly > or EAP server for tests, since we now have JMS hooks ;-) > (See README for details) > > On Tuesday next week I'd like to press the button to release it to the wild. > > PS: I will be working on updating our Openshift cartridge later today... > > -M > > > > > On Thu, Jul 16, 2015 at 5:01 PM, Sebastien Blanc > wrote: >> >> Ship it ! >> >> On Thu, Jul 16, 2015 at 4:59 PM, Matthias Wessendorf >> wrote: >>> >>> Hi, >>> >>> we had a few changes since the last beta: >>> >>> >>> https://issues.jboss.org/issues/?jql=project%20%3D%20AGPUSH%20AND%20fixVersion%20%3D%20ups-1.1.0.final%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC >>> >>> I'd like to run another beta. >>> >>> The DB migrator is not yet there, but Dan and QMX are close on this. yay! >>> >>> >>> So, in the spirit of release often / release early I see zero reasons to >>> not do another beta. >>> >>> >>> Any thoughts? >>> >>> >>> >>> >>> >>> -- >>> 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 -- Stefan Miklosovic Red Hat Brno - JBoss Mobile Platform e-mail: smikloso at redhat.com irc: smikloso From matzew at apache.org Thu Jul 23 12:26:16 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 23 Jul 2015 18:26:16 +0200 Subject: [aerogear-dev] Staging of beta.3 (was: Re: UnifiedPush Server: time for a 1.1.0-beta.3) In-Reply-To: References: Message-ID: Thanks, Stefan! for iOS I was having a hangout w/ Tomas, and Karel. He has issues w/ his .p12 file, and setup w/ Apple at large. We used my .p12 and devices, locally (my machine) and also on OpenShift. Tomas is working on getting his Apple setup fixed for the .Final testing. With that, I will release the beta.3 into the wild. Thanks! -Matthias On Thu, Jul 23, 2015 at 4:15 PM, Stefan Miklosovic wrote: > Hi there, > > I am mostly tracking the notes for Beta2. I'll comment only on the > issues relevant to this release. > > 1. While sending push notification from the browser, there is "No > variants" in variant selection by default. When I do not select any > variant, the message is sent to all variants. It should be renamed to > "All variants" instead "No variants" or it should be said that when > nothing is chosen, by default it will be sent everywhere. > > - "All variants" label is used, I consider this to be resolved. > > 2. For some reason there is a lot of space in the bottom and I can > scroll away all the content - minor issue. > > - resolved > > Bugs: > > 1. After adding variant for simple push in the wizard, all links on > that variant page are dead - they do not do anything. > > - resolved > > UI/UX Quirks > > 1. When hitting the Edit variant button, it shows a dialog where I can > change only the name of the variant. However when I click the Change > network options button, I am presented with the possibility to change > both the name of the variant and the network specific configuration. I > would therefore suggest to not show the name field in the Change > network options dialog as it is not considered a good practise to have > two ways of doing the same thing in UI. > > - this is repaired and name can be changed only via "edit name" link > > Setup: > > I tried it on Wildfly 9.0.0.Final and 8.2.0.Final with MySQL as well > as with Postgres. > > I tried helloworld quickstart on Android tablet, pushes arrived > without problems. It was overall smooth experience and I did it at the > first shot. > > I love the UI. I exercised the UI quite a lot and I do not encounter any > usability nor performance issue. > > I am overall satisfied with this release and I do not raise any > significant objections which would prevent the release of 1.1.0-beta.3 > of UPS. > > I submitted two additional JIRAs for this release: > > https://issues.jboss.org/browse/AGPUSH-1484 > https://issues.jboss.org/browse/AGPUSH-1485 > > I focused only on Android. Tomas Hradec should cover iOS. > > Regards > > On Fri, Jul 17, 2015 at 9:59 AM, Matthias Wessendorf > wrote: > > Hi team, > > > > here is another beta release for the UPS 1.1.0, to stablize before we > will > > hit our final: > > Details about the containing fixes and enhancements are in JIRA: > > https://issues.jboss.org/browse/AGPUSH/fixforversion/12326301/ > > > > Please test the staged release: > > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6061/ > > > > Like w/ the previous beta, please make sure you use a FULL profile > WildFly > > or EAP server for tests, since we now have JMS hooks ;-) > > (See README for details) > > > > On Tuesday next week I'd like to press the button to release it to the > wild. > > > > PS: I will be working on updating our Openshift cartridge later today... > > > > -M > > > > > > > > > > On Thu, Jul 16, 2015 at 5:01 PM, Sebastien Blanc > > wrote: > >> > >> Ship it ! > >> > >> On Thu, Jul 16, 2015 at 4:59 PM, Matthias Wessendorf > > >> wrote: > >>> > >>> Hi, > >>> > >>> we had a few changes since the last beta: > >>> > >>> > >>> > https://issues.jboss.org/issues/?jql=project%20%3D%20AGPUSH%20AND%20fixVersion%20%3D%20ups-1.1.0.final%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC > >>> > >>> I'd like to run another beta. > >>> > >>> The DB migrator is not yet there, but Dan and QMX are close on this. > yay! > >>> > >>> > >>> So, in the spirit of release often / release early I see zero reasons > to > >>> not do another beta. > >>> > >>> > >>> Any thoughts? > >>> > >>> > >>> > >>> > >>> > >>> -- > >>> 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 > > > > -- > Stefan Miklosovic > Red Hat Brno - JBoss Mobile Platform > > e-mail: smikloso at redhat.com > irc: smikloso > _______________________________________________ > 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/20150723/b8b1fdaf/attachment-0001.html From supittma at redhat.com Thu Jul 23 16:51:13 2015 From: supittma at redhat.com (Summers Pittman) Date: Thu, 23 Jul 2015 16:51:13 -0400 Subject: [aerogear-dev] Android topic messaging enhancements (AGDROID-470) Message-ID: So good news, Topic support for GCM is trivial to implement. In fact after 20 minutes I have most of the work done in the Android library. The behavior of topics matches the behavior of categories. I would like to propose some enhancements. 1) Changing categories/topics currently requires the application to unregister and reregister on UPS. I would like to add a subscribe and unsubscibe method to the pushRegistrar interface which will subscribe and unsubscribe the device from topics. 2) All Message listeners receive messages from all topics the device is subscribed to. I would like to extend registrar manager to be able to attach messages handlers per topic as well as globally. This are both simple, easy changes which shouldn't be a lot of work and will really improve the push experience in Agdroid 3.0. wdyt? Summers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150723/e6aeda0a/attachment.html From edewit at redhat.com Fri Jul 24 03:54:45 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 24 Jul 2015 09:54:45 +0200 Subject: [aerogear-dev] Android topic messaging enhancements (AGDROID-470) In-Reply-To: References: Message-ID: I like the idea of having listeners per topic, in fact some users have asked for this feature maybe we could add it to the other libs as well? All we have to do is send the category as part of the message (for platforms that are not android) so that the client can invoke the specific category listener. On Thu, Jul 23, 2015 at 10:51 PM, Summers Pittman wrote: > So good news, > > Topic support for GCM is trivial to implement. In fact after 20 minutes I > have most of the work done in the Android library. The behavior of topics > matches the behavior of categories. I would like to propose some > enhancements. > > 1) Changing categories/topics currently requires the application to > unregister and reregister on UPS. I would like to add a subscribe and > unsubscibe method to the pushRegistrar interface which will subscribe and > unsubscribe the device from topics. > > 2) All Message listeners receive messages from all topics the device is > subscribed to. I would like to extend registrar manager to be able to > attach messages handlers per topic as well as globally. > > This are both simple, easy changes which shouldn't be a lot of work and > will really improve the push experience in Agdroid 3.0. > > wdyt? > > Summers > > _______________________________________________ > 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/20150724/ba8c6616/attachment.html From thradec at gmail.com Fri Jul 24 04:06:31 2015 From: thradec at gmail.com (=?UTF-8?B?VG9tw6HFoSBIcmFkZWM=?=) Date: Fri, 24 Jul 2015 10:06:31 +0200 Subject: [aerogear-dev] Staging of beta.3 (was: Re: UnifiedPush Server: time for a 1.1.0-beta.3) In-Reply-To: References: Message-ID: Hi, after purchasing own apple developer account and setting everything from scratch, it works very smoothly. Thanks Matthias for assistance! Regards Tomas 2015-07-23 18:26 GMT+02:00 Matthias Wessendorf : > Thanks, Stefan! > > for iOS I was having a hangout w/ Tomas, and Karel. He has issues w/ his > .p12 file, and setup w/ Apple at large. We used my .p12 and devices, > locally (my machine) and also on OpenShift. > > Tomas is working on getting his Apple setup fixed for the .Final testing. > > With that, I will release the beta.3 into the wild. > > Thanks! > -Matthias > > On Thu, Jul 23, 2015 at 4:15 PM, Stefan Miklosovic > wrote: > >> Hi there, >> >> I am mostly tracking the notes for Beta2. I'll comment only on the >> issues relevant to this release. >> >> 1. While sending push notification from the browser, there is "No >> variants" in variant selection by default. When I do not select any >> variant, the message is sent to all variants. It should be renamed to >> "All variants" instead "No variants" or it should be said that when >> nothing is chosen, by default it will be sent everywhere. >> >> - "All variants" label is used, I consider this to be resolved. >> >> 2. For some reason there is a lot of space in the bottom and I can >> scroll away all the content - minor issue. >> >> - resolved >> >> Bugs: >> >> 1. After adding variant for simple push in the wizard, all links on >> that variant page are dead - they do not do anything. >> >> - resolved >> >> UI/UX Quirks >> >> 1. When hitting the Edit variant button, it shows a dialog where I can >> change only the name of the variant. However when I click the Change >> network options button, I am presented with the possibility to change >> both the name of the variant and the network specific configuration. I >> would therefore suggest to not show the name field in the Change >> network options dialog as it is not considered a good practise to have >> two ways of doing the same thing in UI. >> >> - this is repaired and name can be changed only via "edit name" link >> >> Setup: >> >> I tried it on Wildfly 9.0.0.Final and 8.2.0.Final with MySQL as well >> as with Postgres. >> >> I tried helloworld quickstart on Android tablet, pushes arrived >> without problems. It was overall smooth experience and I did it at the >> first shot. >> >> I love the UI. I exercised the UI quite a lot and I do not encounter any >> usability nor performance issue. >> >> I am overall satisfied with this release and I do not raise any >> significant objections which would prevent the release of 1.1.0-beta.3 >> of UPS. >> >> I submitted two additional JIRAs for this release: >> >> https://issues.jboss.org/browse/AGPUSH-1484 >> https://issues.jboss.org/browse/AGPUSH-1485 >> >> I focused only on Android. Tomas Hradec should cover iOS. >> >> Regards >> >> On Fri, Jul 17, 2015 at 9:59 AM, Matthias Wessendorf >> wrote: >> > Hi team, >> > >> > here is another beta release for the UPS 1.1.0, to stablize before we >> will >> > hit our final: >> > Details about the containing fixes and enhancements are in JIRA: >> > https://issues.jboss.org/browse/AGPUSH/fixforversion/12326301/ >> > >> > Please test the staged release: >> > >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6061/ >> > >> > Like w/ the previous beta, please make sure you use a FULL profile >> WildFly >> > or EAP server for tests, since we now have JMS hooks ;-) >> > (See README for details) >> > >> > On Tuesday next week I'd like to press the button to release it to the >> wild. >> > >> > PS: I will be working on updating our Openshift cartridge later today... >> > >> > -M >> > >> > >> > >> > >> > On Thu, Jul 16, 2015 at 5:01 PM, Sebastien Blanc >> > wrote: >> >> >> >> Ship it ! >> >> >> >> On Thu, Jul 16, 2015 at 4:59 PM, Matthias Wessendorf < >> matzew at apache.org> >> >> wrote: >> >>> >> >>> Hi, >> >>> >> >>> we had a few changes since the last beta: >> >>> >> >>> >> >>> >> https://issues.jboss.org/issues/?jql=project%20%3D%20AGPUSH%20AND%20fixVersion%20%3D%20ups-1.1.0.final%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC >> >>> >> >>> I'd like to run another beta. >> >>> >> >>> The DB migrator is not yet there, but Dan and QMX are close on this. >> yay! >> >>> >> >>> >> >>> So, in the spirit of release often / release early I see zero reasons >> to >> >>> not do another beta. >> >>> >> >>> >> >>> Any thoughts? >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> -- >> >>> 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 >> >> >> >> -- >> Stefan Miklosovic >> Red Hat Brno - JBoss Mobile Platform >> >> e-mail: smikloso at redhat.com >> irc: smikloso >> _______________________________________________ >> 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/20150724/a77b1d01/attachment-0001.html From matzew at apache.org Fri Jul 24 04:58:27 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 24 Jul 2015 10:58:27 +0200 Subject: [aerogear-dev] UPS 1.1.0-beta.3 and Openshift release Message-ID: Hello folks! On our way to 1.1.0.Final, we have released another beta release. This release contains a new Keycloak version (1.3.1) and a lot of small improvements. List of JIRAs https://issues.jboss.org/browse/AGPUSH/fixforversion/12326301 The release has been uploaded to Maven Central: http://search.maven.org/#search%7Cga%7C1%7Cunifiedpush It's, as usually, available on github too: https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.0-beta.3 Openshift update: As we move towards 1.1.0, the Openshift cartridge has been updated too. It's the first time 1.1.0 is available on Openshift: https://github.com/aerogear/openshift-origin-cartridge-aerogear-push#installation Greetings, Matthias On Fri, Jul 17, 2015 at 4:18 PM, Matthias Wessendorf wrote: > Hi guys, > > > as promissed, here are some updates on Openshift for 1.1.0-beta.3: > > rhc create-app --gear-size medium --no-git YOUR_NAME " > https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshift-origin-cartridge-aerogear-push&commit=653439039d69cd84b05dbc12506cf7fe2b146351 > " > > PR: > https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/20/files > > -Matthias > > On Fri, Jul 17, 2015 at 9:59 AM, Matthias Wessendorf > wrote: > >> Hi team, >> >> here is another beta release for the UPS 1.1.0, to stablize before we >> will hit our final: >> Details about the containing fixes and enhancements are in JIRA: >> https://issues.jboss.org/browse/AGPUSH/fixforversion/12326301/ >> >> Please test the staged release: >> >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6061/ >> >> Like w/ the previous beta, please make sure you use a FULL profile >> WildFly or EAP server for tests, since we now have JMS hooks ;-) >> (See README for details) >> >> On Tuesday next week I'd like to press the button to release it to the >> wild. >> >> PS: I will be working on updating our Openshift cartridge later today... >> >> -M >> >> >> >> >> On Thu, Jul 16, 2015 at 5:01 PM, Sebastien Blanc >> wrote: >> >>> Ship it ! >>> >>> On Thu, Jul 16, 2015 at 4:59 PM, Matthias Wessendorf >>> wrote: >>> >>>> Hi, >>>> >>>> we had a few changes since the last beta: >>>> >>>> >>>> https://issues.jboss.org/issues/?jql=project%20%3D%20AGPUSH%20AND%20fixVersion%20%3D%20ups-1.1.0.final%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC >>>> >>>> I'd like to run another beta. >>>> >>>> The DB migrator is not yet there, but Dan and QMX are close on this. >>>> yay! >>>> >>>> >>>> So, in the spirit of release often / release early I see zero reasons >>>> to not do another beta. >>>> >>>> >>>> Any thoughts? >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> 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 >> > > > > -- > 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/20150724/d0f9ea50/attachment.html From matzew at apache.org Sat Jul 25 05:24:01 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Sat, 25 Jul 2015 11:24:01 +0200 Subject: [aerogear-dev] Android topic messaging enhancements (AGDROID-470) In-Reply-To: References: Message-ID: sorry for the late response ;-) On Thu, Jul 23, 2015 at 10:51 PM, Summers Pittman wrote: > So good news, > > Topic support for GCM is trivial to implement. In fact after 20 minutes I > have most of the work done in the Android library. The behavior of topics > matches the behavior of categories. I would like to propose some > enhancements. > yay > > 1) Changing categories/topics currently requires the application to > unregister and reregister on UPS. I would like to add a subscribe and > unsubscibe method to the pushRegistrar interface which will subscribe and > unsubscribe the device from topics. > Ok, makes sense. Actually I like the idea. Should this be done on the other SDKs too? If so... does it make sense to change the RESTful endpoint to? e.g. do a PUT to update the device metadata? I recall we kinda had this talk before. See: https://issues.jboss.org/browse/AGPUSH-1399 > > 2) All Message listeners receive messages from all topics the device is > subscribed to. I would like to extend registrar manager to be able to > attach messages handlers per topic as well as globally. > Due to the nature of the Android layer around GCM 3, this is specific to Android only, right ? +1 on this. Same reasoning like Erik Jan here :) > > This are both simple, easy changes which shouldn't be a lot of work and > will really improve the push experience in Agdroid 3.0. > > wdyt? > bring it on :) > > Summers > > _______________________________________________ > 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/20150725/71ccf1ac/attachment.html From supittma at redhat.com Sat Jul 25 19:39:28 2015 From: supittma at redhat.com (Summers Pittman) Date: Sat, 25 Jul 2015 19:39:28 -0400 Subject: [aerogear-dev] Android topic messaging enhancements (AGDROID-470) In-Reply-To: References: Message-ID: On Sat, Jul 25, 2015 at 5:24 AM, Matthias Wessendorf wrote: > sorry for the late response ;-) > > On Thu, Jul 23, 2015 at 10:51 PM, Summers Pittman > wrote: > >> So good news, >> >> Topic support for GCM is trivial to implement. In fact after 20 minutes >> I have most of the work done in the Android library. The behavior of >> topics matches the behavior of categories. I would like to propose some >> enhancements. >> > > yay > > >> >> 1) Changing categories/topics currently requires the application to >> unregister and reregister on UPS. I would like to add a subscribe and >> unsubscibe method to the pushRegistrar interface which will subscribe and >> unsubscribe the device from topics. >> > > Ok, makes sense. Actually I like the idea. Should this be done on the > other SDKs too? If so... does it make sense to change the RESTful endpoint > to? e.g. do a PUT to update the device metadata? > So strictly speaking we don't need to have GCM 3 Android register its categories with UPS. Google can handle those. How are we handling compatibility? Would it be weird if 1.2 of UPS requires ADroid push 3.0? > I recall we kinda had this talk before. See: > https://issues.jboss.org/browse/AGPUSH-1399 > > >> >> 2) All Message listeners receive messages from all topics the device is >> subscribed to. I would like to extend registrar manager to be able to >> attach messages handlers per topic as well as globally. >> > > Due to the nature of the Android layer around GCM 3, this is specific to > Android only, right ? > I don't know enough about iOS, sorry :( > > +1 on this. Same reasoning like Erik Jan here :) > > >> >> This are both simple, easy changes which shouldn't be a lot of work and >> will really improve the push experience in Agdroid 3.0. >> >> wdyt? >> > > bring it on :) > > >> >> Summers >> >> _______________________________________________ >> 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/20150725/21720103/attachment-0001.html From matzew at apache.org Mon Jul 27 03:46:37 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 27 Jul 2015 09:46:37 +0200 Subject: [aerogear-dev] Android topic messaging enhancements (AGDROID-470) In-Reply-To: References: Message-ID: On Sun, Jul 26, 2015 at 1:39 AM, Summers Pittman wrote: > > > On Sat, Jul 25, 2015 at 5:24 AM, Matthias Wessendorf > wrote: > >> sorry for the late response ;-) >> >> On Thu, Jul 23, 2015 at 10:51 PM, Summers Pittman >> wrote: >> >>> So good news, >>> >>> Topic support for GCM is trivial to implement. In fact after 20 minutes >>> I have most of the work done in the Android library. The behavior of >>> topics matches the behavior of categories. I would like to propose some >>> enhancements. >>> >> >> yay >> >> >>> >>> 1) Changing categories/topics currently requires the application to >>> unregister and reregister on UPS. I would like to add a subscribe and >>> unsubscibe method to the pushRegistrar interface which will subscribe and >>> unsubscribe the device from topics. >>> >> >> Ok, makes sense. Actually I like the idea. Should this be done on the >> other SDKs too? If so... does it make sense to change the RESTful endpoint >> to? e.g. do a PUT to update the device metadata? >> > > So strictly speaking we don't need to have GCM 3 Android register its > categories with UPS. Google can handle those. > yeah, but we need the info on the UPS for a bunch of reasons... (e.g. only 1m devices per topic allowed). I think this is very easy to translate to our existing categories... > > How are we handling compatibility? > What do you mean here? > Would it be weird if 1.2 of UPS requires ADroid push 3.0? > Well, I do not think this is a problem. the 1.1.0 also requires AGDroid2, due to analytic support. Let's release note it, and be good. I think > > >> I recall we kinda had this talk before. See: >> https://issues.jboss.org/browse/AGPUSH-1399 >> >> >>> >>> 2) All Message listeners receive messages from all topics the device is >>> subscribed to. I would like to extend registrar manager to be able to >>> attach messages handlers per topic as well as globally. >>> >> >> Due to the nature of the Android layer around GCM 3, this is specific to >> Android only, right ? >> > I don't know enough about iOS, sorry :( > Ok, let me ask different: This is something done only on GCM3's topics, right ? > >> +1 on this. Same reasoning like Erik Jan here :) >> >> >>> >>> This are both simple, easy changes which shouldn't be a lot of work and >>> will really improve the push experience in Agdroid 3.0. >>> >>> wdyt? >>> >> >> bring it on :) >> >> >>> >>> Summers >>> >>> _______________________________________________ >>> 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/20150727/d8670cbb/attachment.html From corinnekrych at gmail.com Mon Jul 27 05:00:19 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 27 Jul 2015 11:00:19 +0200 Subject: [aerogear-dev] Android topic messaging enhancements (AGDROID-470) In-Reply-To: References: Message-ID: On 27 July 2015 at 09:46, Matthias Wessendorf wrote: > > > On Sun, Jul 26, 2015 at 1:39 AM, Summers Pittman > wrote: > >> >> >> On Sat, Jul 25, 2015 at 5:24 AM, Matthias Wessendorf >> wrote: >> >>> sorry for the late response ;-) >>> >>> On Thu, Jul 23, 2015 at 10:51 PM, Summers Pittman >>> wrote: >>> >>>> So good news, >>>> >>>> Topic support for GCM is trivial to implement. In fact after 20 >>>> minutes I have most of the work done in the Android library. The behavior >>>> of topics matches the behavior of categories. I would like to propose some >>>> enhancements. >>>> >>> >>> yay >>> >>> >>>> >>>> 1) Changing categories/topics currently requires the application to >>>> unregister and reregister on UPS. I would like to add a subscribe and >>>> unsubscibe method to the pushRegistrar interface which will subscribe and >>>> unsubscribe the device from topics. >>>> >>> >>> Ok, makes sense. Actually I like the idea. Should this be done on the >>> other SDKs too? If so... does it make sense to change the RESTful endpoint >>> to? e.g. do a PUT to update the device metadata? >>> >> >> So strictly speaking we don't need to have GCM 3 Android register its >> categories with UPS. Google can handle those. >> > yeah, but we need the info on the UPS for a bunch of reasons... (e.g. only > 1m devices per topic allowed). > I think this is very easy to translate to our existing categories... > >> >> How are we handling compatibility? >> > > What do you mean here? > > >> Would it be weird if 1.2 of UPS requires ADroid push 3.0? >> > > Well, I do not think this is a problem. the 1.1.0 also requires AGDroid2, > due to analytic support. > Let's release note it, and be good. I think > > >> >> >>> I recall we kinda had this talk before. See: >>> https://issues.jboss.org/browse/AGPUSH-1399 >>> >>> >>>> >>>> 2) All Message listeners receive messages from all topics the device is >>>> subscribed to. I would like to extend registrar manager to be able to >>>> attach messages handlers per topic as well as globally. >>>> >>> >>> Due to the nature of the Android layer around GCM 3, this is specific to >>> Android only, right ? >>> >> I don't know enough about iOS, sorry :( >> > > Ok, let me ask different: This is something done only on GCM3's topics, > right ? > Yep it's GCM3 specific. There is an iOS client to bring GCM / APN https://developers.google.com/cloud-messaging/ios/client Not sure if it's worth investigating further the iOS side of GCM3 topics as this feature seems to me very close to our UPS categories, which we already have implemented ahead of time. > > > >> >>> +1 on this. Same reasoning like Erik Jan here :) >>> >>> >>>> >>>> This are both simple, easy changes which shouldn't be a lot of work and >>>> will really improve the push experience in Agdroid 3.0. >>>> >>>> wdyt? >>>> >>> >>> bring it on :) >>> >>> >>>> >>>> Summers >>>> >>>> _______________________________________________ >>>> 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/20150727/a017f83f/attachment-0001.html From matzew at apache.org Mon Jul 27 07:02:00 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 27 Jul 2015 13:02:00 +0200 Subject: [aerogear-dev] Android topic messaging enhancements (AGDROID-470) In-Reply-To: References: Message-ID: On Monday, July 27, 2015, Corinne Krych wrote: > > > On 27 July 2015 at 09:46, Matthias Wessendorf > wrote: > >> >> >> On Sun, Jul 26, 2015 at 1:39 AM, Summers Pittman > > wrote: >> >>> >>> >>> On Sat, Jul 25, 2015 at 5:24 AM, Matthias Wessendorf >> > wrote: >>> >>>> sorry for the late response ;-) >>>> >>>> On Thu, Jul 23, 2015 at 10:51 PM, Summers Pittman >>> > wrote: >>>> >>>>> So good news, >>>>> >>>>> Topic support for GCM is trivial to implement. In fact after 20 >>>>> minutes I have most of the work done in the Android library. The behavior >>>>> of topics matches the behavior of categories. I would like to propose some >>>>> enhancements. >>>>> >>>> >>>> yay >>>> >>>> >>>>> >>>>> 1) Changing categories/topics currently requires the application to >>>>> unregister and reregister on UPS. I would like to add a subscribe and >>>>> unsubscibe method to the pushRegistrar interface which will subscribe and >>>>> unsubscribe the device from topics. >>>>> >>>> >>>> Ok, makes sense. Actually I like the idea. Should this be done on the >>>> other SDKs too? If so... does it make sense to change the RESTful endpoint >>>> to? e.g. do a PUT to update the device metadata? >>>> >>> >>> So strictly speaking we don't need to have GCM 3 Android register its >>> categories with UPS. Google can handle those. >>> >> yeah, but we need the info on the UPS for a bunch of reasons... (e.g. >> only 1m devices per topic allowed). >> I think this is very easy to translate to our existing categories... >> >>> >>> How are we handling compatibility? >>> >> >> What do you mean here? >> >> >>> Would it be weird if 1.2 of UPS requires ADroid push 3.0? >>> >> >> Well, I do not think this is a problem. the 1.1.0 also requires AGDroid2, >> due to analytic support. >> Let's release note it, and be good. I think >> >> >>> >>> >>>> I recall we kinda had this talk before. See: >>>> https://issues.jboss.org/browse/AGPUSH-1399 >>>> >>>> >>>>> >>>>> 2) All Message listeners receive messages from all topics the device >>>>> is subscribed to. I would like to extend registrar manager to be able to >>>>> attach messages handlers per topic as well as globally. >>>>> >>>> >>>> Due to the nature of the Android layer around GCM 3, this is specific >>>> to Android only, right ? >>>> >>> I don't know enough about iOS, sorry :( >>> >> >> Ok, let me ask different: This is something done only on GCM3's topics, >> right ? >> > > > Yep it's GCM3 specific. > perhaps for iOS we can send the info which category was used. And on the client it might be nice to have same: listener per topic/category? But on iOS at the same time this might just add extra complexity, since there are less decent APIs to stick the finger deep into the notification delivery... hrm.. > There is an iOS client to bring GCM / APN > https://developers.google.com/cloud-messaging/ios/client > Not sure if it's worth investigating further the iOS side of GCM3 topics > as this feature seems to me very close to our UPS categories, which we > already have implemented ahead of time. > I am also not sure if we should use GCM for iOS, atm, but more do to the fact that iOS on UPS than would need both: GCM and APNs setup... Technically our categories are indeed close to their topics. The real benefit regarding topics is: You send just one small request to GCM and it figures out the effected devices. For categories we do that ourselves, and we end up sending a bunch of larger requests to GCM IMO using GCM topics for Android will give us a boost for message delivery! However, Google mentions some latency for Topics on their doc, but my guess is they will be pretty fast. > > > >> >> >> >>> >>>> +1 on this. Same reasoning like Erik Jan here :) >>>> >>>> >>>>> >>>>> This are both simple, easy changes which shouldn't be a lot of work >>>>> and will really improve the push experience in Agdroid 3.0. >>>>> >>>>> wdyt? >>>>> >>>> >>>> bring it on :) >>>> >>>> >>>>> >>>>> Summers >>>>> >>>>> _______________________________________________ >>>>> 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 >> > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150727/c0b55650/attachment.html From supittma at redhat.com Mon Jul 27 11:22:01 2015 From: supittma at redhat.com (Summers Pittman) Date: Mon, 27 Jul 2015 11:22:01 -0400 Subject: [aerogear-dev] GCM Topics in UPS Message-ID: So I've got a few ideas for how to implement this, but I hope some people more experienced with the platform can give some feedback before. Quick Background: In UPS right now we have a concept of categories. A single UPS message can be broadcast to a bunch of devices which are subscribed to this category. Google now supports this for GCM on Chrome, iOS, and Android so UPS can send a single message to GCM and GCM will broadcast that to up to a million devices. End Quick Background So first, how do we switch between sending a message to each device in a category to sending a topic message to GCM? In TokenLoader.java#L113 we are using the clientInstallationService to build a string of deviceTokens based on the variant and message criteria. Is there any reason we can't create a "topicToken" which will be recognized later by GCMPushNotificationSender? Another benefit to making this change here is that if we have over a million subscribers to the category we can just default to the default messaging. There is also an open issue of whether or not we will update the clients to filter based on what category a message was sent to. To do this we will have to include the category information in the message when we send it to devices going forward. In GCM a topic message includes this information. This means that if we have over a million subscriptions in the topic we will need to fall back to using the category information anyway. Continuing on from the thread of falling back, it is possible for a topic message to fail to send because there are too many subscribers. How would UPS handle regenerating the messages as deviceToken instead of topicToken messages? Of course if someone has a better idea than "topicTokens" I'm all ears. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150727/47e6f2c8/attachment.html From bsuchano at redhat.com Mon Jul 27 11:34:32 2015 From: bsuchano at redhat.com (Barbora Suchanova) Date: Mon, 27 Jul 2015 11:34:32 -0400 (EDT) Subject: [aerogear-dev] Problem with opening Aerogear(branch - windows10) in Visual Studio 2015 Message-ID: <82678336.267089.1438011272919.JavaMail.zimbra@redhat.com> Good evening, my name is Barbora Suchanova and I am working on project Keycloak. As a part of my job is to develop a simple Windows Phone application where I am supposed to integrate authentication through Keycloak. Anyway I have an issue with opening your solution of aerogear from GitHub for Windows 10 in new Visual Studio 2015.(update from Visual Studio 2015 RT) Week ago I was able to open in it VS 2015 RT, but now it looks like impossible to migrate the project into VS 2015. Does anybody resolved this issue? I would like to build it and run it and don't want to install VS 2015 RT again... Thank you in advance. Best regards Barbora Suchanova From corinnekrych at gmail.com Mon Jul 27 12:09:14 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 27 Jul 2015 18:09:14 +0200 Subject: [aerogear-dev] What's new in AeroGear? Message-ID: Android AGDroid 3.0 work continues. - aerogear-android-push - We?ve impletmented InstanceIDListener for agdroid-push in master - Topic messaging implementation is here : https://github.com/secondsun/aerogear-android-push/tree/AGDROID-470-TOPIC-MESSAGING - Keep a lookout for a PR with this and UPS sometimes this week. - Someone on StackOverflow has been asking about two way messaging : http://stackoverflow.com/questions/31518805/is-it-possible-to-receive-a-message-from-the-client-on-aerogear/31541069#31541069 - There?s a good discussion on topic APIs on the Mailing list : http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-topic-messaging-enhancements-AGDROID-470-td11997.html Stuff from Summers? mad mind - aerogear-android-store - https://github.com/secondsun/aerogear-android-store/tree/content_provider - AeroGear patterns for using ContentProviders with Store implementations. - Still a work in progress doesn?t even compile right now. - aerogear-android-plugin - https://github.com/secondsun/aerogear-android-plugin - Ultimate goal is to provide automated checks, annotation processing, etc for the AeroGear library in Maven and Gradle - Right now the code can only validate that the broadcase receiver for push messages is set up correctly. iOS lovers Moving forward in Swift2 / iOS9 adaption, aerogear-io-oauth2 has now its ?swift-2.0? branch. Note that we moved to Xcode7 beta4 Swift 2 syntax. This week will bring companion demos repository aerogear-ios-cookbook to Swift 2 too. ? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150727/64108508/attachment-0001.html From matzew at apache.org Tue Jul 28 01:39:13 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 28 Jul 2015 07:39:13 +0200 Subject: [aerogear-dev] [Aerogear-users] What's new in AeroGear? In-Reply-To: References: Message-ID: UnifiedPush Server Moving towards 1.1.0.Final, the beta-3 release is out and our Openshift cartridge has been updated to use this version as well. On Mon, Jul 27, 2015 at 6:09 PM, Corinne Krych wrote: > Android AGDroid 3.0 work continues. > > - aerogear-android-push > - We?ve impletmented InstanceIDListener for agdroid-push in master > - Topic messaging implementation is here : > https://github.com/secondsun/aerogear-android-push/tree/AGDROID-470-TOPIC-MESSAGING > - Keep a lookout for a PR with this and UPS sometimes this week. > - Someone on StackOverflow has been asking about two way messaging : > > http://stackoverflow.com/questions/31518805/is-it-possible-to-receive-a-message-from-the-client-on-aerogear/31541069#31541069 > - There?s a good discussion on topic APIs on the Mailing list : > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-topic-messaging-enhancements-AGDROID-470-td11997.html > > Stuff from Summers? mad mind > > - aerogear-android-store > - > https://github.com/secondsun/aerogear-android-store/tree/content_provider > - AeroGear patterns for using ContentProviders with Store > implementations. > - Still a work in progress doesn?t even compile right now. > - aerogear-android-plugin > - https://github.com/secondsun/aerogear-android-plugin > - Ultimate goal is to provide automated checks, annotation > processing, etc for the AeroGear library in Maven and Gradle > - Right now the code can only validate that the broadcase > receiver for push messages is set up correctly. > > iOS lovers > > Moving forward in Swift2 / iOS9 adaption, aerogear-io-oauth2 has now its > ?swift-2.0? branch. Note that we moved to Xcode7 beta4 Swift 2 syntax. This > week will bring companion demos repository aerogear-ios-cookbook to Swift 2 > too. > ? > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- 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/20150728/9b575b4b/attachment.html From vivek.pandey at pinelabs.com Tue Jul 28 02:36:57 2015 From: vivek.pandey at pinelabs.com (Vivek Pandey) Date: Tue, 28 Jul 2015 12:06:57 +0530 Subject: [aerogear-dev] UPS: Adding collapse_key to push messages Message-ID: <003601d0c8ff$cdb03fc0$6910bf40$@pinelabs.com> Hello UPS Team, Is there a way to inject "collapse_key" attribute in GCM push messages? We are using REST endpoint for sending push notifications. Vivek This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150728/2c0c41c1/attachment.html From scm.blanc at gmail.com Tue Jul 28 02:51:03 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 28 Jul 2015 08:51:03 +0200 Subject: [aerogear-dev] Problem with opening Aerogear(branch - windows10) in Visual Studio 2015 In-Reply-To: <82678336.267089.1438011272919.JavaMail.zimbra@redhat.com> References: <82678336.267089.1438011272919.JavaMail.zimbra@redhat.com> Message-ID: Hello ! I have no experience using VS 2015, our "windows" specialist, Erik, is currently on PTO . In the meantime I suggest you to open a jira ticket with a maximum of details here https://issues.jboss.org/browse/AGWIN that will help us to resolve this issue. Sebi On Mon, Jul 27, 2015 at 5:34 PM, Barbora Suchanova wrote: > Good evening, > my name is Barbora Suchanova and I am working on project Keycloak. As a > part of my job is to develop a simple Windows Phone application > where I am supposed to integrate authentication through Keycloak. > > Anyway I have an issue with opening your solution of aerogear from GitHub > for Windows 10 in new Visual Studio 2015.(update from Visual Studio 2015 RT) > Week ago I was able to open in it VS 2015 RT, but now it looks like > impossible to migrate the project into VS 2015. Does anybody resolved this > issue? > I would like to build it and run it and don't want to install VS 2015 RT > again... > > Thank you in advance. > > Best regards > Barbora Suchanova > _______________________________________________ > 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/20150728/cbb87058/attachment.html From scm.blanc at gmail.com Tue Jul 28 10:20:02 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 28 Jul 2015 16:20:02 +0200 Subject: [aerogear-dev] GCM Topics in UPS In-Reply-To: References: Message-ID: Yo ! I have not enough info on the GCM Topic stuff but reading your message it sounds that we should leverage this "transparently" for the user , meaning it just uses the UPS categories and under the hood we use the GCM topics stuff. Like you said we have to handle the fall over if they are more than 1 million user but since we use JMS batches with counting that should not be too hard (but Lukas should be able to give us more info on that) On Mon, Jul 27, 2015 at 5:22 PM, Summers Pittman wrote: > So I've got a few ideas for how to implement this, but I hope some people > more experienced with the platform can give some feedback before. > > Quick Background: > In UPS right now we have a concept of categories. A single UPS message > can be broadcast to a bunch of devices which are subscribed to this > category. Google now supports this for GCM on Chrome, iOS, and Android so > UPS can send a single message to GCM and GCM will broadcast that to up to a > million devices. > End Quick Background > > So first, how do we switch between sending a message to each device in a > category to sending a topic message to GCM? > > In TokenLoader.java#L113 we are using the clientInstallationService to > build a string of deviceTokens based on the variant and message criteria. > Is there any reason we can't create a "topicToken" which will be recognized > later by GCMPushNotificationSender? Another benefit to making this change > here is that if we have over a million subscribers to the category we can > just default to the default messaging. > > There is also an open issue of whether or not we will update the clients > to filter based on what category a message was sent to. To do this we will > have to include the category information in the message when we send it to > devices going forward. In GCM a topic message includes this information. > This means that if we have over a million subscriptions in the topic we > will need to fall back to using the category information anyway. > > Continuing on from the thread of falling back, it is possible for a topic > message to fail to send because there are too many subscribers. How would > UPS handle regenerating the messages as deviceToken instead of topicToken > messages? > > Of course if someone has a better idea than "topicTokens" I'm all ears. > > > _______________________________________________ > 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/20150728/ca971cb0/attachment-0001.html From scm.blanc at gmail.com Tue Jul 28 10:38:06 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 28 Jul 2015 16:38:06 +0200 Subject: [aerogear-dev] UPS: Adding collapse_key to push messages In-Reply-To: <003601d0c8ff$cdb03fc0$6910bf40$@pinelabs.com> References: <003601d0c8ff$cdb03fc0$6910bf40$@pinelabs.com> Message-ID: Hi Vivek, We don't support that right now but looks like it could be useful ;) Could you please open a JIRA for this and we with make sure to plan this in a next release ? Sebi On Tue, Jul 28, 2015 at 8:36 AM, Vivek Pandey wrote: > Hello UPS Team, > > > > Is there a way to inject ?collapse_key? attribute in GCM push messages? > > We are using REST endpoint for sending push notifications. > > > > Vivek > > ------------------------------ > This message may contain privileged and confidential information and is > solely for the use of intended recipient. The views expressed in this email > are those of the sender and not of Pine Labs. The recipient should check > this email and attachments for the presence of viruses / malwares etc. Pine > Labs accepts no liability for any damage caused by any virus transmitted by > this email. Pine Labs may monitor and record all emails. > ------------------------------ > > > _______________________________________________ > 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/20150728/ae4916be/attachment.html From supittma at redhat.com Tue Jul 28 10:40:38 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 28 Jul 2015 10:40:38 -0400 Subject: [aerogear-dev] GCM Topics in UPS In-Reply-To: References: Message-ID: On Tue, Jul 28, 2015 at 10:20 AM, Sebastien Blanc wrote: > Yo ! > I have not enough info on the GCM Topic stuff but reading your message it > sounds that we should leverage this "transparently" for the user , meaning > it just uses the UPS categories and under the hood we use the GCM topics > stuff. > Like you said we have to handle the fall over if they are more than 1 > million user but since we use JMS batches with counting that should not be > too hard (but Lukas should be able to give us more info on that) > Awesome. I'll run ahead with my ideas then and let people hash out their merits in the PR. > > > On Mon, Jul 27, 2015 at 5:22 PM, Summers Pittman > wrote: > >> So I've got a few ideas for how to implement this, but I hope some people >> more experienced with the platform can give some feedback before. >> >> Quick Background: >> In UPS right now we have a concept of categories. A single UPS message >> can be broadcast to a bunch of devices which are subscribed to this >> category. Google now supports this for GCM on Chrome, iOS, and Android so >> UPS can send a single message to GCM and GCM will broadcast that to up to a >> million devices. >> End Quick Background >> >> So first, how do we switch between sending a message to each device in a >> category to sending a topic message to GCM? >> >> In TokenLoader.java#L113 we are using the clientInstallationService to >> build a string of deviceTokens based on the variant and message criteria. >> Is there any reason we can't create a "topicToken" which will be recognized >> later by GCMPushNotificationSender? Another benefit to making this change >> here is that if we have over a million subscribers to the category we can >> just default to the default messaging. >> >> There is also an open issue of whether or not we will update the clients >> to filter based on what category a message was sent to. To do this we will >> have to include the category information in the message when we send it to >> devices going forward. In GCM a topic message includes this information. >> This means that if we have over a million subscriptions in the topic we >> will need to fall back to using the category information anyway. >> >> Continuing on from the thread of falling back, it is possible for a topic >> message to fail to send because there are too many subscribers. How would >> UPS handle regenerating the messages as deviceToken instead of topicToken >> messages? >> >> Of course if someone has a better idea than "topicTokens" I'm all ears. >> >> >> _______________________________________________ >> 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/20150728/4059a118/attachment.html From supittma at redhat.com Tue Jul 28 16:01:18 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 28 Jul 2015 16:01:18 -0400 Subject: [aerogear-dev] UPS and com.ganyo:gcm-server Message-ID: So it looks like UPS is using a jar packaged by "theganyo" https://github.com/theganyo/gcm-server for its Google stuff. This appears to be a fork of Google's GCM code which was put into maven central. It is also about two years out of date. The fork appears to be based on the code here : https://github.com/google/gcm. For implementing topic support I am probably going to need some functionality from Google's actual code. Even if I don't I am going to need things feature in neither repository (Constants for error messages in response to topic messaging are immediately apparent). I am looking for brainstorming around the best way to gracefully move this functionality forward. I'm thinking drop the ganyo dependency and code and pull the current Google code into UPS. It is apache licensed. Thoughts, fears, tomatoes? Summers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150728/9ff2115c/attachment.html From matzew at apache.org Wed Jul 29 02:28:19 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 29 Jul 2015 08:28:19 +0200 Subject: [aerogear-dev] UPS and com.ganyo:gcm-server In-Reply-To: References: Message-ID: Right, we use that mainly because Google does not publish their stuff to maven central. If they would do, we would use that, and perhaps would have also used slightly updated versions. I was expecting that this dependency needs to go for GCM3 support (e.g. for using topics). But, instead of including the GCM-server source into UPS, why not just release it to a custom maven repo (like done in the given URL). If the GCM-server is fully ASLv2, we could even push it to our JBoss 3rd party repo. On Tue, Jul 28, 2015 at 10:01 PM, Summers Pittman wrote: > So it looks like UPS is using a jar packaged by "theganyo" > https://github.com/theganyo/gcm-server for its Google stuff. This > appears to be a fork of Google's GCM code which was put into maven > central. It is also about two years out of date. > > The fork appears to be based on the code here : > https://github.com/google/gcm. > > For implementing topic support I am probably going to need some > functionality from Google's actual code. Even if I don't I am going to > need things feature in neither repository (Constants for error messages in > response to topic messaging are immediately apparent). > > I am looking for brainstorming around the best way to gracefully move this > functionality forward. I'm thinking drop the ganyo dependency and code and > pull the current Google code into UPS. It is apache licensed. > > Thoughts, fears, tomatoes? > > Summers > > _______________________________________________ > 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/20150729/9d3a09ee/attachment.html From matzew at apache.org Wed Jul 29 02:32:16 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 29 Jul 2015 08:32:16 +0200 Subject: [aerogear-dev] UPS and com.ganyo:gcm-server In-Reply-To: References: Message-ID: On Wed, Jul 29, 2015 at 8:28 AM, Matthias Wessendorf wrote: > Right, > we use that mainly because Google does not publish their stuff to maven > central. If they would do, we would use that, and perhaps would have also > used slightly updated versions. > > I was expecting that this dependency needs to go for GCM3 support (e.g. > for using topics). > > But, instead of including the GCM-server source into UPS, why not just > release it to a custom maven repo (like done in the given URL). > If the GCM-server is fully ASLv2, we could even push it to our JBoss 3rd > party repo. > > > > On Tue, Jul 28, 2015 at 10:01 PM, Summers Pittman > wrote: > >> So it looks like UPS is using a jar packaged by "theganyo" >> https://github.com/theganyo/gcm-server for its Google stuff. This >> appears to be a fork of Google's GCM code which was put into maven >> central. It is also about two years out of date. >> >> The fork appears to be based on the code here : >> https://github.com/google/gcm. >> > https://github.com/google/gcm/tree/master/client-libraries/java/rest-client/src/com/google/android/gcm/server For the XMPP support, we may wanna do for UPS 1.2.x, they don't have anything on github ? -M > >> For implementing topic support I am probably going to need some >> functionality from Google's actual code. Even if I don't I am going to >> need things feature in neither repository (Constants for error messages in >> response to topic messaging are immediately apparent). >> >> I am looking for brainstorming around the best way to gracefully move >> this functionality forward. I'm thinking drop the ganyo dependency and >> code and pull the current Google code into UPS. It is apache licensed. >> >> Thoughts, fears, tomatoes? >> >> Summers >> >> _______________________________________________ >> 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/20150729/840ae0cc/attachment-0001.html From vivek.pandey at pinelabs.com Wed Jul 29 03:02:00 2015 From: vivek.pandey at pinelabs.com (Vivek Pandey) Date: Wed, 29 Jul 2015 12:32:00 +0530 Subject: [aerogear-dev] UPS: Adding collapse_key to push messages In-Reply-To: References: <003601d0c8ff$cdb03fc0$6910bf40$@pinelabs.com> Message-ID: <002d01d0c9cc$777ce6d0$6676b470$@pinelabs.com> Thanks Sebastien, I have logged a jira for this requirement. https://issues.jboss.org/browse/AGPUSH-1487 From: Sebastien Blanc [mailto:scm.blanc at gmail.com] Sent: Tuesday, July 28, 2015 8:08 PM To: Vivek Pandey; AeroGear Developer Mailing List Subject: Re: [aerogear-dev] UPS: Adding collapse_key to push messages Hi Vivek, We don't support that right now but looks like it could be useful ;) Could you please open a JIRA for this and we with make sure to plan this in a next release ? Sebi On Tue, Jul 28, 2015 at 8:36 AM, Vivek Pandey wrote: Hello UPS Team, Is there a way to inject ?collapse_key? attribute in GCM push messages? We are using REST endpoint for sending push notifications. Vivek _____ This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails. _____ _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150729/473b29fa/attachment.html From corinnekrych at gmail.com Wed Jul 29 06:42:56 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 29 Jul 2015 12:42:56 +0200 Subject: [aerogear-dev] Moving security backend authentication demo app to keycloak Message-ID: Hello guys I think it would be nice to move authentication backend demo [1] from Picketlink to Keycloak. There is actually a similar demo in Keycloak repo [2]. I notice some issue with Picketlink when deploying to openshift with jbossas-7 cartridge. I guess AGSEC might be the JIRA project for that. Is it ok to create a jira there? ++ Corinne [1] https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Authentication [2] https://github.com/keycloak/keycloak/tree/master/examples/basic-auth/src/main/java/org/keycloak/example/basicauth -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150729/12f3112f/attachment.html From matzew at apache.org Wed Jul 29 08:34:48 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 29 Jul 2015 14:34:48 +0200 Subject: [aerogear-dev] Moving security backend authentication demo app to keycloak In-Reply-To: References: Message-ID: Would be nice for AeroDoc as well On Wednesday, July 29, 2015, Corinne Krych wrote: > Hello guys > > I think it would be nice to move authentication backend demo [1] from > Picketlink to Keycloak. There is actually a similar demo in Keycloak repo > [2]. I notice some issue with Picketlink when deploying to openshift with > jbossas-7 cartridge. > > I guess AGSEC might be the JIRA project for that. Is it ok to create a > jira there? > > ++ > Corinne > [1] > https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Authentication > [2] > https://github.com/keycloak/keycloak/tree/master/examples/basic-auth/src/main/java/org/keycloak/example/basicauth > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150729/2e746828/attachment.html From supittma at redhat.com Wed Jul 29 09:47:44 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 29 Jul 2015 09:47:44 -0400 Subject: [aerogear-dev] UPS and com.ganyo:gcm-server In-Reply-To: References: Message-ID: On Wed, Jul 29, 2015 at 2:32 AM, Matthias Wessendorf wrote: > > > On Wed, Jul 29, 2015 at 8:28 AM, Matthias Wessendorf > wrote: > >> Right, >> we use that mainly because Google does not publish their stuff to maven >> central. If they would do, we would use that, and perhaps would have also >> used slightly updated versions. >> >> I was expecting that this dependency needs to go for GCM3 support (e.g. >> for using topics). >> >> But, instead of including the GCM-server source into UPS, why not just >> release it to a custom maven repo (like done in the given URL). >> If the GCM-server is fully ASLv2, we could even push it to our JBoss 3rd >> party repo. >> >> >> >> On Tue, Jul 28, 2015 at 10:01 PM, Summers Pittman >> wrote: >> >>> So it looks like UPS is using a jar packaged by "theganyo" >>> https://github.com/theganyo/gcm-server for its Google stuff. This >>> appears to be a fork of Google's GCM code which was put into maven >>> central. It is also about two years out of date. >>> >>> The fork appears to be based on the code here : >>> https://github.com/google/gcm. >>> >> > > https://github.com/google/gcm/tree/master/client-libraries/java/rest-client/src/com/google/android/gcm/server > > For the XMPP support, we may wanna do for UPS 1.2.x, they don't have > anything on github ? > All things considered, Google's code in github for GCM support is rather anemic. I was noticing it didn't have any topics specific stuff in it either. I don't want to say "Let's roll our own" but forking,enhancing, and self hosting might be a good idea. > -M > > > >> >>> For implementing topic support I am probably going to need some >>> functionality from Google's actual code. Even if I don't I am going to >>> need things feature in neither repository (Constants for error messages in >>> response to topic messaging are immediately apparent). >>> >>> I am looking for brainstorming around the best way to gracefully move >>> this functionality forward. I'm thinking drop the ganyo dependency and >>> code and pull the current Google code into UPS. It is apache licensed. >>> >>> Thoughts, fears, tomatoes? >>> >>> Summers >>> >>> _______________________________________________ >>> 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/20150729/6c357786/attachment-0001.html From supittma at redhat.com Wed Jul 29 10:14:49 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 29 Jul 2015 10:14:49 -0400 Subject: [aerogear-dev] Moving security backend authentication demo app to keycloak In-Reply-To: References: Message-ID: +1 On Wed, Jul 29, 2015 at 8:34 AM, Matthias Wessendorf wrote: > Would be nice for AeroDoc as well > > > On Wednesday, July 29, 2015, Corinne Krych wrote: > >> Hello guys >> >> I think it would be nice to move authentication backend demo [1] from >> Picketlink to Keycloak. There is actually a similar demo in Keycloak repo >> [2]. I notice some issue with Picketlink when deploying to openshift with >> jbossas-7 cartridge. >> >> I guess AGSEC might be the JIRA project for that. Is it ok to create a >> jira there? >> >> ++ >> Corinne >> [1] >> https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Authentication >> [2] >> https://github.com/keycloak/keycloak/tree/master/examples/basic-auth/src/main/java/org/keycloak/example/basicauth >> > > > -- > Sent from Gmail Mobile > > _______________________________________________ > 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/20150729/c35f7e96/attachment.html From matzew at apache.org Wed Jul 29 10:28:00 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 29 Jul 2015 16:28:00 +0200 Subject: [aerogear-dev] UPS and com.ganyo:gcm-server In-Reply-To: References: Message-ID: On Wednesday, July 29, 2015, Summers Pittman wrote: > > > On Wed, Jul 29, 2015 at 2:32 AM, Matthias Wessendorf > wrote: > >> >> >> On Wed, Jul 29, 2015 at 8:28 AM, Matthias Wessendorf > > wrote: >> >>> Right, >>> we use that mainly because Google does not publish their stuff to maven >>> central. If they would do, we would use that, and perhaps would have also >>> used slightly updated versions. >>> >>> I was expecting that this dependency needs to go for GCM3 support (e.g. >>> for using topics). >>> >>> But, instead of including the GCM-server source into UPS, why not just >>> release it to a custom maven repo (like done in the given URL). >>> If the GCM-server is fully ASLv2, we could even push it to our JBoss 3rd >>> party repo. >>> >>> >>> >>> On Tue, Jul 28, 2015 at 10:01 PM, Summers Pittman >> > wrote: >>> >>>> So it looks like UPS is using a jar packaged by "theganyo" >>>> https://github.com/theganyo/gcm-server for its Google stuff. This >>>> appears to be a fork of Google's GCM code which was put into maven >>>> central. It is also about two years out of date. >>>> >>>> The fork appears to be based on the code here : >>>> https://github.com/google/gcm. >>>> >>> >> >> https://github.com/google/gcm/tree/master/client-libraries/java/rest-client/src/com/google/android/gcm/server >> >> For the XMPP support, we may wanna do for UPS 1.2.x, they don't have >> anything on github ? >> > > All things considered, Google's code in github for GCM support is rather > anemic. I was noticing it didn't have any topics specific stuff in it > either. I don't want to say "Let's roll our own" but forking,enhancing, > and self hosting might be a good idea. > we do that for aerogear/java-mpns too. Sounds like we need a new XMPP GCm3 lib, right? This will not support http endpoints, right? If not required i think we can skip them initially. Doing the lib standalone, outside of UPS, brings also value to the larger OpenSource community > > >> -M >> >> >> >>> >>>> For implementing topic support I am probably going to need some >>>> functionality from Google's actual code. Even if I don't I am going to >>>> need things feature in neither repository (Constants for error messages in >>>> response to topic messaging are immediately apparent). >>>> >>>> I am looking for brainstorming around the best way to gracefully move >>>> this functionality forward. I'm thinking drop the ganyo dependency and >>>> code and pull the current Google code into UPS. It is apache licensed. >>>> >>>> Thoughts, fears, tomatoes? >>>> >>>> Summers >>>> >>>> _______________________________________________ >>>> 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 >> > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150729/98300238/attachment.html From mfink at email.unc.edu Wed Jul 29 16:39:27 2015 From: mfink at email.unc.edu (Fink, Miles) Date: Wed, 29 Jul 2015 20:39:27 +0000 Subject: [aerogear-dev] Android UPS Variant Category Issue Message-ID: Hi, I?ve successfully got an iOS variant to register categories for installations in my cordova app using the cordova PushPlugin. I?m now trying to get Android to register categories and it seemingly does not take. It registers the installation and alias just fine but not the array of categories . Anyone encountered this? Push notifications work and are received on the android device just no categories are shown on the admin UI for the installation nor do category specific notifications get received. I?m running: * Unified Push Server on OpenShift v1.0.3 * Cordova PushPlugin v2.0.1 Any suggestions / pointers would be greatly appreciated! Thanks! -Miles -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150729/193cb7bf/attachment.html From bruno at abstractj.org Wed Jul 29 19:52:19 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 29 Jul 2015 16:52:19 -0700 (PDT) Subject: [aerogear-dev] Moving security backend authentication demo app to keycloak In-Reply-To: References: Message-ID: <1438213938731.b06980b3@Nodemailer> +1 ? abstractj PGP: 0x84DC9914 On Wed, Jul 29, 2015 at 7:43 AM, Corinne Krych wrote: > Hello guys > I think it would be nice to move authentication backend demo [1] from > Picketlink to Keycloak. There is actually a similar demo in Keycloak repo > [2]. I notice some issue with Picketlink when deploying to openshift with > jbossas-7 cartridge. > I guess AGSEC might be the JIRA project for that. Is it ok to create a jira > there? > ++ > Corinne > [1] > https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Authentication > [2] > https://github.com/keycloak/keycloak/tree/master/examples/basic-auth/src/main/java/org/keycloak/example/basicauth -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150729/461794e3/attachment.html From dpassos at redhat.com Thu Jul 30 10:07:24 2015 From: dpassos at redhat.com (Daniel Passos) Date: Thu, 30 Jul 2015 11:07:24 -0300 Subject: [aerogear-dev] AeroGear Android Push 2.2.1 Message-ID: Hey Guys, Matthias found a bug[1] in our AeroGear Android Push library. It was fixed and staged[2] What is new in this version? - AGDROID-486 - Unregister caches device token We?re planning to release it tomorrow (Friday) in the end of the day. Fell free to test it and let us know if you find any issues. [1] http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Android-SDK-Token-not-renewed-when-unregistering-registering-td153.html [2] https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5774/ ? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150730/ff9d2d7e/attachment-0001.html From supittma at redhat.com Fri Jul 31 11:04:18 2015 From: supittma at redhat.com (Summers Pittman) Date: Fri, 31 Jul 2015 11:04:18 -0400 Subject: [aerogear-dev] UPS 1.2, GCM 3.0 Topics, and Google's rest-client updates Message-ID: Guys and gals, UPS is currently using a fork of Google's rest-client sample to communicate with Google's servers (See the previous thread UPS and com.ganyo:gcm-server for details**). This is an outdated fork from https://github.com/google/gcm. It is in fact very outdated. The rest client code, Message and Builder objects, Constant fields, and Sender code don't support all of the fields/errors/etc needed for GCM topics messaging. Additionally it uses a deprecated field in a few places. I've filed two* issues*** in the gcm project to reach out and begin work with them to resolve this in a more sane way. In the meanwhile we will probably have to patch and support our own fork of the library. Thoughts, comments, tomatoes? PS, this will probably bump XMPP support from aerogear-android-push 3.0 and UPS 1.2. Please let me know if it should and i will pull those from the JIRA epics and we can reschedule them. Summers * https://github.com/google/gcm/issues/84 *** https://github.com/google/gcm/issues/85 ** http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UPS-and-com-ganyo-gcm-server-td12015.html -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150731/53999560/attachment.html From dpassos at redhat.com Fri Jul 31 16:37:59 2015 From: dpassos at redhat.com (Daniel Passos) Date: Fri, 31 Jul 2015 17:37:59 -0300 Subject: [aerogear-dev] AeroGear Android Push 2.2.1 In-Reply-To: References: Message-ID: Hey Guys, I've clicked in release button, it will probably available on Maven Central next Monday. On Thu, Jul 30, 2015 at 11:07 AM, Daniel Passos wrote: > Hey Guys, > > Matthias found a bug[1] in our AeroGear Android Push library. It was fixed > and staged[2] > > What is new in this version? > > - AGDROID-486 - > Unregister caches device token > > We?re planning to release it tomorrow (Friday) in the end of the day. > > Fell free to test it and let us know if you find any issues. > > [1] > http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Android-SDK-Token-not-renewed-when-unregistering-registering-td153.html > [2] > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5774/ > ? > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150731/6bba9ebb/attachment.html