From aliok at redhat.com Wed Aug 2 03:44:45 2017 From: aliok at redhat.com (Ali Ok) Date: Wed, 2 Aug 2017 10:44:45 +0300 Subject: [aerogear-dev] AGDIGGER JIRA components In-Reply-To: References: Message-ID: Hi Leo and Wei, Any ideas? On Mon, Jul 31, 2017 at 10:36 AM, Matthias Wessendorf wrote: > sure thing! > > once we have agreed on them, I'll go ahead and update them > > On Mon, Jul 31, 2017 at 9:03 AM, Ali Ok wrote: > >> Hi, >> >> I think we need to update our JIRA components in AGDIGGER project. >> >> Perhaps these: >> >> - Android support >> - IOS support >> - Ansible Installer >> - Sample (I mean sample Jenkinsfiles) >> - Node client >> - Java client >> >> Anything missing or strange? >> >> @Matthias, can you do that? >> >> Cheers, >> Ali >> > > > > -- > 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/20170802/1e1e16e6/attachment.html From weil at redhat.com Wed Aug 2 04:31:12 2017 From: weil at redhat.com (Wei Li) Date: Wed, 2 Aug 2017 09:31:12 +0100 Subject: [aerogear-dev] AGDIGGER JIRA components In-Reply-To: References: Message-ID: I think these components are reasonable. On Wed, Aug 2, 2017 at 8:44 AM, Ali Ok wrote: > Hi Leo and Wei, > > Any ideas? > > > On Mon, Jul 31, 2017 at 10:36 AM, Matthias Wessendorf > wrote: > >> sure thing! >> >> once we have agreed on them, I'll go ahead and update them >> >> On Mon, Jul 31, 2017 at 9:03 AM, Ali Ok wrote: >> >>> Hi, >>> >>> I think we need to update our JIRA components in AGDIGGER project. >>> >>> Perhaps these: >>> >>> - Android support >>> - IOS support >>> - Ansible Installer >>> - Sample (I mean sample Jenkinsfiles) >>> - Node client >>> - Java client >>> >>> Anything missing or strange? >>> >>> @Matthias, can you do that? >>> >>> Cheers, >>> Ali >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> twitter: http://twitter.com/mwessendorf >> > > -- WEI LI SENIOR SOFTWARE ENGINEER Red Hat Mobile weil at redhat.com M: +353862393272 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170802/9dac4ccf/attachment.html From weil at redhat.com Wed Aug 2 06:45:17 2017 From: weil at redhat.com (Wei Li) Date: Wed, 2 Aug 2017 11:45:17 +0100 Subject: [aerogear-dev] Publish new release of digger-java client Message-ID: Hi AeroGear community, We have been using the digger-java client module in our product for the last couple of months. At this point I think the API is stable enough and I think we should release them. However, because at some point during the 1.0.0-SNAPSHOT version, we have introduced some broken changes (and our product is released using the version before the broken changes are made), we now need to do 2 releases; 1. Release 1.0.1 from this branch: https://github.com/wei-lee/digger-java/tree/fix-for-3-18-release. This is before the broken change is introduced. 2. From master (1.0.2). Apologies in advance for the manually version change. Matthias does point it out that it is not the right way to do it. So, can we publish those releases? Sorry for the problem we have caused, I promise it won't be like this the next time.... -- WEI LI SENIOR SOFTWARE ENGINEER Red Hat Mobile weil at redhat.com M: +353862393272 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170802/e01047fb/attachment.html From matzew at apache.org Wed Aug 2 06:57:21 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 2 Aug 2017 12:57:21 +0200 Subject: [aerogear-dev] Publish new release of digger-java client In-Reply-To: References: Message-ID: On Wed, Aug 2, 2017 at 12:45 PM, Wei Li wrote: > Hi AeroGear community, > > We have been using the digger-java client module in our product for the > last couple of months. At this point I think the API is stable enough and I > think we should release them. > > However, because at some point during the 1.0.0-SNAPSHOT version, we have > introduced some broken changes (and our product is released using the > version before the broken changes are made), we now need to do 2 releases; > > 1. Release 1.0.1 from this branch: https://github.com/ > wei-lee/digger-java/tree/fix-for-3-18-release. This is before the broken > change is introduced. > we can release this, let's make a branch, with a more reasonable name, available on upstream > 2. From master (1.0.2). > ok So, why do we need an old release? Not sure I really get that. > > Apologies in advance for the manually version change. Matthias does point > it out that it is not the right way to do it. > > So, can we publish those releases? Sorry for the problem we have caused, I > promise it won't be like this the next time.... > there are no big problems. I'd suggest we simply continue to follow a normal java release process, as discussed here and avoid manual bumps. Also, it never hurts to release bits to the community very often (release early, release often). This likely avoids issues like the above -M > > > -- > > WEI LI > > SENIOR SOFTWARE ENGINEER > > Red Hat Mobile > > weil at redhat.com M: +353862393272 > > > _______________________________________________ > 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/20170802/1621794f/attachment.html From matzew at apache.org Wed Aug 2 06:59:42 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 2 Aug 2017 12:59:42 +0200 Subject: [aerogear-dev] Publish new release of digger-java client In-Reply-To: References: Message-ID: Related, are we OK to release org.jboss.aerogear::jenkins-client in version 0.3.8 - to maven central ? On Wed, Aug 2, 2017 at 12:57 PM, Matthias Wessendorf wrote: > > > On Wed, Aug 2, 2017 at 12:45 PM, Wei Li wrote: > >> Hi AeroGear community, >> >> We have been using the digger-java client module in our product for the >> last couple of months. At this point I think the API is stable enough and I >> think we should release them. >> >> However, because at some point during the 1.0.0-SNAPSHOT version, we have >> introduced some broken changes (and our product is released using the >> version before the broken changes are made), we now need to do 2 releases; >> >> 1. Release 1.0.1 from this branch: https://github.com/wei >> -lee/digger-java/tree/fix-for-3-18-release. This is before the broken >> change is introduced. >> > > we can release this, let's make a branch, with a more reasonable name, > available on upstream > > >> 2. From master (1.0.2). >> > > ok > > So, why do we need an old release? Not sure I really get that. > > >> >> Apologies in advance for the manually version change. Matthias does point >> it out that it is not the right way to do it. >> >> So, can we publish those releases? Sorry for the problem we have caused, >> I promise it won't be like this the next time.... >> > > there are no big problems. I'd suggest we simply continue to follow a > normal java release process, as discussed here and avoid manual bumps. > > Also, it never hurts to release bits to the community very often (release > early, release often). This likely avoids issues like the above > > -M > >> >> >> -- >> >> WEI LI >> >> SENIOR SOFTWARE ENGINEER >> >> Red Hat Mobile >> >> weil at redhat.com M: +353862393272 >> >> >> _______________________________________________ >> 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 > -- 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/20170802/05cc0e02/attachment-0001.html From matzew at apache.org Wed Aug 2 07:00:22 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 2 Aug 2017 13:00:22 +0200 Subject: [aerogear-dev] Publish new release of digger-java client In-Reply-To: References: Message-ID: On Wed, Aug 2, 2017 at 12:57 PM, Matthias Wessendorf wrote: > > > On Wed, Aug 2, 2017 at 12:45 PM, Wei Li wrote: > >> Hi AeroGear community, >> >> We have been using the digger-java client module in our product for the >> last couple of months. At this point I think the API is stable enough and I >> think we should release them. >> >> However, because at some point during the 1.0.0-SNAPSHOT version, we have >> introduced some broken changes (and our product is released using the >> version before the broken changes are made), we now need to do 2 releases; >> >> 1. Release 1.0.1 from this branch: https://github.com/wei >> -lee/digger-java/tree/fix-for-3-18-release. This is before the broken >> change is introduced. >> > > we can release this, let's make a branch, with a more reasonable name, > available on upstream > > >> 2. From master (1.0.2). >> > > ok > > So, why do we need an old release? Not sure I really get that. > > >> >> Apologies in advance for the manually version change. Matthias does point >> it out that it is not the right way to do it. >> >> So, can we publish those releases? Sorry for the problem we have caused, >> I promise it won't be like this the next time.... >> > > there are no big problems. I'd suggest we simply continue to follow a > normal java release process, as discussed here and avoid manual bumps. > here is the link: https://github.com/aerogear/collateral/wiki/Release-Process-(Java) > > Also, it never hurts to release bits to the community very often (release > early, release often). This likely avoids issues like the above > > -M > >> >> >> -- >> >> WEI LI >> >> SENIOR SOFTWARE ENGINEER >> >> Red Hat Mobile >> >> weil at redhat.com M: +353862393272 >> >> >> _______________________________________________ >> 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 > -- 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/20170802/fc3f32bb/attachment.html From weil at redhat.com Wed Aug 2 07:15:26 2017 From: weil at redhat.com (Wei Li) Date: Wed, 2 Aug 2017 12:15:26 +0100 Subject: [aerogear-dev] Publish new release of digger-java client In-Reply-To: References: Message-ID: Yes, I was just going to ask the same questions. If we can publish it, it will be great. On Wed, Aug 2, 2017 at 11:59 AM, Matthias Wessendorf wrote: > Related, are we OK to release org.jboss.aerogear::jenkins-client in > version 0.3.8 - to maven central ? > > > > On Wed, Aug 2, 2017 at 12:57 PM, Matthias Wessendorf > wrote: > >> >> >> On Wed, Aug 2, 2017 at 12:45 PM, Wei Li wrote: >> >>> Hi AeroGear community, >>> >>> We have been using the digger-java client module in our product for the >>> last couple of months. At this point I think the API is stable enough and I >>> think we should release them. >>> >>> However, because at some point during the 1.0.0-SNAPSHOT version, we >>> have introduced some broken changes (and our product is released using the >>> version before the broken changes are made), we now need to do 2 releases; >>> >>> 1. Release 1.0.1 from this branch: https://github.com/wei >>> -lee/digger-java/tree/fix-for-3-18-release. This is before the broken >>> change is introduced. >>> >> >> we can release this, let's make a branch, with a more reasonable name, >> available on upstream >> >> >>> 2. From master (1.0.2). >>> >> >> ok >> >> So, why do we need an old release? Not sure I really get that. >> >> >>> >>> Apologies in advance for the manually version change. Matthias does >>> point it out that it is not the right way to do it. >>> >>> So, can we publish those releases? Sorry for the problem we have caused, >>> I promise it won't be like this the next time.... >>> >> >> there are no big problems. I'd suggest we simply continue to follow a >> normal java release process, as discussed here and avoid manual bumps. >> >> Also, it never hurts to release bits to the community very often (release >> early, release often). This likely avoids issues like the above >> >> -M >> >>> >>> >>> -- >>> >>> WEI LI >>> >>> SENIOR SOFTWARE ENGINEER >>> >>> Red Hat Mobile >>> >>> weil at redhat.com M: +353862393272 >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > 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 > -- WEI LI SENIOR SOFTWARE ENGINEER Red Hat Mobile weil at redhat.com M: +353862393272 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170802/46f470ae/attachment.html From weil at redhat.com Wed Aug 2 07:18:41 2017 From: weil at redhat.com (Wei Li) Date: Wed, 2 Aug 2017 12:18:41 +0100 Subject: [aerogear-dev] Publish new release of digger-java client In-Reply-To: References: Message-ID: I have create the release-1.0.1 branch: https://github.com/aerogear/digger-java/tree/release-1.0.1. We can do the release from there. On Wed, Aug 2, 2017 at 11:57 AM, Matthias Wessendorf wrote: > > > On Wed, Aug 2, 2017 at 12:45 PM, Wei Li wrote: > >> Hi AeroGear community, >> >> We have been using the digger-java client module in our product for the >> last couple of months. At this point I think the API is stable enough and I >> think we should release them. >> >> However, because at some point during the 1.0.0-SNAPSHOT version, we have >> introduced some broken changes (and our product is released using the >> version before the broken changes are made), we now need to do 2 releases; >> >> 1. Release 1.0.1 from this branch: https://github.com/wei >> -lee/digger-java/tree/fix-for-3-18-release. This is before the broken >> change is introduced. >> > > we can release this, let's make a branch, with a more reasonable name, > available on upstream > > >> 2. From master (1.0.2). >> > > ok > > So, why do we need an old release? Not sure I really get that. > The problem is that 1.0.2 is not backward compatible with 1.0.1. We have a release branch that needs to built with 1.0.1, but master needs to be built with 1.0.2. > > >> >> Apologies in advance for the manually version change. Matthias does point >> it out that it is not the right way to do it. >> >> So, can we publish those releases? Sorry for the problem we have caused, >> I promise it won't be like this the next time.... >> > > there are no big problems. I'd suggest we simply continue to follow a > normal java release process, as discussed here and avoid manual bumps. > > Also, it never hurts to release bits to the community very often (release > early, release often). This likely avoids issues like the above > > -M > >> >> >> -- >> >> WEI LI >> >> SENIOR SOFTWARE ENGINEER >> >> Red Hat Mobile >> >> weil at redhat.com M: +353862393272 >> >> >> _______________________________________________ >> 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 > -- WEI LI SENIOR SOFTWARE ENGINEER Red Hat Mobile weil at redhat.com M: +353862393272 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170802/726fc6ab/attachment-0001.html From weil at redhat.com Wed Aug 2 07:24:40 2017 From: weil at redhat.com (Wei Li) Date: Wed, 2 Aug 2017 12:24:40 +0100 Subject: [aerogear-dev] Publish new release of digger-java client In-Reply-To: References: Message-ID: @Matthias are you ok to publish both releases, and release jenkins-java-client as well? Anything else I can help with? On Wed, Aug 2, 2017 at 12:18 PM, Wei Li wrote: > I have create the release-1.0.1 branch: https://github.com/ > aerogear/digger-java/tree/release-1.0.1. We can do the release from there. > > > On Wed, Aug 2, 2017 at 11:57 AM, Matthias Wessendorf > wrote: > >> >> >> On Wed, Aug 2, 2017 at 12:45 PM, Wei Li wrote: >> >>> Hi AeroGear community, >>> >>> We have been using the digger-java client module in our product for the >>> last couple of months. At this point I think the API is stable enough and I >>> think we should release them. >>> >>> However, because at some point during the 1.0.0-SNAPSHOT version, we >>> have introduced some broken changes (and our product is released using the >>> version before the broken changes are made), we now need to do 2 releases; >>> >>> 1. Release 1.0.1 from this branch: https://github.com/wei >>> -lee/digger-java/tree/fix-for-3-18-release. This is before the broken >>> change is introduced. >>> >> >> we can release this, let's make a branch, with a more reasonable name, >> available on upstream >> >> >>> 2. From master (1.0.2). >>> >> >> ok >> >> So, why do we need an old release? Not sure I really get that. >> > > The problem is that 1.0.2 is not backward compatible with 1.0.1. We have a > release branch that needs to built with 1.0.1, but master needs to be built > with 1.0.2. > > > >> >> >>> >>> Apologies in advance for the manually version change. Matthias does >>> point it out that it is not the right way to do it. >>> >>> So, can we publish those releases? Sorry for the problem we have caused, >>> I promise it won't be like this the next time.... >>> >> >> there are no big problems. I'd suggest we simply continue to follow a >> normal java release process, as discussed here and avoid manual bumps. >> >> Also, it never hurts to release bits to the community very often (release >> early, release often). This likely avoids issues like the above >> >> -M >> >>> >>> >>> -- >>> >>> WEI LI >>> >>> SENIOR SOFTWARE ENGINEER >>> >>> Red Hat Mobile >>> >>> weil at redhat.com M: +353862393272 >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > > WEI LI > > SENIOR SOFTWARE ENGINEER > > Red Hat Mobile > > weil at redhat.com M: +353862393272 > > -- WEI LI SENIOR SOFTWARE ENGINEER Red Hat Mobile weil at redhat.com M: +353862393272 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170802/11b0529e/attachment.html From matzew at apache.org Wed Aug 2 07:33:14 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 2 Aug 2017 13:33:14 +0200 Subject: [aerogear-dev] Publish new release of digger-java client In-Reply-To: References: Message-ID: On Wed, Aug 2, 2017 at 1:18 PM, Wei Li wrote: > I have create the release-1.0.1 branch: https://github.com/ > aerogear/digger-java/tree/release-1.0.1. We can do the release from there. > > > On Wed, Aug 2, 2017 at 11:57 AM, Matthias Wessendorf > wrote: > >> >> >> On Wed, Aug 2, 2017 at 12:45 PM, Wei Li wrote: >> >>> Hi AeroGear community, >>> >>> We have been using the digger-java client module in our product for the >>> last couple of months. At this point I think the API is stable enough and I >>> think we should release them. >>> >>> However, because at some point during the 1.0.0-SNAPSHOT version, we >>> have introduced some broken changes (and our product is released using the >>> version before the broken changes are made), we now need to do 2 releases; >>> >>> 1. Release 1.0.1 from this branch: https://github.com/wei >>> -lee/digger-java/tree/fix-for-3-18-release. This is before the broken >>> change is introduced. >>> >> >> we can release this, let's make a branch, with a more reasonable name, >> available on upstream >> >> >>> 2. From master (1.0.2). >>> >> >> ok >> >> So, why do we need an old release? Not sure I really get that. >> > > The problem is that 1.0.2 is not backward compatible with 1.0.1. We have a > release branch that needs to built with 1.0.1, but master needs to be built > with 1.0.2. > to follow semVer, let's name it 1.1.0 - instead of 1.0.2 since it's not backwards compatible > > > >> >> >>> >>> Apologies in advance for the manually version change. Matthias does >>> point it out that it is not the right way to do it. >>> >>> So, can we publish those releases? Sorry for the problem we have caused, >>> I promise it won't be like this the next time.... >>> >> >> there are no big problems. I'd suggest we simply continue to follow a >> normal java release process, as discussed here and avoid manual bumps. >> >> Also, it never hurts to release bits to the community very often (release >> early, release often). This likely avoids issues like the above >> >> -M >> >>> >>> >>> -- >>> >>> WEI LI >>> >>> SENIOR SOFTWARE ENGINEER >>> >>> Red Hat Mobile >>> >>> weil at redhat.com M: +353862393272 >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > > WEI LI > > SENIOR SOFTWARE ENGINEER > > Red Hat Mobile > > weil at redhat.com M: +353862393272 > > > _______________________________________________ > 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/20170802/088b83b2/attachment-0001.html From kpiwko at redhat.com Wed Aug 2 07:35:17 2017 From: kpiwko at redhat.com (Karel Piwko) Date: Wed, 2 Aug 2017 13:35:17 +0200 Subject: [aerogear-dev] Publish new release of digger-java client In-Reply-To: References: Message-ID: Hello All, should not the version bump be minor/major to indicated backwards compatibility changes according to semver? Also by releasing 1.0.2 you remove the path to (eventually) patch 1.0.1 in the future and release as 1.0.2. Releasing it as 1.0.3 would add even more confusion imho. Thanks, Karel On Wed, Aug 2, 2017 at 1:18 PM, Wei Li wrote: > I have create the release-1.0.1 branch: https://github.com/ > aerogear/digger-java/tree/release-1.0.1. We can do the release from there. > > > On Wed, Aug 2, 2017 at 11:57 AM, Matthias Wessendorf > wrote: > >> >> >> On Wed, Aug 2, 2017 at 12:45 PM, Wei Li wrote: >> >>> Hi AeroGear community, >>> >>> We have been using the digger-java client module in our product for the >>> last couple of months. At this point I think the API is stable enough and I >>> think we should release them. >>> >>> However, because at some point during the 1.0.0-SNAPSHOT version, we >>> have introduced some broken changes (and our product is released using the >>> version before the broken changes are made), we now need to do 2 releases; >>> >>> 1. Release 1.0.1 from this branch: https://github.com/wei >>> -lee/digger-java/tree/fix-for-3-18-release. This is before the broken >>> change is introduced. >>> >> >> we can release this, let's make a branch, with a more reasonable name, >> available on upstream >> >> >>> 2. From master (1.0.2). >>> >> >> ok >> >> So, why do we need an old release? Not sure I really get that. >> > > The problem is that 1.0.2 is not backward compatible with 1.0.1. We have a > release branch that needs to built with 1.0.1, but master needs to be built > with 1.0.2. > > > >> >> >>> >>> Apologies in advance for the manually version change. Matthias does >>> point it out that it is not the right way to do it. >>> >>> So, can we publish those releases? Sorry for the problem we have caused, >>> I promise it won't be like this the next time.... >>> >> >> there are no big problems. I'd suggest we simply continue to follow a >> normal java release process, as discussed here and avoid manual bumps. >> >> Also, it never hurts to release bits to the community very often (release >> early, release often). This likely avoids issues like the above >> >> -M >> >>> >>> >>> -- >>> >>> WEI LI >>> >>> SENIOR SOFTWARE ENGINEER >>> >>> Red Hat Mobile >>> >>> weil at redhat.com M: +353862393272 >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > > WEI LI > > SENIOR SOFTWARE ENGINEER > > Red Hat Mobile > > weil at redhat.com M: +353862393272 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- KAREL PIWKO MANAGER, MOBILE QE Red Hat Czech Republic Purky?ova 647/111 612 00 Brno, Czech Republic kpiwko at redhat.com IM: kpiwko TRIED. TESTED. TRUSTED. @redhatway @redhatinc @redhatsnaps -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170802/a25aab68/attachment.html From kpiwko at redhat.com Wed Aug 2 07:35:58 2017 From: kpiwko at redhat.com (Karel Piwko) Date: Wed, 2 Aug 2017 13:35:58 +0200 Subject: [aerogear-dev] Publish new release of digger-java client In-Reply-To: References: Message-ID: On Wed, Aug 2, 2017 at 1:33 PM, Matthias Wessendorf wrote: > > > On Wed, Aug 2, 2017 at 1:18 PM, Wei Li wrote: > >> I have create the release-1.0.1 branch: https://github.com/aer >> ogear/digger-java/tree/release-1.0.1. We can do the release from there. >> >> >> On Wed, Aug 2, 2017 at 11:57 AM, Matthias Wessendorf >> wrote: >> >>> >>> >>> On Wed, Aug 2, 2017 at 12:45 PM, Wei Li wrote: >>> >>>> Hi AeroGear community, >>>> >>>> We have been using the digger-java client module in our product for the >>>> last couple of months. At this point I think the API is stable enough and I >>>> think we should release them. >>>> >>>> However, because at some point during the 1.0.0-SNAPSHOT version, we >>>> have introduced some broken changes (and our product is released using the >>>> version before the broken changes are made), we now need to do 2 releases; >>>> >>>> 1. Release 1.0.1 from this branch: https://github.com/wei >>>> -lee/digger-java/tree/fix-for-3-18-release. This is before the broken >>>> change is introduced. >>>> >>> >>> we can release this, let's make a branch, with a more reasonable name, >>> available on upstream >>> >>> >>>> 2. From master (1.0.2). >>>> >>> >>> ok >>> >>> So, why do we need an old release? Not sure I really get that. >>> >> >> The problem is that 1.0.2 is not backward compatible with 1.0.1. We have >> a release branch that needs to built with 1.0.1, but master needs to be >> built with 1.0.2. >> > > to follow semVer, let's name it 1.1.0 - instead of 1.0.2 since it's not > backwards compatible > +1, exactly my point :-) > > >> >> >> >>> >>> >>>> >>>> Apologies in advance for the manually version change. Matthias does >>>> point it out that it is not the right way to do it. >>>> >>>> So, can we publish those releases? Sorry for the problem we have >>>> caused, I promise it won't be like this the next time.... >>>> >>> >>> there are no big problems. I'd suggest we simply continue to follow a >>> normal java release process, as discussed here and avoid manual bumps. >>> >>> Also, it never hurts to release bits to the community very often >>> (release early, release often). This likely avoids issues like the above >>> >>> -M >>> >>>> >>>> >>>> -- >>>> >>>> WEI LI >>>> >>>> SENIOR SOFTWARE ENGINEER >>>> >>>> Red Hat Mobile >>>> >>>> weil at redhat.com M: +353862393272 >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> >> >> -- >> >> WEI LI >> >> SENIOR SOFTWARE ENGINEER >> >> Red Hat Mobile >> >> weil at redhat.com M: +353862393272 >> >> >> _______________________________________________ >> 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 > -- KAREL PIWKO MANAGER, MOBILE QE Red Hat Czech Republic Purky?ova 647/111 612 00 Brno, Czech Republic kpiwko at redhat.com IM: kpiwko TRIED. TESTED. TRUSTED. @redhatway @redhatinc @redhatsnaps -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170802/1edf468e/attachment-0001.html From matzew at apache.org Wed Aug 2 07:38:05 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 2 Aug 2017 13:38:05 +0200 Subject: [aerogear-dev] Java-Jenkins-client API Message-ID: Hi, on the digger_dev branch, I get: [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins-client-it-docker/src/test/java/com/offbytwo/jenkins/integration/NoExecutorStartedManageCredentialsIT.java:[85,9] cannot find symbol symbol: class AppleDeveloperProfileCredential location: class com.offbytwo.jenkins.integration.NoExecutorStartedManageCredentialsIT [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins-client-it-docker/src/test/java/com/offbytwo/jenkins/integration/NoExecutorStartedManageCredentialsIT.java:[85,63] cannot find symbol symbol: class AppleDeveloperProfileCredential location: class com.offbytwo.jenkins.integration.NoExecutorStartedManageCredentialsIT [INFO] 2 errors [INFO] ------------------------------------------------------------- [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Jenkins API client for Java ........................ SUCCESS [ 1.810 s] [INFO] Jenkins API client for Java :: The Client. ......... SUCCESS [ 12.036 s] [INFO] Jenkins API client for Java :: IT Docker ........... FAILURE [ 0.236 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 14.336 s [INFO] Finished at: 2017-08-02T13:36:27+02:00 [INFO] Final Memory: 61M/1356M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.6.0:testCompile (default-testCompile) on project jenkins-client-it-docker: Compilation failure: Compilation failure: [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins-client-it-docker/src/test/java/com/offbytwo/jenkins/integration/NoExecutorStartedManageCredentialsIT.java:[85,9] cannot find symbol [ERROR] symbol: class AppleDeveloperProfileCredential [ERROR] location: class com.offbytwo.jenkins.integration.NoExecutorStartedManageCredentialsIT [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins-client-it-docker/src/test/java/com/offbytwo/jenkins/integration/NoExecutorStartedManageCredentialsIT.java:[85,63] cannot find symbol [ERROR] symbol: class AppleDeveloperProfileCredential [ERROR] location: class com.offbytwo.jenkins.integration.NoExecutorStartedManageCredentialsIT [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] -- 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/20170802/04edf4a4/attachment.html From weil at redhat.com Wed Aug 2 07:38:39 2017 From: weil at redhat.com (Wei Li) Date: Wed, 2 Aug 2017 12:38:39 +0100 Subject: [aerogear-dev] Publish new release of digger-java client In-Reply-To: References: Message-ID: Sure, let's do that. On Wed, Aug 2, 2017 at 12:35 PM, Karel Piwko wrote: > > > On Wed, Aug 2, 2017 at 1:33 PM, Matthias Wessendorf > wrote: > >> >> >> On Wed, Aug 2, 2017 at 1:18 PM, Wei Li wrote: >> >>> I have create the release-1.0.1 branch: https://github.com/aer >>> ogear/digger-java/tree/release-1.0.1. We can do the release from there. >>> >>> >>> On Wed, Aug 2, 2017 at 11:57 AM, Matthias Wessendorf >>> wrote: >>> >>>> >>>> >>>> On Wed, Aug 2, 2017 at 12:45 PM, Wei Li wrote: >>>> >>>>> Hi AeroGear community, >>>>> >>>>> We have been using the digger-java client module in our product for >>>>> the last couple of months. At this point I think the API is stable enough >>>>> and I think we should release them. >>>>> >>>>> However, because at some point during the 1.0.0-SNAPSHOT version, we >>>>> have introduced some broken changes (and our product is released using the >>>>> version before the broken changes are made), we now need to do 2 releases; >>>>> >>>>> 1. Release 1.0.1 from this branch: https://github.com/wei >>>>> -lee/digger-java/tree/fix-for-3-18-release. This is before the broken >>>>> change is introduced. >>>>> >>>> >>>> we can release this, let's make a branch, with a more reasonable name, >>>> available on upstream >>>> >>>> >>>>> 2. From master (1.0.2). >>>>> >>>> >>>> ok >>>> >>>> So, why do we need an old release? Not sure I really get that. >>>> >>> >>> The problem is that 1.0.2 is not backward compatible with 1.0.1. We have >>> a release branch that needs to built with 1.0.1, but master needs to be >>> built with 1.0.2. >>> >> >> to follow semVer, let's name it 1.1.0 - instead of 1.0.2 since it's not >> backwards compatible >> > > +1, exactly my point :-) > >> >> >>> >>> >>> >>>> >>>> >>>>> >>>>> Apologies in advance for the manually version change. Matthias does >>>>> point it out that it is not the right way to do it. >>>>> >>>>> So, can we publish those releases? Sorry for the problem we have >>>>> caused, I promise it won't be like this the next time.... >>>>> >>>> >>>> there are no big problems. I'd suggest we simply continue to follow a >>>> normal java release process, as discussed here and avoid manual bumps. >>>> >>>> Also, it never hurts to release bits to the community very often >>>> (release early, release often). This likely avoids issues like the above >>>> >>>> -M >>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> WEI LI >>>>> >>>>> SENIOR SOFTWARE ENGINEER >>>>> >>>>> Red Hat Mobile >>>>> >>>>> weil at redhat.com M: +353862393272 >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>> >>> >>> >>> -- >>> >>> WEI LI >>> >>> SENIOR SOFTWARE ENGINEER >>> >>> Red Hat Mobile >>> >>> weil at redhat.com M: +353862393272 >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > > KAREL PIWKO > > MANAGER, MOBILE QE > > Red Hat Czech Republic > > Purky?ova 647/111 > > 612 00 Brno, Czech Republic > > kpiwko at redhat.com IM: kpiwko > > TRIED. TESTED. TRUSTED. > @redhatway @redhatinc > @redhatsnaps > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- WEI LI SENIOR SOFTWARE ENGINEER Red Hat Mobile weil at redhat.com M: +353862393272 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170802/24db31db/attachment-0001.html From weil at redhat.com Wed Aug 2 07:44:13 2017 From: weil at redhat.com (Wei Li) Date: Wed, 2 Aug 2017 12:44:13 +0100 Subject: [aerogear-dev] Java-Jenkins-client API In-Reply-To: References: Message-ID: I am looking into this now. On Wed, Aug 2, 2017 at 12:38 PM, Matthias Wessendorf wrote: > Hi, > > on the digger_dev branch, I get: > > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins- > client-it-docker/src/test/java/com/offbytwo/jenkins/integration/ > NoExecutorStartedManageCredentialsIT.java:[85,9] cannot find symbol > symbol: class AppleDeveloperProfileCredential > location: class com.offbytwo.jenkins.integration. > NoExecutorStartedManageCredentialsIT > [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins- > client-it-docker/src/test/java/com/offbytwo/jenkins/integration/ > NoExecutorStartedManageCredentialsIT.java:[85,63] cannot find symbol > symbol: class AppleDeveloperProfileCredential > location: class com.offbytwo.jenkins.integration. > NoExecutorStartedManageCredentialsIT > [INFO] 2 errors > [INFO] ------------------------------------------------------------- > [INFO] ------------------------------------------------------------ > ------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Jenkins API client for Java ........................ SUCCESS [ > 1.810 s] > [INFO] Jenkins API client for Java :: The Client. ......... SUCCESS [ > 12.036 s] > [INFO] Jenkins API client for Java :: IT Docker ........... FAILURE [ > 0.236 s] > [INFO] ------------------------------------------------------------ > ------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------ > ------------ > [INFO] Total time: 14.336 s > [INFO] Finished at: 2017-08-02T13:36:27+02:00 > [INFO] Final Memory: 61M/1356M > [INFO] ------------------------------------------------------------ > ------------ > [ERROR] Failed to execute goal org.apache.maven.plugins: > maven-compiler-plugin:3.6.0:testCompile (default-testCompile) on project > jenkins-client-it-docker: Compilation failure: Compilation failure: > [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins- > client-it-docker/src/test/java/com/offbytwo/jenkins/integration/ > NoExecutorStartedManageCredentialsIT.java:[85,9] cannot find symbol > [ERROR] symbol: class AppleDeveloperProfileCredential > [ERROR] location: class com.offbytwo.jenkins.integration. > NoExecutorStartedManageCredentialsIT > [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins- > client-it-docker/src/test/java/com/offbytwo/jenkins/integration/ > NoExecutorStartedManageCredentialsIT.java:[85,63] cannot find symbol > [ERROR] symbol: class AppleDeveloperProfileCredential > [ERROR] location: class com.offbytwo.jenkins.integration. > NoExecutorStartedManageCredentialsIT > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > > > > > > -- > 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 > -- WEI LI SENIOR SOFTWARE ENGINEER Red Hat Mobile weil at redhat.com M: +353862393272 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170802/414ea7ac/attachment.html From weil at redhat.com Wed Aug 2 07:53:12 2017 From: weil at redhat.com (Wei Li) Date: Wed, 2 Aug 2017 12:53:12 +0100 Subject: [aerogear-dev] Java-Jenkins-client API In-Reply-To: References: Message-ID: @Matthias: https://github.com/aerogear/java-client-api/pull/6 On Wed, Aug 2, 2017 at 12:44 PM, Wei Li wrote: > I am looking into this now. > > On Wed, Aug 2, 2017 at 12:38 PM, Matthias Wessendorf > wrote: > >> Hi, >> >> on the digger_dev branch, I get: >> >> [ERROR] COMPILATION ERROR : >> [INFO] ------------------------------------------------------------- >> [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins-client- >> it-docker/src/test/java/com/offbytwo/jenkins/integration/N >> oExecutorStartedManageCredentialsIT.java:[85,9] cannot find symbol >> symbol: class AppleDeveloperProfileCredential >> location: class com.offbytwo.jenkins.integrati >> on.NoExecutorStartedManageCredentialsIT >> [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins-client- >> it-docker/src/test/java/com/offbytwo/jenkins/integration/N >> oExecutorStartedManageCredentialsIT.java:[85,63] cannot find symbol >> symbol: class AppleDeveloperProfileCredential >> location: class com.offbytwo.jenkins.integrati >> on.NoExecutorStartedManageCredentialsIT >> [INFO] 2 errors >> [INFO] ------------------------------------------------------------- >> [INFO] ------------------------------------------------------------ >> ------------ >> [INFO] Reactor Summary: >> [INFO] >> [INFO] Jenkins API client for Java ........................ SUCCESS [ >> 1.810 s] >> [INFO] Jenkins API client for Java :: The Client. ......... SUCCESS [ >> 12.036 s] >> [INFO] Jenkins API client for Java :: IT Docker ........... FAILURE [ >> 0.236 s] >> [INFO] ------------------------------------------------------------ >> ------------ >> [INFO] BUILD FAILURE >> [INFO] ------------------------------------------------------------ >> ------------ >> [INFO] Total time: 14.336 s >> [INFO] Finished at: 2017-08-02T13:36:27+02:00 >> [INFO] Final Memory: 61M/1356M >> [INFO] ------------------------------------------------------------ >> ------------ >> [ERROR] Failed to execute goal org.apache.maven.plugins:maven >> -compiler-plugin:3.6.0:testCompile (default-testCompile) on project >> jenkins-client-it-docker: Compilation failure: Compilation failure: >> [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins-client- >> it-docker/src/test/java/com/offbytwo/jenkins/integration/N >> oExecutorStartedManageCredentialsIT.java:[85,9] cannot find symbol >> [ERROR] symbol: class AppleDeveloperProfileCredential >> [ERROR] location: class com.offbytwo.jenkins.integrati >> on.NoExecutorStartedManageCredentialsIT >> [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins-client- >> it-docker/src/test/java/com/offbytwo/jenkins/integration/N >> oExecutorStartedManageCredentialsIT.java:[85,63] cannot find symbol >> [ERROR] symbol: class AppleDeveloperProfileCredential >> [ERROR] location: class com.offbytwo.jenkins.integrati >> on.NoExecutorStartedManageCredentialsIT >> [ERROR] -> [Help 1] >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with the >> -e switch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> >> >> >> >> >> -- >> 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 >> > > > > -- > > WEI LI > > SENIOR SOFTWARE ENGINEER > > Red Hat Mobile > > weil at redhat.com M: +353862393272 > > -- WEI LI SENIOR SOFTWARE ENGINEER Red Hat Mobile weil at redhat.com M: +353862393272 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170802/be1965ab/attachment.html From matzew at apache.org Wed Aug 2 08:20:49 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 2 Aug 2017 14:20:49 +0200 Subject: [aerogear-dev] Java-Jenkins-client API In-Reply-To: References: Message-ID: 0.3.8 is on its way to maven central On Wed, Aug 2, 2017 at 1:53 PM, Wei Li wrote: > @Matthias: https://github.com/aerogear/java-client-api/pull/6 > > On Wed, Aug 2, 2017 at 12:44 PM, Wei Li wrote: > >> I am looking into this now. >> >> On Wed, Aug 2, 2017 at 12:38 PM, Matthias Wessendorf >> wrote: >> >>> Hi, >>> >>> on the digger_dev branch, I get: >>> >>> [ERROR] COMPILATION ERROR : >>> [INFO] ------------------------------------------------------------- >>> [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins-client- >>> it-docker/src/test/java/com/offbytwo/jenkins/integration/NoE >>> xecutorStartedManageCredentialsIT.java:[85,9] cannot find symbol >>> symbol: class AppleDeveloperProfileCredential >>> location: class com.offbytwo.jenkins.integrati >>> on.NoExecutorStartedManageCredentialsIT >>> [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins-client- >>> it-docker/src/test/java/com/offbytwo/jenkins/integration/NoE >>> xecutorStartedManageCredentialsIT.java:[85,63] cannot find symbol >>> symbol: class AppleDeveloperProfileCredential >>> location: class com.offbytwo.jenkins.integrati >>> on.NoExecutorStartedManageCredentialsIT >>> [INFO] 2 errors >>> [INFO] ------------------------------------------------------------- >>> [INFO] ------------------------------------------------------------ >>> ------------ >>> [INFO] Reactor Summary: >>> [INFO] >>> [INFO] Jenkins API client for Java ........................ SUCCESS [ >>> 1.810 s] >>> [INFO] Jenkins API client for Java :: The Client. ......... SUCCESS [ >>> 12.036 s] >>> [INFO] Jenkins API client for Java :: IT Docker ........... FAILURE [ >>> 0.236 s] >>> [INFO] ------------------------------------------------------------ >>> ------------ >>> [INFO] BUILD FAILURE >>> [INFO] ------------------------------------------------------------ >>> ------------ >>> [INFO] Total time: 14.336 s >>> [INFO] Finished at: 2017-08-02T13:36:27+02:00 >>> [INFO] Final Memory: 61M/1356M >>> [INFO] ------------------------------------------------------------ >>> ------------ >>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven >>> -compiler-plugin:3.6.0:testCompile (default-testCompile) on project >>> jenkins-client-it-docker: Compilation failure: Compilation failure: >>> [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins-client- >>> it-docker/src/test/java/com/offbytwo/jenkins/integration/NoE >>> xecutorStartedManageCredentialsIT.java:[85,9] cannot find symbol >>> [ERROR] symbol: class AppleDeveloperProfileCredential >>> [ERROR] location: class com.offbytwo.jenkins.integrati >>> on.NoExecutorStartedManageCredentialsIT >>> [ERROR] /home/Matthias/Work/AeroGear/java-client-api/jenkins-client- >>> it-docker/src/test/java/com/offbytwo/jenkins/integration/NoE >>> xecutorStartedManageCredentialsIT.java:[85,63] cannot find symbol >>> [ERROR] symbol: class AppleDeveloperProfileCredential >>> [ERROR] location: class com.offbytwo.jenkins.integrati >>> on.NoExecutorStartedManageCredentialsIT >>> [ERROR] -> [Help 1] >>> [ERROR] >>> [ERROR] To see the full stack trace of the errors, re-run Maven with the >>> -e switch. >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>> [ERROR] >>> >>> >>> >>> >>> >>> -- >>> 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 >>> >> >> >> >> -- >> >> WEI LI >> >> SENIOR SOFTWARE ENGINEER >> >> Red Hat Mobile >> >> weil at redhat.com M: +353862393272 >> >> > > > > -- > > WEI LI > > SENIOR SOFTWARE ENGINEER > > Red Hat Mobile > > weil at redhat.com M: +353862393272 > > > _______________________________________________ > 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/20170802/25504f86/attachment-0001.html From dimitrazuccarelli at gmail.com Wed Aug 2 12:45:41 2017 From: dimitrazuccarelli at gmail.com (Dimitra Zuccarelli) Date: Wed, 2 Aug 2017 17:45:41 +0100 Subject: [aerogear-dev] Kafka cdi serialiser problems Message-ID: Hi everyone, I'm currently trying to add a generic serializer/deserializer to the kafka CDI library that allows producers and consumers to handle objects of type T. To test I've updated one of the kafka producers we've implemented to send records with key/value pairs of String/Variant types. As far as I can tell the Serdes are actually being returned, but for some reason I cannot seem to grasp, the GenericSerializer class is being called again (not using the overlaoded constructor which is necessary to pass in the type of the object) and a NullPointerException is then thrown. Here is the updated producer: https://github.com/dimitraz/aerogear-unifiedpush-server/commit/cbc3b3da867fcef17ec419edee13a30d8c938dae Here are the updates to the Kafka-cdi library with the serialiser changes: https://github.com/dimitraz/kafka-cdi/commit/09de7ff7c87120f242655253825e4efca186e518 Any help at all would be highly appreciated! Dimitra -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170802/f944de34/attachment.html From matzew at apache.org Thu Aug 3 04:13:35 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 3 Aug 2017 10:13:35 +0200 Subject: [aerogear-dev] Publish new release of digger-java client In-Reply-To: References: Message-ID: Hello, I've pushed 1.1.0 (master) and 1.0.1 JARs over to maven central They should be online tomorrow .... On Wed, Aug 2, 2017 at 1:38 PM, Wei Li wrote: > Sure, let's do that. > > On Wed, Aug 2, 2017 at 12:35 PM, Karel Piwko wrote: > >> >> >> On Wed, Aug 2, 2017 at 1:33 PM, Matthias Wessendorf >> wrote: >> >>> >>> >>> On Wed, Aug 2, 2017 at 1:18 PM, Wei Li wrote: >>> >>>> I have create the release-1.0.1 branch: https://github.com/aer >>>> ogear/digger-java/tree/release-1.0.1. We can do the release from there. >>>> >>>> >>>> On Wed, Aug 2, 2017 at 11:57 AM, Matthias Wessendorf >>> > wrote: >>>> >>>>> >>>>> >>>>> On Wed, Aug 2, 2017 at 12:45 PM, Wei Li wrote: >>>>> >>>>>> Hi AeroGear community, >>>>>> >>>>>> We have been using the digger-java client module in our product for >>>>>> the last couple of months. At this point I think the API is stable enough >>>>>> and I think we should release them. >>>>>> >>>>>> However, because at some point during the 1.0.0-SNAPSHOT version, we >>>>>> have introduced some broken changes (and our product is released using the >>>>>> version before the broken changes are made), we now need to do 2 releases; >>>>>> >>>>>> 1. Release 1.0.1 from this branch: https://github.com/wei >>>>>> -lee/digger-java/tree/fix-for-3-18-release. This is before the >>>>>> broken change is introduced. >>>>>> >>>>> >>>>> we can release this, let's make a branch, with a more reasonable name, >>>>> available on upstream >>>>> >>>>> >>>>>> 2. From master (1.0.2). >>>>>> >>>>> >>>>> ok >>>>> >>>>> So, why do we need an old release? Not sure I really get that. >>>>> >>>> >>>> The problem is that 1.0.2 is not backward compatible with 1.0.1. We >>>> have a release branch that needs to built with 1.0.1, but master needs to >>>> be built with 1.0.2. >>>> >>> >>> to follow semVer, let's name it 1.1.0 - instead of 1.0.2 since it's not >>> backwards compatible >>> >> >> +1, exactly my point :-) >> >>> >>> >>>> >>>> >>>> >>>>> >>>>> >>>>>> >>>>>> Apologies in advance for the manually version change. Matthias does >>>>>> point it out that it is not the right way to do it. >>>>>> >>>>>> So, can we publish those releases? Sorry for the problem we have >>>>>> caused, I promise it won't be like this the next time.... >>>>>> >>>>> >>>>> there are no big problems. I'd suggest we simply continue to follow a >>>>> normal java release process, as discussed here and avoid manual bumps. >>>>> >>>>> Also, it never hurts to release bits to the community very often >>>>> (release early, release often). This likely avoids issues like the above >>>>> >>>>> -M >>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> WEI LI >>>>>> >>>>>> SENIOR SOFTWARE ENGINEER >>>>>> >>>>>> Red Hat Mobile >>>>>> >>>>>> weil at redhat.com M: +353862393272 >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> WEI LI >>>> >>>> SENIOR SOFTWARE ENGINEER >>>> >>>> Red Hat Mobile >>>> >>>> weil at redhat.com M: +353862393272 >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> >> >> -- >> >> KAREL PIWKO >> >> MANAGER, MOBILE QE >> >> Red Hat Czech Republic >> >> Purky?ova 647/111 >> >> 612 00 Brno, Czech Republic >> >> kpiwko at redhat.com IM: kpiwko >> >> TRIED. TESTED. TRUSTED. >> @redhatway @redhatinc >> @redhatsnaps >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > > WEI LI > > SENIOR SOFTWARE ENGINEER > > Red Hat Mobile > > weil at redhat.com M: +353862393272 > > > _______________________________________________ > 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/20170803/a3477215/attachment-0001.html From weil at redhat.com Thu Aug 3 04:27:59 2017 From: weil at redhat.com (Wei Li) Date: Thu, 3 Aug 2017 09:27:59 +0100 Subject: [aerogear-dev] Publish new release of digger-java client In-Reply-To: References: Message-ID: Great. Thanks Matthias. On Thu, Aug 3, 2017 at 9:13 AM, Matthias Wessendorf wrote: > Hello, > > I've pushed 1.1.0 (master) and 1.0.1 JARs over to maven central > > They should be online tomorrow .... > > On Wed, Aug 2, 2017 at 1:38 PM, Wei Li wrote: > >> Sure, let's do that. >> >> On Wed, Aug 2, 2017 at 12:35 PM, Karel Piwko wrote: >> >>> >>> >>> On Wed, Aug 2, 2017 at 1:33 PM, Matthias Wessendorf >>> wrote: >>> >>>> >>>> >>>> On Wed, Aug 2, 2017 at 1:18 PM, Wei Li wrote: >>>> >>>>> I have create the release-1.0.1 branch: https://github.com/aer >>>>> ogear/digger-java/tree/release-1.0.1. We can do the release from >>>>> there. >>>>> >>>>> >>>>> On Wed, Aug 2, 2017 at 11:57 AM, Matthias Wessendorf < >>>>> matzew at apache.org> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Wed, Aug 2, 2017 at 12:45 PM, Wei Li wrote: >>>>>> >>>>>>> Hi AeroGear community, >>>>>>> >>>>>>> We have been using the digger-java client module in our product for >>>>>>> the last couple of months. At this point I think the API is stable enough >>>>>>> and I think we should release them. >>>>>>> >>>>>>> However, because at some point during the 1.0.0-SNAPSHOT version, we >>>>>>> have introduced some broken changes (and our product is released using the >>>>>>> version before the broken changes are made), we now need to do 2 releases; >>>>>>> >>>>>>> 1. Release 1.0.1 from this branch: https://github.com/wei >>>>>>> -lee/digger-java/tree/fix-for-3-18-release. This is before the >>>>>>> broken change is introduced. >>>>>>> >>>>>> >>>>>> we can release this, let's make a branch, with a more reasonable >>>>>> name, available on upstream >>>>>> >>>>>> >>>>>>> 2. From master (1.0.2). >>>>>>> >>>>>> >>>>>> ok >>>>>> >>>>>> So, why do we need an old release? Not sure I really get that. >>>>>> >>>>> >>>>> The problem is that 1.0.2 is not backward compatible with 1.0.1. We >>>>> have a release branch that needs to built with 1.0.1, but master needs to >>>>> be built with 1.0.2. >>>>> >>>> >>>> to follow semVer, let's name it 1.1.0 - instead of 1.0.2 since it's not >>>> backwards compatible >>>> >>> >>> +1, exactly my point :-) >>> >>>> >>>> >>>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> Apologies in advance for the manually version change. Matthias does >>>>>>> point it out that it is not the right way to do it. >>>>>>> >>>>>>> So, can we publish those releases? Sorry for the problem we have >>>>>>> caused, I promise it won't be like this the next time.... >>>>>>> >>>>>> >>>>>> there are no big problems. I'd suggest we simply continue to follow a >>>>>> normal java release process, as discussed here and avoid manual bumps. >>>>>> >>>>>> Also, it never hurts to release bits to the community very often >>>>>> (release early, release often). This likely avoids issues like the above >>>>>> >>>>>> -M >>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> WEI LI >>>>>>> >>>>>>> SENIOR SOFTWARE ENGINEER >>>>>>> >>>>>>> Red Hat Mobile >>>>>>> >>>>>>> weil at redhat.com M: +353862393272 >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> WEI LI >>>>> >>>>> SENIOR SOFTWARE ENGINEER >>>>> >>>>> Red Hat Mobile >>>>> >>>>> weil at redhat.com M: +353862393272 >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>> >>> >>> >>> -- >>> >>> KAREL PIWKO >>> >>> MANAGER, MOBILE QE >>> >>> Red Hat Czech Republic >>> >>> Purky?ova 647/111 >>> >>> 612 00 Brno, Czech Republic >>> >>> kpiwko at redhat.com IM: kpiwko >>> >>> TRIED. TESTED. TRUSTED. >>> @redhatway @redhatinc >>> @redhatsnaps >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> >> WEI LI >> >> SENIOR SOFTWARE ENGINEER >> >> Red Hat Mobile >> >> weil at redhat.com M: +353862393272 >> >> >> _______________________________________________ >> 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 > -- WEI LI SENIOR SOFTWARE ENGINEER Red Hat Mobile weil at redhat.com M: +353862393272 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170803/6601c86e/attachment-0001.html From matzew at apache.org Fri Aug 4 03:41:39 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 4 Aug 2017 09:41:39 +0200 Subject: [aerogear-dev] Publish new release of digger-java client In-Reply-To: References: Message-ID: published: http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.jboss.aerogear%22%20AND%20a%3A%22digger-java-client%22 On Thu, Aug 3, 2017 at 10:27 AM, Wei Li wrote: > Great. Thanks Matthias. > > On Thu, Aug 3, 2017 at 9:13 AM, Matthias Wessendorf > wrote: > >> Hello, >> >> I've pushed 1.1.0 (master) and 1.0.1 JARs over to maven central >> >> They should be online tomorrow .... >> >> On Wed, Aug 2, 2017 at 1:38 PM, Wei Li wrote: >> >>> Sure, let's do that. >>> >>> On Wed, Aug 2, 2017 at 12:35 PM, Karel Piwko wrote: >>> >>>> >>>> >>>> On Wed, Aug 2, 2017 at 1:33 PM, Matthias Wessendorf >>>> wrote: >>>> >>>>> >>>>> >>>>> On Wed, Aug 2, 2017 at 1:18 PM, Wei Li wrote: >>>>> >>>>>> I have create the release-1.0.1 branch: https://github.com/aer >>>>>> ogear/digger-java/tree/release-1.0.1. We can do the release from >>>>>> there. >>>>>> >>>>>> >>>>>> On Wed, Aug 2, 2017 at 11:57 AM, Matthias Wessendorf < >>>>>> matzew at apache.org> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Aug 2, 2017 at 12:45 PM, Wei Li wrote: >>>>>>> >>>>>>>> Hi AeroGear community, >>>>>>>> >>>>>>>> We have been using the digger-java client module in our product for >>>>>>>> the last couple of months. At this point I think the API is stable enough >>>>>>>> and I think we should release them. >>>>>>>> >>>>>>>> However, because at some point during the 1.0.0-SNAPSHOT version, >>>>>>>> we have introduced some broken changes (and our product is released using >>>>>>>> the version before the broken changes are made), we now need to do 2 >>>>>>>> releases; >>>>>>>> >>>>>>>> 1. Release 1.0.1 from this branch: https://github.com/wei >>>>>>>> -lee/digger-java/tree/fix-for-3-18-release. This is before the >>>>>>>> broken change is introduced. >>>>>>>> >>>>>>> >>>>>>> we can release this, let's make a branch, with a more reasonable >>>>>>> name, available on upstream >>>>>>> >>>>>>> >>>>>>>> 2. From master (1.0.2). >>>>>>>> >>>>>>> >>>>>>> ok >>>>>>> >>>>>>> So, why do we need an old release? Not sure I really get that. >>>>>>> >>>>>> >>>>>> The problem is that 1.0.2 is not backward compatible with 1.0.1. We >>>>>> have a release branch that needs to built with 1.0.1, but master needs to >>>>>> be built with 1.0.2. >>>>>> >>>>> >>>>> to follow semVer, let's name it 1.1.0 - instead of 1.0.2 since it's >>>>> not backwards compatible >>>>> >>>> >>>> +1, exactly my point :-) >>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Apologies in advance for the manually version change. Matthias does >>>>>>>> point it out that it is not the right way to do it. >>>>>>>> >>>>>>>> So, can we publish those releases? Sorry for the problem we have >>>>>>>> caused, I promise it won't be like this the next time.... >>>>>>>> >>>>>>> >>>>>>> there are no big problems. I'd suggest we simply continue to follow >>>>>>> a normal java release process, as discussed here and avoid manual bumps. >>>>>>> >>>>>>> Also, it never hurts to release bits to the community very often >>>>>>> (release early, release often). This likely avoids issues like the above >>>>>>> >>>>>>> -M >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> WEI LI >>>>>>>> >>>>>>>> SENIOR SOFTWARE ENGINEER >>>>>>>> >>>>>>>> Red Hat Mobile >>>>>>>> >>>>>>>> weil at redhat.com M: +353862393272 >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> WEI LI >>>>>> >>>>>> SENIOR SOFTWARE ENGINEER >>>>>> >>>>>> Red Hat Mobile >>>>>> >>>>>> weil at redhat.com M: +353862393272 >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> KAREL PIWKO >>>> >>>> MANAGER, MOBILE QE >>>> >>>> Red Hat Czech Republic >>>> >>>> Purky?ova 647/111 >>>> >>>> 612 00 Brno, Czech Republic >>>> >>>> kpiwko at redhat.com IM: kpiwko >>>> >>>> TRIED. TESTED. TRUSTED. >>>> @redhatway @redhatinc >>>> @redhatsnaps >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> >>> WEI LI >>> >>> SENIOR SOFTWARE ENGINEER >>> >>> Red Hat Mobile >>> >>> weil at redhat.com M: +353862393272 >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > > WEI LI > > SENIOR SOFTWARE ENGINEER > > Red Hat Mobile > > weil at redhat.com M: +353862393272 > > > _______________________________________________ > 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/20170804/63be4125/attachment-0001.html From jgallaso at redhat.com Mon Aug 7 05:43:20 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Mon, 7 Aug 2017 11:43:20 +0200 Subject: [aerogear-dev] UPS not finding admin-ui-keycloak.json In-Reply-To: References: Message-ID: Hi Matthias, I'm not using Wildfly anymore but eap-6.4. The branch I'm trying to deploy is fheng/ups-rhmap_3.16.x JOSE MIGUEL GALLAS OLMEDO ASSOCIATE QE, mobile Red Hat M: +34618488633 On 28 July 2017 at 09:11, Matthias Wessendorf wrote: > did you also run this config ? > > https://github.com/aerogear/aerogear-unifiedpush-server/ > blob/1.1.x-dev/configuration/jms-setup-wildfly.cli > > It's now also needed on 1.1.x - like on master > > On Thu, Jul 27, 2017 at 1:14 PM, Jose Miguel Gallas Olmedo < > jgallaso at redhat.com> wrote: > >> $ ls -al >> total 12828 >> drwxrwxr-x. 3 jgallaso jgallaso 4096 Jul 26 12:23 . >> drwxrwxr-x. 8 jgallaso jgallaso 4096 Jul 12 16:27 .. >> drwxrwxr-x. 12 jgallaso jgallaso 4096 Jul 26 12:18 ag-push.war >> -rw-rw-r--. 1 jgallaso jgallaso 11 Jul 26 12:18 >> ag-push.war.deployed >> -rw-rw-r--. 1 jgallaso jgallaso 13100156 <310-0156> Jul 26 12:18 >> auth-server.war >> -rw-rw-r--. 1 jgallaso jgallaso 15 Jul 26 12:18 >> auth-server.war.deployed >> -rw-rw-r--. 1 jgallaso jgallaso 9041 Apr 27 10:55 README.txt >> >> >> On 27 July 2017 at 09:58, Matthias Wessendorf wrote: >> >>> what is the value of the deployments folder ? >>> ls -la $JBOSS_HOME/standalone/deployments >>> >>> On Wed, Jul 26, 2017 at 12:43 PM, Jose Miguel Gallas Olmedo < >>> jgallaso at redhat.com> wrote: >>> >>>> Hi, >>>> >>>> I've been trying to deploy UPS for quite some time and it won't work. >>>> I'm following this instructions word by word ( >>>> https://github.com/aerogear/aerogear.org/blob/master/docs/u >>>> nifiedpush/ups_userguide/server-installation.asciidoc) and I've >>>> started from scratch twice already, the problem is when I open the browser, >>>> it keeps refreshing over and over with a blank page and this message error: >>>> >>>> *Get http://localhost:8080/ag-push/config/admin-ui-keycloak.json >>>> (404 Not >>>> found)* >>>> >>>> I'm using 1.1.x-dev with JBoss EAP 6.4, I have both DB with docker >>>> (using docker-compose) and both ag-push.was and auth-server.war are >>>> deployed. No error in Jboss log.. >>>> >>>> So at this point, clueless as I am, is anyone able to help me? >>>> >>>> Thanks, >>>> >>>> -- >>>> >>>> JOSE MIGUEL GALLAS OLMEDO >>>> >>>> ASSOCIATE QE, mobile >>>> >>>> Red Hat >>>> >>>> >>>> >>>> M: +34618488633 >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> >> >> -- >> >> JOSE MIGUEL GALLAS OLMEDO >> >> ASSOCIATE QE, mobile >> >> Red Hat >> >> >> >> M: +34618488633 >> >> >> >> _______________________________________________ >> 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/20170807/2d22b8d3/attachment.html From matzew at apache.org Mon Aug 7 06:45:42 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 7 Aug 2017 12:45:42 +0200 Subject: [aerogear-dev] UPS not finding admin-ui-keycloak.json In-Reply-To: References: Message-ID: right, please run the jms config - it's required for 1.1.x branch and branches, based on that On Mon, Aug 7, 2017 at 11:43 AM, Jose Miguel Gallas Olmedo < jgallaso at redhat.com> wrote: > Hi Matthias, > > I'm not using Wildfly anymore but eap-6.4. The branch I'm trying to deploy > is fheng/ups-rhmap_3.16.x > > JOSE MIGUEL GALLAS OLMEDO > > ASSOCIATE QE, mobile > > Red Hat > > > > M: +34618488633 > > > > On 28 July 2017 at 09:11, Matthias Wessendorf wrote: > >> did you also run this config ? >> >> https://github.com/aerogear/aerogear-unifiedpush-server/blob >> /1.1.x-dev/configuration/jms-setup-wildfly.cli >> >> It's now also needed on 1.1.x - like on master >> >> On Thu, Jul 27, 2017 at 1:14 PM, Jose Miguel Gallas Olmedo < >> jgallaso at redhat.com> wrote: >> >>> $ ls -al >>> total 12828 >>> drwxrwxr-x. 3 jgallaso jgallaso 4096 Jul 26 12:23 . >>> drwxrwxr-x. 8 jgallaso jgallaso 4096 Jul 12 16:27 .. >>> drwxrwxr-x. 12 jgallaso jgallaso 4096 Jul 26 12:18 ag-push.war >>> -rw-rw-r--. 1 jgallaso jgallaso 11 Jul 26 12:18 >>> ag-push.war.deployed >>> -rw-rw-r--. 1 jgallaso jgallaso 13100156 <310-0156> Jul 26 12:18 >>> auth-server.war >>> -rw-rw-r--. 1 jgallaso jgallaso 15 Jul 26 12:18 >>> auth-server.war.deployed >>> -rw-rw-r--. 1 jgallaso jgallaso 9041 Apr 27 10:55 README.txt >>> >>> >>> On 27 July 2017 at 09:58, Matthias Wessendorf wrote: >>> >>>> what is the value of the deployments folder ? >>>> ls -la $JBOSS_HOME/standalone/deployments >>>> >>>> On Wed, Jul 26, 2017 at 12:43 PM, Jose Miguel Gallas Olmedo < >>>> jgallaso at redhat.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> I've been trying to deploy UPS for quite some time and it won't work. >>>>> I'm following this instructions word by word ( >>>>> https://github.com/aerogear/aerogear.org/blob/master/docs/u >>>>> nifiedpush/ups_userguide/server-installation.asciidoc) and I've >>>>> started from scratch twice already, the problem is when I open the browser, >>>>> it keeps refreshing over and over with a blank page and this message error: >>>>> >>>>> *Get http://localhost:8080/ag-push/config/admin-ui-keycloak.json >>>>> (404 Not >>>>> found)* >>>>> >>>>> I'm using 1.1.x-dev with JBoss EAP 6.4, I have both DB with docker >>>>> (using docker-compose) and both ag-push.was and auth-server.war are >>>>> deployed. No error in Jboss log.. >>>>> >>>>> So at this point, clueless as I am, is anyone able to help me? >>>>> >>>>> Thanks, >>>>> >>>>> -- >>>>> >>>>> JOSE MIGUEL GALLAS OLMEDO >>>>> >>>>> ASSOCIATE QE, mobile >>>>> >>>>> Red Hat >>>>> >>>>> >>>>> >>>>> M: +34618488633 >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>> >>> >>> >>> -- >>> >>> JOSE MIGUEL GALLAS OLMEDO >>> >>> ASSOCIATE QE, mobile >>> >>> Red Hat >>> >>> >>> >>> M: +34618488633 >>> >>> >>> >>> _______________________________________________ >>> 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 >> > > > _______________________________________________ > 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/20170807/93e5e847/attachment-0001.html From matzew at apache.org Mon Aug 7 06:46:24 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 7 Aug 2017 12:46:24 +0200 Subject: [aerogear-dev] UPS not finding admin-ui-keycloak.json In-Reply-To: References: Message-ID: ignore that the file is named wildfly ... it's generic.... On Mon, Aug 7, 2017 at 12:45 PM, Matthias Wessendorf wrote: > right, please run the jms config - it's required for 1.1.x branch and > branches, based on that > > On Mon, Aug 7, 2017 at 11:43 AM, Jose Miguel Gallas Olmedo < > jgallaso at redhat.com> wrote: > >> Hi Matthias, >> >> I'm not using Wildfly anymore but eap-6.4. The branch I'm trying to >> deploy is fheng/ups-rhmap_3.16.x >> >> JOSE MIGUEL GALLAS OLMEDO >> >> ASSOCIATE QE, mobile >> >> Red Hat >> >> >> >> M: +34618488633 >> >> >> >> On 28 July 2017 at 09:11, Matthias Wessendorf wrote: >> >>> did you also run this config ? >>> >>> https://github.com/aerogear/aerogear-unifiedpush-server/blob >>> /1.1.x-dev/configuration/jms-setup-wildfly.cli >>> >>> It's now also needed on 1.1.x - like on master >>> >>> On Thu, Jul 27, 2017 at 1:14 PM, Jose Miguel Gallas Olmedo < >>> jgallaso at redhat.com> wrote: >>> >>>> $ ls -al >>>> total 12828 >>>> drwxrwxr-x. 3 jgallaso jgallaso 4096 Jul 26 12:23 . >>>> drwxrwxr-x. 8 jgallaso jgallaso 4096 Jul 12 16:27 .. >>>> drwxrwxr-x. 12 jgallaso jgallaso 4096 Jul 26 12:18 ag-push.war >>>> -rw-rw-r--. 1 jgallaso jgallaso 11 Jul 26 12:18 >>>> ag-push.war.deployed >>>> -rw-rw-r--. 1 jgallaso jgallaso 13100156 <310-0156> Jul 26 12:18 >>>> auth-server.war >>>> -rw-rw-r--. 1 jgallaso jgallaso 15 Jul 26 12:18 >>>> auth-server.war.deployed >>>> -rw-rw-r--. 1 jgallaso jgallaso 9041 Apr 27 10:55 README.txt >>>> >>>> >>>> On 27 July 2017 at 09:58, Matthias Wessendorf >>>> wrote: >>>> >>>>> what is the value of the deployments folder ? >>>>> ls -la $JBOSS_HOME/standalone/deployments >>>>> >>>>> On Wed, Jul 26, 2017 at 12:43 PM, Jose Miguel Gallas Olmedo < >>>>> jgallaso at redhat.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I've been trying to deploy UPS for quite some time and it won't work. >>>>>> I'm following this instructions word by word ( >>>>>> https://github.com/aerogear/aerogear.org/blob/master/docs/u >>>>>> nifiedpush/ups_userguide/server-installation.asciidoc) and I've >>>>>> started from scratch twice already, the problem is when I open the browser, >>>>>> it keeps refreshing over and over with a blank page and this message error: >>>>>> >>>>>> *Get http://localhost:8080/ag-push/config/admin-ui-keycloak.json >>>>>> (404 Not >>>>>> found)* >>>>>> >>>>>> I'm using 1.1.x-dev with JBoss EAP 6.4, I have both DB with docker >>>>>> (using docker-compose) and both ag-push.was and auth-server.war are >>>>>> deployed. No error in Jboss log.. >>>>>> >>>>>> So at this point, clueless as I am, is anyone able to help me? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> -- >>>>>> >>>>>> JOSE MIGUEL GALLAS OLMEDO >>>>>> >>>>>> ASSOCIATE QE, mobile >>>>>> >>>>>> Red Hat >>>>>> >>>>>> >>>>>> >>>>>> M: +34618488633 >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> JOSE MIGUEL GALLAS OLMEDO >>>> >>>> ASSOCIATE QE, mobile >>>> >>>> Red Hat >>>> >>>> >>>> >>>> M: +34618488633 >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> >> _______________________________________________ >> 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 > -- 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/20170807/300b2ebb/attachment.html From jgallaso at redhat.com Tue Aug 8 03:30:08 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Tue, 8 Aug 2017 09:30:08 +0200 Subject: [aerogear-dev] UPS not finding admin-ui-keycloak.json In-Reply-To: References: Message-ID: Well the thing is that there is no such file in ups_rhmap_3.16.x I checkout'ed "1.1.x-dev" I tried to run the jms-setup-wildfly.cli but it gives me an error: Failed to get the list of the operation properties: "JBAS014883: No resource definition is registered for address [ ("subsystem" => "messaging-activemq"), ("server" => "default"), ("address-setting" => "jms.queue.GCMPushMessageQueue") ]" ?Anyway, if this is necessary in 1.1.x as you say, the documentation is wrong -> https://github.com/aerogear/aerogear.org/blob/master/docs/unifiedpush/ups_userguide/server-installation.asciidoc#configure-jms-destinations-for-the-unifiedpush ? JOSE MIGUEL GALLAS OLMEDO ASSOCIATE QE, mobile Red Hat M: +34618488633 On 7 August 2017 at 12:46, Matthias Wessendorf wrote: > ignore that the file is named wildfly ... it's generic.... > > On Mon, Aug 7, 2017 at 12:45 PM, Matthias Wessendorf > wrote: > >> right, please run the jms config - it's required for 1.1.x branch and >> branches, based on that >> >> On Mon, Aug 7, 2017 at 11:43 AM, Jose Miguel Gallas Olmedo < >> jgallaso at redhat.com> wrote: >> >>> Hi Matthias, >>> >>> I'm not using Wildfly anymore but eap-6.4. The branch I'm trying to >>> deploy is fheng/ups-rhmap_3.16.x >>> >>> JOSE MIGUEL GALLAS OLMEDO >>> >>> ASSOCIATE QE, mobile >>> >>> Red Hat >>> >>> >>> >>> M: +34618488633 >>> >>> >>> >>> On 28 July 2017 at 09:11, Matthias Wessendorf wrote: >>> >>>> did you also run this config ? >>>> >>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob >>>> /1.1.x-dev/configuration/jms-setup-wildfly.cli >>>> >>>> It's now also needed on 1.1.x - like on master >>>> >>>> On Thu, Jul 27, 2017 at 1:14 PM, Jose Miguel Gallas Olmedo < >>>> jgallaso at redhat.com> wrote: >>>> >>>>> $ ls -al >>>>> total 12828 >>>>> drwxrwxr-x. 3 jgallaso jgallaso 4096 Jul 26 12:23 . >>>>> drwxrwxr-x. 8 jgallaso jgallaso 4096 Jul 12 16:27 .. >>>>> drwxrwxr-x. 12 jgallaso jgallaso 4096 Jul 26 12:18 ag-push.war >>>>> -rw-rw-r--. 1 jgallaso jgallaso 11 Jul 26 12:18 >>>>> ag-push.war.deployed >>>>> -rw-rw-r--. 1 jgallaso jgallaso 13100156 <310-0156> Jul 26 12:18 >>>>> auth-server.war >>>>> -rw-rw-r--. 1 jgallaso jgallaso 15 Jul 26 12:18 >>>>> auth-server.war.deployed >>>>> -rw-rw-r--. 1 jgallaso jgallaso 9041 Apr 27 10:55 README.txt >>>>> >>>>> >>>>> On 27 July 2017 at 09:58, Matthias Wessendorf >>>>> wrote: >>>>> >>>>>> what is the value of the deployments folder ? >>>>>> ls -la $JBOSS_HOME/standalone/deployments >>>>>> >>>>>> On Wed, Jul 26, 2017 at 12:43 PM, Jose Miguel Gallas Olmedo < >>>>>> jgallaso at redhat.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I've been trying to deploy UPS for quite some time and it won't >>>>>>> work. I'm following this instructions word by word ( >>>>>>> https://github.com/aerogear/aerogear.org/blob/master/docs/u >>>>>>> nifiedpush/ups_userguide/server-installation.asciidoc) and I've >>>>>>> started from scratch twice already, the problem is when I open the browser, >>>>>>> it keeps refreshing over and over with a blank page and this message error: >>>>>>> >>>>>>> *Get http://localhost:8080/ag-push/config/admin-ui-keycloak.json >>>>>>> (404 Not >>>>>>> found)* >>>>>>> >>>>>>> I'm using 1.1.x-dev with JBoss EAP 6.4, I have both DB with docker >>>>>>> (using docker-compose) and both ag-push.was and auth-server.war are >>>>>>> deployed. No error in Jboss log.. >>>>>>> >>>>>>> So at this point, clueless as I am, is anyone able to help me? >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> JOSE MIGUEL GALLAS OLMEDO >>>>>>> >>>>>>> ASSOCIATE QE, mobile >>>>>>> >>>>>>> Red Hat >>>>>>> >>>>>>> >>>>>>> >>>>>>> M: +34618488633 >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> JOSE MIGUEL GALLAS OLMEDO >>>>> >>>>> ASSOCIATE QE, mobile >>>>> >>>>> Red Hat >>>>> >>>>> >>>>> >>>>> M: +34618488633 >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > 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/20170808/a7791e11/attachment-0001.html From matzew at apache.org Tue Aug 8 04:01:04 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 8 Aug 2017 10:01:04 +0200 Subject: [aerogear-dev] UPS not finding admin-ui-keycloak.json In-Reply-To: References: Message-ID: On Tue, Aug 8, 2017 at 9:30 AM, Jose Miguel Gallas Olmedo < jgallaso at redhat.com> wrote: > Well the thing is that there is no such file in ups_rhmap_3.16.x > that's a different branch, let's focus on 1.1.x-dev here > > I checkout'ed "1.1.x-dev" I tried to run the jms-setup-wildfly.cli but it > gives me an error: > > Failed to get the list of the operation properties: "JBAS014883: No > resource definition is registered for address [ > ("subsystem" => "messaging-activemq"), > ("server" => "default"), > ("address-setting" => "jms.queue.GCMPushMessageQueue") > ]" > > Oh, I think the subsystem in EAP is called "messaging", instead of "messaging-activemq", likely a typo in the CLI file > > ?Anyway, if this is necessary in 1.1.x as you say, the documentation is > wrong -> https://github.com/aerogear/aerogear.org/blob/master/docs/un > ifiedpush/ups_userguide/server-installation.asciidoc#configu > re-jms-destinations-for-the-unifiedpush > ? > > yep, that's right.. as stated in an earlier email > JOSE MIGUEL GALLAS OLMEDO > > ASSOCIATE QE, mobile > > Red Hat > > > > M: +34618488633 > > > > On 7 August 2017 at 12:46, Matthias Wessendorf wrote: > >> ignore that the file is named wildfly ... it's generic.... >> >> On Mon, Aug 7, 2017 at 12:45 PM, Matthias Wessendorf >> wrote: >> >>> right, please run the jms config - it's required for 1.1.x branch and >>> branches, based on that >>> >>> On Mon, Aug 7, 2017 at 11:43 AM, Jose Miguel Gallas Olmedo < >>> jgallaso at redhat.com> wrote: >>> >>>> Hi Matthias, >>>> >>>> I'm not using Wildfly anymore but eap-6.4. The branch I'm trying to >>>> deploy is fheng/ups-rhmap_3.16.x >>>> >>>> JOSE MIGUEL GALLAS OLMEDO >>>> >>>> ASSOCIATE QE, mobile >>>> >>>> Red Hat >>>> >>>> >>>> >>>> M: +34618488633 >>>> >>>> >>>> >>>> On 28 July 2017 at 09:11, Matthias Wessendorf >>>> wrote: >>>> >>>>> did you also run this config ? >>>>> >>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob >>>>> /1.1.x-dev/configuration/jms-setup-wildfly.cli >>>>> >>>>> It's now also needed on 1.1.x - like on master >>>>> >>>>> On Thu, Jul 27, 2017 at 1:14 PM, Jose Miguel Gallas Olmedo < >>>>> jgallaso at redhat.com> wrote: >>>>> >>>>>> $ ls -al >>>>>> total 12828 >>>>>> drwxrwxr-x. 3 jgallaso jgallaso 4096 Jul 26 12:23 . >>>>>> drwxrwxr-x. 8 jgallaso jgallaso 4096 Jul 12 16:27 .. >>>>>> drwxrwxr-x. 12 jgallaso jgallaso 4096 Jul 26 12:18 ag-push.war >>>>>> -rw-rw-r--. 1 jgallaso jgallaso 11 Jul 26 12:18 >>>>>> ag-push.war.deployed >>>>>> -rw-rw-r--. 1 jgallaso jgallaso 13100156 <310-0156> Jul 26 12:18 >>>>>> auth-server.war >>>>>> -rw-rw-r--. 1 jgallaso jgallaso 15 Jul 26 12:18 >>>>>> auth-server.war.deployed >>>>>> -rw-rw-r--. 1 jgallaso jgallaso 9041 Apr 27 10:55 README.txt >>>>>> >>>>>> >>>>>> On 27 July 2017 at 09:58, Matthias Wessendorf >>>>>> wrote: >>>>>> >>>>>>> what is the value of the deployments folder ? >>>>>>> ls -la $JBOSS_HOME/standalone/deployments >>>>>>> >>>>>>> On Wed, Jul 26, 2017 at 12:43 PM, Jose Miguel Gallas Olmedo < >>>>>>> jgallaso at redhat.com> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I've been trying to deploy UPS for quite some time and it won't >>>>>>>> work. I'm following this instructions word by word ( >>>>>>>> https://github.com/aerogear/aerogear.org/blob/master/docs/u >>>>>>>> nifiedpush/ups_userguide/server-installation.asciidoc) and I've >>>>>>>> started from scratch twice already, the problem is when I open the browser, >>>>>>>> it keeps refreshing over and over with a blank page and this message error: >>>>>>>> >>>>>>>> *Get http://localhost:8080/ag-push/config/admin-ui-keycloak.json >>>>>>>> (404 Not >>>>>>>> found)* >>>>>>>> >>>>>>>> I'm using 1.1.x-dev with JBoss EAP 6.4, I have both DB with docker >>>>>>>> (using docker-compose) and both ag-push.was and auth-server.war are >>>>>>>> deployed. No error in Jboss log.. >>>>>>>> >>>>>>>> So at this point, clueless as I am, is anyone able to help me? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> JOSE MIGUEL GALLAS OLMEDO >>>>>>>> >>>>>>>> ASSOCIATE QE, mobile >>>>>>>> >>>>>>>> Red Hat >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> M: +34618488633 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> JOSE MIGUEL GALLAS OLMEDO >>>>>> >>>>>> ASSOCIATE QE, mobile >>>>>> >>>>>> Red Hat >>>>>> >>>>>> >>>>>> >>>>>> M: +34618488633 >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> >> >> -- >> 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 >> > > > _______________________________________________ > 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/20170808/46a9c8d0/attachment-0001.html From matzew at apache.org Tue Aug 8 04:05:28 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 8 Aug 2017 10:05:28 +0200 Subject: [aerogear-dev] UPS not finding admin-ui-keycloak.json In-Reply-To: References: Message-ID: On Tue, Aug 8, 2017 at 10:01 AM, Matthias Wessendorf wrote: > > > On Tue, Aug 8, 2017 at 9:30 AM, Jose Miguel Gallas Olmedo < > jgallaso at redhat.com> wrote: > >> Well the thing is that there is no such file in ups_rhmap_3.16.x >> > > that's a different branch, let's focus on 1.1.x-dev here > > >> >> I checkout'ed "1.1.x-dev" I tried to run the jms-setup-wildfly.cli but it >> gives me an error: >> >> Failed to get the list of the operation properties: "JBAS014883: No >> resource definition is registered for address [ >> ("subsystem" => "messaging-activemq"), >> ("server" => "default"), >> ("address-setting" => "jms.queue.GCMPushMessageQueue") >> ]" >> >> > > Oh, I think the subsystem in EAP is called "messaging", instead of > "messaging-activemq", likely a typo in the CLI file > I think it needs to be: "subsystem=messaging/hornetq-server" instead of "subsystem=messaging-activemq/server" can you replace those lines and try ? > >> >> ?Anyway, if this is necessary in 1.1.x as you say, the documentation is >> wrong -> https://github.com/aerogear/aerogear.org/blob/master/docs/un >> ifiedpush/ups_userguide/server-installation.asciidoc#configu >> re-jms-destinations-for-the-unifiedpush >> ? >> >> > > yep, that's right.. as stated in an earlier email > > > > > >> JOSE MIGUEL GALLAS OLMEDO >> >> ASSOCIATE QE, mobile >> >> Red Hat >> >> >> >> M: +34618488633 >> >> >> >> On 7 August 2017 at 12:46, Matthias Wessendorf wrote: >> >>> ignore that the file is named wildfly ... it's generic.... >>> >>> On Mon, Aug 7, 2017 at 12:45 PM, Matthias Wessendorf >>> wrote: >>> >>>> right, please run the jms config - it's required for 1.1.x branch and >>>> branches, based on that >>>> >>>> On Mon, Aug 7, 2017 at 11:43 AM, Jose Miguel Gallas Olmedo < >>>> jgallaso at redhat.com> wrote: >>>> >>>>> Hi Matthias, >>>>> >>>>> I'm not using Wildfly anymore but eap-6.4. The branch I'm trying to >>>>> deploy is fheng/ups-rhmap_3.16.x >>>>> >>>>> JOSE MIGUEL GALLAS OLMEDO >>>>> >>>>> ASSOCIATE QE, mobile >>>>> >>>>> Red Hat >>>>> >>>>> >>>>> >>>>> M: +34618488633 >>>>> >>>>> >>>>> >>>>> On 28 July 2017 at 09:11, Matthias Wessendorf >>>>> wrote: >>>>> >>>>>> did you also run this config ? >>>>>> >>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob >>>>>> /1.1.x-dev/configuration/jms-setup-wildfly.cli >>>>>> >>>>>> It's now also needed on 1.1.x - like on master >>>>>> >>>>>> On Thu, Jul 27, 2017 at 1:14 PM, Jose Miguel Gallas Olmedo < >>>>>> jgallaso at redhat.com> wrote: >>>>>> >>>>>>> $ ls -al >>>>>>> total 12828 >>>>>>> drwxrwxr-x. 3 jgallaso jgallaso 4096 Jul 26 12:23 . >>>>>>> drwxrwxr-x. 8 jgallaso jgallaso 4096 Jul 12 16:27 .. >>>>>>> drwxrwxr-x. 12 jgallaso jgallaso 4096 Jul 26 12:18 ag-push.war >>>>>>> -rw-rw-r--. 1 jgallaso jgallaso 11 Jul 26 12:18 >>>>>>> ag-push.war.deployed >>>>>>> -rw-rw-r--. 1 jgallaso jgallaso 13100156 <310-0156> Jul 26 12:18 >>>>>>> auth-server.war >>>>>>> -rw-rw-r--. 1 jgallaso jgallaso 15 Jul 26 12:18 >>>>>>> auth-server.war.deployed >>>>>>> -rw-rw-r--. 1 jgallaso jgallaso 9041 Apr 27 10:55 README.txt >>>>>>> >>>>>>> >>>>>>> On 27 July 2017 at 09:58, Matthias Wessendorf >>>>>>> wrote: >>>>>>> >>>>>>>> what is the value of the deployments folder ? >>>>>>>> ls -la $JBOSS_HOME/standalone/deployments >>>>>>>> >>>>>>>> On Wed, Jul 26, 2017 at 12:43 PM, Jose Miguel Gallas Olmedo < >>>>>>>> jgallaso at redhat.com> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I've been trying to deploy UPS for quite some time and it won't >>>>>>>>> work. I'm following this instructions word by word ( >>>>>>>>> https://github.com/aerogear/aerogear.org/blob/master/docs/u >>>>>>>>> nifiedpush/ups_userguide/server-installation.asciidoc) and I've >>>>>>>>> started from scratch twice already, the problem is when I open the browser, >>>>>>>>> it keeps refreshing over and over with a blank page and this message error: >>>>>>>>> >>>>>>>>> *Get http://localhost:8080/ag-push/config/admin-ui-keycloak.json >>>>>>>>> (404 Not >>>>>>>>> found)* >>>>>>>>> >>>>>>>>> I'm using 1.1.x-dev with JBoss EAP 6.4, I have both DB with docker >>>>>>>>> (using docker-compose) and both ag-push.was and auth-server.war are >>>>>>>>> deployed. No error in Jboss log.. >>>>>>>>> >>>>>>>>> So at this point, clueless as I am, is anyone able to help me? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> JOSE MIGUEL GALLAS OLMEDO >>>>>>>>> >>>>>>>>> ASSOCIATE QE, mobile >>>>>>>>> >>>>>>>>> Red Hat >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> M: +34618488633 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> JOSE MIGUEL GALLAS OLMEDO >>>>>>> >>>>>>> ASSOCIATE QE, mobile >>>>>>> >>>>>>> Red Hat >>>>>>> >>>>>>> >>>>>>> >>>>>>> M: +34618488633 >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>> >>> >>> >>> -- >>> 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 >>> >> >> >> _______________________________________________ >> 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 > -- 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/20170808/1783ca14/attachment-0001.html From matzew at apache.org Tue Aug 8 04:13:09 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 8 Aug 2017 10:13:09 +0200 Subject: [aerogear-dev] UPS not finding admin-ui-keycloak.json In-Reply-To: References: Message-ID: see https://github.com/aerogear/aerogear-unifiedpush-server/pull/878 On Tue, Aug 8, 2017 at 10:05 AM, Matthias Wessendorf wrote: > > > On Tue, Aug 8, 2017 at 10:01 AM, Matthias Wessendorf > wrote: > >> >> >> On Tue, Aug 8, 2017 at 9:30 AM, Jose Miguel Gallas Olmedo < >> jgallaso at redhat.com> wrote: >> >>> Well the thing is that there is no such file in ups_rhmap_3.16.x >>> >> >> that's a different branch, let's focus on 1.1.x-dev here >> >> >>> >>> I checkout'ed "1.1.x-dev" I tried to run the jms-setup-wildfly.cli but >>> it gives me an error: >>> >>> Failed to get the list of the operation properties: "JBAS014883: No >>> resource definition is registered for address [ >>> ("subsystem" => "messaging-activemq"), >>> ("server" => "default"), >>> ("address-setting" => "jms.queue.GCMPushMessageQueue") >>> ]" >>> >>> >> >> Oh, I think the subsystem in EAP is called "messaging", instead of >> "messaging-activemq", likely a typo in the CLI file >> > > > I think it needs to be: > "subsystem=messaging/hornetq-server" > > instead of > "subsystem=messaging-activemq/server" > > can you replace those lines and try ? > > >> >>> >>> ?Anyway, if this is necessary in 1.1.x as you say, the documentation is >>> wrong -> https://github.com/aerogear/aerogear.org/blob/master/docs/un >>> ifiedpush/ups_userguide/server-installation.asciidoc#configu >>> re-jms-destinations-for-the-unifiedpush >>> ? >>> >>> >> >> yep, that's right.. as stated in an earlier email >> >> >> >> >> >>> JOSE MIGUEL GALLAS OLMEDO >>> >>> ASSOCIATE QE, mobile >>> >>> Red Hat >>> >>> >>> >>> M: +34618488633 >>> >>> >>> >>> On 7 August 2017 at 12:46, Matthias Wessendorf >>> wrote: >>> >>>> ignore that the file is named wildfly ... it's generic.... >>>> >>>> On Mon, Aug 7, 2017 at 12:45 PM, Matthias Wessendorf >>> > wrote: >>>> >>>>> right, please run the jms config - it's required for 1.1.x branch and >>>>> branches, based on that >>>>> >>>>> On Mon, Aug 7, 2017 at 11:43 AM, Jose Miguel Gallas Olmedo < >>>>> jgallaso at redhat.com> wrote: >>>>> >>>>>> Hi Matthias, >>>>>> >>>>>> I'm not using Wildfly anymore but eap-6.4. The branch I'm trying to >>>>>> deploy is fheng/ups-rhmap_3.16.x >>>>>> >>>>>> JOSE MIGUEL GALLAS OLMEDO >>>>>> >>>>>> ASSOCIATE QE, mobile >>>>>> >>>>>> Red Hat >>>>>> >>>>>> >>>>>> >>>>>> M: +34618488633 >>>>>> >>>>>> >>>>>> >>>>>> On 28 July 2017 at 09:11, Matthias Wessendorf >>>>>> wrote: >>>>>> >>>>>>> did you also run this config ? >>>>>>> >>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob >>>>>>> /1.1.x-dev/configuration/jms-setup-wildfly.cli >>>>>>> >>>>>>> It's now also needed on 1.1.x - like on master >>>>>>> >>>>>>> On Thu, Jul 27, 2017 at 1:14 PM, Jose Miguel Gallas Olmedo < >>>>>>> jgallaso at redhat.com> wrote: >>>>>>> >>>>>>>> $ ls -al >>>>>>>> total 12828 >>>>>>>> drwxrwxr-x. 3 jgallaso jgallaso 4096 Jul 26 12:23 . >>>>>>>> drwxrwxr-x. 8 jgallaso jgallaso 4096 Jul 12 16:27 .. >>>>>>>> drwxrwxr-x. 12 jgallaso jgallaso 4096 Jul 26 12:18 ag-push.war >>>>>>>> -rw-rw-r--. 1 jgallaso jgallaso 11 Jul 26 12:18 >>>>>>>> ag-push.war.deployed >>>>>>>> -rw-rw-r--. 1 jgallaso jgallaso 13100156 <310-0156> Jul 26 12:18 >>>>>>>> auth-server.war >>>>>>>> -rw-rw-r--. 1 jgallaso jgallaso 15 Jul 26 12:18 >>>>>>>> auth-server.war.deployed >>>>>>>> -rw-rw-r--. 1 jgallaso jgallaso 9041 Apr 27 10:55 README.txt >>>>>>>> >>>>>>>> >>>>>>>> On 27 July 2017 at 09:58, Matthias Wessendorf >>>>>>>> wrote: >>>>>>>> >>>>>>>>> what is the value of the deployments folder ? >>>>>>>>> ls -la $JBOSS_HOME/standalone/deployments >>>>>>>>> >>>>>>>>> On Wed, Jul 26, 2017 at 12:43 PM, Jose Miguel Gallas Olmedo < >>>>>>>>> jgallaso at redhat.com> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> I've been trying to deploy UPS for quite some time and it won't >>>>>>>>>> work. I'm following this instructions word by word ( >>>>>>>>>> https://github.com/aerogear/aerogear.org/blob/master/docs/u >>>>>>>>>> nifiedpush/ups_userguide/server-installation.asciidoc) and I've >>>>>>>>>> started from scratch twice already, the problem is when I open the browser, >>>>>>>>>> it keeps refreshing over and over with a blank page and this message error: >>>>>>>>>> >>>>>>>>>> *Get http://localhost:8080/ag-push/config/admin-ui-keycloak.json >>>>>>>>>> (404 Not >>>>>>>>>> found)* >>>>>>>>>> >>>>>>>>>> I'm using 1.1.x-dev with JBoss EAP 6.4, I have both DB with >>>>>>>>>> docker (using docker-compose) and both ag-push.was and auth-server.war are >>>>>>>>>> deployed. No error in Jboss log.. >>>>>>>>>> >>>>>>>>>> So at this point, clueless as I am, is anyone able to help me? >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> >>>>>>>>>> JOSE MIGUEL GALLAS OLMEDO >>>>>>>>>> >>>>>>>>>> ASSOCIATE QE, mobile >>>>>>>>>> >>>>>>>>>> Red Hat >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> M: +34618488633 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> JOSE MIGUEL GALLAS OLMEDO >>>>>>>> >>>>>>>> ASSOCIATE QE, mobile >>>>>>>> >>>>>>>> Red Hat >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> M: +34618488633 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> 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 >>>> >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > 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/20170808/085680ba/attachment-0001.html From aliok at redhat.com Tue Aug 8 04:42:16 2017 From: aliok at redhat.com (Ali Ok) Date: Tue, 8 Aug 2017 11:42:16 +0300 Subject: [aerogear-dev] AGDIGGER JIRA components In-Reply-To: References: Message-ID: @matzew, could you do this? I guess we had enough feedback :) Cheers On Wed, Aug 2, 2017 at 11:31 AM, Wei Li wrote: > I think these components are reasonable. > > On Wed, Aug 2, 2017 at 8:44 AM, Ali Ok wrote: > >> Hi Leo and Wei, >> >> Any ideas? >> >> >> On Mon, Jul 31, 2017 at 10:36 AM, Matthias Wessendorf >> wrote: >> >>> sure thing! >>> >>> once we have agreed on them, I'll go ahead and update them >>> >>> On Mon, Jul 31, 2017 at 9:03 AM, Ali Ok wrote: >>> >>>> Hi, >>>> >>>> I think we need to update our JIRA components in AGDIGGER project. >>>> >>>> Perhaps these: >>>> >>>> - Android support >>>> - IOS support >>>> - Ansible Installer >>>> - Sample (I mean sample Jenkinsfiles) >>>> - Node client >>>> - Java client >>>> >>>> Anything missing or strange? >>>> >>>> @Matthias, can you do that? >>>> >>>> Cheers, >>>> Ali >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> twitter: http://twitter.com/mwessendorf >>> >> >> > > > -- > > WEI LI > > SENIOR SOFTWARE ENGINEER > > Red Hat Mobile > > weil at redhat.com M: +353862393272 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170808/dd1de740/attachment.html From matzew at apache.org Tue Aug 8 04:56:35 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 8 Aug 2017 10:56:35 +0200 Subject: [aerogear-dev] AGDIGGER JIRA components In-Reply-To: References: Message-ID: hrm, not sure I can, actually... sorry On Tue, Aug 8, 2017 at 10:42 AM, Ali Ok wrote: > @matzew, > > could you do this? I guess we had enough feedback :) > > Cheers > > On Wed, Aug 2, 2017 at 11:31 AM, Wei Li wrote: > >> I think these components are reasonable. >> >> On Wed, Aug 2, 2017 at 8:44 AM, Ali Ok wrote: >> >>> Hi Leo and Wei, >>> >>> Any ideas? >>> >>> >>> On Mon, Jul 31, 2017 at 10:36 AM, Matthias Wessendorf >> > wrote: >>> >>>> sure thing! >>>> >>>> once we have agreed on them, I'll go ahead and update them >>>> >>>> On Mon, Jul 31, 2017 at 9:03 AM, Ali Ok wrote: >>>> >>>>> Hi, >>>>> >>>>> I think we need to update our JIRA components in AGDIGGER project. >>>>> >>>>> Perhaps these: >>>>> >>>>> - Android support >>>>> - IOS support >>>>> - Ansible Installer >>>>> - Sample (I mean sample Jenkinsfiles) >>>>> - Node client >>>>> - Java client >>>>> >>>>> Anything missing or strange? >>>>> >>>>> @Matthias, can you do that? >>>>> >>>>> Cheers, >>>>> Ali >>>>> >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> twitter: http://twitter.com/mwessendorf >>>> >>> >>> >> >> >> -- >> >> WEI LI >> >> SENIOR SOFTWARE ENGINEER >> >> Red Hat Mobile >> >> weil at redhat.com M: +353862393272 >> >> > > -- 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/20170808/a38d42fb/attachment.html From aliok at redhat.com Tue Aug 8 05:05:14 2017 From: aliok at redhat.com (Ali Ok) Date: Tue, 8 Aug 2017 12:05:14 +0300 Subject: [aerogear-dev] AGDIGGER JIRA components In-Reply-To: References: Message-ID: :D Not enough access rights? Or, what's wrong? On Tue, Aug 8, 2017 at 11:56 AM, Matthias Wessendorf wrote: > hrm, not sure I can, actually... sorry > > On Tue, Aug 8, 2017 at 10:42 AM, Ali Ok wrote: > >> @matzew, >> >> could you do this? I guess we had enough feedback :) >> >> Cheers >> >> On Wed, Aug 2, 2017 at 11:31 AM, Wei Li wrote: >> >>> I think these components are reasonable. >>> >>> On Wed, Aug 2, 2017 at 8:44 AM, Ali Ok wrote: >>> >>>> Hi Leo and Wei, >>>> >>>> Any ideas? >>>> >>>> >>>> On Mon, Jul 31, 2017 at 10:36 AM, Matthias Wessendorf < >>>> matzew at apache.org> wrote: >>>> >>>>> sure thing! >>>>> >>>>> once we have agreed on them, I'll go ahead and update them >>>>> >>>>> On Mon, Jul 31, 2017 at 9:03 AM, Ali Ok wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I think we need to update our JIRA components in AGDIGGER project. >>>>>> >>>>>> Perhaps these: >>>>>> >>>>>> - Android support >>>>>> - IOS support >>>>>> - Ansible Installer >>>>>> - Sample (I mean sample Jenkinsfiles) >>>>>> - Node client >>>>>> - Java client >>>>>> >>>>>> Anything missing or strange? >>>>>> >>>>>> @Matthias, can you do that? >>>>>> >>>>>> Cheers, >>>>>> Ali >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matthias Wessendorf >>>>> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>> twitter: http://twitter.com/mwessendorf >>>>> >>>> >>>> >>> >>> >>> -- >>> >>> WEI LI >>> >>> SENIOR SOFTWARE ENGINEER >>> >>> Red Hat Mobile >>> >>> weil at redhat.com M: +353862393272 >>> >>> >> >> > > > -- > 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/20170808/338f7e35/attachment-0001.html From matzew at apache.org Tue Aug 8 05:54:59 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 08 Aug 2017 09:54:59 +0000 Subject: [aerogear-dev] AGDIGGER JIRA components In-Reply-To: References: Message-ID: I don't know. On Tue, 8 Aug 2017 at 11:05, Ali Ok wrote: > :D Not enough access rights? Or, what's wrong? > > On Tue, Aug 8, 2017 at 11:56 AM, Matthias Wessendorf > wrote: > >> hrm, not sure I can, actually... sorry >> >> On Tue, Aug 8, 2017 at 10:42 AM, Ali Ok wrote: >> >>> @matzew, >>> >>> could you do this? I guess we had enough feedback :) >>> >>> Cheers >>> >>> On Wed, Aug 2, 2017 at 11:31 AM, Wei Li wrote: >>> >>>> I think these components are reasonable. >>>> >>>> On Wed, Aug 2, 2017 at 8:44 AM, Ali Ok wrote: >>>> >>>>> Hi Leo and Wei, >>>>> >>>>> Any ideas? >>>>> >>>>> >>>>> On Mon, Jul 31, 2017 at 10:36 AM, Matthias Wessendorf < >>>>> matzew at apache.org> wrote: >>>>> >>>>>> sure thing! >>>>>> >>>>>> once we have agreed on them, I'll go ahead and update them >>>>>> >>>>>> On Mon, Jul 31, 2017 at 9:03 AM, Ali Ok wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I think we need to update our JIRA components in AGDIGGER project. >>>>>>> >>>>>>> Perhaps these: >>>>>>> >>>>>>> - Android support >>>>>>> - IOS support >>>>>>> - Ansible Installer >>>>>>> - Sample (I mean sample Jenkinsfiles) >>>>>>> - Node client >>>>>>> - Java client >>>>>>> >>>>>>> Anything missing or strange? >>>>>>> >>>>>>> @Matthias, can you do that? >>>>>>> >>>>>>> Cheers, >>>>>>> Ali >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Matthias Wessendorf >>>>>> >>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>> twitter: http://twitter.com/mwessendorf >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> WEI LI >>>> >>>> SENIOR SOFTWARE ENGINEER >>>> >>>> Red Hat Mobile >>>> >>>> weil at redhat.com M: +353862393272 >>>> >>>> >>> >>> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> 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/20170808/a430908c/attachment.html From dimitrazuccarelli at gmail.com Tue Aug 8 16:42:15 2017 From: dimitrazuccarelli at gmail.com (Dimitra Zuccarelli) Date: Tue, 8 Aug 2017 21:42:15 +0100 Subject: [aerogear-dev] GSoC week 11 update Message-ID: Hi guys, It's week 11 of GSoC, which means we only have about 3 weeks left until the end! Here's a quick summary of what we've been doing: * Right now I'm currently working on implementing custom object serialisers and deserialisers to give us the ability to produce whatever we want to our topics. It's been a bit of a bumpy ride so far but Matthias just did a PR which resolves some of the issues we were having with generics. We'll hopefully have this sorted by the end of the week, so we can start using it for the producers/consumers/streams that we implement. * Polina has already done AGPUSH-2159 related to our first "custom" producer but hasn't sent a PR off yet, given the aforementioned issues. She's also currently working on getting a fancier test environment up for all of our future consumers and producers :) * Since we have a very short amount of time left after that, we'll jump right into some more implementation with AGPUSH-2165 and AGPUSH-2166 , which we'll be working on in our next sprint. That's it, just wanted to update on what's going on. Thanks for the feedback and help, we always appreciate it! Dimitra -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170808/091526e4/attachment.html From matzew at apache.org Wed Aug 9 03:53:20 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 9 Aug 2017 09:53:20 +0200 Subject: [aerogear-dev] GSoC week 11 update In-Reply-To: References: Message-ID: Hey Dimitra, thanks a lot for the updates! It's really cool to see the progress on the project. Also struggles and issues are part of the job, so it's good to see you run into those, and are able to sort things ;-) Keep it up! On Tue, Aug 8, 2017 at 10:42 PM, Dimitra Zuccarelli < dimitrazuccarelli at gmail.com> wrote: > Hi guys, > > It's week 11 of GSoC, which means we only have about 3 weeks left until > the end! Here's a quick summary of what we've been doing: > > * Right now I'm currently working on implementing custom object > serialisers and deserialisers to give us the ability to produce whatever we > want to our topics. > It's been a bit of a bumpy ride so far but Matthias just did a PR > which resolves some of the > issues we were having with generics. We'll hopefully have this sorted by > the end of the week, so we can start using it for the > producers/consumers/streams that we implement. > > * Polina has already done AGPUSH-2159 > related to our first > "custom" producer but hasn't sent a PR off yet, given the aforementioned > issues. She's also currently working on getting a fancier test environment > up for all of our future consumers and producers :) > > * Since we have a very short amount of time left after that, we'll jump > right into some more implementation with AGPUSH-2165 > and AGPUSH-2166 > , which we'll be working on > in our next sprint. > > That's it, just wanted to update on what's going on. > Thanks for the feedback and help, we always appreciate it! > > Dimitra > > _______________________________________________ > 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/20170809/840471da/attachment.html From dimitrazuccarelli at gmail.com Wed Aug 9 04:35:17 2017 From: dimitrazuccarelli at gmail.com (Dimitra Zuccarelli) Date: Wed, 9 Aug 2017 09:35:17 +0100 Subject: [aerogear-dev] GSoC week 11 update In-Reply-To: References: Message-ID: Hi guys, here's the PR for the generic ser/des: https://github.com/matzew/ kafka-cdi/pull/17 As far as testing goes, there are a few issues with abstract classes obviously, and since most of the objects we'll be producing contain 'Variant' (which is an abstract class) we'll have to come up with a nice solution for that - we're open to ideas! Right now it won't work "out of the box" with Polina's PR due to the List in the PushApplication class: Caused by: com.fasterxml.jackson.databind.JsonMappingException: Can not construct instance of org.jboss.aerogear.unifiedpush.api.Variant, problem: abstract types either need to be mapped to concrete types, have custom deserializer, or be instantiated with additional type information at [Source: [B at d4163ef; line: 1, column: 229] (through reference chain: org.jboss.aerogear.unifiedpush.api.PushApplication["variants"]) Two other things: * Bad things will happen if objects of incorrect type are pushed to the same topic. This will definitely have to be addressed by enforcing some basic security (AGPUSH-2109 ) * We'll have to make sure our logs are a little more "informative" as we can't log whole objects obviously for readability. Right now, even with just two consumers, the log is quite overwhelming (i.e. consumer configs etc) On Tue, Aug 8, 2017 at 9:42 PM, Dimitra Zuccarelli < dimitrazuccarelli at gmail.com> wrote: > Hi guys, > > It's week 11 of GSoC, which means we only have about 3 weeks left until > the end! Here's a quick summary of what we've been doing: > > * Right now I'm currently working on implementing custom object > serialisers and deserialisers to give us the ability to produce whatever we > want to our topics. > It's been a bit of a bumpy ride so far but Matthias just did a PR > which resolves some of the > issues we were having with generics. We'll hopefully have this sorted by > the end of the week, so we can start using it for the > producers/consumers/streams that we implement. > > * Polina has already done AGPUSH-2159 > related to our first > "custom" producer but hasn't sent a PR off yet, given the aforementioned > issues. She's also currently working on getting a fancier test environment > up for all of our future consumers and producers :) > > * Since we have a very short amount of time left after that, we'll jump > right into some more implementation with AGPUSH-2165 > and AGPUSH-2166 > , which we'll be working on > in our next sprint. > > That's it, just wanted to update on what's going on. > Thanks for the feedback and help, we always appreciate it! > > Dimitra > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170809/d969f1b1/attachment-0001.html From matzew at apache.org Wed Aug 9 04:46:56 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 9 Aug 2017 10:46:56 +0200 Subject: [aerogear-dev] GSoC week 11 update In-Reply-To: References: Message-ID: On Wed, Aug 9, 2017 at 10:35 AM, Dimitra Zuccarelli < dimitrazuccarelli at gmail.com> wrote: > Hi guys, here's the PR for the generic ser/des: https://github.com/ > matzew/kafka-cdi/pull/17 > > As far as testing goes, there are a few issues with abstract classes > obviously, and since most of the objects we'll be producing contain > 'Variant' (which is an abstract class) we'll have to come up with a nice > solution for that - we're open to ideas! > not sure I follow :-) but why not using one of the concrete impls of it ? > > Right now it won't work "out of the box" with Polina's PR due to the > List in the PushApplication class: > > Caused by: com.fasterxml.jackson.databind.JsonMappingException: Can not > construct instance of org.jboss.aerogear.unifiedpush.api.Variant, > problem: abstract types either need to be mapped to concrete types, have > custom deserializer, or be instantiated with additional type information > > at [Source: [B at d4163ef; line: 1, column: 229] (through reference chain: > org.jboss.aerogear.unifiedpush.api.PushApplication["variants"]) > > > > do we need to define some mapping in UPS? > Two other things: > > > * Bad things will happen if objects of incorrect type are pushed to the > same topic. > when or how ? any code/pointers? > This will definitely have to be addressed by enforcing some basic security > (AGPUSH-2109 ) > > * We'll have to make sure our logs are a little more "informative" as we > can't log whole objects obviously for readability. > +1 > Right now, even with just two consumers, the log is quite overwhelming > (i.e. consumer configs etc) > we could make the kafka own logging quiet ;-) That's IMO the verbose one, which is sometimes handy. But in WildFly we could limit those to WARN/ERROR > > On Tue, Aug 8, 2017 at 9:42 PM, Dimitra Zuccarelli < > dimitrazuccarelli at gmail.com> wrote: > >> Hi guys, >> >> It's week 11 of GSoC, which means we only have about 3 weeks left until >> the end! Here's a quick summary of what we've been doing: >> >> * Right now I'm currently working on implementing custom object >> serialisers and deserialisers to give us the ability to produce whatever we >> want to our topics. >> It's been a bit of a bumpy ride so far but Matthias just did a PR >> which resolves some of the >> issues we were having with generics. We'll hopefully have this sorted by >> the end of the week, so we can start using it for the >> producers/consumers/streams that we implement. >> >> * Polina has already done AGPUSH-2159 >> related to our first >> "custom" producer but hasn't sent a PR off yet, given the aforementioned >> issues. She's also currently working on getting a fancier test environment >> up for all of our future consumers and producers :) >> >> * Since we have a very short amount of time left after that, we'll jump >> right into some more implementation with AGPUSH-2165 >> and AGPUSH-2166 >> , which we'll be working on >> in our next sprint. >> >> That's it, just wanted to update on what's going on. >> Thanks for the feedback and help, we always appreciate it! >> >> Dimitra >> > > > _______________________________________________ > 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/20170809/4c207752/attachment.html From dimitrazuccarelli at gmail.com Wed Aug 9 05:30:07 2017 From: dimitrazuccarelli at gmail.com (Dimitra Zuccarelli) Date: Wed, 9 Aug 2017 10:30:07 +0100 Subject: [aerogear-dev] GSoC week 11 update In-Reply-To: References: Message-ID: Thanks Matthias! :) On Wed, Aug 9, 2017 at 9:46 AM, Matthias Wessendorf wrote: > > > On Wed, Aug 9, 2017 at 10:35 AM, Dimitra Zuccarelli < > dimitrazuccarelli at gmail.com> wrote: > >> Hi guys, here's the PR for the generic ser/des: https://github.com/ma >> tzew/kafka-cdi/pull/17 >> >> As far as testing goes, there are a few issues with abstract classes >> obviously, and since most of the objects we'll be producing contain >> 'Variant' (which is an abstract class) we'll have to come up with a nice >> solution for that - we're open to ideas! >> > > not sure I follow :-) but why not using one of the concrete impls of it ? > Because then we'd have to define a producer/consumer for every concrete implementation, like SimpleKafkaProducer, SimpleKafkaProducer etc.. I think that would be extremely inefficient > > >> >> Right now it won't work "out of the box" with Polina's PR due to the >> List in the PushApplication class: >> >> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Can not >> construct instance of org.jboss.aerogear.unifiedpush.api.Variant, >> problem: abstract types either need to be mapped to concrete types, have >> custom deserializer, or be instantiated with additional type information >> >> at [Source: [B at d4163ef; line: 1, column: 229] (through reference chain: >> org.jboss.aerogear.unifiedpush.api.PushApplication["variants"]) >> >> >> >> > do we need to define some mapping in UPS? > What do you mean? > > >> Two other things: >> >> >> * Bad things will happen if objects of incorrect type are pushed to the >> same topic. >> > > when or how ? any code/pointers? > > >> This will definitely have to be addressed by enforcing some basic >> security (AGPUSH-2109 ) >> > > >> * We'll have to make sure our logs are a little more "informative" as we >> can't log whole objects obviously for readability. >> > +1 > > >> Right now, even with just two consumers, the log is quite overwhelming >> (i.e. consumer configs etc) >> > > we could make the kafka own logging quiet ;-) That's IMO the verbose one, > which is sometimes handy. > > But in WildFly we could limit those to WARN/ERROR > +1 It's handy for development but otherwise we should limit it I think > > >> >> On Tue, Aug 8, 2017 at 9:42 PM, Dimitra Zuccarelli < >> dimitrazuccarelli at gmail.com> wrote: >> >>> Hi guys, >>> >>> It's week 11 of GSoC, which means we only have about 3 weeks left until >>> the end! Here's a quick summary of what we've been doing: >>> >>> * Right now I'm currently working on implementing custom object >>> serialisers and deserialisers to give us the ability to produce whatever we >>> want to our topics. >>> It's been a bit of a bumpy ride so far but Matthias just did a PR >>> which resolves some of >>> the issues we were having with generics. We'll hopefully have this sorted >>> by the end of the week, so we can start using it for the >>> producers/consumers/streams that we implement. >>> >>> * Polina has already done AGPUSH-2159 >>> related to our first >>> "custom" producer but hasn't sent a PR off yet, given the aforementioned >>> issues. She's also currently working on getting a fancier test environment >>> up for all of our future consumers and producers :) >>> >>> * Since we have a very short amount of time left after that, we'll jump >>> right into some more implementation with AGPUSH-2165 >>> and AGPUSH-2166 >>> , which we'll be working >>> on in our next sprint. >>> >>> That's it, just wanted to update on what's going on. >>> Thanks for the feedback and help, we always appreciate it! >>> >>> Dimitra >>> >> >> >> _______________________________________________ >> 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/20170809/574be209/attachment-0001.html From matzew at apache.org Wed Aug 9 06:41:48 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 9 Aug 2017 12:41:48 +0200 Subject: [aerogear-dev] GSoC week 11 update In-Reply-To: References: Message-ID: On Wed, Aug 9, 2017 at 11:30 AM, Dimitra Zuccarelli < dimitrazuccarelli at gmail.com> wrote: > Thanks Matthias! :) > > > On Wed, Aug 9, 2017 at 9:46 AM, Matthias Wessendorf > wrote: > >> >> >> On Wed, Aug 9, 2017 at 10:35 AM, Dimitra Zuccarelli < >> dimitrazuccarelli at gmail.com> wrote: >> >>> Hi guys, here's the PR for the generic ser/des: https://github.com/ma >>> tzew/kafka-cdi/pull/17 >>> >>> As far as testing goes, there are a few issues with abstract classes >>> obviously, and since most of the objects we'll be producing contain >>> 'Variant' (which is an abstract class) we'll have to come up with a nice >>> solution for that - we're open to ideas! >>> >> >> not sure I follow :-) but why not using one of the concrete impls of it ? >> > > Because then we'd have to define a producer/consumer for every concrete > implementation, > how about "" ? > like SimpleKafkaProducer, > SimpleKafkaProducer etc.. I think that would be > extremely inefficient > yeah, perhaps we just route all to one topic, and use some streaming fu to dispatch them to their actual origins ? > > >> >> >>> >>> Right now it won't work "out of the box" with Polina's PR due to the >>> List in the PushApplication class: >>> >>> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Can not >>> construct instance of org.jboss.aerogear.unifiedpush.api.Variant, >>> problem: abstract types either need to be mapped to concrete types, have >>> custom deserializer, or be instantiated with additional type information >>> >>> at [Source: [B at d4163ef; line: 1, column: 229] (through reference >>> chain: org.jboss.aerogear.unifiedpush.api.PushApplication["variants"]) >>> >>> >>> >>> >> do we need to define some mapping in UPS? >> > > What do you mean? > > >> >> >>> Two other things: >>> >>> >>> * Bad things will happen if objects of incorrect type are pushed to the >>> same topic. >>> >> >> when or how ? any code/pointers? >> >> >>> This will definitely have to be addressed by enforcing some basic >>> security (AGPUSH-2109 ) >>> >> >> >>> * We'll have to make sure our logs are a little more "informative" as we >>> can't log whole objects obviously for readability. >>> >> +1 >> >> >>> Right now, even with just two consumers, the log is quite overwhelming >>> (i.e. consumer configs etc) >>> >> >> we could make the kafka own logging quiet ;-) That's IMO the verbose one, >> which is sometimes handy. >> >> But in WildFly we could limit those to WARN/ERROR >> > > +1 > It's handy for development but otherwise we should limit it I think > > >> >> >>> >>> On Tue, Aug 8, 2017 at 9:42 PM, Dimitra Zuccarelli < >>> dimitrazuccarelli at gmail.com> wrote: >>> >>>> Hi guys, >>>> >>>> It's week 11 of GSoC, which means we only have about 3 weeks left until >>>> the end! Here's a quick summary of what we've been doing: >>>> >>>> * Right now I'm currently working on implementing custom object >>>> serialisers and deserialisers to give us the ability to produce whatever we >>>> want to our topics. >>>> It's been a bit of a bumpy ride so far but Matthias just did a PR >>>> which resolves some of >>>> the issues we were having with generics. We'll hopefully have this sorted >>>> by the end of the week, so we can start using it for the >>>> producers/consumers/streams that we implement. >>>> >>>> * Polina has already done AGPUSH-2159 >>>> related to our first >>>> "custom" producer but hasn't sent a PR off yet, given the aforementioned >>>> issues. She's also currently working on getting a fancier test environment >>>> up for all of our future consumers and producers :) >>>> >>>> * Since we have a very short amount of time left after that, we'll jump >>>> right into some more implementation with AGPUSH-2165 >>>> and AGPUSH-2166 >>>> , which we'll be working >>>> on in our next sprint. >>>> >>>> That's it, just wanted to update on what's going on. >>>> Thanks for the feedback and help, we always appreciate it! >>>> >>>> Dimitra >>>> >>> >>> >>> _______________________________________________ >>> 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 >> > > > _______________________________________________ > 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/20170809/8fd7d3e0/attachment.html From matzew at apache.org Wed Aug 9 07:11:05 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 9 Aug 2017 13:11:05 +0200 Subject: [aerogear-dev] GSOC_2017_kafka branch: updates Message-ID: Hi, I've just fixed the PR from Massimo, and did land the JMS/metrics removal (and flat model) on master. Now, i;ve just rebased our GSOC_2017_kafka branch - to be on 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/20170809/becd4980/attachment.html From matzew at apache.org Wed Aug 9 12:03:54 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 9 Aug 2017 18:03:54 +0200 Subject: [aerogear-dev] UPS: FCM push and how to deal w/ "old" tokens Message-ID: Hi, in the ups we have some code, that deals w/ old, non InstanceID tokens (which do not contain a ':' char), since those are not FCM compliant, and are therefore not usable for the topic support in FCM. Currently I am looking at the tokenloader, and I see there is a bit of complexity, and odd code, that deals w/ that. While I do understand that in the 1.1.x line we wanna keep this, do we really want to keep if for the master branch ? How realistically is it, that UPS users are using a non InstanceID token? Or Android Push APIs are now over a year on the latest of Google's FCM APIs (in android/client). Do we feel OK to remove that from the master branch, at some point ? 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/20170809/c036310b/attachment-0001.html From supittma at redhat.com Wed Aug 9 13:53:29 2017 From: supittma at redhat.com (Summers Pittman) Date: Wed, 9 Aug 2017 13:53:29 -0400 Subject: [aerogear-dev] UPS: FCM push and how to deal w/ "old" tokens In-Reply-To: References: Message-ID: On Wed, Aug 9, 2017 at 12:03 PM, Matthias Wessendorf wrote: > Hi, > > in the ups we have some code, that deals w/ old, non InstanceID tokens > (which do not contain a ':' char), since those are not FCM compliant, and > are therefore not usable for the topic support in FCM. > > Currently I am looking at the tokenloader, and I see there is a bit of > complexity, and odd code, that deals w/ that. While I do understand that in > the 1.1.x line we wanna keep this, do we really want to keep if for the > master branch ? > > How realistically is it, that UPS users are using a non InstanceID token? > Or Android Push APIs are now over a year on the latest of Google's FCM APIs > (in android/client). > So it is unlikely that users of newer versions of UPS are not updating their client apps. So users using the new versions of UPS which only support FCM probably will have the FCM version of the AeroGear libraries. > Do we feel OK to remove that from the master branch, at some point ? > I think that is a reasonable idea. > > Cheers, > Matthias > > > > -- > 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/20170809/d55f52f0/attachment.html From pwright at redhat.com Fri Aug 11 06:26:07 2017 From: pwright at redhat.com (Paul Wright) Date: Fri, 11 Aug 2017 11:26:07 +0100 Subject: [aerogear-dev] Aerogear documentation navigation Message-ID: <8b4aad03-305d-f139-3a3f-490d6444abec@redhat.com> Excuse my ignorance, but I've been caught a few times by the docs navigation on aerogear.org, specifically, I click 'Docs' and then cannot find any guides: Ok, it does say this is 'API Doc and Specs' in low contrast text and there are links to 'Guides ' if I scroll to the bottom of the page, but is this how we want it to work? That's where my ignorance comes in, is there some plan here that I'm not aware of, or should I just go ahead and make a PR? thanks, Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170811/7a33f240/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2017-08-11 11-20-41.png Type: image/png Size: 100204 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170811/7a33f240/attachment-0001.png From jgallaso at redhat.com Fri Aug 11 07:14:28 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Fri, 11 Aug 2017 13:14:28 +0200 Subject: [aerogear-dev] Aerogear documentation navigation In-Reply-To: <8b4aad03-305d-f139-3a3f-490d6444abec@redhat.com> References: <8b4aad03-305d-f139-3a3f-490d6444abec@redhat.com> Message-ID: I think the problem is "Doc" means "Reference" and the actual documentation is under "getting started". But it should be more accessible, maybe we should make "Docs" a dropdown with "Reference" and "Guides" inside. JOSE MIGUEL GALLAS OLMEDO ASSOCIATE QE, mobile Red Hat M: +34618488633 On 11 August 2017 at 12:26, Paul Wright wrote: > Excuse my ignorance, but I've been caught a few times by the docs > navigation on aerogear.org, specifically, I click 'Docs' and then cannot > find any guides: > > > Ok, it does say this is 'API Doc and Specs' in low contrast text and there > are links to 'Guides ' if I > scroll to the bottom of the page, but is this how we want it to work? > > That's where my ignorance comes in, is there some plan here that I'm not > aware of, or should I just go ahead and make a PR? > > thanks, > Paul > > > > _______________________________________________ > 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/20170811/5790592d/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2017-08-11 11-20-41.png Type: image/png Size: 100204 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170811/5790592d/attachment-0001.png From matzew at apache.org Fri Aug 11 07:29:48 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 11 Aug 2017 13:29:48 +0200 Subject: [aerogear-dev] Aerogear documentation navigation In-Reply-To: <8b4aad03-305d-f139-3a3f-490d6444abec@redhat.com> References: <8b4aad03-305d-f139-3a3f-490d6444abec@redhat.com> Message-ID: Hey Paul, feel free to send a PR for this. Thx! On Fri, Aug 11, 2017 at 12:26 PM, Paul Wright wrote: > Excuse my ignorance, but I've been caught a few times by the docs > navigation on aerogear.org, specifically, I click 'Docs' and then cannot > find any guides: > > > Ok, it does say this is 'API Doc and Specs' in low contrast text and there > are links to 'Guides ' if I > scroll to the bottom of the page, but is this how we want it to work? > > That's where my ignorance comes in, is there some plan here that I'm not > aware of, or should I just go ahead and make a PR? > > thanks, > Paul > > > > _______________________________________________ > 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/20170811/d8fa0757/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2017-08-11 11-20-41.png Type: image/png Size: 100204 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170811/d8fa0757/attachment-0001.png From supittma at redhat.com Fri Aug 11 11:16:28 2017 From: supittma at redhat.com (Summers Pittman) Date: Fri, 11 Aug 2017 11:16:28 -0400 Subject: [aerogear-dev] Aerogear documentation navigation In-Reply-To: References: <8b4aad03-305d-f139-3a3f-490d6444abec@redhat.com> Message-ID: Or feel free to make suggestions, the reference docs and guides probably need a fresh critical eye anyway. On Fri, Aug 11, 2017 at 7:29 AM, Matthias Wessendorf wrote: > Hey Paul, > > feel free to send a PR for this. Thx! > > On Fri, Aug 11, 2017 at 12:26 PM, Paul Wright wrote: > >> Excuse my ignorance, but I've been caught a few times by the docs >> navigation on aerogear.org, specifically, I click 'Docs' and then cannot >> find any guides: >> >> >> Ok, it does say this is 'API Doc and Specs' in low contrast text and >> there are links to 'Guides ' if >> I scroll to the bottom of the page, but is this how we want it to work? >> >> That's where my ignorance comes in, is there some plan here that I'm not >> aware of, or should I just go ahead and make a PR? >> >> thanks, >> Paul >> >> >> >> _______________________________________________ >> 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/20170811/8115f318/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2017-08-11 11-20-41.png Type: image/png Size: 100204 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170811/8115f318/attachment-0001.png From pwright at redhat.com Mon Aug 14 05:46:44 2017 From: pwright at redhat.com (Paul Wright) Date: Mon, 14 Aug 2017 10:46:44 +0100 Subject: [aerogear-dev] Aerogear documentation navigation In-Reply-To: References: <8b4aad03-305d-f139-3a3f-490d6444abec@redhat.com> Message-ID: Thanks, I could just create a PR for this particular issue, or ... how about a refresh/doc review, and replacing jekyll with asciibinder : * Allow us publish multiple branches of docs (releases) * Allow contributors familiar with asciibinder, eg openshift contributors to contribute * Allow me sync with downstream docs in a consistent process (distros) Ok, that last one is just for me, but it should be possible to keep the aerogear look and feel, but provide a better experience for users. asciibinder is designed by red hatters for multiple distros of documentation, and is what openshift use: https://docs.openshift.com/container-platform/3.6/welcome/index.html Anyone object if we go down this road? (again, there might be unique feature of the current website that I'm not familiar with) thanks, Paul On 08/11/2017 04:16 PM, Summers Pittman wrote: > Or feel free to make suggestions, the reference docs and guides > probably need a fresh critical eye anyway. > > On Fri, Aug 11, 2017 at 7:29 AM, Matthias Wessendorf > > wrote: > > Hey Paul, > > feel free to send a PR for this. Thx! > > On Fri, Aug 11, 2017 at 12:26 PM, Paul Wright > wrote: > > Excuse my ignorance, but I've been caught a few times by the > docs navigation on aerogear.org , > specifically, I click 'Docs' and then cannot find any guides: > > > > Ok, it does say this is 'API Doc and Specs' in low contrast > text and there are links to 'Guides > ' if I scroll to the > bottom of the page, but is this how we want it to work? > > That's where my ignorance comes in, is there some plan here > that I'm not aware of, or should I just go ahead and make a PR? > > thanks, > Paul > > > > _______________________________________________ > 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 > > > > > > _______________________________________________ > 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/20170814/edc6934b/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2017-08-11 11-20-41.png Type: image/png Size: 100204 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170814/edc6934b/attachment-0001.png From dpassos at redhat.com Tue Aug 15 08:25:01 2017 From: dpassos at redhat.com (Daniel Passos) Date: Tue, 15 Aug 2017 09:25:01 -0300 Subject: [aerogear-dev] Are we maintaining Cordova? In-Reply-To: References: Message-ID: Hey Julio, Thanks for raising this one. For sure we should take some time and update/improve or Cordova plugins. I have create a Jira to track it => https://issues.jboss.org/browse/AGCORDOVA-175 On Thu, Jul 27, 2017 at 6:33 AM, Julio Cesar Sanchez Hernandez < jusanche at redhat.com> wrote: > Hi, > > I have noticed that we have 5 Cordova plugins in aerogear repo > > https://github.com/aerogear/aerogear-cordova-otp > https://github.com/aerogear/aerogear-cordova-geo > https://github.com/aerogear/aerogear-cordova-crypto > https://github.com/aerogear/aerogear-cordova-oauth2 > https://github.com/aerogear/aerogear-cordova-push > > The only one that has been updated in the last 2 years it's the push > plugin. Are we maintaining the rest of them? > > Also, there is a cookbook repo with Cordova apps, they have not been > updated in the last 2 years neither, and it has significantly less apps > than the iOS and Android cookbooks repos > https://github.com/aerogear/aerogear-cordova-cookbook > > Should we review this cookbooks and plugins to make sure they are working > with latest Cordova CLI and create a few more cookbook apps to match the > iOS and Android ones? Should we deprecate some of them if they don't make > sense anymore? > > > > _______________________________________________ > 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/20170815/f94f3e33/attachment.html From lgriffin at redhat.com Tue Aug 15 09:25:16 2017 From: lgriffin at redhat.com (Leigh Griffin) Date: Tue, 15 Aug 2017 14:25:16 +0100 Subject: [aerogear-dev] AGDIGGER JIRA components In-Reply-To: References: Message-ID: I'm a bit late with PTO but I just created the components as per your mail. If you want to add an optional description let me know, for example I put a 1 liner in to clarify what you meant by Sample! Leigh On Tue, Aug 8, 2017 at 10:54 AM, Matthias Wessendorf wrote: > I don't know. > > On Tue, 8 Aug 2017 at 11:05, Ali Ok wrote: > >> :D Not enough access rights? Or, what's wrong? >> >> On Tue, Aug 8, 2017 at 11:56 AM, Matthias Wessendorf >> wrote: >> >>> hrm, not sure I can, actually... sorry >>> >>> On Tue, Aug 8, 2017 at 10:42 AM, Ali Ok wrote: >>> >>>> @matzew, >>>> >>>> could you do this? I guess we had enough feedback :) >>>> >>>> Cheers >>>> >>>> On Wed, Aug 2, 2017 at 11:31 AM, Wei Li wrote: >>>> >>>>> I think these components are reasonable. >>>>> >>>>> On Wed, Aug 2, 2017 at 8:44 AM, Ali Ok wrote: >>>>> >>>>>> Hi Leo and Wei, >>>>>> >>>>>> Any ideas? >>>>>> >>>>>> >>>>>> On Mon, Jul 31, 2017 at 10:36 AM, Matthias Wessendorf < >>>>>> matzew at apache.org> wrote: >>>>>> >>>>>>> sure thing! >>>>>>> >>>>>>> once we have agreed on them, I'll go ahead and update them >>>>>>> >>>>>>> On Mon, Jul 31, 2017 at 9:03 AM, Ali Ok wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I think we need to update our JIRA components in AGDIGGER project. >>>>>>>> >>>>>>>> Perhaps these: >>>>>>>> >>>>>>>> - Android support >>>>>>>> - IOS support >>>>>>>> - Ansible Installer >>>>>>>> - Sample (I mean sample Jenkinsfiles) >>>>>>>> - Node client >>>>>>>> - Java client >>>>>>>> >>>>>>>> Anything missing or strange? >>>>>>>> >>>>>>>> @Matthias, can you do that? >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Ali >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Matthias Wessendorf >>>>>>> >>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> WEI LI >>>>> >>>>> SENIOR SOFTWARE ENGINEER >>>>> >>>>> Red Hat Mobile >>>>> >>>>> weil at redhat.com M: +353862393272 >>>>> >>>>> >>>> >>>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> 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 > -- LEIGH GRIFFIN ENGINEERING MANAGER, MOBILE Red Hat Ireland Communications House, Cork Road Waterford City, Ireland X91NY33 lgriffin at redhat.com M: +353877545162 IM: lgriffin TRIED. TESTED. TRUSTED. @redhatway @redhatinc @redhatsnaps -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170815/d831f8ee/attachment.html From aliok at redhat.com Wed Aug 16 02:26:29 2017 From: aliok at redhat.com (Ali Ok) Date: Wed, 16 Aug 2017 09:26:29 +0300 Subject: [aerogear-dev] AGDIGGER JIRA components In-Reply-To: References: Message-ID: Hey Leigh, Thanks a lot! Sample: Sample Jenkinsfiles and templates Could you remove these old components please? I moved all issues to other components. - abcd - digger-jenkins - Android Container Cheers On Tue, Aug 15, 2017 at 4:25 PM, Leigh Griffin wrote: > I'm a bit late with PTO but I just created the components as per your > mail. If you want to add an optional description let me know, for example I > put a 1 liner in to clarify what you meant by Sample! > > Leigh > > On Tue, Aug 8, 2017 at 10:54 AM, Matthias Wessendorf > wrote: > >> I don't know. >> >> On Tue, 8 Aug 2017 at 11:05, Ali Ok wrote: >> >>> :D Not enough access rights? Or, what's wrong? >>> >>> On Tue, Aug 8, 2017 at 11:56 AM, Matthias Wessendorf >>> wrote: >>> >>>> hrm, not sure I can, actually... sorry >>>> >>>> On Tue, Aug 8, 2017 at 10:42 AM, Ali Ok wrote: >>>> >>>>> @matzew, >>>>> >>>>> could you do this? I guess we had enough feedback :) >>>>> >>>>> Cheers >>>>> >>>>> On Wed, Aug 2, 2017 at 11:31 AM, Wei Li wrote: >>>>> >>>>>> I think these components are reasonable. >>>>>> >>>>>> On Wed, Aug 2, 2017 at 8:44 AM, Ali Ok wrote: >>>>>> >>>>>>> Hi Leo and Wei, >>>>>>> >>>>>>> Any ideas? >>>>>>> >>>>>>> >>>>>>> On Mon, Jul 31, 2017 at 10:36 AM, Matthias Wessendorf < >>>>>>> matzew at apache.org> wrote: >>>>>>> >>>>>>>> sure thing! >>>>>>>> >>>>>>>> once we have agreed on them, I'll go ahead and update them >>>>>>>> >>>>>>>> On Mon, Jul 31, 2017 at 9:03 AM, Ali Ok wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I think we need to update our JIRA components in AGDIGGER project. >>>>>>>>> >>>>>>>>> Perhaps these: >>>>>>>>> >>>>>>>>> - Android support >>>>>>>>> - IOS support >>>>>>>>> - Ansible Installer >>>>>>>>> - Sample (I mean sample Jenkinsfiles) >>>>>>>>> - Node client >>>>>>>>> - Java client >>>>>>>>> >>>>>>>>> Anything missing or strange? >>>>>>>>> >>>>>>>>> @Matthias, can you do that? >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Ali >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Matthias Wessendorf >>>>>>>> >>>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> WEI LI >>>>>> >>>>>> SENIOR SOFTWARE ENGINEER >>>>>> >>>>>> Red Hat Mobile >>>>>> >>>>>> weil at redhat.com M: +353862393272 >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> 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 >> > > > > -- > > LEIGH GRIFFIN > > ENGINEERING MANAGER, MOBILE > > Red Hat Ireland > > Communications House, Cork Road > > Waterford City, Ireland X91NY33 > > lgriffin at redhat.com M: +353877545162 IM: lgriffin > > TRIED. TESTED. TRUSTED. > > @redhatway @redhatinc > @redhatsnaps > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170816/bb5778ef/attachment-0001.html From lgriffin at redhat.com Wed Aug 16 05:01:27 2017 From: lgriffin at redhat.com (Leigh Griffin) Date: Wed, 16 Aug 2017 10:01:27 +0100 Subject: [aerogear-dev] AGDIGGER JIRA components In-Reply-To: References: Message-ID: That's updated now Ali. Leigh. On Wed, Aug 16, 2017 at 7:26 AM, Ali Ok wrote: > Hey Leigh, > > Thanks a lot! > > Sample: Sample Jenkinsfiles and templates > > Could you remove these old components please? I moved all issues to other > components. > > - abcd > - digger-jenkins > - Android Container > > Cheers > > On Tue, Aug 15, 2017 at 4:25 PM, Leigh Griffin > wrote: > >> I'm a bit late with PTO but I just created the components as per your >> mail. If you want to add an optional description let me know, for example I >> put a 1 liner in to clarify what you meant by Sample! >> >> Leigh >> >> On Tue, Aug 8, 2017 at 10:54 AM, Matthias Wessendorf >> wrote: >> >>> I don't know. >>> >>> On Tue, 8 Aug 2017 at 11:05, Ali Ok wrote: >>> >>>> :D Not enough access rights? Or, what's wrong? >>>> >>>> On Tue, Aug 8, 2017 at 11:56 AM, Matthias Wessendorf >>> > wrote: >>>> >>>>> hrm, not sure I can, actually... sorry >>>>> >>>>> On Tue, Aug 8, 2017 at 10:42 AM, Ali Ok wrote: >>>>> >>>>>> @matzew, >>>>>> >>>>>> could you do this? I guess we had enough feedback :) >>>>>> >>>>>> Cheers >>>>>> >>>>>> On Wed, Aug 2, 2017 at 11:31 AM, Wei Li wrote: >>>>>> >>>>>>> I think these components are reasonable. >>>>>>> >>>>>>> On Wed, Aug 2, 2017 at 8:44 AM, Ali Ok wrote: >>>>>>> >>>>>>>> Hi Leo and Wei, >>>>>>>> >>>>>>>> Any ideas? >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Jul 31, 2017 at 10:36 AM, Matthias Wessendorf < >>>>>>>> matzew at apache.org> wrote: >>>>>>>> >>>>>>>>> sure thing! >>>>>>>>> >>>>>>>>> once we have agreed on them, I'll go ahead and update them >>>>>>>>> >>>>>>>>> On Mon, Jul 31, 2017 at 9:03 AM, Ali Ok wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> I think we need to update our JIRA components in AGDIGGER project. >>>>>>>>>> >>>>>>>>>> Perhaps these: >>>>>>>>>> >>>>>>>>>> - Android support >>>>>>>>>> - IOS support >>>>>>>>>> - Ansible Installer >>>>>>>>>> - Sample (I mean sample Jenkinsfiles) >>>>>>>>>> - Node client >>>>>>>>>> - Java client >>>>>>>>>> >>>>>>>>>> Anything missing or strange? >>>>>>>>>> >>>>>>>>>> @Matthias, can you do that? >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Ali >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Matthias Wessendorf >>>>>>>>> >>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> WEI LI >>>>>>> >>>>>>> SENIOR SOFTWARE ENGINEER >>>>>>> >>>>>>> Red Hat Mobile >>>>>>> >>>>>>> weil at redhat.com M: +353862393272 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Matthias Wessendorf >>>>> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>> 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 >>> >> >> >> >> -- >> >> LEIGH GRIFFIN >> >> ENGINEERING MANAGER, MOBILE >> >> Red Hat Ireland >> >> Communications House, Cork Road >> >> Waterford City, Ireland X91NY33 >> >> lgriffin at redhat.com M: +353877545162 IM: lgriffin >> >> TRIED. TESTED. TRUSTED. >> >> @redhatway @redhatinc >> @redhatsnaps >> >> > > -- LEIGH GRIFFIN ENGINEERING MANAGER, MOBILE Red Hat Ireland Communications House, Cork Road Waterford City, Ireland X91NY33 lgriffin at redhat.com M: +353877545162 IM: lgriffin TRIED. TESTED. TRUSTED. @redhatway @redhatinc @redhatsnaps -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170816/b5a2412e/attachment.html From roregan at redhat.com Fri Aug 18 07:56:44 2017 From: roregan at redhat.com (Rachael O'Regan) Date: Fri, 18 Aug 2017 12:56:44 +0100 Subject: [aerogear-dev] jboss server missing/unsatisified dependencies Message-ID: Hi all, I?m having issues with the jboss server on my vm. It?s failing to start and the server log reports this error: JBAS014775: New missing/unsatisfied dependencies: service jboss.remoting.endpoint.management (missing) dependents: [service jboss.remoting.management.channel.registry] I?m using the latest fhcap and jboss-eap-6.4.15. My jboss config can be found here => https://gist.github.com/rachael-oregan/01e59e609a59a3b32fe436ada1e45c9b The server log can be found here => https://gist.github.com/rachael-oregan/ab5f268529e48c0f9fb253f82841db22 I?ve tried changing the config so remoting doesn?t use the management endpoint too - I?ve created a new vm and still getting the same error. Any help is appreciated. Thanks, RACHAEL O'REGAN Red Hat Mobile Communications House, Cork Road Waterford City, Ireland X91NY33 roregan at redhat.com IM: roregan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170818/4cc9576f/attachment-0001.html From matzew at apache.org Mon Aug 21 07:00:08 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 21 Aug 2017 13:00:08 +0200 Subject: [aerogear-dev] jboss server missing/unsatisified dependencies In-Reply-To: References: Message-ID: https://gist.github.com/rachael-oregan/ab5f268529e48c0f9fb253f82841db22#file-server-log-L104-L107 can you search inside the EAP instance if there is some mention / ref. on that "logmanager" ? On Fri, Aug 18, 2017 at 1:56 PM, Rachael O'Regan wrote: > Hi all, > > I?m having issues with the jboss server on my vm. It?s failing to start > and the server log reports this error: > > JBAS014775: New missing/unsatisfied dependencies: service > jboss.remoting.endpoint.management (missing) dependents: [service > jboss.remoting.management.channel.registry] > > I?m using the latest fhcap and jboss-eap-6.4.15. > > My jboss config can be found here => https://gist.github.com/ > rachael-oregan/01e59e609a59a3b32fe436ada1e45c9b > The server log can be found here => https://gist.github.com/ > rachael-oregan/ab5f268529e48c0f9fb253f82841db22 > > I?ve tried changing the config so remoting doesn?t use the management > endpoint too - > > I?ve created a new vm and still getting the same error. Any help is > appreciated. > > Thanks, > RACHAEL O'REGAN > Red Hat Mobile > Communications House, Cork Road > Waterford City, Ireland X91NY33 > roregan at redhat.com IM: roregan > > > _______________________________________________ > 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/20170821/a90ae621/attachment.html From matzew at apache.org Mon Aug 21 07:01:09 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 21 Aug 2017 13:01:09 +0200 Subject: [aerogear-dev] jboss server missing/unsatisified dependencies In-Reply-To: References: Message-ID: https://gist.github.com/rachael-oregan/01e59e609a59a3b32fe436ada1e45c9b#file-standalone-full-xml-L156-L158 remove that XML piece On Mon, Aug 21, 2017 at 1:00 PM, Matthias Wessendorf wrote: > https://gist.github.com/rachael-oregan/ab5f268529e48c0f9fb253f82841db > 22#file-server-log-L104-L107 > > can you search inside the EAP instance if there is some mention / ref. on > that "logmanager" ? > > On Fri, Aug 18, 2017 at 1:56 PM, Rachael O'Regan > wrote: > >> Hi all, >> >> I?m having issues with the jboss server on my vm. It?s failing to start >> and the server log reports this error: >> >> JBAS014775: New missing/unsatisfied dependencies: service >> jboss.remoting.endpoint.management (missing) dependents: [service >> jboss.remoting.management.channel.registry] >> >> I?m using the latest fhcap and jboss-eap-6.4.15. >> >> My jboss config can be found here => https://gist.github.com/rac >> hael-oregan/01e59e609a59a3b32fe436ada1e45c9b >> The server log can be found here => https://gist.github.com/rac >> hael-oregan/ab5f268529e48c0f9fb253f82841db22 >> >> I?ve tried changing the config so remoting doesn?t use the management >> endpoint too - >> >> I?ve created a new vm and still getting the same error. Any help is >> appreciated. >> >> Thanks, >> RACHAEL O'REGAN >> Red Hat Mobile >> Communications House, Cork Road >> Waterford City, Ireland X91NY33 >> roregan at redhat.com IM: roregan >> >> >> _______________________________________________ >> 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 > -- 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/20170821/b166d1b7/attachment.html From matzew at apache.org Mon Aug 21 07:02:47 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 21 Aug 2017 13:02:47 +0200 Subject: [aerogear-dev] jboss server missing/unsatisified dependencies In-Reply-To: References: Message-ID: https://gist.github.com/rachael-oregan/01e59e609a59a3b32fe436ada1e45c 9b#file-standalone-full-xml-L156-L158 remove that XML piece On Mon, Aug 21, 2017 at 1:00 PM, Matthias Wessendorf wrote: > https://gist.github.com/rachael-oregan/ab5f268529e48c0f9fb253f82841db > 22#file-server-log-L104-L107 > > can you search inside the EAP instance if there is some mention / ref. on > that "logmanager" ? > > On Fri, Aug 18, 2017 at 1:56 PM, Rachael O'Regan > wrote: > >> Hi all, >> >> I?m having issues with the jboss server on my vm. It?s failing to start >> and the server log reports this error: >> >> JBAS014775: New missing/unsatisfied dependencies: service >> jboss.remoting.endpoint.management (missing) dependents: [service >> jboss.remoting.management.channel.registry] >> >> I?m using the latest fhcap and jboss-eap-6.4.15. >> >> My jboss config can be found here => https://gist.github.com/rac >> hael-oregan/01e59e609a59a3b32fe436ada1e45c9b >> The server log can be found here => https://gist.github.com/rac >> hael-oregan/ab5f268529e48c0f9fb253f82841db22 >> >> I?ve tried changing the config so remoting doesn?t use the management >> endpoint too - >> >> I?ve created a new vm and still getting the same error. Any help is >> appreciated. >> >> Thanks, >> RACHAEL O'REGAN >> Red Hat Mobile >> Communications House, Cork Road >> Waterford City, Ireland X91NY33 >> roregan at redhat.com IM: roregan >> >> >> _______________________________________________ >> 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 > -- 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/20170821/b83d8a68/attachment.html From roregan at redhat.com Mon Aug 21 10:37:40 2017 From: roregan at redhat.com (Rachael O'Regan) Date: Mon, 21 Aug 2017 15:37:40 +0100 Subject: [aerogear-dev] jboss server missing/unsatisified dependencies In-Reply-To: References: Message-ID: <6E118EE1-6107-41E3-AE6B-5175AC65C76D@redhat.com> Hi Karel & Matthias, Thanks for your suggested solutions but unfortunately I?m still seeing the same error. I tried removing the xml code that referenced logmanager and I also tried changing the name to how it is defined in jboss/modules/system/layers/base/org/jboss/logmanager/main/module.xml which is name=?org.jboss.logmanager?. I also tried removing the xml code for logmanager and removing the data directory inside jboss/standalone. Any other suggestions? Thanks, RACHAEL O'REGAN Red Hat Mobile Communications House, Cork Road Waterford City, Ireland X91NY33 roregan at redhat.com IM: roregan > On 21 Aug 2017, at 12:01, Matthias Wessendorf wrote: > > https://gist.github.com/rachael-oregan/01e59e609a59a3b32fe436ada1e45c9b#file-standalone-full-xml-L156-L158 > > remove that XML piece > > On Mon, Aug 21, 2017 at 1:00 PM, Matthias Wessendorf > wrote: > https://gist.github.com/rachael-oregan/ab5f268529e48c0f9fb253f82841db22#file-server-log-L104-L107 > > can you search inside the EAP instance if there is some mention / ref. on that "logmanager" ? > > On Fri, Aug 18, 2017 at 1:56 PM, Rachael O'Regan > wrote: > Hi all, > > I?m having issues with the jboss server on my vm. It?s failing to start and the server log reports this error: > > JBAS014775: New missing/unsatisfied dependencies: service jboss.remoting.endpoint.management (missing) dependents: [service jboss.remoting.management.channel.registry] > > I?m using the latest fhcap and jboss-eap-6.4.15. > > My jboss config can be found here => https://gist.github.com/rachael-oregan/01e59e609a59a3b32fe436ada1e45c9b > The server log can be found here => https://gist.github.com/rachael-oregan/ab5f268529e48c0f9fb253f82841db22 > > I?ve tried changing the config so remoting doesn?t use the management endpoint too - > > I?ve created a new vm and still getting the same error. Any help is appreciated. > > Thanks, > RACHAEL O'REGAN > Red Hat Mobile > Communications House, Cork Road > Waterford City, Ireland X91NY33 > roregan at redhat.com IM: roregan > > > _______________________________________________ > 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 > > > -- > 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/20170821/593fb365/attachment-0001.html From tolisemm at gmail.com Mon Aug 21 14:15:09 2017 From: tolisemm at gmail.com (Tolis Emmanouilidis) Date: Mon, 21 Aug 2017 21:15:09 +0300 Subject: [aerogear-dev] jboss server missing/unsatisified dependencies In-Reply-To: <6E118EE1-6107-41E3-AE6B-5175AC65C76D@redhat.com> References: <6E118EE1-6107-41E3-AE6B-5175AC65C76D@redhat.com> Message-ID: Hello, Maybe you could try the opposite direction, to install the missing module. Your standalone xml is using jboss-logmanager-ext [1] module which adds extra functionality to the standard org.jboss.logmanager module pre-included by JBoss EAP. The log file mentions that the module cannot be loaded. You may install it using CLI (if your server can be started e.g on admin-only mode and then execute the CLI) or manually (if your server cannot be started). jboss-logmanager-ext could be downloaded from: https://repository.jboss.org/ nexus/service/local/repositories/releases/content/ org/jboss/logmanager/jboss-logmanager-ext/1.0.0.Alpha3/ jboss-logmanager-ext-1.0.0.Alpha3.jar CLI: batch module add --name=org.jboss.logmanager.ext --dependencies=org.jboss.logmanager,javax.json.api,javax.xml.stream.api --resources=~/your_folder_where_the_downloaded_module_exists/jboss-logmanager-ext-1.0.0.Alpha3.jar :reload run-batch Manual procedure Create the org/jboss/logmanager/ext/main folder. Add the downloaded JBoss Log Manager Ext jar inside it. Create a module.xml containing something like the following: resource-root path should refer to the version you downloaded Not sure how your filesystem looks like, if you're using a custom location for your modules or if you're using a layered distribution [1]: https://github.com/jamezp/jboss-logmanager-ext 2017-08-21 17:37 GMT+03:00 Rachael O'Regan : > Hi Karel & Matthias, > > Thanks for your suggested solutions but unfortunately I?m still seeing the > same error. I tried removing the xml code that referenced logmanager and > I also tried changing the name to how it is defined in > jboss/modules/system/layers/base/org/jboss/logmanager/main/module.xml which > is name=?org.jboss.logmanager?. I also tried removing the xml code for > logmanager and removing the data directory inside jboss/standalone. > > Any other suggestions? > > Thanks, > > RACHAEL O'REGAN > Red Hat Mobile > Communications House, Cork Road > Waterford City, Ireland X91NY33 > roregan at redhat.com IM: roregan > > On 21 Aug 2017, at 12:01, Matthias Wessendorf wrote: > > https://gist.github.com/rachael-oregan/01e59e609a59a3b32fe436ada1e45c > 9b#file-standalone-full-xml-L156-L158 > > remove that XML piece > > On Mon, Aug 21, 2017 at 1:00 PM, Matthias Wessendorf > wrote: > >> https://gist.github.com/rachael-oregan/ab5f268529e48c0f9fb25 >> 3f82841db22#file-server-log-L104-L107 >> >> can you search inside the EAP instance if there is some mention / ref. on >> that "logmanager" ? >> >> On Fri, Aug 18, 2017 at 1:56 PM, Rachael O'Regan w >> rote: >> >>> Hi all, >>> >>> I?m having issues with the jboss server on my vm. It?s failing to start >>> and the server log reports this error: >>> >>> JBAS014775: New missing/unsatisfied dependencies: service >>> jboss.remoting.endpoint.management (missing) dependents: [service >>> jboss.remoting.management.channel.registry] >>> >>> I?m using the latest fhcap and jboss-eap-6.4.15. >>> >>> My jboss config can be found here => https://gist.github.com/rac >>> hael-oregan/01e59e609a59a3b32fe436ada1e45c9b >>> The server log can be found here => https://gist.github.com/rac >>> hael-oregan/ab5f268529e48c0f9fb253f82841db22 >>> >>> I?ve tried changing the config so remoting doesn?t use the management >>> endpoint too - >>> >>> I?ve created a new vm and still getting the same error. Any help is >>> appreciated. >>> >>> Thanks, >>> RACHAEL O'REGAN >>> Red Hat Mobile >>> Communications House, Cork Road >>> Waterford City, Ireland X91NY33 >>> roregan at redhat.com IM: roregan >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > 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 > > > > _______________________________________________ > 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/20170821/b86087d4/attachment.html From matzew at apache.org Mon Aug 21 16:29:57 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 21 Aug 2017 22:29:57 +0200 Subject: [aerogear-dev] jboss server missing/unsatisified dependencies In-Reply-To: References: <6E118EE1-6107-41E3-AE6B-5175AC65C76D@redhat.com> Message-ID: that logger is not needed at all. this is a problem on the running EAP. It's not correctly configured On Mon, Aug 21, 2017 at 8:15 PM, Tolis Emmanouilidis wrote: > Hello, > > Maybe you could try the opposite direction, to install the missing module. > Your standalone xml is using jboss-logmanager-ext [1] module which adds > extra functionality to the standard org.jboss.logmanager module > pre-included by JBoss EAP. > > The log file mentions that the module cannot be loaded. You may install it > using CLI (if your server can be started e.g on admin-only mode and then > execute the CLI) or manually (if your server cannot be started). > > jboss-logmanager-ext could be downloaded from: > https://repository.jboss.org/nexus/service/local/repositorie > s/releases/content/org/jboss/logmanager/jboss-logmanager- > ext/1.0.0.Alpha3/jboss-logmanager-ext-1.0.0.Alpha3.jar > > CLI: > > batch > module add --name=org.jboss.logmanager.ext --dependencies=org.jboss.logmanager,javax.json.api,javax.xml.stream.api --resources=~/your_folder_where_the_downloaded_module_exists/jboss-logmanager-ext-1.0.0.Alpha3.jar > > :reload > run-batch > > Manual procedure > > Create the org/jboss/logmanager/ext/main folder. Add the downloaded JBoss > Log Manager Ext jar inside it. Create a module.xml containing something > like the following: > > > > > > > > > > > > > > > resource-root path should refer to the version you downloaded > Not sure how your filesystem looks like, if you're using a custom location > for your modules or if you're using a layered distribution > > [1]: https://github.com/jamezp/jboss-logmanager-ext > > 2017-08-21 17:37 GMT+03:00 Rachael O'Regan : > >> Hi Karel & Matthias, >> >> Thanks for your suggested solutions but unfortunately I?m still seeing >> the same error. I tried removing the xml code that referenced logmanager >> and I also tried changing the name to how it is defined in >> jboss/modules/system/layers/base/org/jboss/logmanager/main/module.xml which >> is name=?org.jboss.logmanager?. I also tried removing the xml code for >> logmanager and removing the data directory inside jboss/standalone. >> >> Any other suggestions? >> >> Thanks, >> >> RACHAEL O'REGAN >> Red Hat Mobile >> Communications House, Cork Road >> Waterford City, Ireland X91NY33 >> roregan at redhat.com IM: roregan >> >> On 21 Aug 2017, at 12:01, Matthias Wessendorf wrote: >> >> https://gist.github.com/rachael-oregan/01e59e609a59a3b32fe43 >> 6ada1e45c9b#file-standalone-full-xml-L156-L158 >> >> remove that XML piece >> >> On Mon, Aug 21, 2017 at 1:00 PM, Matthias Wessendorf >> wrote: >> >>> https://gist.github.com/rachael-oregan/ab5f268529e48c0f9fb25 >>> 3f82841db22#file-server-log-L104-L107 >>> >>> can you search inside the EAP instance if there is some mention / ref. >>> on that "logmanager" ? >>> >>> On Fri, Aug 18, 2017 at 1:56 PM, Rachael O'Regan w >>> rote: >>> >>>> Hi all, >>>> >>>> I?m having issues with the jboss server on my vm. It?s failing to start >>>> and the server log reports this error: >>>> >>>> JBAS014775: New missing/unsatisfied dependencies: service >>>> jboss.remoting.endpoint.management (missing) dependents: [service >>>> jboss.remoting.management.channel.registry] >>>> >>>> I?m using the latest fhcap and jboss-eap-6.4.15. >>>> >>>> My jboss config can be found here => https://gist.github.com/rac >>>> hael-oregan/01e59e609a59a3b32fe436ada1e45c9b >>>> The server log can be found here => https://gist.github.com/rac >>>> hael-oregan/ab5f268529e48c0f9fb253f82841db22 >>>> >>>> I?ve tried changing the config so remoting doesn?t use the management >>>> endpoint too - >>>> >>>> I?ve created a new vm and still getting the same error. Any help is >>>> appreciated. >>>> >>>> Thanks, >>>> RACHAEL O'REGAN >>>> Red Hat Mobile >>>> Communications House, Cork Road >>>> Waterford City, Ireland X91NY33 >>>> roregan at redhat.com IM: roregan >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> >> >> -- >> 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 >> >> >> >> _______________________________________________ >> 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/20170821/76c89efe/attachment-0001.html From polina.n.koleva at gmail.com Wed Aug 23 05:41:03 2017 From: polina.n.koleva at gmail.com (Polina Koleva) Date: Wed, 23 Aug 2017 11:41:03 +0200 Subject: [aerogear-dev] GSoC Update - a week before the end Message-ID: Hey, everyone :) It is almost the end of GSoC 2017, we have one more week left. Here is a quick summary what we have achieved since the previous update: * Dimitra has finished the implementation of custom object serialisers and deserialisers which gives us the ability to produce whatever we want to our topics. * We completely removed JMS. We are using Kafka producers, consumers and streams instead of it. So we can say that our push message epic is completely implemented. * We have our first Kafka Stream ready to be merged. See PR * We set up our test environment which gives us the ability to test consumers and producers used in UPS. See PR * The next check on our list is collecting stats for push messages using Apache Kafka.The basic idea is summarized in this epic AGPUSH-2111 . We have already come up with some proposals - AGPUSH-2187 AGPUSH-2186 AGPUSH-2188 . But we are open for new ideas. What information will be good to have in terms of stats for push messages? For example, how many push messages are sent per application? per OS? in some interval of time? Glad to hear what you think. * Also stress testing of current Kafka implementation is good to be done if enough time available. For more information, you can take a look at our dashboard here. Thanks for the support and the help. Feedback is always appreciated. Polina & Dimitra -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170823/59b07126/attachment.html From lgriffin at redhat.com Wed Aug 23 06:29:18 2017 From: lgriffin at redhat.com (Leigh Griffin) Date: Wed, 23 Aug 2017 11:29:18 +0100 Subject: [aerogear-dev] GSoC Update - a week before the end In-Reply-To: References: Message-ID: Great work and progress Polina & Dimitra. Really happy to see the progress and looking forward to seeing the wrap up of what has been a very successful and enjoyable GSoC. Well done, Leigh On Wed, Aug 23, 2017 at 10:41 AM, Polina Koleva wrote: > Hey, everyone :) > > It is almost the end of GSoC 2017, we have one more week left. Here is a > quick summary what we have achieved since the previous update: > > * Dimitra has finished the implementation of custom object serialisers > and deserialisers which gives us the ability to produce whatever we want > to our topics. > > * We completely removed JMS. We are using Kafka producers, consumers and > streams instead of it. So we can say that our push message epic > is completely implemented. > > * We have our first Kafka Stream ready to be merged. See PR > > > * We set up our test environment which gives us the ability to test > consumers and producers used in UPS. See PR > > > * The next check on our list is collecting stats for push messages using > Apache Kafka.The basic idea is summarized in this epic AGPUSH-2111 > . We have already come up > with some proposals - AGPUSH-2187 > AGPUSH-2186 > AGPUSH-2188 > . But we are open for new > ideas. What information will be good to have in terms of stats for push > messages? For example, how many push messages are sent per application? per > OS? in some interval of time? Glad to hear what you think. > > * Also stress testing of current Kafka implementation is good to be done > if enough time available. > > For more information, you can take a look at our dashboard here. > > > > Thanks for the support and the help. Feedback is always appreciated. > > Polina & Dimitra > -- LEIGH GRIFFIN ENGINEERING MANAGER, MOBILE Red Hat Ireland Communications House, Cork Road Waterford City, Ireland X91NY33 lgriffin at redhat.com M: +353877545162 IM: lgriffin TRIED. TESTED. TRUSTED. @redhatway @redhatinc @redhatsnaps -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170823/d7762f16/attachment.html From matzew at apache.org Wed Aug 23 10:52:13 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 23 Aug 2017 16:52:13 +0200 Subject: [aerogear-dev] Roadmap: UPS 1.2.0.Final and UPS.next Message-ID: Folks! GSoC is wrapping up, and Polina and Dimitra have done great work on our "GSOC_2017_kafka branch" for brining in Apache Kafka. The work will not be merged to master, and stays for a little bit longer on that branch.... == 1.2.0.Final == Our last release for the 1.2.0 series was a BETA1, in May: https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.2.0-beta.1 In order to move forward and release a 1.2.0 release to the community, I will be re-starting the looooooooooooong outstanding work to decouple UPS from our legacy Keycloak: https://issues.jboss.org/browse/AGPUSH-1047 this also helps us to be able to work on latest of WildFly, our legacy Keycloak currently is a blocker for moving towards WF11: https://issues.jboss.org/browse/AGPUSH-2117 Once that decoupling is done and complete, there will be a UPS 1.2.0.Final release, and Docker images will be updated to relay on WF11.Final (once out). == What's next ? == After that I'd like to merge the GSOC_2017_kafka branch to master, and also bump the version to 2.0.0-SNAPSHOT, since than we have Kafka integrated for the centralized messaging. Also, Docker images (and Openshift templates) will be updated - but all of that starts really _after_ the 1.2.0.Final is out. Any thoughts or comments? Thanks, 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/20170823/0eaa8e5f/attachment.html From matzew at apache.org Wed Aug 23 11:11:47 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 23 Aug 2017 17:11:47 +0200 Subject: [aerogear-dev] GSoC Update - a week before the end In-Reply-To: References: Message-ID: Also, really happy about the project. Did we agree to do a hangout-on-air on September first ? If so, I will send an invite/announce email on this list On Wed, Aug 23, 2017 at 12:29 PM, Leigh Griffin wrote: > Great work and progress Polina & Dimitra. Really happy to see the progress > and looking forward to seeing the wrap up of what has been a very > successful and enjoyable GSoC. > > Well done, > Leigh > > On Wed, Aug 23, 2017 at 10:41 AM, Polina Koleva > wrote: > >> Hey, everyone :) >> >> It is almost the end of GSoC 2017, we have one more week left. Here is a >> quick summary what we have achieved since the previous update: >> >> * Dimitra has finished the implementation of custom object serialisers >> and deserialisers which gives us the ability to produce whatever we want >> to our topics. >> >> * We completely removed JMS. We are using Kafka producers, consumers and >> streams instead of it. So we can say that our push message epic >> is completely implemented. >> >> * We have our first Kafka Stream ready to be merged. See PR >> >> >> * We set up our test environment which gives us the ability to test >> consumers and producers used in UPS. See PR >> >> >> * The next check on our list is collecting stats for push messages using >> Apache Kafka.The basic idea is summarized in this epic AGPUSH-2111 >> . We have already come up >> with some proposals - AGPUSH-2187 >> AGPUSH-2186 >> AGPUSH-2188 >> . But we are open for new >> ideas. What information will be good to have in terms of stats for push >> messages? For example, how many push messages are sent per application? per >> OS? in some interval of time? Glad to hear what you think. >> >> * Also stress testing of current Kafka implementation is good to be done >> if enough time available. >> >> For more information, you can take a look at our dashboard here. >> >> >> >> Thanks for the support and the help. Feedback is always appreciated. >> >> Polina & Dimitra >> > > > > -- > > LEIGH GRIFFIN > > ENGINEERING MANAGER, MOBILE > > Red Hat Ireland > > Communications House, Cork Road > > Waterford City, Ireland X91NY33 > > lgriffin at redhat.com M: +353877545162 IM: lgriffin > > TRIED. TESTED. TRUSTED. > > @redhatway @redhatinc > @redhatsnaps > > > _______________________________________________ > 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/20170823/882143af/attachment-0001.html From mm at napp.dk Wed Aug 23 12:05:46 2017 From: mm at napp.dk (=?iso-8859-1?Q?Mads_M=F8ller?=) Date: Wed, 23 Aug 2017 16:05:46 +0000 Subject: [aerogear-dev] Roadmap: UPS 1.2.0.Final and UPS.next In-Reply-To: References: Message-ID: Sounds like a great plan ???? MED VENLIG HILSEN / BEST REGARDS __________________ MADS M?LLER CTO, PARTNER Napp A/S T: 42 42 80 60 M: 20 28 20 26 E: mm at napp.dk W: www.napp.dk __________________ On 23 Aug 2017, at 17.55, Matthias Wessendorf > wrote: Folks! GSoC is wrapping up, and Polina and Dimitra have done great work on our "GSOC_2017_kafka branch" for brining in Apache Kafka. The work will not be merged to master, and stays for a little bit longer on that branch.... == 1.2.0.Final == Our last release for the 1.2.0 series was a BETA1, in May: https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.2.0-beta.1 In order to move forward and release a 1.2.0 release to the community, I will be re-starting the looooooooooooong outstanding work to decouple UPS from our legacy Keycloak: https://issues.jboss.org/browse/AGPUSH-1047 this also helps us to be able to work on latest of WildFly, our legacy Keycloak currently is a blocker for moving towards WF11: https://issues.jboss.org/browse/AGPUSH-2117 Once that decoupling is done and complete, there will be a UPS 1.2.0.Final release, and Docker images will be updated to relay on WF11.Final (once out). == What's next ? == After that I'd like to merge the GSOC_2017_kafka branch to master, and also bump the version to 2.0.0-SNAPSHOT, since than we have Kafka integrated for the centralized messaging. Also, Docker images (and Openshift templates) will be updated - but all of that starts really _after_ the 1.2.0.Final is out. Any thoughts or comments? Thanks, Matthias! -- 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/20170823/d4b827e8/attachment.html From lholmqui at redhat.com Wed Aug 23 13:42:26 2017 From: lholmqui at redhat.com (Luke Holmquist) Date: Wed, 23 Aug 2017 13:42:26 -0400 Subject: [aerogear-dev] Roadmap: UPS 1.2.0.Final and UPS.next In-Reply-To: References: Message-ID: On Wed, Aug 23, 2017 at 10:52 AM, Matthias Wessendorf wrote: > Folks! > > GSoC is wrapping up, and Polina and Dimitra have done great work on our > "GSOC_2017_kafka branch" for brining in Apache Kafka. The work will not be > merged to master, and stays for a little bit longer on that branch.... > > == 1.2.0.Final == > > Our last release for the 1.2.0 series was a BETA1, in May: > https://github.com/aerogear/aerogear-unifiedpush-server/ > releases/tag/1.2.0-beta.1 > > In order to move forward and release a 1.2.0 release to the community, I > will be re-starting the looooooooooooong outstanding work to decouple UPS > from our legacy Keycloak: > https://issues.jboss.org/browse/AGPUSH-1047 > YAY!!!!!!1!!!11!!! > > this also helps us to be able to work on latest of WildFly, our legacy > Keycloak currently is a blocker for moving towards WF11: > https://issues.jboss.org/browse/AGPUSH-2117 > > Once that decoupling is done and complete, there will be a UPS 1.2.0.Final > release, and Docker images will be updated to relay on WF11.Final (once > out). > > == What's next ? == > > After that I'd like to merge the GSOC_2017_kafka branch to master, and > also bump the version to 2.0.0-SNAPSHOT, since than we have Kafka > integrated for the centralized messaging. Also, Docker images (and > Openshift templates) will be updated - but all of that starts really > _after_ the 1.2.0.Final is out. > > > Any thoughts or comments? > > Thanks, Matthias! > > > -- > 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/20170823/784d710e/attachment.html From kpiwko at redhat.com Thu Aug 24 05:03:23 2017 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 24 Aug 2017 11:03:23 +0200 Subject: [aerogear-dev] Roadmap: UPS 1.2.0.Final and UPS.next In-Reply-To: References: Message-ID: On Wed, Aug 23, 2017 at 7:42 PM, Luke Holmquist wrote: > > > On Wed, Aug 23, 2017 at 10:52 AM, Matthias Wessendorf > wrote: > >> Folks! >> >> GSoC is wrapping up, and Polina and Dimitra have done great work on our >> "GSOC_2017_kafka branch" for brining in Apache Kafka. The work will not be >> merged to master, and stays for a little bit longer on that branch.... >> >> == 1.2.0.Final == >> >> Our last release for the 1.2.0 series was a BETA1, in May: >> https://github.com/aerogear/aerogear-unifiedpush-server/rele >> ases/tag/1.2.0-beta.1 >> >> In order to move forward and release a 1.2.0 release to the community, I >> will be re-starting the looooooooooooong outstanding work to decouple UPS >> from our legacy Keycloak: >> https://issues.jboss.org/browse/AGPUSH-1047 >> > > YAY!!!!!!1!!!11!!! > Well said Luke! :-) > >> this also helps us to be able to work on latest of WildFly, our legacy >> Keycloak currently is a blocker for moving towards WF11: >> https://issues.jboss.org/browse/AGPUSH-2117 >> >> Once that decoupling is done and complete, there will be a UPS >> 1.2.0.Final release, and Docker images will be updated to relay on >> WF11.Final (once out). >> >> == What's next ? == >> >> After that I'd like to merge the GSOC_2017_kafka branch to master, and >> also bump the version to 2.0.0-SNAPSHOT, since than we have Kafka >> integrated for the centralized messaging. Also, Docker images (and >> Openshift templates) will be updated - but all of that starts really >> _after_ the 1.2.0.Final is out. >> >> >> Any thoughts or comments? >> >> Thanks, Matthias! >> >> >> -- >> 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 >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- KAREL PIWKO MANAGER, MOBILE QE Red Hat Czech Republic Purky?ova 647/111 612 00 Brno, Czech Republic kpiwko at redhat.com IM: kpiwko TRIED. TESTED. TRUSTED. @redhatway @redhatinc @redhatsnaps -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170824/615cc703/attachment.html From lgriffin at redhat.com Thu Aug 24 05:22:18 2017 From: lgriffin at redhat.com (Leigh Griffin) Date: Thu, 24 Aug 2017 10:22:18 +0100 Subject: [aerogear-dev] GSoC Update - a week before the end In-Reply-To: References: Message-ID: Yup, we are going to have a public close out where Dimitra & Polina will talk about the project, what was achieved, maybe some demos and some follow on work. Can you handle the invite Matthias and we can record the session for those who cannot make it? On Wed, Aug 23, 2017 at 4:11 PM, Matthias Wessendorf wrote: > Also, really happy about the project. > > Did we agree to do a hangout-on-air on September first ? If so, I will > send an invite/announce email on this list > > On Wed, Aug 23, 2017 at 12:29 PM, Leigh Griffin > wrote: > >> Great work and progress Polina & Dimitra. Really happy to see the >> progress and looking forward to seeing the wrap up of what has been a very >> successful and enjoyable GSoC. >> >> Well done, >> Leigh >> >> On Wed, Aug 23, 2017 at 10:41 AM, Polina Koleva < >> polina.n.koleva at gmail.com> wrote: >> >>> Hey, everyone :) >>> >>> It is almost the end of GSoC 2017, we have one more week left. Here is a >>> quick summary what we have achieved since the previous update: >>> >>> * Dimitra has finished the implementation of custom object serialisers >>> and deserialisers which gives us the ability to produce whatever we >>> want to our topics. >>> >>> * We completely removed JMS. We are using Kafka producers, consumers and >>> streams instead of it. So we can say that our push message epic >>> is completely >>> implemented. >>> >>> * We have our first Kafka Stream ready to be merged. See PR >>> >>> >>> * We set up our test environment which gives us the ability to test >>> consumers and producers used in UPS. See PR >>> >>> >>> * The next check on our list is collecting stats for push messages using >>> Apache Kafka.The basic idea is summarized in this epic AGPUSH-2111 >>> . We have already come up >>> with some proposals - AGPUSH-2187 >>> AGPUSH-2186 >>> AGPUSH-2188 >>> . But we are open for new >>> ideas. What information will be good to have in terms of stats for push >>> messages? For example, how many push messages are sent per application? per >>> OS? in some interval of time? Glad to hear what you think. >>> >>> * Also stress testing of current Kafka implementation is good to be done >>> if enough time available. >>> >>> For more information, you can take a look at our dashboard here. >>> >>> >>> >>> Thanks for the support and the help. Feedback is always appreciated. >>> >>> Polina & Dimitra >>> >> >> >> >> -- >> >> LEIGH GRIFFIN >> >> ENGINEERING MANAGER, MOBILE >> >> Red Hat Ireland >> >> Communications House, Cork Road >> >> Waterford City, Ireland X91NY33 >> >> lgriffin at redhat.com M: +353877545162 IM: lgriffin >> >> TRIED. TESTED. TRUSTED. >> >> @redhatway @redhatinc >> @redhatsnaps >> >> >> _______________________________________________ >> 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 > -- LEIGH GRIFFIN ENGINEERING MANAGER, MOBILE Red Hat Ireland Communications House, Cork Road Waterford City, Ireland X91NY33 lgriffin at redhat.com M: +353877545162 IM: lgriffin TRIED. TESTED. TRUSTED. @redhatway @redhatinc @redhatsnaps -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170824/07a8b033/attachment-0001.html From mwessend at redhat.com Thu Aug 24 08:14:10 2017 From: mwessend at redhat.com (Matthias Wessendorf) Date: Thu, 24 Aug 2017 14:14:10 +0200 Subject: [aerogear-dev] GSoC Update - a week before the end In-Reply-To: References: Message-ID: yes, I can handle that. Are we all fine doing that on Friday, Sept 1st, in the afternoon ? hangout on air is recorded automatically, so it's persistent for those not able to attend :-) On Thu, Aug 24, 2017 at 11:22 AM, Leigh Griffin wrote: > Yup, we are going to have a public close out where Dimitra & Polina will > talk about the project, what was achieved, maybe some demos and some follow > on work. Can you handle the invite Matthias and we can record the session > for those who cannot make it? > > On Wed, Aug 23, 2017 at 4:11 PM, Matthias Wessendorf > wrote: > >> Also, really happy about the project. >> >> Did we agree to do a hangout-on-air on September first ? If so, I will >> send an invite/announce email on this list >> >> On Wed, Aug 23, 2017 at 12:29 PM, Leigh Griffin >> wrote: >> >>> Great work and progress Polina & Dimitra. Really happy to see the >>> progress and looking forward to seeing the wrap up of what has been a very >>> successful and enjoyable GSoC. >>> >>> Well done, >>> Leigh >>> >>> On Wed, Aug 23, 2017 at 10:41 AM, Polina Koleva < >>> polina.n.koleva at gmail.com> wrote: >>> >>>> Hey, everyone :) >>>> >>>> It is almost the end of GSoC 2017, we have one more week left. Here is >>>> a quick summary what we have achieved since the previous update: >>>> >>>> * Dimitra has finished the implementation of custom object serialisers >>>> and deserialisers which gives us the ability to produce whatever we >>>> want to our topics. >>>> >>>> * We completely removed JMS. We are using Kafka producers, consumers >>>> and streams instead of it. So we can say that our push message epic >>>> is completely >>>> implemented. >>>> >>>> * We have our first Kafka Stream ready to be merged. See PR >>>> >>>> >>>> * We set up our test environment which gives us the ability to test >>>> consumers and producers used in UPS. See PR >>>> >>>> >>>> * The next check on our list is collecting stats for push messages >>>> using Apache Kafka.The basic idea is summarized in this epic >>>> AGPUSH-2111 . We have >>>> already come up with some proposals - AGPUSH-2187 >>>> AGPUSH-2186 >>>> AGPUSH-2188 >>>> . But we are open for new >>>> ideas. What information will be good to have in terms of stats for push >>>> messages? For example, how many push messages are sent per application? per >>>> OS? in some interval of time? Glad to hear what you think. >>>> >>>> * Also stress testing of current Kafka implementation is good to be >>>> done if enough time available. >>>> >>>> For more information, you can take a look at our dashboard here. >>>> >>>> >>>> >>>> Thanks for the support and the help. Feedback is always appreciated. >>>> >>>> Polina & Dimitra >>>> >>> >>> >>> >>> -- >>> >>> LEIGH GRIFFIN >>> >>> ENGINEERING MANAGER, MOBILE >>> >>> Red Hat Ireland >>> >>> Communications House, Cork Road >>> >>> Waterford City, Ireland X91NY33 >>> >>> lgriffin at redhat.com M: +353877545162 IM: lgriffin >>> >>> TRIED. TESTED. TRUSTED. >>> >>> @redhatway @redhatinc >>> @redhatsnaps >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > > LEIGH GRIFFIN > > ENGINEERING MANAGER, MOBILE > > Red Hat Ireland > > Communications House, Cork Road > > Waterford City, Ireland X91NY33 > > lgriffin at redhat.com M: +353877545162 IM: lgriffin > > TRIED. TESTED. TRUSTED. > > @redhatway @redhatinc > @redhatsnaps > > -- Project lead AeroGear.org -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170824/dd4d5c24/attachment.html From lgriffin at redhat.com Thu Aug 24 10:22:31 2017 From: lgriffin at redhat.com (Leigh Griffin) Date: Thu, 24 Aug 2017 15:22:31 +0100 Subject: [aerogear-dev] GSoC Update - a week before the end In-Reply-To: References: Message-ID: I believe that Polina and Dimitra had previously confirmed but let us nail this down! Shall we say 14:30 UTC which should be long enough after breakfast time for US folks and not beyond office hours for EU folks. My brain won't allow me find out what that time is for others who are involved but I hope that it's ok :) On Thu, Aug 24, 2017 at 1:14 PM, Matthias Wessendorf wrote: > yes, I can handle that. > > Are we all fine doing that on Friday, Sept 1st, in the afternoon ? > > hangout on air is recorded automatically, so it's persistent for those not > able to attend :-) > > On Thu, Aug 24, 2017 at 11:22 AM, Leigh Griffin > wrote: > >> Yup, we are going to have a public close out where Dimitra & Polina will >> talk about the project, what was achieved, maybe some demos and some follow >> on work. Can you handle the invite Matthias and we can record the session >> for those who cannot make it? >> >> On Wed, Aug 23, 2017 at 4:11 PM, Matthias Wessendorf >> wrote: >> >>> Also, really happy about the project. >>> >>> Did we agree to do a hangout-on-air on September first ? If so, I will >>> send an invite/announce email on this list >>> >>> On Wed, Aug 23, 2017 at 12:29 PM, Leigh Griffin >>> wrote: >>> >>>> Great work and progress Polina & Dimitra. Really happy to see the >>>> progress and looking forward to seeing the wrap up of what has been a very >>>> successful and enjoyable GSoC. >>>> >>>> Well done, >>>> Leigh >>>> >>>> On Wed, Aug 23, 2017 at 10:41 AM, Polina Koleva < >>>> polina.n.koleva at gmail.com> wrote: >>>> >>>>> Hey, everyone :) >>>>> >>>>> It is almost the end of GSoC 2017, we have one more week left. Here is >>>>> a quick summary what we have achieved since the previous update: >>>>> >>>>> * Dimitra has finished the implementation of custom object >>>>> serialisers and deserialisers which gives us the ability to produce >>>>> whatever we want to our topics. >>>>> >>>>> * We completely removed JMS. We are using Kafka producers, consumers >>>>> and streams instead of it. So we can say that our push message epic >>>>> is completely >>>>> implemented. >>>>> >>>>> * We have our first Kafka Stream ready to be merged. See PR >>>>> >>>>> >>>>> * We set up our test environment which gives us the ability to test >>>>> consumers and producers used in UPS. See PR >>>>> >>>>> >>>>> * The next check on our list is collecting stats for push messages >>>>> using Apache Kafka.The basic idea is summarized in this epic >>>>> AGPUSH-2111 . We have >>>>> already come up with some proposals - AGPUSH-2187 >>>>> AGPUSH-2186 >>>>> AGPUSH-2188 >>>>> . But we are open for >>>>> new ideas. What information will be good to have in terms of stats for push >>>>> messages? For example, how many push messages are sent per application? per >>>>> OS? in some interval of time? Glad to hear what you think. >>>>> >>>>> * Also stress testing of current Kafka implementation is good to be >>>>> done if enough time available. >>>>> >>>>> For more information, you can take a look at our dashboard here. >>>>> >>>>> >>>>> >>>>> Thanks for the support and the help. Feedback is always appreciated. >>>>> >>>>> Polina & Dimitra >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> LEIGH GRIFFIN >>>> >>>> ENGINEERING MANAGER, MOBILE >>>> >>>> Red Hat Ireland >>>> >>>> Communications House, Cork Road >>>> >>>> Waterford City, Ireland X91NY33 >>>> >>>> lgriffin at redhat.com M: +353877545162 IM: lgriffin >>>> >>>> TRIED. TESTED. TRUSTED. >>>> >>>> @redhatway @redhatinc >>>> @redhatsnaps >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> >> >> -- >> >> LEIGH GRIFFIN >> >> ENGINEERING MANAGER, MOBILE >> >> Red Hat Ireland >> >> Communications House, Cork Road >> >> Waterford City, Ireland X91NY33 >> >> lgriffin at redhat.com M: +353877545162 IM: lgriffin >> >> TRIED. TESTED. TRUSTED. >> >> @redhatway @redhatinc >> @redhatsnaps >> >> > > > > -- > Project lead AeroGear.org > -- LEIGH GRIFFIN ENGINEERING MANAGER, MOBILE Red Hat Ireland Communications House, Cork Road Waterford City, Ireland X91NY33 lgriffin at redhat.com M: +353877545162 IM: lgriffin TRIED. TESTED. TRUSTED. @redhatway @redhatinc @redhatsnaps -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170824/90020e23/attachment-0001.html From matzew at apache.org Thu Aug 24 11:37:51 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 24 Aug 2017 17:37:51 +0200 Subject: [aerogear-dev] GSoC Update - a week before the end In-Reply-To: References: Message-ID: +1 Polina, Dimitra, please confirm if the time is right On Thu, Aug 24, 2017 at 4:22 PM, Leigh Griffin wrote: > I believe that Polina and Dimitra had previously confirmed but let us nail > this down! > > Shall we say 14:30 UTC which should be long enough after breakfast time > for US folks and not beyond office hours for EU folks. My brain won't allow > me find out what that time is for others who are involved but I hope that > it's ok :) > > On Thu, Aug 24, 2017 at 1:14 PM, Matthias Wessendorf > wrote: > >> yes, I can handle that. >> >> Are we all fine doing that on Friday, Sept 1st, in the afternoon ? >> >> hangout on air is recorded automatically, so it's persistent for those >> not able to attend :-) >> >> On Thu, Aug 24, 2017 at 11:22 AM, Leigh Griffin >> wrote: >> >>> Yup, we are going to have a public close out where Dimitra & Polina will >>> talk about the project, what was achieved, maybe some demos and some follow >>> on work. Can you handle the invite Matthias and we can record the session >>> for those who cannot make it? >>> >>> On Wed, Aug 23, 2017 at 4:11 PM, Matthias Wessendorf >>> wrote: >>> >>>> Also, really happy about the project. >>>> >>>> Did we agree to do a hangout-on-air on September first ? If so, I will >>>> send an invite/announce email on this list >>>> >>>> On Wed, Aug 23, 2017 at 12:29 PM, Leigh Griffin >>>> wrote: >>>> >>>>> Great work and progress Polina & Dimitra. Really happy to see the >>>>> progress and looking forward to seeing the wrap up of what has been a very >>>>> successful and enjoyable GSoC. >>>>> >>>>> Well done, >>>>> Leigh >>>>> >>>>> On Wed, Aug 23, 2017 at 10:41 AM, Polina Koleva < >>>>> polina.n.koleva at gmail.com> wrote: >>>>> >>>>>> Hey, everyone :) >>>>>> >>>>>> It is almost the end of GSoC 2017, we have one more week left. Here >>>>>> is a quick summary what we have achieved since the previous update: >>>>>> >>>>>> * Dimitra has finished the implementation of custom object >>>>>> serialisers and deserialisers which gives us the ability to produce >>>>>> whatever we want to our topics. >>>>>> >>>>>> * We completely removed JMS. We are using Kafka producers, consumers >>>>>> and streams instead of it. So we can say that our push message epic >>>>>> is completely >>>>>> implemented. >>>>>> >>>>>> * We have our first Kafka Stream ready to be merged. See PR >>>>>> >>>>>> >>>>>> * We set up our test environment which gives us the ability to test >>>>>> consumers and producers used in UPS. See PR >>>>>> >>>>>> >>>>>> * The next check on our list is collecting stats for push messages >>>>>> using Apache Kafka.The basic idea is summarized in this epic >>>>>> AGPUSH-2111 . We have >>>>>> already come up with some proposals - AGPUSH-2187 >>>>>> AGPUSH-2186 >>>>>> AGPUSH-2188 >>>>>> . But we are open for >>>>>> new ideas. What information will be good to have in terms of stats for push >>>>>> messages? For example, how many push messages are sent per application? per >>>>>> OS? in some interval of time? Glad to hear what you think. >>>>>> >>>>>> * Also stress testing of current Kafka implementation is good to be >>>>>> done if enough time available. >>>>>> >>>>>> For more information, you can take a look at our dashboard here. >>>>>> >>>>>> >>>>>> >>>>>> Thanks for the support and the help. Feedback is always appreciated. >>>>>> >>>>>> Polina & Dimitra >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> LEIGH GRIFFIN >>>>> >>>>> ENGINEERING MANAGER, MOBILE >>>>> >>>>> Red Hat Ireland >>>>> >>>>> Communications House, Cork Road >>>>> >>>>> Waterford City, Ireland X91NY33 >>>>> >>>>> lgriffin at redhat.com M: +353877545162 IM: lgriffin >>>>> >>>>> TRIED. TESTED. TRUSTED. >>>>> >>>>> @redhatway @redhatinc >>>>> @redhatsnaps >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>> >>> >>> >>> -- >>> >>> LEIGH GRIFFIN >>> >>> ENGINEERING MANAGER, MOBILE >>> >>> Red Hat Ireland >>> >>> Communications House, Cork Road >>> >>> Waterford City, Ireland X91NY33 >>> >>> lgriffin at redhat.com M: +353877545162 IM: lgriffin >>> >>> TRIED. TESTED. TRUSTED. >>> >>> @redhatway @redhatinc >>> @redhatsnaps >>> >>> >> >> >> >> -- >> Project lead AeroGear.org >> > > > > -- > > LEIGH GRIFFIN > > ENGINEERING MANAGER, MOBILE > > Red Hat Ireland > > Communications House, Cork Road > > Waterford City, Ireland X91NY33 > > lgriffin at redhat.com M: +353877545162 IM: lgriffin > > TRIED. TESTED. TRUSTED. > > @redhatway @redhatinc > @redhatsnaps > > > _______________________________________________ > 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/20170824/4a74ea53/attachment-0001.html From dimitrazuccarelli at gmail.com Thu Aug 24 12:02:12 2017 From: dimitrazuccarelli at gmail.com (Dimitra Zuccarelli) Date: Thu, 24 Aug 2017 17:02:12 +0100 Subject: [aerogear-dev] GSoC Update - a week before the end In-Reply-To: References: Message-ID: +1, thats good for me! On Thu, Aug 24, 2017 at 4:37 PM, Matthias Wessendorf wrote: > +1 > > Polina, Dimitra, please confirm if the time is right > > On Thu, Aug 24, 2017 at 4:22 PM, Leigh Griffin > wrote: > >> I believe that Polina and Dimitra had previously confirmed but let us >> nail this down! >> >> Shall we say 14:30 UTC which should be long enough after breakfast time >> for US folks and not beyond office hours for EU folks. My brain won't allow >> me find out what that time is for others who are involved but I hope that >> it's ok :) >> >> On Thu, Aug 24, 2017 at 1:14 PM, Matthias Wessendorf > > wrote: >> >>> yes, I can handle that. >>> >>> Are we all fine doing that on Friday, Sept 1st, in the afternoon ? >>> >>> hangout on air is recorded automatically, so it's persistent for those >>> not able to attend :-) >>> >>> On Thu, Aug 24, 2017 at 11:22 AM, Leigh Griffin >>> wrote: >>> >>>> Yup, we are going to have a public close out where Dimitra & Polina >>>> will talk about the project, what was achieved, maybe some demos and some >>>> follow on work. Can you handle the invite Matthias and we can record the >>>> session for those who cannot make it? >>>> >>>> On Wed, Aug 23, 2017 at 4:11 PM, Matthias Wessendorf >>> > wrote: >>>> >>>>> Also, really happy about the project. >>>>> >>>>> Did we agree to do a hangout-on-air on September first ? If so, I will >>>>> send an invite/announce email on this list >>>>> >>>>> On Wed, Aug 23, 2017 at 12:29 PM, Leigh Griffin >>>>> wrote: >>>>> >>>>>> Great work and progress Polina & Dimitra. Really happy to see the >>>>>> progress and looking forward to seeing the wrap up of what has been a very >>>>>> successful and enjoyable GSoC. >>>>>> >>>>>> Well done, >>>>>> Leigh >>>>>> >>>>>> On Wed, Aug 23, 2017 at 10:41 AM, Polina Koleva < >>>>>> polina.n.koleva at gmail.com> wrote: >>>>>> >>>>>>> Hey, everyone :) >>>>>>> >>>>>>> It is almost the end of GSoC 2017, we have one more week left. Here >>>>>>> is a quick summary what we have achieved since the previous update: >>>>>>> >>>>>>> * Dimitra has finished the implementation of custom object >>>>>>> serialisers and deserialisers which gives us the ability to produce >>>>>>> whatever we want to our topics. >>>>>>> >>>>>>> * We completely removed JMS. We are using Kafka producers, consumers >>>>>>> and streams instead of it. So we can say that our push message epic >>>>>>> is completely >>>>>>> implemented. >>>>>>> >>>>>>> * We have our first Kafka Stream ready to be merged. See PR >>>>>>> >>>>>>> >>>>>>> * We set up our test environment which gives us the ability to test >>>>>>> consumers and producers used in UPS. See PR >>>>>>> >>>>>>> >>>>>>> * The next check on our list is collecting stats for push messages >>>>>>> using Apache Kafka.The basic idea is summarized in this epic >>>>>>> AGPUSH-2111 . We have >>>>>>> already come up with some proposals - AGPUSH-2187 >>>>>>> AGPUSH-2186 >>>>>>> AGPUSH-2188 >>>>>>> . But we are open for >>>>>>> new ideas. What information will be good to have in terms of stats for push >>>>>>> messages? For example, how many push messages are sent per application? per >>>>>>> OS? in some interval of time? Glad to hear what you think. >>>>>>> >>>>>>> * Also stress testing of current Kafka implementation is good to be >>>>>>> done if enough time available. >>>>>>> >>>>>>> For more information, you can take a look at our dashboard here. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks for the support and the help. Feedback is always appreciated. >>>>>>> >>>>>>> Polina & Dimitra >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> LEIGH GRIFFIN >>>>>> >>>>>> ENGINEERING MANAGER, MOBILE >>>>>> >>>>>> Red Hat Ireland >>>>>> >>>>>> Communications House, Cork Road >>>>>> >>>>>> Waterford City, Ireland X91NY33 >>>>>> >>>>>> lgriffin at redhat.com M: +353877545162 IM: lgriffin >>>>>> >>>>>> TRIED. TESTED. TRUSTED. >>>>>> >>>>>> @redhatway @redhatinc >>>>>> @redhatsnaps >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> LEIGH GRIFFIN >>>> >>>> ENGINEERING MANAGER, MOBILE >>>> >>>> Red Hat Ireland >>>> >>>> Communications House, Cork Road >>>> >>>> Waterford City, Ireland X91NY33 >>>> >>>> lgriffin at redhat.com M: +353877545162 IM: lgriffin >>>> >>>> TRIED. TESTED. TRUSTED. >>>> >>>> @redhatway @redhatinc >>>> @redhatsnaps >>>> >>>> >>> >>> >>> >>> -- >>> Project lead AeroGear.org >>> >> >> >> >> -- >> >> LEIGH GRIFFIN >> >> ENGINEERING MANAGER, MOBILE >> >> Red Hat Ireland >> >> Communications House, Cork Road >> >> Waterford City, Ireland X91NY33 >> >> lgriffin at redhat.com M: +353877545162 IM: lgriffin >> >> TRIED. TESTED. TRUSTED. >> >> @redhatway @redhatinc >> @redhatsnaps >> >> >> _______________________________________________ >> 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/20170824/b6b01b6e/attachment-0001.html From matzew at apache.org Thu Aug 24 14:14:02 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 24 Aug 2017 20:14:02 +0200 Subject: [aerogear-dev] GSoC: no longer requiring the full profile Message-ID: Hi, on the GSOC branch I just verified that we can use the normal config, no need for the -full profile. See for details: https://issues.jboss.org/browse/AGPUSH-2197 -M -- 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/20170824/5e0234be/attachment.html From matzew at apache.org Thu Aug 24 14:23:09 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 24 Aug 2017 20:23:09 +0200 Subject: [aerogear-dev] GSoC: no longer requiring the full profile In-Reply-To: References: Message-ID: Of course, that's than based on Kafka ;-) But, we can move CPU power of UPS out, and move it to other "systems". That is generally something we wanted to do in a long time, a more modular system: Now that Kafka is used for messaging, we can factor out some parts into indivudial apps, that just consume records from the event stream, e.g. metrics. A standalone metrics app could publish it to what ever system etc. This GSOC branch is a good POC and the right direction for the future. On Thu, Aug 24, 2017 at 8:14 PM, Matthias Wessendorf wrote: > Hi, > > on the GSOC branch I just verified that we can use the normal config, no > need for the -full profile. > > See for details: > https://issues.jboss.org/browse/AGPUSH-2197 > > -M > > -- > 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/20170824/80ae6bc0/attachment.html From polina.n.koleva at gmail.com Thu Aug 24 15:19:00 2017 From: polina.n.koleva at gmail.com (Polina Koleva) Date: Thu, 24 Aug 2017 21:19:00 +0200 Subject: [aerogear-dev] GSoC Update - a week before the end In-Reply-To: References: Message-ID: +1 On 24 August 2017 at 17:37, Matthias Wessendorf wrote: > +1 > > Polina, Dimitra, please confirm if the time is right > > On Thu, Aug 24, 2017 at 4:22 PM, Leigh Griffin > wrote: > >> I believe that Polina and Dimitra had previously confirmed but let us >> nail this down! >> >> Shall we say 14:30 UTC which should be long enough after breakfast time >> for US folks and not beyond office hours for EU folks. My brain won't allow >> me find out what that time is for others who are involved but I hope that >> it's ok :) >> >> On Thu, Aug 24, 2017 at 1:14 PM, Matthias Wessendorf > > wrote: >> >>> yes, I can handle that. >>> >>> Are we all fine doing that on Friday, Sept 1st, in the afternoon ? >>> >>> hangout on air is recorded automatically, so it's persistent for those >>> not able to attend :-) >>> >>> On Thu, Aug 24, 2017 at 11:22 AM, Leigh Griffin >>> wrote: >>> >>>> Yup, we are going to have a public close out where Dimitra & Polina >>>> will talk about the project, what was achieved, maybe some demos and some >>>> follow on work. Can you handle the invite Matthias and we can record the >>>> session for those who cannot make it? >>>> >>>> On Wed, Aug 23, 2017 at 4:11 PM, Matthias Wessendorf >>> > wrote: >>>> >>>>> Also, really happy about the project. >>>>> >>>>> Did we agree to do a hangout-on-air on September first ? If so, I will >>>>> send an invite/announce email on this list >>>>> >>>>> On Wed, Aug 23, 2017 at 12:29 PM, Leigh Griffin >>>>> wrote: >>>>> >>>>>> Great work and progress Polina & Dimitra. Really happy to see the >>>>>> progress and looking forward to seeing the wrap up of what has been a very >>>>>> successful and enjoyable GSoC. >>>>>> >>>>>> Well done, >>>>>> Leigh >>>>>> >>>>>> On Wed, Aug 23, 2017 at 10:41 AM, Polina Koleva < >>>>>> polina.n.koleva at gmail.com> wrote: >>>>>> >>>>>>> Hey, everyone :) >>>>>>> >>>>>>> It is almost the end of GSoC 2017, we have one more week left. Here >>>>>>> is a quick summary what we have achieved since the previous update: >>>>>>> >>>>>>> * Dimitra has finished the implementation of custom object >>>>>>> serialisers and deserialisers which gives us the ability to produce >>>>>>> whatever we want to our topics. >>>>>>> >>>>>>> * We completely removed JMS. We are using Kafka producers, consumers >>>>>>> and streams instead of it. So we can say that our push message epic >>>>>>> is completely >>>>>>> implemented. >>>>>>> >>>>>>> * We have our first Kafka Stream ready to be merged. See PR >>>>>>> >>>>>>> >>>>>>> * We set up our test environment which gives us the ability to test >>>>>>> consumers and producers used in UPS. See PR >>>>>>> >>>>>>> >>>>>>> * The next check on our list is collecting stats for push messages >>>>>>> using Apache Kafka.The basic idea is summarized in this epic >>>>>>> AGPUSH-2111 . We have >>>>>>> already come up with some proposals - AGPUSH-2187 >>>>>>> AGPUSH-2186 >>>>>>> AGPUSH-2188 >>>>>>> . But we are open for >>>>>>> new ideas. What information will be good to have in terms of stats for push >>>>>>> messages? For example, how many push messages are sent per application? per >>>>>>> OS? in some interval of time? Glad to hear what you think. >>>>>>> >>>>>>> * Also stress testing of current Kafka implementation is good to be >>>>>>> done if enough time available. >>>>>>> >>>>>>> For more information, you can take a look at our dashboard here. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks for the support and the help. Feedback is always appreciated. >>>>>>> >>>>>>> Polina & Dimitra >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> LEIGH GRIFFIN >>>>>> >>>>>> ENGINEERING MANAGER, MOBILE >>>>>> >>>>>> Red Hat Ireland >>>>>> >>>>>> Communications House, Cork Road >>>>>> >>>>>> Waterford City, Ireland X91NY33 >>>>>> >>>>>> lgriffin at redhat.com M: +353877545162 IM: lgriffin >>>>>> >>>>>> TRIED. TESTED. TRUSTED. >>>>>> >>>>>> @redhatway @redhatinc >>>>>> @redhatsnaps >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> LEIGH GRIFFIN >>>> >>>> ENGINEERING MANAGER, MOBILE >>>> >>>> Red Hat Ireland >>>> >>>> Communications House, Cork Road >>>> >>>> Waterford City, Ireland X91NY33 >>>> >>>> lgriffin at redhat.com M: +353877545162 IM: lgriffin >>>> >>>> TRIED. TESTED. TRUSTED. >>>> >>>> @redhatway @redhatinc >>>> @redhatsnaps >>>> >>>> >>> >>> >>> >>> -- >>> Project lead AeroGear.org >>> >> >> >> >> -- >> >> LEIGH GRIFFIN >> >> ENGINEERING MANAGER, MOBILE >> >> Red Hat Ireland >> >> Communications House, Cork Road >> >> Waterford City, Ireland X91NY33 >> >> lgriffin at redhat.com M: +353877545162 IM: lgriffin >> >> TRIED. TESTED. TRUSTED. >> >> @redhatway @redhatinc >> @redhatsnaps >> >> >> _______________________________________________ >> 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/20170824/fe6ba4e8/attachment-0001.html From matzew at apache.org Fri Aug 25 17:18:59 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 25 Aug 2017 23:18:59 +0200 Subject: [aerogear-dev] Removing old and deprecated Push Networks ? Message-ID: Hi, we have server-side support for ADM (Amazon's Kindle Device push) as well as support for Microsofts' deprecated MPNS (Microsoft Push Notification Service) and SimplePush (from Firefox). I was wondering if we should remove those, on the master branch, going forward ? Would mean that UPS would be just supporting: * APNs (HTTP/2 only) * FCM (via HTTP only) * WNS (Windows Push Notification Services) How do folks feel about that ? Anyone actively using ADM, SimplePush or MPNS? Thanks, 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/20170825/d9f3924d/attachment.html From supittma at redhat.com Mon Aug 28 09:07:19 2017 From: supittma at redhat.com (Summers Pittman) Date: Mon, 28 Aug 2017 09:07:19 -0400 Subject: [aerogear-dev] Removing old and deprecated Push Networks ? In-Reply-To: References: Message-ID: ADM seems still maintained by Amazon, but I can't imagine it has a huge install base. So +.25 on that (+1 if it is a PITA to maintain) MPNS and SimplePush are dead as door nails. So +1 on those. On Fri, Aug 25, 2017 at 5:18 PM, Matthias Wessendorf wrote: > Hi, > > we have server-side support for ADM (Amazon's Kindle Device push) as well > as support for Microsofts' deprecated MPNS (Microsoft Push Notification > Service) and SimplePush (from Firefox). > > I was wondering if we should remove those, on the master branch, going > forward ? > > Would mean that UPS would be just supporting: > * APNs (HTTP/2 only) > * FCM (via HTTP only) > * WNS (Windows Push Notification Services) > > > How do folks feel about that ? Anyone actively using ADM, SimplePush or > MPNS? > > Thanks, > Matthias > > > -- > 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/20170828/58f355ff/attachment.html From matzew at apache.org Mon Aug 28 11:49:11 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 28 Aug 2017 17:49:11 +0200 Subject: [aerogear-dev] Removing old and deprecated Push Networks ? In-Reply-To: References: Message-ID: fair point, let's start w/ the two: https://issues.jboss.org/browse/AGPUSH-2201 On Mon, Aug 28, 2017 at 3:07 PM, Summers Pittman wrote: > ADM seems still maintained by Amazon, but I can't imagine it has a huge > install base. So +.25 on that (+1 if it is a PITA to maintain) > MPNS and SimplePush are dead as door nails. So +1 on those. > > On Fri, Aug 25, 2017 at 5:18 PM, Matthias Wessendorf > wrote: > >> Hi, >> >> we have server-side support for ADM (Amazon's Kindle Device push) as well >> as support for Microsofts' deprecated MPNS (Microsoft Push Notification >> Service) and SimplePush (from Firefox). >> >> I was wondering if we should remove those, on the master branch, going >> forward ? >> >> Would mean that UPS would be just supporting: >> * APNs (HTTP/2 only) >> * FCM (via HTTP only) >> * WNS (Windows Push Notification Services) >> >> >> How do folks feel about that ? Anyone actively using ADM, SimplePush or >> MPNS? >> >> Thanks, >> Matthias >> >> >> -- >> 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 >> > > > _______________________________________________ > 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/20170828/f8aa1180/attachment.html From idel.pivnitskiy at gmail.com Mon Aug 28 14:02:22 2017 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Mon, 28 Aug 2017 11:02:22 -0700 Subject: [aerogear-dev] Removing old and deprecated Push Networks ? In-Reply-To: References: Message-ID: Even Mozilla disabled support of SimplePush this month: https://twitter.com/MozillaWebpush/status/896095563942318080 +1 to remove it. On Mon, Aug 28, 2017 at 8:49 AM, Matthias Wessendorf wrote: > fair point, let's start w/ the two: > > https://issues.jboss.org/browse/AGPUSH-2201 > > > > On Mon, Aug 28, 2017 at 3:07 PM, Summers Pittman > wrote: > >> ADM seems still maintained by Amazon, but I can't imagine it has a huge >> install base. So +.25 on that (+1 if it is a PITA to maintain) >> MPNS and SimplePush are dead as door nails. So +1 on those. >> >> On Fri, Aug 25, 2017 at 5:18 PM, Matthias Wessendorf >> wrote: >> >>> Hi, >>> >>> we have server-side support for ADM (Amazon's Kindle Device push) as >>> well as support for Microsofts' deprecated MPNS (Microsoft Push >>> Notification Service) and SimplePush (from Firefox). >>> >>> I was wondering if we should remove those, on the master branch, going >>> forward ? >>> >>> Would mean that UPS would be just supporting: >>> * APNs (HTTP/2 only) >>> * FCM (via HTTP only) >>> * WNS (Windows Push Notification Services) >>> >>> >>> How do folks feel about that ? Anyone actively using ADM, SimplePush or >>> MPNS? >>> >>> Thanks, >>> Matthias >>> >>> >>> -- >>> 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 >>> >> >> >> _______________________________________________ >> 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/20170828/f71e8e9e/attachment.html From matzew at apache.org Mon Aug 28 15:24:19 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 28 Aug 2017 21:24:19 +0200 Subject: [aerogear-dev] Removing old and deprecated Push Networks ? In-Reply-To: References: Message-ID: Ah, great :-) thanks for the heads up :) Now even makes more sense, merging the WebPush client/integration :-) On Mon, Aug 28, 2017 at 8:02 PM, Idel Pivnitskiy wrote: > Even Mozilla disabled support of SimplePush this month: > https://twitter.com/MozillaWebpush/status/896095563942318080 > +1 to remove it. > > > On Mon, Aug 28, 2017 at 8:49 AM, Matthias Wessendorf > wrote: > >> fair point, let's start w/ the two: >> >> https://issues.jboss.org/browse/AGPUSH-2201 >> >> >> >> On Mon, Aug 28, 2017 at 3:07 PM, Summers Pittman >> wrote: >> >>> ADM seems still maintained by Amazon, but I can't imagine it has a huge >>> install base. So +.25 on that (+1 if it is a PITA to maintain) >>> MPNS and SimplePush are dead as door nails. So +1 on those. >>> >>> On Fri, Aug 25, 2017 at 5:18 PM, Matthias Wessendorf >>> wrote: >>> >>>> Hi, >>>> >>>> we have server-side support for ADM (Amazon's Kindle Device push) as >>>> well as support for Microsofts' deprecated MPNS (Microsoft Push >>>> Notification Service) and SimplePush (from Firefox). >>>> >>>> I was wondering if we should remove those, on the master branch, going >>>> forward ? >>>> >>>> Would mean that UPS would be just supporting: >>>> * APNs (HTTP/2 only) >>>> * FCM (via HTTP only) >>>> * WNS (Windows Push Notification Services) >>>> >>>> >>>> How do folks feel about that ? Anyone actively using ADM, SimplePush or >>>> MPNS? >>>> >>>> Thanks, >>>> Matthias >>>> >>>> >>>> -- >>>> 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 >>>> >>> >>> >>> _______________________________________________ >>> 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 >> > > > _______________________________________________ > 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/20170828/4a3927de/attachment-0001.html From matzew at apache.org Tue Aug 29 07:14:46 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 29 Aug 2017 13:14:46 +0200 Subject: [aerogear-dev] GSoC 2017: Student presentation, September 1st Message-ID: Hi, as you all know, Polina Koleva and Dimitra Zuccarelli were our students this year, working on a POC that brings the UPS towards Apache Kafka as its internal message bus. On September 1st, 14:30 UTC, we will do a hangout-on-air, where the students give a little presentation about their work. 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/20170829/c82077d7/attachment.html From matzew at apache.org Tue Aug 29 07:25:29 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 29 Aug 2017 13:25:29 +0200 Subject: [aerogear-dev] GSoC 2017: Student presentation, September 1st In-Reply-To: References: Message-ID: https://www.youtube.com/watch?v=sBQBGRHDWtU On Tue, Aug 29, 2017 at 1:14 PM, Matthias Wessendorf wrote: > Hi, > > as you all know, Polina Koleva and Dimitra Zuccarelli were our students > this year, working on a POC that brings the UPS towards Apache Kafka as its > internal message bus. > > On September 1st, 14:30 UTC, we will do a hangout-on-air, where the > students give a little presentation about their work. > > Cheers, > Matthias > > -- > 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/20170829/714207b8/attachment.html From matzew at apache.org Thu Aug 31 10:01:50 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 31 Aug 2017 16:01:50 +0200 Subject: [aerogear-dev] WildFly loggers for Kafka Message-ID: Hi, by default the Kafka client APIs log a lot on INFO. On IRC Polina and Dimitra were mentioning that. Here is a snippet for the "standalone.xml", to be inserted in the logging subsystem: Greetings, 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/20170831/19c94456/attachment.html From dimitrazuccarelli at gmail.com Thu Aug 31 10:52:19 2017 From: dimitrazuccarelli at gmail.com (Dimitra Zuccarelli) Date: Thu, 31 Aug 2017 15:52:19 +0100 Subject: [aerogear-dev] WildFly loggers for Kafka In-Reply-To: References: Message-ID: Great thanks! That's really helpful On Thu, Aug 31, 2017 at 3:01 PM, Matthias Wessendorf wrote: > Hi, > > by default the Kafka client APIs log a lot on INFO. On IRC Polina and > Dimitra were mentioning that. > > Here is a snippet for the "standalone.xml", to be inserted in the logging > subsystem: > > > > > > > > > > > > > > > > Greetings, > Matthias > > > -- > 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/20170831/5b66dad2/attachment.html