From mm at napp.dk Mon Oct 3 05:14:00 2016 From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=) Date: Mon, 3 Oct 2016 09:14:00 +0000 Subject: [aerogear-dev] Loosing data in AeroGear Unified Push Server? Message-ID: <38F8FE6D-ACAC-42BE-BB24-836EE3A9460F@napp.dk> Hi there, I just found out that we are loosing the push messages from the push_message_info table. They are simply removed by something in the Aerogear push code. This is super scary for us. Do anyone know of current or previous bugs regarding the messages from that table have been deleted because of that a bug in the source code? BEST REGARDS __________________ MADS M?LLER TECHNICAL PARTNER Napp A/S T: +45 42 42 80 60 M: +45 20 28 20 26 E: mm at napp.dk W: https://napp.dk __________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161003/97bdabe9/attachment.html From matzew at apache.org Mon Oct 3 06:15:02 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 3 Oct 2016 12:15:02 +0200 Subject: [aerogear-dev] Loosing data in AeroGear Unified Push Server? In-Reply-To: <38F8FE6D-ACAC-42BE-BB24-836EE3A9460F@napp.dk> References: <38F8FE6D-ACAC-42BE-BB24-836EE3A9460F@napp.dk> Message-ID: data taht's older than 30 days will be removed: https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/metrics/PushMessageMetricsService.java#L133-L136 but... you can override that default behavior: https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/metrics/PushMessageMetricsService.java#L41 By starting the server with a system property, like: -Daerogear.metrics.storage.days=YOUR_DESIRED_DAYS -M On Mon, Oct 3, 2016 at 11:14 AM, Mads M?ller wrote: > Hi there, > > > > I just found out that we are loosing the push messages from the > push_message_info table. They are simply removed by something in the > Aerogear push code. > > This is super scary for us. > > > > Do anyone know of current or previous bugs regarding the messages from > that table have been deleted because of that a bug in the source code? > > > > > > > > BEST REGARDS > > *__________________* > > *MADS M?LLER* > > TECHNICAL PARTNER > > > > Napp A/S > > T: +45 42 42 80 60 > > M: +45 20 28 20 26 > > E: mm at napp.dk > > W: https://napp.dk > > *__________________* > > > > _______________________________________________ > 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/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161003/aa5324ac/attachment-0001.html From mm at napp.dk Mon Oct 3 09:04:08 2016 From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=) Date: Mon, 3 Oct 2016 13:04:08 +0000 Subject: [aerogear-dev] Loosing data in AeroGear Unified Push Server? In-Reply-To: References: <38F8FE6D-ACAC-42BE-BB24-836EE3A9460F@napp.dk> Message-ID: Hi Matthias, Thanks for the reply. So since I dont have any experience with build java from source, is there an environment file I can change? We are hosting the service in Openshift Cartridge setup. BEST REGARDS __________________ MADS M?LLER TECHNICAL PARTNER Napp A/S T: +45 42 42 80 60 M: +45 20 28 20 26 E: mm at napp.dk W: https://napp.dk __________________ From: on behalf of Matthias Wessendorf Reply-To: AeroGear Developer Mailing List Date: Monday 3 October 2016 at 12:15 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] Loosing data in AeroGear Unified Push Server? data taht's older than 30 days will be removed: https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/metrics/PushMessageMetricsService.java#L133-L136 but... you can override that default behavior: https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/metrics/PushMessageMetricsService.java#L41 By starting the server with a system property, like: -Daerogear.metrics.storage.days=YOUR_DESIRED_DAYS -M On Mon, Oct 3, 2016 at 11:14 AM, Mads M?ller > wrote: Hi there, I just found out that we are loosing the push messages from the push_message_info table. They are simply removed by something in the Aerogear push code. This is super scary for us. Do anyone know of current or previous bugs regarding the messages from that table have been deleted because of that a bug in the source code? BEST REGARDS __________________ MADS M?LLER TECHNICAL PARTNER Napp A/S T: +45 42 42 80 60 M: +45 20 28 20 26 E: mm at napp.dk W: https://napp.dk __________________ _______________________________________________ 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/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161003/09a1bffd/attachment.html From supittma at redhat.com Mon Oct 3 09:09:34 2016 From: supittma at redhat.com (Summers Pittman) Date: Mon, 3 Oct 2016 09:09:34 -0400 Subject: [aerogear-dev] Loosing data in AeroGear Unified Push Server? In-Reply-To: References: <38F8FE6D-ACAC-42BE-BB24-836EE3A9460F@napp.dk> Message-ID: You need to set the JAVA_OPTS_EXT(1) variable to include " -Daerogear.metrics.storage.days=YOUR_DESIRED_DAYS". Here are some docs : 1: https://developers.openshift.com/managing-your-applications/environment-variables.html#java-variables On Mon, Oct 3, 2016 at 9:04 AM, Mads M?ller wrote: > Hi Matthias, > > > > Thanks for the reply. > > So since I dont have any experience with build java from source, is there > an environment file I can change? > > We are hosting the service in Openshift Cartridge setup. > > > > > > > > BEST REGARDS > > *__________________* > > *MADS M?LLER* > > TECHNICAL PARTNER > > > > Napp A/S > > T: +45 42 42 80 60 > > M: +45 20 28 20 26 > > E: mm at napp.dk > > W: https://napp.dk > > *__________________* > > > > > > *From: * on behalf of Matthias > Wessendorf > *Reply-To: *AeroGear Developer Mailing List > *Date: *Monday 3 October 2016 at 12:15 > *To: *AeroGear Developer Mailing List > *Subject: *Re: [aerogear-dev] Loosing data in AeroGear Unified Push > Server? > > > > data taht's older than 30 days will be removed: > > https://github.com/aerogear/aerogear-unifiedpush-server/ > blob/master/service/src/main/java/org/jboss/aerogear/ > unifiedpush/service/metrics/PushMessageMetricsService.java#L133-L136 > > > > but... you can override that default behavior: > > https://github.com/aerogear/aerogear-unifiedpush-server/ > blob/master/service/src/main/java/org/jboss/aerogear/ > unifiedpush/service/metrics/PushMessageMetricsService.java#L41 > > > > By starting the server with a system property, like: > > -Daerogear.metrics.storage.days=YOUR_DESIRED_DAYS > > > > -M > > > > > > > > On Mon, Oct 3, 2016 at 11:14 AM, Mads M?ller wrote: > > Hi there, > > > > I just found out that we are loosing the push messages from the > push_message_info table. They are simply removed by something in the > Aerogear push code. > > This is super scary for us. > > > > Do anyone know of current or previous bugs regarding the messages from > that table have been deleted because of that a bug in the source code? > > > > > > > > BEST REGARDS > > *__________________* > > *MADS M?LLER* > > TECHNICAL PARTNER > > > > Napp A/S > > T: +45 42 42 80 60 > > M: +45 20 28 20 26 > > E: mm at napp.dk > > W: https://napp.dk > > *__________________* > > > > > _______________________________________________ > 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/ > 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/20161003/db2663aa/attachment-0001.html From matzew at apache.org Tue Oct 4 04:01:34 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 4 Oct 2016 10:01:34 +0200 Subject: [aerogear-dev] Loosing data in AeroGear Unified Push Server? In-Reply-To: References: <38F8FE6D-ACAC-42BE-BB24-836EE3A9460F@napp.dk> Message-ID: Hello, yes, on the config file, go this line: https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/blob/master/versions/1.1.3/standalone/configuration/standalone.xml#L31 and after the above line, add the following: On Mon, Oct 3, 2016 at 3:04 PM, Mads M?ller wrote: > Hi Matthias, > > > > Thanks for the reply. > > So since I dont have any experience with build java from source, is there > an environment file I can change? > > We are hosting the service in Openshift Cartridge setup. > > > > > > > > BEST REGARDS > > *__________________* > > *MADS M?LLER* > > TECHNICAL PARTNER > > > > Napp A/S > > T: +45 42 42 80 60 > > M: +45 20 28 20 26 > > E: mm at napp.dk > > W: https://napp.dk > > *__________________* > > > > > > *From: * on behalf of Matthias > Wessendorf > *Reply-To: *AeroGear Developer Mailing List > *Date: *Monday 3 October 2016 at 12:15 > *To: *AeroGear Developer Mailing List > *Subject: *Re: [aerogear-dev] Loosing data in AeroGear Unified Push > Server? > > > > data taht's older than 30 days will be removed: > > https://github.com/aerogear/aerogear-unifiedpush-server/ > blob/master/service/src/main/java/org/jboss/aerogear/ > unifiedpush/service/metrics/PushMessageMetricsService.java#L133-L136 > > > > but... you can override that default behavior: > > https://github.com/aerogear/aerogear-unifiedpush-server/ > blob/master/service/src/main/java/org/jboss/aerogear/ > unifiedpush/service/metrics/PushMessageMetricsService.java#L41 > > > > By starting the server with a system property, like: > > -Daerogear.metrics.storage.days=YOUR_DESIRED_DAYS > > > > -M > > > > > > > > On Mon, Oct 3, 2016 at 11:14 AM, Mads M?ller wrote: > > Hi there, > > > > I just found out that we are loosing the push messages from the > push_message_info table. They are simply removed by something in the > Aerogear push code. > > This is super scary for us. > > > > Do anyone know of current or previous bugs regarding the messages from > that table have been deleted because of that a bug in the source code? > > > > > > > > BEST REGARDS > > *__________________* > > *MADS M?LLER* > > TECHNICAL PARTNER > > > > Napp A/S > > T: +45 42 42 80 60 > > M: +45 20 28 20 26 > > E: mm at napp.dk > > W: https://napp.dk > > *__________________* > > > > > _______________________________________________ > 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/ > 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/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161004/40d6baab/attachment.html From xiang.wang3 at hpe.com Sun Oct 9 05:00:59 2016 From: xiang.wang3 at hpe.com (Wang, Xiang (Flynn, HPIT-DS)) Date: Sun, 9 Oct 2016 09:00:59 +0000 Subject: [aerogear-dev] help -- how to configure a proxy for Aerogear push server Message-ID: Hello Aerogear, Now I'm trying to use the Aerogear push server to push message to Android devices. But my local network needs a proxy server to visit Google's server. So is there a way to config a proxy server in Aerogear? Regards, Wang, Xiang(Flynn) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161009/43752edc/attachment.html From matzew at apache.org Mon Oct 10 03:36:39 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 10 Oct 2016 09:36:39 +0200 Subject: [aerogear-dev] help -- how to configure a proxy for Aerogear push server In-Reply-To: References: Message-ID: No, we don't have support for that :-( We have an old JIRA for this, since it was asked on the community ML before: https://issues.jboss.org/browse/AGPUSH-306 But I am not sure when will add this new feature. HTH, Matthias On Sun, Oct 9, 2016 at 11:00 AM, Wang, Xiang (Flynn, HPIT-DS) < xiang.wang3 at hpe.com> wrote: > Hello Aerogear, > > Now I?m trying to use the Aerogear push server to push message > to Android devices. But my local network needs a proxy server to visit > Google?s server. So is there a way to config a proxy server in Aerogear? > > > > > > > > Regards, > > Wang, Xiang(Flynn) > > > > _______________________________________________ > 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/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161010/f704b1ed/attachment-0001.html From a.carolinabm at gmail.com Tue Oct 11 18:11:28 2016 From: a.carolinabm at gmail.com (Andrea Carolina Buitrago) Date: Tue, 11 Oct 2016 17:11:28 -0500 Subject: [aerogear-dev] oAuth with Keycloak OpenId in Android Client Message-ID: Hi, I want to authenticate a user (using his username and password) in an Android App using aerogear with a server using Keycloak. I haven't been able to do it, help me please. I currently can authenticate the user without aerogear, but I want to use this library since it can help me to refresh the token when is needed. I authenticate the user making a POST call to the server like this (but from android): curl -X POST http://127.0.0.1:8080/auth/realms/example/protocol/openid-connect/token -H "Content-Type: application/x-www-form-urlencoded" -d "username=auser" -d 'password=apassword' -d 'grant_type=password' -d 'client_id=clientId' -d 'client_secret=secret' What I have tried with Aerogear is this: private void authz() { try { AuthzModule authzModule = AuthorizationManager.config("KeyCloakAuthz", OAuth2AuthorizationConfiguration.class) .setBaseURL(new URL("http://127.0.0.1:8080/")) .setAuthzEndpoint("/realms/example/protocol/openid-connect/auth") .setAccessTokenEndpoint("/realms/example/protocol/openid-connect/token") .setAccountId("keycloak-token") .setClientId("clientId") .setClientSecret("secret") .setRedirectURL("http://oauth2callback") .setScopes(Arrays.asList("openid")) .addAdditionalAuthorizationParam((Pair.create("grant_type", "password"))) .addAdditionalAuthorizationParam((Pair.create("username", "aUserName"))) .addAdditionalAuthorizationParam((Pair.create("password", "aPassword"))) .asModule(); authzModule.requestAccess(this, new Callback() { @Override public void onSuccess(String o) { Log.d("TOKEN ", o); } @Override public void onFailure(Exception e) { System.err.println("Error!!"); Toast.makeText(getApplicationContext(), e.getMessage(), Toast.LENGTH_LONG).show(); } }); } catch (Exception e) { e.printStackTrace(); throw new RuntimeException(e); }} However this doesn't do anything. What I don't understand is: 1. How can I specify that I'm doing and OpenID Connect with Keycloak in Aerogear(Android) ? I've seen it in the swift library but I cannot find it in Android 2. How and where can I send the username and password? 3. How can I specify the grant_type? (My HTTP POST to the server does not work if I don't include this, so it's important) I'm really sorry if this is a very basic question, but I haven't been able to work it out on my own. Any help or documentation would be appreciated. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161011/8663c6f4/attachment.html From supittma at redhat.com Thu Oct 13 10:40:07 2016 From: supittma at redhat.com (Summers Pittman) Date: Thu, 13 Oct 2016 10:40:07 -0400 Subject: [aerogear-dev] oAuth with Keycloak OpenId in Android Client In-Reply-To: References: Message-ID: On Tue, Oct 11, 2016 at 6:11 PM, Andrea Carolina Buitrago < a.carolinabm at gmail.com> wrote: > Hi, I want to authenticate a user (using his username and password) in an > Android App using aerogear with a server using Keycloak. I haven't been > able to do it, help me please. > > I currently can authenticate the user without aerogear, but I want to use > this library since it can help me to refresh the token when is needed. I > authenticate the user making a POST call to the server like this (but from > android): > > curl -X POST http://127.0.0.1:8080/auth/realms/example/protocol/openid-connect/token > -H "Content-Type: application/x-www-form-urlencoded" -d "username=auser" -d 'password=apassword' -d 'grant_type=password' > -d 'client_id=clientId' -d 'client_secret=secret' > > What I have tried with Aerogear is this: > > private void authz() { > try { > > AuthzModule authzModule = AuthorizationManager.config("KeyCloakAuthz", OAuth2AuthorizationConfiguration.class) > .setBaseURL(new URL("http://127.0.0.1:8080/")) > .setAuthzEndpoint("/realms/example/protocol/openid-connect/auth") > .setAccessTokenEndpoint("/realms/example/protocol/openid-connect/token") > .setAccountId("keycloak-token") > .setClientId("clientId") > .setClientSecret("secret") > .setRedirectURL("http://oauth2callback") > .setScopes(Arrays.asList("openid")) > .addAdditionalAuthorizationParam((Pair.create("grant_type", "password"))) > .addAdditionalAuthorizationParam((Pair.create("username", "aUserName"))) > .addAdditionalAuthorizationParam((Pair.create("password", "aPassword"))) > .asModule(); > > > authzModule.requestAccess(this, new Callback() { > @Override > public void onSuccess(String o) { > Log.d("TOKEN ", o); > } > > @Override > public void onFailure(Exception e) { > System.err.println("Error!!"); > Toast.makeText(getApplicationContext(), e.getMessage(), Toast.LENGTH_LONG).show(); > } > }); > > } catch (Exception e) { > > e.printStackTrace(); > throw new RuntimeException(e); > }} > > > However this doesn't do anything. What I don't understand is: > > 1. How can I specify that I'm doing and OpenID Connect with Keycloak > in Aerogear(Android) ? I've seen it in the swift library but I cannot find > it in Android > 2. How and where can I send the username and password? > 3. How can I specify the grant_type? (My HTTP POST to the server does > not work if I don't include this, so it's important) > > So with OAuth flows you usually don't post a username/password to a server. OAuth directs you to a trusted page, you input your credentials there, then the service provides to the library a token and the library exchanges that token for a token to use for your session. In AGDroid we use a webview to show the login page. I'm not familiar with iOS at all, does it support this workflow there? I also don't think we've worked with OpenID Connect before. If it works it is by happy coincidence, but Daniel Passos might be able to provide some insight (he's the other AGDroid developer) Do you have a github project i can poke at? > I'm really sorry if this is a very basic question, but I haven't been able > to work it out on my own. Any help or documentation would be appreciated. > > > _______________________________________________ > 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/20161013/b1982990/attachment-0001.html From matzew at apache.org Thu Oct 13 14:24:10 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 13 Oct 2016 20:24:10 +0200 Subject: [aerogear-dev] JWT based auth for APNs Message-ID: Hi, I've added a new issue to the HTTP/2 epic, since APNs ("coming later this year") will support Token based authentification: https://issues.jboss.org/browse/AGPUSH-1900 For HTTP/2 we'll be using Pushy, which already has a branch/PR for this feature: https://github.com/relayrides/pushy/pull/319 Cheers, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161013/a7840cb7/attachment.html From michael at 410labs.com Thu Oct 13 17:37:38 2016 From: michael at 410labs.com (Michael Doo) Date: Thu, 13 Oct 2016 17:37:38 -0400 Subject: [aerogear-dev] Aerogear iOS OAuth2 webview issues Message-ID: Hello, When using the iOS OAuth2 library, getting an odd issue where, after signing in and using my 2FA code, I get the permissions page. Fine. On that page, it lists permissions then I click 'Allow'. So far so good. But after clicking 'Allow', it doesn't dismiss the webview or even redirect to a blank screen. Just hangs. From Xcode, hard to see if Google has issues the redirect URL with a code or error. This might be a Google issue (likely), but sending to the list just in case anyone has any tips. Best, Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161013/a780c478/attachment.html From matzew at apache.org Fri Oct 14 04:40:55 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 14 Oct 2016 10:40:55 +0200 Subject: [aerogear-dev] AeroGear Digger: Build Containters Message-ID: Hi, since a few days we have two new repos on aerogear's GH org: * https://github.com/aerogear/digger-build-cli * https://github.com/aerogear/digger-build-containers The first is a Python based CLI, called 'abcd', that knows how to build Android apps; The second is a Linux container that, can be used for running Android builds inside a container, using the abcd tool. I am happy to say that we have a first (0.2.0) release of 'abcd' (see [1]), supporting: * Android native (Gradle / Ant) * Apache Corodova CLI The 'abcd' CLI is used in the latest version of the 'aerogear/mobile-sdk' container ([2]), which supports Android and Cordova! Greetings, Matthias [1] https://github.com/aerogear/digger-build-cli/releases [2] https://hub.docker.com/r/aerogear/mobile-sdk/ -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161014/8ccc2f08/attachment.html From lrossett at redhat.com Fri Oct 14 04:57:20 2016 From: lrossett at redhat.com (Leonardo Rossetti) Date: Fri, 14 Oct 2016 05:57:20 -0300 Subject: [aerogear-dev] digger-build-containers: image and container name per platform Message-ID: Hello, Right now we have one image named "0.1" [1] which contains everything. We could use better names based on platform [2], including a base image. This way we have a base image with the "abcd" cli and platform specific images will be based from the base image to install their specific required tools (java, ant, cordova, etc) and environment variables (ANDROID_HOME for example). Also, I think that it makes sense for the android image to install cordova as well since it is such a small addition that it isn't worth to create another image for android-cordova. WDYT? [1] https://github.com/aerogear/digger-build-containers [2] https://github.com/odra/digger-build-containers/tree/refactor -- Leonardo Rossetti lrossett at redhat.com +55 11 99703 0621 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161014/172c8c94/attachment.html From matzew at apache.org Fri Oct 14 05:00:09 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 14 Oct 2016 11:00:09 +0200 Subject: [aerogear-dev] digger-build-containers: image and container name per platform In-Reply-To: References: Message-ID: I like that idea, but I am wondering what that means for Docker hub. would that mean we add multiple (automated) triggers, per folder ? PS: Can you create a AGDIGGER jira ticket for this, Leo ? On Fri, Oct 14, 2016 at 10:57 AM, Leonardo Rossetti wrote: > Hello, > > Right now we have one image named "0.1" [1] which contains everything. > > We could use better names based on platform [2], including a base image. > > This way we have a base image with the "abcd" cli and platform specific > images will be based from the base image to install their specific required > tools (java, ant, cordova, etc) and environment variables (ANDROID_HOME for > example). > > Also, I think that it makes sense for the android image to install cordova > as well since it is such a small addition that it isn't worth to create > another image for android-cordova. > > WDYT? > > [1] https://github.com/aerogear/digger-build-containers > [2] https://github.com/odra/digger-build-containers/tree/refactor > > -- > Leonardo Rossetti > lrossett at redhat.com > +55 11 99703 0621 > > _______________________________________________ > 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/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161014/e4808110/attachment.html From lrossett at redhat.com Fri Oct 14 05:27:17 2016 From: lrossett at redhat.com (Leonardo Rossetti) Date: Fri, 14 Oct 2016 06:27:17 -0300 Subject: [aerogear-dev] digger-build-containers: image and container name per platform In-Reply-To: References: Message-ID: Correct, we would need one trigger per platform/folder. Jira ticket created: https://issues.jboss.org/browse/AGDIGGER-4 On Fri, Oct 14, 2016 at 6:00 AM, Matthias Wessendorf wrote: > I like that idea, but I am wondering what that means for Docker hub. would > that mean we add multiple (automated) triggers, per folder ? > > > PS: Can you create a AGDIGGER jira ticket for this, Leo ? > > On Fri, Oct 14, 2016 at 10:57 AM, Leonardo Rossetti > wrote: > >> Hello, >> >> Right now we have one image named "0.1" [1] which contains everything. >> >> We could use better names based on platform [2], including a base image. >> >> This way we have a base image with the "abcd" cli and platform specific >> images will be based from the base image to install their specific required >> tools (java, ant, cordova, etc) and environment variables (ANDROID_HOME for >> example). >> >> Also, I think that it makes sense for the android image to install >> cordova as well since it is such a small addition that it isn't worth to >> create another image for android-cordova. >> >> WDYT? >> >> [1] https://github.com/aerogear/digger-build-containers >> [2] https://github.com/odra/digger-build-containers/tree/refactor >> >> -- >> Leonardo Rossetti >> lrossett at redhat.com >> +55 11 99703 0621 >> >> _______________________________________________ >> 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/ > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Leonardo Rossetti lrossett at redhat.com +55 11 99703 0621 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161014/84b58209/attachment-0001.html From matzew at apache.org Fri Oct 14 06:12:50 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 14 Oct 2016 12:12:50 +0200 Subject: [aerogear-dev] digger-build-containers: image and container name per platform In-Reply-To: References: Message-ID: sounds good! On Fri, Oct 14, 2016 at 11:27 AM, Leonardo Rossetti wrote: > Correct, we would need one trigger per platform/folder. > > Jira ticket created: https://issues.jboss.org/browse/AGDIGGER-4 > > On Fri, Oct 14, 2016 at 6:00 AM, Matthias Wessendorf > wrote: > >> I like that idea, but I am wondering what that means for Docker hub. >> would that mean we add multiple (automated) triggers, per folder ? >> >> >> PS: Can you create a AGDIGGER jira ticket for this, Leo ? >> >> On Fri, Oct 14, 2016 at 10:57 AM, Leonardo Rossetti >> wrote: >> >>> Hello, >>> >>> Right now we have one image named "0.1" [1] which contains everything. >>> >>> We could use better names based on platform [2], including a base image. >>> >>> This way we have a base image with the "abcd" cli and platform specific >>> images will be based from the base image to install their specific required >>> tools (java, ant, cordova, etc) and environment variables (ANDROID_HOME for >>> example). >>> >>> Also, I think that it makes sense for the android image to install >>> cordova as well since it is such a small addition that it isn't worth to >>> create another image for android-cordova. >>> >>> WDYT? >>> >>> [1] https://github.com/aerogear/digger-build-containers >>> [2] https://github.com/odra/digger-build-containers/tree/refactor >>> >>> -- >>> Leonardo Rossetti >>> lrossett at redhat.com >>> +55 11 99703 0621 >>> >>> _______________________________________________ >>> 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/ >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Leonardo Rossetti > lrossett at redhat.com > +55 11 99703 0621 > > _______________________________________________ > 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/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161014/e6c89f63/attachment.html From corinnekrych at gmail.com Mon Oct 17 04:43:00 2016 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 17 Oct 2016 10:43:00 +0200 Subject: [aerogear-dev] AeroGear iOS libraries released for Swift2.3... Swift 3 on its way Message-ID: Hello iOS lovers, Swift AeroGear libraries have been moved to run under Xcode8 and run with iOS10. Here is the version to used: - AeroGear-Push-Swift -> 1.3.0 - AeroGearHttp -> 0.8.0 - AeroGearOAuth2 -> 0.8.0 - AeroGear-Push-Swift -> 1.3.0 - AeroGearSyncJsonPatch -> 1.0.0-alpha.5 - AeroGearSyncClientJsonPatch -> 1.0.0-alpha.5 Note that all cookbook demos have been updated accordingly [1]. The next step is to release the libraries to target Swift3, this is coming very soon! Special thanks to our contributor tuzonghua for his work on aerogear-ios-http and aerogear-ios-oauth2. As always feedback and contributions are always welcome. Enjoy! ++ Corinne [1] https://github.com/aerogear/aerogear-ios-cookbook -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161017/2f1e7b5b/attachment.html From matzew at apache.org Mon Oct 17 10:19:13 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 17 Oct 2016 16:19:13 +0200 Subject: [aerogear-dev] AeroGear Digger: Build Containters In-Reply-To: References: Message-ID: we have no also released abcd to the Python Package Index: https://pypi.python.org/pypi/abcd/0.3.0 so you can now run pip install abcd -M On Fri, Oct 14, 2016 at 10:40 AM, Matthias Wessendorf wrote: > Hi, > > since a few days we have two new repos on aerogear's GH org: > * https://github.com/aerogear/digger-build-cli > * https://github.com/aerogear/digger-build-containers > > The first is a Python based CLI, called 'abcd', that knows how to build > Android apps; > The second is a Linux container that, can be used for running Android > builds inside a container, using the abcd tool. > > I am happy to say that we have a first (0.2.0) release of 'abcd' (see > [1]), supporting: > * Android native (Gradle / Ant) > * Apache Corodova CLI > > The 'abcd' CLI is used in the latest version of the 'aerogear/mobile-sdk' > container ([2]), which supports Android and Cordova! > > > Greetings, > Matthias > > [1] https://github.com/aerogear/digger-build-cli/releases > [2] https://hub.docker.com/r/aerogear/mobile-sdk/ > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161017/179ebf7d/attachment.html From lrossett at redhat.com Tue Oct 18 05:04:18 2016 From: lrossett at redhat.com (Leonardo Rossetti) Date: Tue, 18 Oct 2016 07:04:18 -0200 Subject: [aerogear-dev] [digger-build-cli] thoughts around the CLI usage Message-ID: Hello, I was thinking on some enhancements around the CLI usage: *Log files* Right now it automatically saves the command output into a text file, but it wouldn't need to since you can always use a pipe to to that like "abcd buid > build.log" or "abcd build | tee build.log". *Setup command* A setup command to set default configurations "abcd setup" such as default android debug keystore config, android home path, cordova path, etc. *Build config file* An optional hidden yaml/json file ".digger" or ".abcd" that would have some information for the CLI such as the build type and platform ("andoid" and "gradle" for example) in the future this could also specify a different build version or path to use. *Debug flag* Commands that start another process (such as "build' or "sign") could use a flag "--debug" which if set to true would output everything into stdout, otherwise would just print the actual command response (for example the build command would output a list of generated APKs). Default value for debug would be true. WDYT? -- Leonardo Rossetti lrossett at redhat.com +55 11 99703 0621 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161018/e218f1a4/attachment.html From aliok at redhat.com Tue Oct 18 05:57:55 2016 From: aliok at redhat.com (Ali Ok) Date: Tue, 18 Oct 2016 12:57:55 +0300 Subject: [aerogear-dev] [digger-build-cli] thoughts around the CLI usage In-Reply-To: References: Message-ID: > > > *Log files*Right now it automatically saves the command output into a > text file, but it wouldn't need to since you can always use a pipe to to > that like "abcd buid > build.log" or "abcd build | tee build.log". +1. Leave it to the user how to save the logs. > > *Build config file*An optional hidden yaml/json file ".digger" or ".abcd" > that would have some information for the CLI such as the build type and > platform ("andoid" and "gradle" for example) in the future this could also > specify a different build version or path to use. You mean in projects, right? Like travis.yml file. *Setup command* A setup command to set default configurations "abcd setup" such as default > android debug keystore config, android home path, cordova path, etc. I think saving these things into ~/digger-config.yml would be great. +1 on the others too. Awesome suggestions Leonardo! On Tue, Oct 18, 2016 at 12:04 PM, Leonardo Rossetti wrote: > Hello, > > I was thinking on some enhancements around the CLI usage: > > *Log files* > Right now it automatically saves the command output into a text file, but > it wouldn't need to since you can always use a pipe to to that like "abcd > buid > build.log" or "abcd build | tee build.log". > > *Setup command* > A setup command to set default configurations "abcd setup" such as default > android debug keystore config, android home path, cordova path, etc. > > *Build config file* > An optional hidden yaml/json file ".digger" or ".abcd" that would have > some information for the CLI such as the build type and platform ("andoid" > and "gradle" for example) in the future this could also specify a different > build version or path to use. > > *Debug flag* > Commands that start another process (such as "build' or "sign") could use > a flag "--debug" which if set to true would output everything into stdout, > otherwise would just print the actual command response (for example the > build command would output a list of generated APKs). Default value for > debug would be true. > > WDYT? > -- > Leonardo Rossetti > lrossett at redhat.com > +55 11 99703 0621 > > _______________________________________________ > 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/20161018/2df6e360/attachment-0001.html From matzew at apache.org Tue Oct 18 06:05:24 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 18 Oct 2016 12:05:24 +0200 Subject: [aerogear-dev] [digger-build-cli] thoughts around the CLI usage In-Reply-To: References: Message-ID: Great suggestions for us moving forward w/ 'abcd' @Leo can you file an EPIC on AGDIGGER JIRA instance, where each of the four suggestions is its own issue ? Thx, Matthias On Tue, Oct 18, 2016 at 11:57 AM, Ali Ok wrote: > >> *Log files*Right now it automatically saves the command output into a >> text file, but it wouldn't need to since you can always use a pipe to to >> that like "abcd buid > build.log" or "abcd build | tee build.log". > > +1. > Leave it to the user how to save the logs. > > >> >> *Build config file*An optional hidden yaml/json file ".digger" or >> ".abcd" that would have some information for the CLI such as the build type >> and platform ("andoid" and "gradle" for example) in the future this could >> also specify a different build version or path to use. > > You mean in projects, right? Like travis.yml file. > > *Setup command* > > A setup command to set default configurations "abcd setup" such as default >> android debug keystore config, android home path, cordova path, etc. > > I think saving these things into ~/digger-config.yml would be great. > > +1 on the others too. > > Awesome suggestions Leonardo! > > > On Tue, Oct 18, 2016 at 12:04 PM, Leonardo Rossetti > wrote: > >> Hello, >> >> I was thinking on some enhancements around the CLI usage: >> >> *Log files* >> Right now it automatically saves the command output into a text file, but >> it wouldn't need to since you can always use a pipe to to that like "abcd >> buid > build.log" or "abcd build | tee build.log". >> >> *Setup command* >> A setup command to set default configurations "abcd setup" such as >> default android debug keystore config, android home path, cordova path, etc. >> >> *Build config file* >> An optional hidden yaml/json file ".digger" or ".abcd" that would have >> some information for the CLI such as the build type and platform ("andoid" >> and "gradle" for example) in the future this could also specify a different >> build version or path to use. >> >> *Debug flag* >> Commands that start another process (such as "build' or "sign") could use >> a flag "--debug" which if set to true would output everything into stdout, >> otherwise would just print the actual command response (for example the >> build command would output a list of generated APKs). Default value for >> debug would be true. >> >> WDYT? >> -- >> Leonardo Rossetti >> lrossett at redhat.com >> +55 11 99703 0621 >> >> _______________________________________________ >> 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/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161018/56467594/attachment.html From lrossett at redhat.com Tue Oct 18 07:17:20 2016 From: lrossett at redhat.com (Leonardo Rossetti) Date: Tue, 18 Oct 2016 09:17:20 -0200 Subject: [aerogear-dev] [digger-build-cli] thoughts around the CLI usage In-Reply-To: References: Message-ID: Epic created: https://issues.jboss.org/browse/AGDIGGER-9 On Tue, Oct 18, 2016 at 8:05 AM, Matthias Wessendorf wrote: > Great suggestions for us moving forward w/ 'abcd' > > @Leo can you file an EPIC on AGDIGGER JIRA instance, where each of the > four suggestions is its own issue ? > > Thx, > Matthias > > On Tue, Oct 18, 2016 at 11:57 AM, Ali Ok wrote: > >> >>> *Log files*Right now it automatically saves the command output into a >>> text file, but it wouldn't need to since you can always use a pipe to to >>> that like "abcd buid > build.log" or "abcd build | tee build.log". >> >> +1. >> Leave it to the user how to save the logs. >> >> >>> >>> *Build config file*An optional hidden yaml/json file ".digger" or >>> ".abcd" that would have some information for the CLI such as the build type >>> and platform ("andoid" and "gradle" for example) in the future this could >>> also specify a different build version or path to use. >> >> You mean in projects, right? Like travis.yml file. >> >> *Setup command* >> >> A setup command to set default configurations "abcd setup" such as >>> default android debug keystore config, android home path, cordova path, etc. >> >> I think saving these things into ~/digger-config.yml would be great. >> >> +1 on the others too. >> >> Awesome suggestions Leonardo! >> >> >> On Tue, Oct 18, 2016 at 12:04 PM, Leonardo Rossetti >> wrote: >> >>> Hello, >>> >>> I was thinking on some enhancements around the CLI usage: >>> >>> *Log files* >>> Right now it automatically saves the command output into a text file, >>> but it wouldn't need to since you can always use a pipe to to that like >>> "abcd buid > build.log" or "abcd build | tee build.log". >>> >>> *Setup command* >>> A setup command to set default configurations "abcd setup" such as >>> default android debug keystore config, android home path, cordova path, etc. >>> >>> *Build config file* >>> An optional hidden yaml/json file ".digger" or ".abcd" that would have >>> some information for the CLI such as the build type and platform ("andoid" >>> and "gradle" for example) in the future this could also specify a different >>> build version or path to use. >>> >>> *Debug flag* >>> Commands that start another process (such as "build' or "sign") could >>> use a flag "--debug" which if set to true would output everything into >>> stdout, otherwise would just print the actual command response (for example >>> the build command would output a list of generated APKs). Default value for >>> debug would be true. >>> >>> WDYT? >>> -- >>> Leonardo Rossetti >>> lrossett at redhat.com >>> +55 11 99703 0621 >>> >>> _______________________________________________ >>> 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/ > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Leonardo Rossetti lrossett at redhat.com +55 11 99703 0621 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161018/d28fb099/attachment.html From matzew at apache.org Tue Oct 18 11:08:44 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 18 Oct 2016 17:08:44 +0200 Subject: [aerogear-dev] CLI docs published Message-ID: hello, there are now published docs for the abcd tool: http://digger-build-cli.readthedocs.io/en/latest/ Cheers, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161018/bf30880d/attachment.html From aliok at redhat.com Fri Oct 21 12:40:47 2016 From: aliok at redhat.com (Ali Ok) Date: Fri, 21 Oct 2016 17:40:47 +0100 Subject: [aerogear-dev] [digger-build-cli] thoughts around the CLI usage In-Reply-To: References: Message-ID: An addition here: "--version" command. Sometimes it is necessary to see what version of abcd is the one that is used. Created https://issues.jboss.org/browse/AGDIGGER-14 part of the epic. On Tue, Oct 18, 2016 at 12:17 PM, Leonardo Rossetti wrote: > Epic created: https://issues.jboss.org/browse/AGDIGGER-9 > > On Tue, Oct 18, 2016 at 8:05 AM, Matthias Wessendorf > wrote: > >> Great suggestions for us moving forward w/ 'abcd' >> >> @Leo can you file an EPIC on AGDIGGER JIRA instance, where each of the >> four suggestions is its own issue ? >> >> Thx, >> Matthias >> >> On Tue, Oct 18, 2016 at 11:57 AM, Ali Ok wrote: >> >>> >>>> *Log files*Right now it automatically saves the command output into a >>>> text file, but it wouldn't need to since you can always use a pipe to to >>>> that like "abcd buid > build.log" or "abcd build | tee build.log". >>> >>> +1. >>> Leave it to the user how to save the logs. >>> >>> >>>> >>>> *Build config file*An optional hidden yaml/json file ".digger" or >>>> ".abcd" that would have some information for the CLI such as the build type >>>> and platform ("andoid" and "gradle" for example) in the future this could >>>> also specify a different build version or path to use. >>> >>> You mean in projects, right? Like travis.yml file. >>> >>> *Setup command* >>> >>> A setup command to set default configurations "abcd setup" such as >>>> default android debug keystore config, android home path, cordova path, etc. >>> >>> I think saving these things into ~/digger-config.yml would be great. >>> >>> +1 on the others too. >>> >>> Awesome suggestions Leonardo! >>> >>> >>> On Tue, Oct 18, 2016 at 12:04 PM, Leonardo Rossetti >> > wrote: >>> >>>> Hello, >>>> >>>> I was thinking on some enhancements around the CLI usage: >>>> >>>> *Log files* >>>> Right now it automatically saves the command output into a text file, >>>> but it wouldn't need to since you can always use a pipe to to that like >>>> "abcd buid > build.log" or "abcd build | tee build.log". >>>> >>>> *Setup command* >>>> A setup command to set default configurations "abcd setup" such as >>>> default android debug keystore config, android home path, cordova path, etc. >>>> >>>> *Build config file* >>>> An optional hidden yaml/json file ".digger" or ".abcd" that would have >>>> some information for the CLI such as the build type and platform ("andoid" >>>> and "gradle" for example) in the future this could also specify a different >>>> build version or path to use. >>>> >>>> *Debug flag* >>>> Commands that start another process (such as "build' or "sign") could >>>> use a flag "--debug" which if set to true would output everything into >>>> stdout, otherwise would just print the actual command response (for example >>>> the build command would output a list of generated APKs). Default value for >>>> debug would be true. >>>> >>>> WDYT? >>>> -- >>>> Leonardo Rossetti >>>> lrossett at redhat.com >>>> +55 11 99703 0621 >>>> >>>> _______________________________________________ >>>> 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/ >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Leonardo Rossetti > lrossett at redhat.com > +55 11 99703 0621 > > _______________________________________________ > 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/20161021/f413d39d/attachment-0001.html From matzew at apache.org Fri Oct 21 15:33:16 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 21 Oct 2016 21:33:16 +0200 Subject: [aerogear-dev] [Build Containers] Kotlin / Ceylon language support Message-ID: Hi, I tried our Android Build Container with Android apps written in different JVM languages. Out of the box this Kotlin based app was working: https://github.com/matzew/NotesKotlin yay! After installing Ceylon-SDK to our Docker-formatted container image: https://github.com/matzew/digger-build-containers/tree/Ceylon I was able to build another Android App, written in Ceylon: https://github.com/matzew/TimesLon/tree/Error-Fix Have fun! -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161021/22dc38f8/attachment.html From matzew at apache.org Sat Oct 22 13:14:04 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Sat, 22 Oct 2016 19:14:04 +0200 Subject: [aerogear-dev] [Build Containers] CI integration for Android builds Message-ID: Hi, sometimes Travis' Android support is a bit instable..., we have noticed that on our own Anroid apps, as well on our different libraries. Today I've done a simple test to use our new tool for CI builds of Android apps (see [1]). For now I've used Travis ;-) but not their Android support, I am just executing a few docker commands. So this solution is also easy to use on other systems, like Jenkins. Works fine: https://travis-ci.org/matzew/helloworld-android-gradle/builds/169769410#L389 However, there is one bug on the underlying Python CLI (see [2])....., but overall it's something we should be looking forward to use! Cheers, Matthias [1] https://github.com/matzew/helloworld-android-gradle/pull/2 [2] https://issues.jboss.org/browse/AGDIGGER-15 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161022/4a429719/attachment.html From morten.oftedal at adresseavisen.no Tue Oct 25 08:24:33 2016 From: morten.oftedal at adresseavisen.no (Morten Oftedal) Date: Tue, 25 Oct 2016 12:24:33 +0000 Subject: [aerogear-dev] mutable-content on apns notification. Message-ID: Hi! Currently developing an application using aerogear to send notifications, mostly to android and IOS devices. We are currently in the process of enabling support for pictures in notifications, downloaded from an URL. On android, this is not a problem, simply adding the URL as user data does the trick. Using iOS however requires the message sent from the server to include a key; mutable-content with a value of 1, described here: https://developer.apple.com/library/prerelease/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ModifyingNotifications.html Is this supported through aerogear, and if not are there any plans for supporting it? Best Regards Morten Oftedal Adresseavisen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161025/c82ce597/attachment.html From mywork.jatin at gmail.com Fri Oct 28 16:06:07 2016 From: mywork.jatin at gmail.com (mywork.jatin at gmail.com) Date: Sat, 29 Oct 2016 01:36:07 +0530 Subject: [aerogear-dev] (no subject) Message-ID: <5813afba.c632620a.c99f1.431b@mx.google.com> I am looking for contributing to AeroGear project, I want to work on the issue AGDROID-568. I?m new so I don?t know how to setup whole project. Can someone from team help me from basic like how to setup project and test project? Jatin -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161029/a57fdff0/attachment.html From idel.pivnitskiy at gmail.com Fri Oct 28 19:38:36 2016 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Fri, 28 Oct 2016 16:38:36 -0700 Subject: [aerogear-dev] (no subject) In-Reply-To: <5813afba.c632620a.c99f1.431b@mx.google.com> References: <5813afba.c632620a.c99f1.431b@mx.google.com> Message-ID: Hi Jatin, Thanks for your interest in the AeroGear project! For the first look on the project, you can just launch the AeroGear UPS on OpenShift. Follow this guide [1] and just press the button "Launch on OpenShift". You will be able to set up the server really quickly. Go to the admin panel and try to make basic settings for a new app/device. The Docker container is also a good opportunity to run it quickly. It's up to you. When you will be ready to go deeper, to the source code, try to clone the repository and follow the next guide [2]. It contains a good explanation of the main UPS workflow. You will be able to set up and configure everything that you need to run the UPS (WildFly/database/message queue/etc.). If you will have any specific questions or problems when you will follow this guides, ask them here. Also try to explore the AeroGear website, it contains a lot of interesting materials. Enjoy your work on this project! [1] https://github.com/aerogear/aerogear-unifiedpush-server#getting-started [2] https://aerogear.org/docs/unifiedpush/ups_userguide/index/ Best regards, Idel Pivnitskiy -- Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy On Fri, Oct 28, 2016 at 1:06 PM, wrote: > I am looking for contributing to AeroGear project, I want to work on the > issue AGDROID-568 . I?m new > so I don?t know how to setup whole project. > > Can someone from team help me from basic like how to setup project and > test project? > > > > Jatin > > > > _______________________________________________ > 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/20161028/e7cec366/attachment-0001.html From dpassos at redhat.com Fri Oct 28 21:26:38 2016 From: dpassos at redhat.com (Daniel Passos) Date: Sat, 29 Oct 2016 02:26:38 +0100 Subject: [aerogear-dev] (no subject) In-Reply-To: <5813afba.c632620a.c99f1.431b@mx.google.com> References: <5813afba.c632620a.c99f1.431b@mx.google.com> Message-ID: Hi Jatin, For AeroGear Android we have a doc[1] for it. It's a little outdate about the version but still the same steps. https://aerogear.org/docs/guides/aerogear-android/how-to-build-aerogear-android/ On Fri, Oct 28, 2016 at 9:06 PM, wrote: > I am looking for contributing to AeroGear project, I want to work on the > issue AGDROID-568 . I?m new > so I don?t know how to setup whole project. > > Can someone from team help me from basic like how to setup project and > test project? > > > > Jatin > > > > _______________________________________________ > 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/20161029/4a1de5c3/attachment.html From mywork.jatin at gmail.com Sat Oct 29 17:22:34 2016 From: mywork.jatin at gmail.com (mywork.jatin at gmail.com) Date: Sun, 30 Oct 2016 02:52:34 +0530 Subject: [aerogear-dev] (no subject) In-Reply-To: References: <5813afba.c632620a.c99f1.431b@mx.google.com> Message-ID: <58151327.82ca620a.67dc5.60f9@mx.google.com> Thanks Idel and Daniel for help, but some how I?m unable to use openshift launch button for AeroGear, which making account its giving a message No New Users Accepted The OpenShift Online (Next Gen) Developer Preview is here! We will not be accepting new users onto the OpenShift Online (v2) platform. So now I?m trying to deploy war files on Jboss EAP7 stand alone server usind there files https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.2.0-alpha.3 but there are multiple war files and I don?t know which one to deploy first. And I am also going to try them using docker on AWS. Jatin From: Idel Pivnitskiy Sent: Saturday, October 29, 2016 5:11 AM To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] (no subject) Hi Jatin, Thanks for your interest in the AeroGear project! For the first look on the project, you can just launch the AeroGear UPS on OpenShift. Follow?this guide [1] and just press the button "Launch on OpenShift". You will be able to set up the server really quickly. Go to the admin panel and try to make basic settings for a new app/device. The Docker container is also a good opportunity to run it quickly. It's up to you. When you will be ready to go deeper, to the source code, try to clone the repository and follow the next guide [2]. It contains a good explanation of the main UPS workflow. You will be able to set up and configure everything that you need to run the UPS (WildFly/database/message queue/etc.). If you will have any specific questions or problems when you will follow this guides, ask them here. Also try to explore the AeroGear website, it contains a lot of interesting materials. Enjoy your work on this project! [1]?https://github.com/aerogear/aerogear-unifiedpush-server#getting-started [2]?https://aerogear.org/docs/unifiedpush/ups_userguide/index/ Best regards, Idel Pivnitskiy -- Twitter: @idelpivnitskiy GitHub:?@idelpivnitskiy On Fri, Oct 28, 2016 at 1:06 PM, wrote: I am looking for contributing to AeroGear project, I want to work on the issue AGDROID-568. I?m new so I don?t know how to setup whole project. Can someone from team help me from basic like how to setup project and test project? ? Jatin ? _______________________________________________ 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/20161030/869d7e87/attachment.html From mywork.jatin at gmail.com Sun Oct 30 08:57:03 2016 From: mywork.jatin at gmail.com (mywork.jatin at gmail.com) Date: Sun, 30 Oct 2016 18:27:03 +0530 Subject: [aerogear-dev] =?utf-8?q?_Getting_the_error_while_deploying_?= =?utf-8?b?4oCcdW5pZmllZHB1c2gtc2VydmVyLXdpbGRmbHkud2Fy4oCd?= Message-ID: <5815ee2b.48c6620a.11e1d.91ac@mx.google.com> Getting the error while deploying ?unifiedpush-server-wildfly.war?. I did all configuration following the Documentation but getting this error while deploying war file. I deployed ?unifiedpush-auth-server.war? which is deployed without any error, but I don?t know use of this. Cannot upload deployment: {"WFLYCTL0080: Failed services" => {"jboss.persistenceunit.\"unifiedpush-server-wildfly.war#unifiedpush-default\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"unifiedpush-server-wildfly.war#unifiedpush-default\": javax.persistence.PersistenceException: [PersistenceUnit: unifiedpush-default] Unable to build Hibernate SessionFactory Caused by: javax.persistence.PersistenceException: [PersistenceUnit: unifiedpush-default] Unable to build Hibernate SessionFactory Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [adm_variant]"},"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear.unifiedpush.message.MetricsCollector\".metricsQueue is missing [jboss.naming.context.java.queue.MetricsQueue]","jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer\".gcmPushMessageQueue is missing [jboss.naming.context.java.queue.GCMPushMessageQueue]","jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear.unifiedpush.message.MetricsCollector\".batchLoadedQueue is missing [jboss.naming.context.java.queue.BatchLoadedQueue]","jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer\".simplePushMessageQueue is missing [jboss.naming.context.java.queue.SimplePushMessageQueue]","jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer\".admPushMessageQueue is missing [jboss.naming.context.java.queue.AdmPushMessageQueue]","jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear.unifiedpush.message.jms.VariantMetricInformationProducer\".metricsQueue is missing [jboss.naming.context.java.queue.MetricsQueue]","jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer\".apnsPushMessageQueue is missing [jboss.naming.context.java.queue.APNsPushMessageQueue]","jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear.unifiedpush.message.MetricsCollector\".allBatchesLoaded is missing [jboss.naming.context.java.queue.AllBatchesLoadedQueue]","jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer\".mpnsPushMessageQueue is missing [jboss.naming.context.java.queue.MPNSPushMessageQueue]","jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer\".wnsPushMessageQueue is missing [jboss.naming.context.java.queue.WNSPushMessageQueue]"]} Jatin -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161030/cb009a31/attachment-0001.html From idel.pivnitskiy at gmail.com Sun Oct 30 21:38:19 2016 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Sun, 30 Oct 2016 18:38:19 -0700 Subject: [aerogear-dev] (no subject) In-Reply-To: <58151327.82ca620a.67dc5.60f9@mx.google.com> References: <5813afba.c632620a.c99f1.431b@mx.google.com> <58151327.82ca620a.67dc5.60f9@mx.google.com> Message-ID: Hi Jatin, So now I?m trying to deploy war files on Jboss EAP7 stand alone server > usind there files https://github.com/aerogear/aerogear-unifiedpush-server/ > releases/tag/1.2.0-alpha.3 but there are multiple war files and I don?t > know which one to deploy first. > > And I am also going to try them using docker on AWS. > See "Deploy the UnifiedPush Server" section in the guide which I sent to you early: https://aerogear.org/docs/unifiedpush/ups_userguide/index/#deploy Best regards, Idel Pivnitskiy -- Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy On Sat, Oct 29, 2016 at 2:22 PM, wrote: > Thanks Idel and Daniel for help, but some how I?m unable to use openshift > launch button for AeroGear, which making account its giving a message > No New Users Accepted > > The OpenShift Online (Next Gen) Developer Preview is here! We will not be > accepting new users onto the OpenShift Online (v2) platform. > > So now I?m trying to deploy war files on Jboss EAP7 stand alone server > usind there files https://github.com/aerogear/aerogear-unifiedpush-server/ > releases/tag/1.2.0-alpha.3 but there are multiple war files and I don?t > know which one to deploy first. > > And I am also going to try them using docker on AWS. > > > > Jatin > > > > *From: *Idel Pivnitskiy > *Sent: *Saturday, October 29, 2016 5:11 AM > *To: *AeroGear Developer Mailing List > *Subject: *Re: [aerogear-dev] (no subject) > > > > Hi Jatin, > > > > Thanks for your interest in the AeroGear project! > > > > For the first look on the project, you can just launch the AeroGear UPS on > OpenShift. Follow this guide [1] and just press the button "Launch on > OpenShift". You will be able to set up the server really quickly. Go to the > admin panel and try to make basic settings for a new app/device. The Docker > container is also a good opportunity to run it quickly. It's up to you. > > > > When you will be ready to go deeper, to the source code, try to clone the > repository and follow the next guide [2]. It contains a good explanation of > the main UPS workflow. You will be able to set up and configure everything > that you need to run the UPS (WildFly/database/message queue/etc.). If you > will have any specific questions or problems when you will follow this > guides, ask them here. > > > > Also try to explore the AeroGear website, it contains a lot of interesting > materials. Enjoy your work on this project! > > > > [1] https://github.com/aerogear/aerogear-unifiedpush- > server#getting-started > > [2] https://aerogear.org/docs/unifiedpush/ups_userguide/index/ > > > Best regards, > > Idel Pivnitskiy > > -- > > Twitter: @idelpivnitskiy > > GitHub: @idelpivnitskiy > > > > On Fri, Oct 28, 2016 at 1:06 PM, wrote: > > I am looking for contributing to AeroGear project, I want to work on the > issue AGDROID-568 . I?m new > so I don?t know how to setup whole project. > > Can someone from team help me from basic like how to setup project and > test project? > > > > Jatin > > > > > _______________________________________________ > 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/20161030/bffa6f45/attachment.html From vinod.gorla at kroger.com Mon Oct 31 16:53:00 2016 From: vinod.gorla at kroger.com (Gorla, Vinod (NonEmp)) Date: Mon, 31 Oct 2016 20:53:00 +0000 Subject: [aerogear-dev] Support for Aerogear Message-ID: Hi Aerogear team, Now that Redhat has Feedhenry as mobile platform for both development and backend how much support will Aerogear receive from Redhat? I have read that LiveOak MBaaS is stopped. Can you please give me some info that would be helpful for me to make a right choice for the push platform? Thanks Vinod ________________________________ This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is confidential and protected by law from unauthorized disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161031/eab5736c/attachment.html From idel.pivnitskiy at gmail.com Mon Oct 31 17:48:26 2016 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Mon, 31 Oct 2016 14:48:26 -0700 Subject: [aerogear-dev] =?utf-8?q?Getting_the_error_while_deploying_?= =?utf-8?b?4oCcdW5pZmllZHB1c2gtc2VydmVyLXdpbGRmbHkud2Fy4oCd?= In-Reply-To: <5815ee2b.48c6620a.11e1d.91ac@mx.google.com> References: <5815ee2b.48c6620a.11e1d.91ac@mx.google.com> Message-ID: Hi Jatin, Have you finished all previous steps for Message Queue and Database configuration? Are you sure that you completed this steps without errors in logs? Looks like you don't have a table with name "adm_variant". Also, check that you pulled the latest version of the source code from the repository. I did the whole installation process on the new machine recently, everything worked well. Used WildFly 10 and PostgreSQL 9.5.4. Best regards, Idel Pivnitskiy -- Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy On Sun, Oct 30, 2016 at 5:57 AM, wrote: > Getting the error while deploying ?unifiedpush-server-wildfly.war?. I did > all configuration following the Documentation > but > getting this error while deploying war file. > > I deployed ?unifiedpush-auth-server.war? which is deployed without any > error, but I don?t know use of this. > > > > > > Cannot upload deployment: {"WFLYCTL0080: Failed services" => > {"jboss.persistenceunit.\"unifiedpush-server-wildfly.war#unifiedpush-default\"" > => "org.jboss.msc.service.StartException in service > jboss.persistenceunit.\"unifiedpush-server-wildfly.war#unifiedpush-default\": > javax.persistence.PersistenceException: [PersistenceUnit: > unifiedpush-default] Unable to build Hibernate SessionFactory Caused by: > javax.persistence.PersistenceException: [PersistenceUnit: > unifiedpush-default] Unable to build Hibernate SessionFactory Caused by: > org.hibernate.tool.schema.spi.SchemaManagementException: > Schema-validation: missing table [adm_variant]"},"WFLYCTL0180: Services > with missing/unavailable dependencies" => ["jboss.naming.context.java. > module.ag-push.ag-push.env.\"org.jboss.aerogear.unifiedpush.message. > MetricsCollector\".metricsQueue is missing [jboss.naming.context.java. > queue.MetricsQueue]","jboss.naming.context.java.module.ag- > push.ag-push.env.\"org.jboss.aerogear.unifiedpush.message.jms. > MessageHolderWithVariantsProducer\".gcmPushMessageQueue is missing > [jboss.naming.context.java.queue.GCMPushMessageQueue]"," > jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear. > unifiedpush.message.MetricsCollector\".batchLoadedQueue is missing > [jboss.naming.context.java.queue.BatchLoadedQueue]"," > jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear. > unifiedpush.message.jms.MessageHolderWithVariantsProducer\".simplePushMessageQueue > is missing [jboss.naming.context.java.queue.SimplePushMessageQueue]" > ,"jboss.naming.context.java.module.ag-push.ag-push.env.\" > org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer\".admPushMessageQueue > is missing [jboss.naming.context.java.queue.AdmPushMessageQueue]"," > jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear. > unifiedpush.message.jms.VariantMetricInformationProducer\".metricsQueue > is missing [jboss.naming.context.java.queue.MetricsQueue]","jboss. > naming.context.java.module.ag-push.ag-push.env.\"org.jboss. > aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer\".apnsPushMessageQueue > is missing [jboss.naming.context.java.queue.APNsPushMessageQueue]"," > jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear. > unifiedpush.message.MetricsCollector\".allBatchesLoaded is missing > [jboss.naming.context.java.queue.AllBatchesLoadedQueue]", > "jboss.naming.context.java.module.ag-push.ag-push.env.\" > org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer\".mpnsPushMessageQueue > is missing [jboss.naming.context.java.queue.MPNSPushMessageQueue]"," > jboss.naming.context.java.module.ag-push.ag-push.env.\"org.jboss.aerogear. > unifiedpush.message.jms.MessageHolderWithVariantsProducer\".wnsPushMessageQueue > is missing [jboss.naming.context.java.queue.WNSPushMessageQueue]"]} > > > > > > > > Jatin > > _______________________________________________ > 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/20161031/fb5a1ae1/attachment-0001.html