From matzew at apache.org  Mon Nov  2 04:35:42 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 2 Nov 2015 10:35:42 +0100
Subject: [aerogear-dev] Staging of UPS 1.1.0.Final
In-Reply-To: <CAAg5f2S_qEc1a097e-1xv=8jPs-97JKTEwCCbPh_1st1dcfpTQ@mail.gmail.com>
References: <CAD_dpu1j2=Q0mOxVzT9NUNS12S4VNC_UjMw2SKYz4ZSfcbx_pg@mail.gmail.com>
	<CAAg5f2Rc-SDjGJouKmrfm+_cq73_PMKST35dvr+wtFgpELvOKQ@mail.gmail.com>
	<CAAg5f2TW9s2x_3zRP7XymR+5P=S=PJ1fGbE9=qwxRb6Z0VAHYA@mail.gmail.com>
	<CAN+BUJqTkfXL20uF7w4LSY+WJ=Qs_7-h3PwNa74E83-HQ8F-dA@mail.gmail.com>
	<CAD_dpu2Bh6tuhcsf6q+x1tAQkK2J7erExrchQObmUPzVBKL1mg@mail.gmail.com>
	<CAEroY37GU3DqdepzKdYknVZMSE3JBAQtTqCAnkJYaBeza3WiRQ@mail.gmail.com>
	<CAEroY377W=RzqE295j0DcrQF1Uu=kW3e1rc65F-DA8-=mLQJ1Q@mail.gmail.com>
	<CAL8vO=dU46=XnebksQi7Vh3XwuTyp9_oup+nuWYv4ZzGWcB0YQ@mail.gmail.com>
	<CAEroY37TP6PFhA784iY=gQzr0FUXOgN5Jcc7gHfEPe+TvGcuYA@mail.gmail.com>
	<CAAnALH=qMzKgubUhWDZ_fcvuBbL25no4HVpMiF2=zS+gH4t1fA@mail.gmail.com>
	<CADF=h2s_x9c9CrsHX989APVetfeCfNnOR_KTJxXhAmW1rouEBQ@mail.gmail.com>
	<CAAnALH=mGJ3gauiC6Xo5E0SWAprf=Aweqxvdtmd5zLsvBTewpQ@mail.gmail.com>
	<CAAnALHkcs9Af+-ZHLOM2rvwdFg1ATPhnpYh3XDq228jeDAcm0Q@mail.gmail.com>
	<CAAg5f2RoCzLuvBxqFqL3vM_ewVivfb5cryK_ap8GGE+BM-VnKQ@mail.gmail.com>
	<CAAnALHn44SRsr5DYuN+j_ZST9hATsbkQGDSkXx=4ZDL5RX1SKw@mail.gmail.com>
	<CAAnALHmfHAU04EmM8a8ZXrhYMmQ-=qimEdEqM3u9DdQp2iS7uA@mail.gmail.com>
	<CAAg5f2SDesQFZTYG1VK7ZGBL7Gg6fW=HJGEuEq_a-8tZe2U7FQ@mail.gmail.com>
	<CAAg5f2TZ7c0bChc3SuWaFCvSBNHhAXqKUUTmy1+wNL-qn_zH4Q@mail.gmail.com>
	<CAPXQee7Uw+207y0xa0pbJ7JNvMiis-xpXXgqALUet4rMCyRMKg@mail.gmail.com>
	<CAAg5f2S_qEc1a097e-1xv=8jPs-97JKTEwCCbPh_1st1dcfpTQ@mail.gmail.com>
Message-ID: <CAAg5f2R4_nkAHaoBt_jPRwQoYyL6bq_zP7fKBnVesb13vWps4Q@mail.gmail.com>

Ok, I think it's time to move forward and finally release this version of
the UPS

On Tue, Oct 27, 2015 at 12:20 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi Karel,
>
> any thoughts about getting this release shipped ?
>
> On Thu, Oct 22, 2015 at 10:13 AM, Karel Piwko <kpiwko at redhat.com> wrote:
>
>> Thanks Matthias,
>>
>> I'll give it a try this evening and Friday morning.
>>
>> Cheers,
>>
>> Karel
>>
>> On Wed, Oct 21, 2015 at 12:57 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hey folks,
>>>
>>> here is the new URL, containing the updated 1.1.0.Final bits
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6959/
>>>
>>>
>>>
>>> On Tue, Oct 20, 2015 at 10:09 AM, Matthias Wessendorf <matzew at apache.org
>>> > wrote:
>>>
>>>> Ok,
>>>>
>>>> on it
>>>>
>>>> On Mon, Oct 19, 2015 at 4:33 PM, Lukas Fryc <lfryc at redhat.com> wrote:
>>>>
>>>>> *Unfortunately :-)
>>>>>
>>>>> On Mon, Oct 19, 2015 at 4:25 PM, Lukas Fryc <lfryc at redhat.com> wrote:
>>>>>
>>>>>> Yes, that was the plan. Fortunately we haven't hit AGPUSH-1513 until
>>>>>> we deployed to OpenShift, there is is especially apparent.
>>>>>>
>>>>>> On Mon, Oct 19, 2015 at 3:14 PM, Matthias Wessendorf <
>>>>>> matzew at apache.org> wrote:
>>>>>>
>>>>>>> so, that mean we skip the staged 1.1.0? and will do a re-staging,
>>>>>>> that includes the fixes?
>>>>>>>
>>>>>>> I'd say so ...
>>>>>>>
>>>>>>> On Mon, Oct 19, 2015 at 3:03 PM, Lukas Fryc <lfryc at redhat.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Here are aforementioned patches, could you please take a look?
>>>>>>>>
>>>>>>>> AGPUSH-1513 UPS Console shows Pending - because servedVariants <
>>>>>>>> totalVariants
>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/636
>>>>>>>>
>>>>>>>> AGPUSH-1516 Change AerogearLogger to use fully-qualified class
>>>>>>>> names instead of simple class names
>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/637
>>>>>>>>
>>>>>>>> AGCORDOVA-120 NullReferenceException when delivering message to WP8
>>>>>>>> app on foreground
>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/638
>>>>>>>> https://github.com/aerogear/aerogear.org/pull/613
>>>>>>>> https://github.com/aerogear/aerogear-cordova-push/pull/80
>>>>>>>>
>>>>>>>> ~ Lukas
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Oct 5, 2015 at 5:38 PM, Lukas Fryc <lfryc at redhat.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi guys,
>>>>>>>>>
>>>>>>>>> Ad) 1.1.0 RELEASE
>>>>>>>>>
>>>>>>>>> we have agreed with Sebi to restage 1.1.0 including these fixes:
>>>>>>>>>
>>>>>>>>> AGPUSH-1513 UPS Console shows Pending - because servedVariants <
>>>>>>>>> totalVariants
>>>>>>>>> AGPUSH-1516 Change AerogearLogger to use fully-qualified class
>>>>>>>>> names instead of simple class names
>>>>>>>>> AGCORDOVA-120 NullReferenceException when delivering message to
>>>>>>>>> WP8 app on foreground
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I will create release-1.1.0 branch so we can continue developing /
>>>>>>>>> merging changes into master for version 1.1.x.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Ad) TRIAGE
>>>>>>>>>
>>>>>>>>> We also did a triage of 1.1.x issues, resulting into 2 versions:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 1.1.1: critical fixes & small UX improvements
>>>>>>>>>
>>>>>>>>> https://issues.jboss.org/projects/AGPUSH/versions/12327457
>>>>>>>>>
>>>>>>>>> 1.1.x: other minor improvements for 1.1 that can wait for later
>>>>>>>>> releases
>>>>>>>>>
>>>>>>>>> https://issues.jboss.org/projects/AGPUSH/versions/12323762
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Cheers!
>>>>>>>>>
>>>>>>>>> ~ Lukas
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, Oct 2, 2015 at 2:05 PM, Daniel Passos <dpassos at redhat.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I've finished my tests to native Android and everything works
>>>>>>>>>> perfect.
>>>>>>>>>>
>>>>>>>>>> On Fri, Oct 2, 2015 at 4:29 AM, Lukas Fryc <lfryc at redhat.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> I've finished my testing - Cordova apps on Android, iOS and WP8
>>>>>>>>>>> against OpenShift 1.1.0.Final deployment and found these issues:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> https://issues.jboss.org/issues/?jql=reporter%3Dlfryc%20AND%20project%20IN%20(AGPUSH%2C%20AGCORDOVA)%20AND%20created%20%3E%3D%20'2015-09-28'%20and%20created%20%3C%3D%20'2015-10-03
>>>>>>>>>>> '
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Oct 1, 2015 at 2:43 PM, Luk?? Fry? <lukas.fryc at gmail.com
>>>>>>>>>>> > wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Thanks Corinne, I forgot about it, tbh I didn't think about it
>>>>>>>>>>>> as 1.1.0.Final issue, but yea, it is probably linked to it :-)
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Oct 1, 2015 at 10:20 AM, Corinne Krych <
>>>>>>>>>>>> corinnekrych at gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks Lukas,
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Cordova iOS side you also discovered the enable_bitcode
>>>>>>>>>>>>> issue which is fixed by this PR [1].
>>>>>>>>>>>>> Interesting Cordova is working on making the default project
>>>>>>>>>>>>> set-up with ENABLE_BITCODE=No [2] which is less restrictive (no need to
>>>>>>>>>>>>> have all dependent lib built with bitcode enabled).
>>>>>>>>>>>>>
>>>>>>>>>>>>> ++
>>>>>>>>>>>>> Corinne
>>>>>>>>>>>>>
>>>>>>>>>>>>> [1] https://github.com/aerogear/aerogear-cordova-push/pull/79
>>>>>>>>>>>>> [2]
>>>>>>>>>>>>> https://github.com/apache/cordova-ios/commit/ca07a7153e2afd6e5a1239806151c69d80758245
>>>>>>>>>>>>> https://issues.apache.org/jira/browse/CB-9721
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 1 October 2015 at 09:34, Luk?? Fry? <lukas.fryc at gmail.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hey guys,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I was testing iOS and Android devices against OpenShift
>>>>>>>>>>>>>> 1.1.0.Final deployment,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I discovered few issues:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>    -
>>>>>>>>>>>>>>    - Activity log - shows pending AGPUSH-1513
>>>>>>>>>>>>>>    <https://issues.jboss.org/browse/AGPUSH-1513>
>>>>>>>>>>>>>>    - Windows Phone 8 / Cordova app - shows Registering, but
>>>>>>>>>>>>>>    never registers (still debugging this, may be something wrong with my setup)
>>>>>>>>>>>>>>    - UX improvement: when switching to Analytics, the data
>>>>>>>>>>>>>>    aren?t loaded and shows No Data blank slate
>>>>>>>>>>>>>>    - debugging improvement: enable fully qualified names in
>>>>>>>>>>>>>>    debug log: FINE  [NotificationDispatcher] -> FINE
>>>>>>>>>>>>>>    [org.jboss.aerogear....NotificationDispatcher]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> >From the mentioned issues only AGPUSH-1513 is considered a
>>>>>>>>>>>>>> blocker,
>>>>>>>>>>>>>> we have agreed with Sebi to restage 1.1.0 with AGPUSH-1513
>>>>>>>>>>>>>> and then implement AGPUSH-1512 in 1.1.1.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ~ Lukas
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Sep 29, 2015 at 7:56 AM, Luk?? Fry? <
>>>>>>>>>>>>>> lukas.fryc at gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Don't ship yet, I'm taking look today :-)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, Sep 23, 2015 at 3:44 PM, Sebastien Blanc <
>>>>>>>>>>>>>>> scm.blanc at gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> As anyone done any tests for this really important release,
>>>>>>>>>>>>>>>> it has been staging now for more than 2 weeks ?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Sep 8, 2015 at 2:12 PM, Idel Pivnitskiy <
>>>>>>>>>>>>>>>> idel.pivnitskiy at gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Done:
>>>>>>>>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/633
>>>>>>>>>>>>>>>>> It would be great if someone will check the whole API
>>>>>>>>>>>>>>>>> documentation. Hope it doesn't have typos or other problems.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Best regards,
>>>>>>>>>>>>>>>>> Idel Pivnitskiy
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com
>>>>>>>>>>>>>>>>> Twitter: @idelpivnitskiy
>>>>>>>>>>>>>>>>> <https://twitter.com/idelpivnitskiy>
>>>>>>>>>>>>>>>>> GitHub: @idelpivnitskiy
>>>>>>>>>>>>>>>>> <https://github.com/idelpivnitskiy>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Sep 8, 2015 at 3:11 PM, Matthias Wessendorf <
>>>>>>>>>>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> here is the OpenShift PR:
>>>>>>>>>>>>>>>>>> https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/22
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> -Matthias
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Sep 8, 2015 at 11:17 AM, Matthias Wessendorf <
>>>>>>>>>>>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> alright, thanks!
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I will do the OpenShift updates, based on the git tag
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tue, Sep 8, 2015 at 11:15 AM, Sebastien Blanc <
>>>>>>>>>>>>>>>>>>> scm.blanc at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Hi team,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I'm happy to announce that UPS 1.1.0 Final has been
>>>>>>>>>>>>>>>>>>>> staged.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Please test the staged release :
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6516
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> By the end of the week I'd like to press the button to
>>>>>>>>>>>>>>>>>>>> release it to the wild.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Sebi
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> ps : the openshift update will follow
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Matthias Wessendorf
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>>>>>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>>>>>>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Matthias Wessendorf
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>>>>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>>>>>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Luk?? Fry?
>>>>>>>>>>> Software Engineer
>>>>>>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> -- Passos
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Luk?? Fry?
>>>>>>>>> Software Engineer
>>>>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Luk?? Fry?
>>>>>>>> Software Engineer
>>>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Matthias Wessendorf
>>>>>>>
>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Luk?? Fry?
>>>>>> Software Engineer
>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Luk?? Fry?
>>>>> Software Engineer
>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151102/3de8e8f5/attachment-0001.html 

From kpiwko at redhat.com  Mon Nov  2 05:06:18 2015
From: kpiwko at redhat.com (Karel Piwko)
Date: Mon, 2 Nov 2015 11:06:18 +0100
Subject: [aerogear-dev] Staging of UPS 1.1.0.Final
In-Reply-To: <CAAg5f2R4_nkAHaoBt_jPRwQoYyL6bq_zP7fKBnVesb13vWps4Q@mail.gmail.com>
References: <CAD_dpu1j2=Q0mOxVzT9NUNS12S4VNC_UjMw2SKYz4ZSfcbx_pg@mail.gmail.com>
	<CAAg5f2Rc-SDjGJouKmrfm+_cq73_PMKST35dvr+wtFgpELvOKQ@mail.gmail.com>
	<CAAg5f2TW9s2x_3zRP7XymR+5P=S=PJ1fGbE9=qwxRb6Z0VAHYA@mail.gmail.com>
	<CAN+BUJqTkfXL20uF7w4LSY+WJ=Qs_7-h3PwNa74E83-HQ8F-dA@mail.gmail.com>
	<CAD_dpu2Bh6tuhcsf6q+x1tAQkK2J7erExrchQObmUPzVBKL1mg@mail.gmail.com>
	<CAEroY37GU3DqdepzKdYknVZMSE3JBAQtTqCAnkJYaBeza3WiRQ@mail.gmail.com>
	<CAEroY377W=RzqE295j0DcrQF1Uu=kW3e1rc65F-DA8-=mLQJ1Q@mail.gmail.com>
	<CAL8vO=dU46=XnebksQi7Vh3XwuTyp9_oup+nuWYv4ZzGWcB0YQ@mail.gmail.com>
	<CAEroY37TP6PFhA784iY=gQzr0FUXOgN5Jcc7gHfEPe+TvGcuYA@mail.gmail.com>
	<CAAnALH=qMzKgubUhWDZ_fcvuBbL25no4HVpMiF2=zS+gH4t1fA@mail.gmail.com>
	<CADF=h2s_x9c9CrsHX989APVetfeCfNnOR_KTJxXhAmW1rouEBQ@mail.gmail.com>
	<CAAnALH=mGJ3gauiC6Xo5E0SWAprf=Aweqxvdtmd5zLsvBTewpQ@mail.gmail.com>
	<CAAnALHkcs9Af+-ZHLOM2rvwdFg1ATPhnpYh3XDq228jeDAcm0Q@mail.gmail.com>
	<CAAg5f2RoCzLuvBxqFqL3vM_ewVivfb5cryK_ap8GGE+BM-VnKQ@mail.gmail.com>
	<CAAnALHn44SRsr5DYuN+j_ZST9hATsbkQGDSkXx=4ZDL5RX1SKw@mail.gmail.com>
	<CAAnALHmfHAU04EmM8a8ZXrhYMmQ-=qimEdEqM3u9DdQp2iS7uA@mail.gmail.com>
	<CAAg5f2SDesQFZTYG1VK7ZGBL7Gg6fW=HJGEuEq_a-8tZe2U7FQ@mail.gmail.com>
	<CAAg5f2TZ7c0bChc3SuWaFCvSBNHhAXqKUUTmy1+wNL-qn_zH4Q@mail.gmail.com>
	<CAPXQee7Uw+207y0xa0pbJ7JNvMiis-xpXXgqALUet4rMCyRMKg@mail.gmail.com>
	<CAAg5f2S_qEc1a097e-1xv=8jPs-97JKTEwCCbPh_1st1dcfpTQ@mail.gmail.com>
	<CAAg5f2R4_nkAHaoBt_jPRwQoYyL6bq_zP7fKBnVesb13vWps4Q@mail.gmail.com>
Message-ID: <CAPXQee57naSqzcvajzvVtnSbPPFijfe46FTt7SQVyX2-1aFezg@mail.gmail.com>

Hello Matthias,

I did a quick sanity check on Friday and I've found just minor issues
related to stale aerogear.org pages. They are in AEROGEAR jira.

Ship it!

Cheers,

Karel

On Mon, Nov 2, 2015 at 10:35 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Ok, I think it's time to move forward and finally release this version of
> the UPS
>
> On Tue, Oct 27, 2015 at 12:20 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi Karel,
>>
>> any thoughts about getting this release shipped ?
>>
>> On Thu, Oct 22, 2015 at 10:13 AM, Karel Piwko <kpiwko at redhat.com> wrote:
>>
>>> Thanks Matthias,
>>>
>>> I'll give it a try this evening and Friday morning.
>>>
>>> Cheers,
>>>
>>> Karel
>>>
>>> On Wed, Oct 21, 2015 at 12:57 PM, Matthias Wessendorf <matzew at apache.org
>>> > wrote:
>>>
>>>> Hey folks,
>>>>
>>>> here is the new URL, containing the updated 1.1.0.Final bits
>>>>
>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6959/
>>>>
>>>>
>>>>
>>>> On Tue, Oct 20, 2015 at 10:09 AM, Matthias Wessendorf <
>>>> matzew at apache.org> wrote:
>>>>
>>>>> Ok,
>>>>>
>>>>> on it
>>>>>
>>>>> On Mon, Oct 19, 2015 at 4:33 PM, Lukas Fryc <lfryc at redhat.com> wrote:
>>>>>
>>>>>> *Unfortunately :-)
>>>>>>
>>>>>> On Mon, Oct 19, 2015 at 4:25 PM, Lukas Fryc <lfryc at redhat.com> wrote:
>>>>>>
>>>>>>> Yes, that was the plan. Fortunately we haven't hit AGPUSH-1513 until
>>>>>>> we deployed to OpenShift, there is is especially apparent.
>>>>>>>
>>>>>>> On Mon, Oct 19, 2015 at 3:14 PM, Matthias Wessendorf <
>>>>>>> matzew at apache.org> wrote:
>>>>>>>
>>>>>>>> so, that mean we skip the staged 1.1.0? and will do a re-staging,
>>>>>>>> that includes the fixes?
>>>>>>>>
>>>>>>>> I'd say so ...
>>>>>>>>
>>>>>>>> On Mon, Oct 19, 2015 at 3:03 PM, Lukas Fryc <lfryc at redhat.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Here are aforementioned patches, could you please take a look?
>>>>>>>>>
>>>>>>>>> AGPUSH-1513 UPS Console shows Pending - because servedVariants <
>>>>>>>>> totalVariants
>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/636
>>>>>>>>>
>>>>>>>>> AGPUSH-1516 Change AerogearLogger to use fully-qualified class
>>>>>>>>> names instead of simple class names
>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/637
>>>>>>>>>
>>>>>>>>> AGCORDOVA-120 NullReferenceException when delivering message to
>>>>>>>>> WP8 app on foreground
>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/638
>>>>>>>>> https://github.com/aerogear/aerogear.org/pull/613
>>>>>>>>> https://github.com/aerogear/aerogear-cordova-push/pull/80
>>>>>>>>>
>>>>>>>>> ~ Lukas
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Oct 5, 2015 at 5:38 PM, Lukas Fryc <lfryc at redhat.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi guys,
>>>>>>>>>>
>>>>>>>>>> Ad) 1.1.0 RELEASE
>>>>>>>>>>
>>>>>>>>>> we have agreed with Sebi to restage 1.1.0 including these fixes:
>>>>>>>>>>
>>>>>>>>>> AGPUSH-1513 UPS Console shows Pending - because servedVariants <
>>>>>>>>>> totalVariants
>>>>>>>>>> AGPUSH-1516 Change AerogearLogger to use fully-qualified class
>>>>>>>>>> names instead of simple class names
>>>>>>>>>> AGCORDOVA-120 NullReferenceException when delivering message to
>>>>>>>>>> WP8 app on foreground
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I will create release-1.1.0 branch so we can continue developing
>>>>>>>>>> / merging changes into master for version 1.1.x.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Ad) TRIAGE
>>>>>>>>>>
>>>>>>>>>> We also did a triage of 1.1.x issues, resulting into 2 versions:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 1.1.1: critical fixes & small UX improvements
>>>>>>>>>>
>>>>>>>>>> https://issues.jboss.org/projects/AGPUSH/versions/12327457
>>>>>>>>>>
>>>>>>>>>> 1.1.x: other minor improvements for 1.1 that can wait for later
>>>>>>>>>> releases
>>>>>>>>>>
>>>>>>>>>> https://issues.jboss.org/projects/AGPUSH/versions/12323762
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Cheers!
>>>>>>>>>>
>>>>>>>>>> ~ Lukas
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Fri, Oct 2, 2015 at 2:05 PM, Daniel Passos <dpassos at redhat.com
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> I've finished my tests to native Android and everything works
>>>>>>>>>>> perfect.
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Oct 2, 2015 at 4:29 AM, Lukas Fryc <lfryc at redhat.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I've finished my testing - Cordova apps on Android, iOS and WP8
>>>>>>>>>>>> against OpenShift 1.1.0.Final deployment and found these issues:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> https://issues.jboss.org/issues/?jql=reporter%3Dlfryc%20AND%20project%20IN%20(AGPUSH%2C%20AGCORDOVA)%20AND%20created%20%3E%3D%20'2015-09-28'%20and%20created%20%3C%3D%20'2015-10-03
>>>>>>>>>>>> '
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Oct 1, 2015 at 2:43 PM, Luk?? Fry? <
>>>>>>>>>>>> lukas.fryc at gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks Corinne, I forgot about it, tbh I didn't think about it
>>>>>>>>>>>>> as 1.1.0.Final issue, but yea, it is probably linked to it :-)
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Oct 1, 2015 at 10:20 AM, Corinne Krych <
>>>>>>>>>>>>> corinnekrych at gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks Lukas,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Cordova iOS side you also discovered the enable_bitcode
>>>>>>>>>>>>>> issue which is fixed by this PR [1].
>>>>>>>>>>>>>> Interesting Cordova is working on making the default project
>>>>>>>>>>>>>> set-up with ENABLE_BITCODE=No [2] which is less restrictive (no need to
>>>>>>>>>>>>>> have all dependent lib built with bitcode enabled).
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ++
>>>>>>>>>>>>>> Corinne
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [1] https://github.com/aerogear/aerogear-cordova-push/pull/79
>>>>>>>>>>>>>> [2]
>>>>>>>>>>>>>> https://github.com/apache/cordova-ios/commit/ca07a7153e2afd6e5a1239806151c69d80758245
>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/CB-9721
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 1 October 2015 at 09:34, Luk?? Fry? <lukas.fryc at gmail.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hey guys,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I was testing iOS and Android devices against OpenShift
>>>>>>>>>>>>>>> 1.1.0.Final deployment,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I discovered few issues:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>    -
>>>>>>>>>>>>>>>    - Activity log - shows pending AGPUSH-1513
>>>>>>>>>>>>>>>    <https://issues.jboss.org/browse/AGPUSH-1513>
>>>>>>>>>>>>>>>    - Windows Phone 8 / Cordova app - shows Registering, but
>>>>>>>>>>>>>>>    never registers (still debugging this, may be something wrong with my setup)
>>>>>>>>>>>>>>>    - UX improvement: when switching to Analytics, the data
>>>>>>>>>>>>>>>    aren?t loaded and shows No Data blank slate
>>>>>>>>>>>>>>>    - debugging improvement: enable fully qualified names in
>>>>>>>>>>>>>>>    debug log: FINE  [NotificationDispatcher] -> FINE
>>>>>>>>>>>>>>>    [org.jboss.aerogear....NotificationDispatcher]
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> >From the mentioned issues only AGPUSH-1513 is considered a
>>>>>>>>>>>>>>> blocker,
>>>>>>>>>>>>>>> we have agreed with Sebi to restage 1.1.0 with AGPUSH-1513
>>>>>>>>>>>>>>> and then implement AGPUSH-1512 in 1.1.1.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ~ Lukas
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Sep 29, 2015 at 7:56 AM, Luk?? Fry? <
>>>>>>>>>>>>>>> lukas.fryc at gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Don't ship yet, I'm taking look today :-)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Wed, Sep 23, 2015 at 3:44 PM, Sebastien Blanc <
>>>>>>>>>>>>>>>> scm.blanc at gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> As anyone done any tests for this really important
>>>>>>>>>>>>>>>>> release, it has been staging now for more than 2 weeks ?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Sep 8, 2015 at 2:12 PM, Idel Pivnitskiy <
>>>>>>>>>>>>>>>>> idel.pivnitskiy at gmail.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Done:
>>>>>>>>>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/633
>>>>>>>>>>>>>>>>>> It would be great if someone will check the whole API
>>>>>>>>>>>>>>>>>> documentation. Hope it doesn't have typos or other problems.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Best regards,
>>>>>>>>>>>>>>>>>> Idel Pivnitskiy
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com
>>>>>>>>>>>>>>>>>> Twitter: @idelpivnitskiy
>>>>>>>>>>>>>>>>>> <https://twitter.com/idelpivnitskiy>
>>>>>>>>>>>>>>>>>> GitHub: @idelpivnitskiy
>>>>>>>>>>>>>>>>>> <https://github.com/idelpivnitskiy>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Sep 8, 2015 at 3:11 PM, Matthias Wessendorf <
>>>>>>>>>>>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> here is the OpenShift PR:
>>>>>>>>>>>>>>>>>>> https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/22
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> -Matthias
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tue, Sep 8, 2015 at 11:17 AM, Matthias Wessendorf <
>>>>>>>>>>>>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> alright, thanks!
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I will do the OpenShift updates, based on the git tag
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Tue, Sep 8, 2015 at 11:15 AM, Sebastien Blanc <
>>>>>>>>>>>>>>>>>>>> scm.blanc at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Hi team,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I'm happy to announce that UPS 1.1.0 Final has been
>>>>>>>>>>>>>>>>>>>>> staged.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Please test the staged release :
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6516
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> By the end of the week I'd like to press the button to
>>>>>>>>>>>>>>>>>>>>> release it to the wild.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Sebi
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> ps : the openshift update will follow
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> Matthias Wessendorf
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>>>>>>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>>>>>>>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Matthias Wessendorf
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>>>>>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>>>>>>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Luk?? Fry?
>>>>>>>>>>>> Software Engineer
>>>>>>>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> -- Passos
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Luk?? Fry?
>>>>>>>>>> Software Engineer
>>>>>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Luk?? Fry?
>>>>>>>>> Software Engineer
>>>>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> aerogear-dev mailing list
>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Matthias Wessendorf
>>>>>>>>
>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Luk?? Fry?
>>>>>>> Software Engineer
>>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Luk?? Fry?
>>>>>> Software Engineer
>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151102/e3449a66/attachment-0001.html 

From matzew at apache.org  Mon Nov  2 05:13:44 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 2 Nov 2015 11:13:44 +0100
Subject: [aerogear-dev] Staging of UPS 1.1.0.Final
In-Reply-To: <CAPXQee57naSqzcvajzvVtnSbPPFijfe46FTt7SQVyX2-1aFezg@mail.gmail.com>
References: <CAD_dpu1j2=Q0mOxVzT9NUNS12S4VNC_UjMw2SKYz4ZSfcbx_pg@mail.gmail.com>
	<CAAg5f2Rc-SDjGJouKmrfm+_cq73_PMKST35dvr+wtFgpELvOKQ@mail.gmail.com>
	<CAAg5f2TW9s2x_3zRP7XymR+5P=S=PJ1fGbE9=qwxRb6Z0VAHYA@mail.gmail.com>
	<CAN+BUJqTkfXL20uF7w4LSY+WJ=Qs_7-h3PwNa74E83-HQ8F-dA@mail.gmail.com>
	<CAD_dpu2Bh6tuhcsf6q+x1tAQkK2J7erExrchQObmUPzVBKL1mg@mail.gmail.com>
	<CAEroY37GU3DqdepzKdYknVZMSE3JBAQtTqCAnkJYaBeza3WiRQ@mail.gmail.com>
	<CAEroY377W=RzqE295j0DcrQF1Uu=kW3e1rc65F-DA8-=mLQJ1Q@mail.gmail.com>
	<CAL8vO=dU46=XnebksQi7Vh3XwuTyp9_oup+nuWYv4ZzGWcB0YQ@mail.gmail.com>
	<CAEroY37TP6PFhA784iY=gQzr0FUXOgN5Jcc7gHfEPe+TvGcuYA@mail.gmail.com>
	<CAAnALH=qMzKgubUhWDZ_fcvuBbL25no4HVpMiF2=zS+gH4t1fA@mail.gmail.com>
	<CADF=h2s_x9c9CrsHX989APVetfeCfNnOR_KTJxXhAmW1rouEBQ@mail.gmail.com>
	<CAAnALH=mGJ3gauiC6Xo5E0SWAprf=Aweqxvdtmd5zLsvBTewpQ@mail.gmail.com>
	<CAAnALHkcs9Af+-ZHLOM2rvwdFg1ATPhnpYh3XDq228jeDAcm0Q@mail.gmail.com>
	<CAAg5f2RoCzLuvBxqFqL3vM_ewVivfb5cryK_ap8GGE+BM-VnKQ@mail.gmail.com>
	<CAAnALHn44SRsr5DYuN+j_ZST9hATsbkQGDSkXx=4ZDL5RX1SKw@mail.gmail.com>
	<CAAnALHmfHAU04EmM8a8ZXrhYMmQ-=qimEdEqM3u9DdQp2iS7uA@mail.gmail.com>
	<CAAg5f2SDesQFZTYG1VK7ZGBL7Gg6fW=HJGEuEq_a-8tZe2U7FQ@mail.gmail.com>
	<CAAg5f2TZ7c0bChc3SuWaFCvSBNHhAXqKUUTmy1+wNL-qn_zH4Q@mail.gmail.com>
	<CAPXQee7Uw+207y0xa0pbJ7JNvMiis-xpXXgqALUet4rMCyRMKg@mail.gmail.com>
	<CAAg5f2S_qEc1a097e-1xv=8jPs-97JKTEwCCbPh_1st1dcfpTQ@mail.gmail.com>
	<CAAg5f2R4_nkAHaoBt_jPRwQoYyL6bq_zP7fKBnVesb13vWps4Q@mail.gmail.com>
	<CAPXQee57naSqzcvajzvVtnSbPPFijfe46FTt7SQVyX2-1aFezg@mail.gmail.com>
Message-ID: <CAAg5f2S5ieNTdZ=X6Bhamidg1N4vUB-ePBASOgb_T1y9iWe6Sg@mail.gmail.com>

awesome!!!!!



On Mon, Nov 2, 2015 at 11:06 AM, Karel Piwko <kpiwko at redhat.com> wrote:

> Hello Matthias,
>
> I did a quick sanity check on Friday and I've found just minor issues
> related to stale aerogear.org pages. They are in AEROGEAR jira.
>
> Ship it!
>
> Cheers,
>
> Karel
>
> On Mon, Nov 2, 2015 at 10:35 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Ok, I think it's time to move forward and finally release this version of
>> the UPS
>>
>> On Tue, Oct 27, 2015 at 12:20 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi Karel,
>>>
>>> any thoughts about getting this release shipped ?
>>>
>>> On Thu, Oct 22, 2015 at 10:13 AM, Karel Piwko <kpiwko at redhat.com> wrote:
>>>
>>>> Thanks Matthias,
>>>>
>>>> I'll give it a try this evening and Friday morning.
>>>>
>>>> Cheers,
>>>>
>>>> Karel
>>>>
>>>> On Wed, Oct 21, 2015 at 12:57 PM, Matthias Wessendorf <
>>>> matzew at apache.org> wrote:
>>>>
>>>>> Hey folks,
>>>>>
>>>>> here is the new URL, containing the updated 1.1.0.Final bits
>>>>>
>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6959/
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Oct 20, 2015 at 10:09 AM, Matthias Wessendorf <
>>>>> matzew at apache.org> wrote:
>>>>>
>>>>>> Ok,
>>>>>>
>>>>>> on it
>>>>>>
>>>>>> On Mon, Oct 19, 2015 at 4:33 PM, Lukas Fryc <lfryc at redhat.com> wrote:
>>>>>>
>>>>>>> *Unfortunately :-)
>>>>>>>
>>>>>>> On Mon, Oct 19, 2015 at 4:25 PM, Lukas Fryc <lfryc at redhat.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Yes, that was the plan. Fortunately we haven't hit AGPUSH-1513
>>>>>>>> until we deployed to OpenShift, there is is especially apparent.
>>>>>>>>
>>>>>>>> On Mon, Oct 19, 2015 at 3:14 PM, Matthias Wessendorf <
>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>
>>>>>>>>> so, that mean we skip the staged 1.1.0? and will do a re-staging,
>>>>>>>>> that includes the fixes?
>>>>>>>>>
>>>>>>>>> I'd say so ...
>>>>>>>>>
>>>>>>>>> On Mon, Oct 19, 2015 at 3:03 PM, Lukas Fryc <lfryc at redhat.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Here are aforementioned patches, could you please take a look?
>>>>>>>>>>
>>>>>>>>>> AGPUSH-1513 UPS Console shows Pending - because servedVariants <
>>>>>>>>>> totalVariants
>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/636
>>>>>>>>>>
>>>>>>>>>> AGPUSH-1516 Change AerogearLogger to use fully-qualified class
>>>>>>>>>> names instead of simple class names
>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/637
>>>>>>>>>>
>>>>>>>>>> AGCORDOVA-120 NullReferenceException when delivering message to
>>>>>>>>>> WP8 app on foreground
>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/638
>>>>>>>>>> https://github.com/aerogear/aerogear.org/pull/613
>>>>>>>>>> https://github.com/aerogear/aerogear-cordova-push/pull/80
>>>>>>>>>>
>>>>>>>>>> ~ Lukas
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Oct 5, 2015 at 5:38 PM, Lukas Fryc <lfryc at redhat.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi guys,
>>>>>>>>>>>
>>>>>>>>>>> Ad) 1.1.0 RELEASE
>>>>>>>>>>>
>>>>>>>>>>> we have agreed with Sebi to restage 1.1.0 including these fixes:
>>>>>>>>>>>
>>>>>>>>>>> AGPUSH-1513 UPS Console shows Pending - because servedVariants <
>>>>>>>>>>> totalVariants
>>>>>>>>>>> AGPUSH-1516 Change AerogearLogger to use fully-qualified class
>>>>>>>>>>> names instead of simple class names
>>>>>>>>>>> AGCORDOVA-120 NullReferenceException when delivering message to
>>>>>>>>>>> WP8 app on foreground
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I will create release-1.1.0 branch so we can continue developing
>>>>>>>>>>> / merging changes into master for version 1.1.x.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Ad) TRIAGE
>>>>>>>>>>>
>>>>>>>>>>> We also did a triage of 1.1.x issues, resulting into 2 versions:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 1.1.1: critical fixes & small UX improvements
>>>>>>>>>>>
>>>>>>>>>>> https://issues.jboss.org/projects/AGPUSH/versions/12327457
>>>>>>>>>>>
>>>>>>>>>>> 1.1.x: other minor improvements for 1.1 that can wait for later
>>>>>>>>>>> releases
>>>>>>>>>>>
>>>>>>>>>>> https://issues.jboss.org/projects/AGPUSH/versions/12323762
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Cheers!
>>>>>>>>>>>
>>>>>>>>>>> ~ Lukas
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Oct 2, 2015 at 2:05 PM, Daniel Passos <
>>>>>>>>>>> dpassos at redhat.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I've finished my tests to native Android and everything works
>>>>>>>>>>>> perfect.
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Oct 2, 2015 at 4:29 AM, Lukas Fryc <lfryc at redhat.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I've finished my testing - Cordova apps on Android, iOS and
>>>>>>>>>>>>> WP8 against OpenShift 1.1.0.Final deployment and found these issues:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> https://issues.jboss.org/issues/?jql=reporter%3Dlfryc%20AND%20project%20IN%20(AGPUSH%2C%20AGCORDOVA)%20AND%20created%20%3E%3D%20'2015-09-28'%20and%20created%20%3C%3D%20'2015-10-03
>>>>>>>>>>>>> '
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Oct 1, 2015 at 2:43 PM, Luk?? Fry? <
>>>>>>>>>>>>> lukas.fryc at gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks Corinne, I forgot about it, tbh I didn't think about
>>>>>>>>>>>>>> it as 1.1.0.Final issue, but yea, it is probably linked to it :-)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Thu, Oct 1, 2015 at 10:20 AM, Corinne Krych <
>>>>>>>>>>>>>> corinnekrych at gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks Lukas,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Cordova iOS side you also discovered the enable_bitcode
>>>>>>>>>>>>>>> issue which is fixed by this PR [1].
>>>>>>>>>>>>>>> Interesting Cordova is working on making the default project
>>>>>>>>>>>>>>> set-up with ENABLE_BITCODE=No [2] which is less restrictive (no need to
>>>>>>>>>>>>>>> have all dependent lib built with bitcode enabled).
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ++
>>>>>>>>>>>>>>> Corinne
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [1]
>>>>>>>>>>>>>>> https://github.com/aerogear/aerogear-cordova-push/pull/79
>>>>>>>>>>>>>>> [2]
>>>>>>>>>>>>>>> https://github.com/apache/cordova-ios/commit/ca07a7153e2afd6e5a1239806151c69d80758245
>>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/CB-9721
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 1 October 2015 at 09:34, Luk?? Fry? <lukas.fryc at gmail.com
>>>>>>>>>>>>>>> > wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hey guys,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I was testing iOS and Android devices against OpenShift
>>>>>>>>>>>>>>>> 1.1.0.Final deployment,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I discovered few issues:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>    -
>>>>>>>>>>>>>>>>    - Activity log - shows pending AGPUSH-1513
>>>>>>>>>>>>>>>>    <https://issues.jboss.org/browse/AGPUSH-1513>
>>>>>>>>>>>>>>>>    - Windows Phone 8 / Cordova app - shows Registering,
>>>>>>>>>>>>>>>>    but never registers (still debugging this, may be something wrong with my
>>>>>>>>>>>>>>>>    setup)
>>>>>>>>>>>>>>>>    - UX improvement: when switching to Analytics, the data
>>>>>>>>>>>>>>>>    aren?t loaded and shows No Data blank slate
>>>>>>>>>>>>>>>>    - debugging improvement: enable fully qualified names
>>>>>>>>>>>>>>>>    in debug log: FINE  [NotificationDispatcher] -> FINE
>>>>>>>>>>>>>>>>    [org.jboss.aerogear....NotificationDispatcher]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> >From the mentioned issues only AGPUSH-1513 is considered a
>>>>>>>>>>>>>>>> blocker,
>>>>>>>>>>>>>>>> we have agreed with Sebi to restage 1.1.0 with AGPUSH-1513
>>>>>>>>>>>>>>>> and then implement AGPUSH-1512 in 1.1.1.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ~ Lukas
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Sep 29, 2015 at 7:56 AM, Luk?? Fry? <
>>>>>>>>>>>>>>>> lukas.fryc at gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Don't ship yet, I'm taking look today :-)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Wed, Sep 23, 2015 at 3:44 PM, Sebastien Blanc <
>>>>>>>>>>>>>>>>> scm.blanc at gmail.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> As anyone done any tests for this really important
>>>>>>>>>>>>>>>>>> release, it has been staging now for more than 2 weeks ?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Sep 8, 2015 at 2:12 PM, Idel Pivnitskiy <
>>>>>>>>>>>>>>>>>> idel.pivnitskiy at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Done:
>>>>>>>>>>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/633
>>>>>>>>>>>>>>>>>>> It would be great if someone will check the whole API
>>>>>>>>>>>>>>>>>>> documentation. Hope it doesn't have typos or other problems.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Best regards,
>>>>>>>>>>>>>>>>>>> Idel Pivnitskiy
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com
>>>>>>>>>>>>>>>>>>> Twitter: @idelpivnitskiy
>>>>>>>>>>>>>>>>>>> <https://twitter.com/idelpivnitskiy>
>>>>>>>>>>>>>>>>>>> GitHub: @idelpivnitskiy
>>>>>>>>>>>>>>>>>>> <https://github.com/idelpivnitskiy>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tue, Sep 8, 2015 at 3:11 PM, Matthias Wessendorf <
>>>>>>>>>>>>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> here is the OpenShift PR:
>>>>>>>>>>>>>>>>>>>> https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/22
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> -Matthias
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Tue, Sep 8, 2015 at 11:17 AM, Matthias Wessendorf <
>>>>>>>>>>>>>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> alright, thanks!
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I will do the OpenShift updates, based on the git tag
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Tue, Sep 8, 2015 at 11:15 AM, Sebastien Blanc <
>>>>>>>>>>>>>>>>>>>>> scm.blanc at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Hi team,
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> I'm happy to announce that UPS 1.1.0 Final has been
>>>>>>>>>>>>>>>>>>>>>> staged.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Please test the staged release :
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6516
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> By the end of the week I'd like to press the button
>>>>>>>>>>>>>>>>>>>>>> to release it to the wild.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Sebi
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> ps : the openshift update will follow
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Matthias Wessendorf
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>>>>>>>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>>>>>>>>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> Matthias Wessendorf
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>>>>>>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>>>>>>>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Luk?? Fry?
>>>>>>>>>>>>> Software Engineer
>>>>>>>>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>>>>>>>>
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> -- Passos
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Luk?? Fry?
>>>>>>>>>>> Software Engineer
>>>>>>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Luk?? Fry?
>>>>>>>>>> Software Engineer
>>>>>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Matthias Wessendorf
>>>>>>>>>
>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> aerogear-dev mailing list
>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Luk?? Fry?
>>>>>>>> Software Engineer
>>>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Luk?? Fry?
>>>>>>> Software Engineer
>>>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Matthias Wessendorf
>>>>>>
>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151102/03c0a579/attachment-0001.html 

From rsmeral at redhat.com  Mon Nov  2 14:38:22 2015
From: rsmeral at redhat.com (Ron Smeral)
Date: Mon, 2 Nov 2015 20:38:22 +0100
Subject: [aerogear-dev] UPS: deviceType semantics
Message-ID: <5637BBAE.8050904@redhat.com>

Hi all,

I noticed the "deviceType" field in UPS seems to be used inconsistently between Server and the SDKs, and is perhaps underspecified.

The docs only say this much:
https://aerogear.org/docs/unifiedpush/client-registration/
* "deviceType: The device type of the device or the user agent."
- what does "device type of the device" mean? "Type" in what sense?

https://aerogear.org/docs/unifiedpush/push-message-format/
* "deviceType: A list of raw device types that should receive the message (e.g. Coupon only for iPad and AndroidTablets). The deviceType needs to be stored when the device is registering itself with the server."
- what's a "raw device type"?
- "needs to be stored" - who needs to do that? Store where?


When trying to use the Sender API, the obvious question is: what's the list of possible values? The docs don't answer that.

Another missing piece of information:
* Is the deviceType an arbitrary string set by the user during registration?
* Or, is it somehow automatically set by the client SDKs?

After a bit of digging through the SDKs and APIs, I can see this (not necessarily 100% correct):

* The Sender API accepts arbitrary values

* Android SDK - has deviceType in model, sets to "ANDROID" by default
* Windows SDK - doesn't even have deviceType in model
* iOS SDK - has deviceType in model, doesn't set to any default value

* Cordova Android - doesn't set, so uses "ANDROID"
* Cordova WP8 - not in model, not set
* Cordova iOS - sets UIDevice.model (I can't really read ObjC, just a guess by looking at the code)


Can we come up with clearer semantics for the deviceType field?

Thanks,
Ron

-- 
Ron Smeral
Technical Writer, FeedHenry
Red Hat
Brno

From lholmqui at redhat.com  Mon Nov  2 14:43:14 2015
From: lholmqui at redhat.com (Luke Holmquist)
Date: Mon, 2 Nov 2015 14:43:14 -0500
Subject: [aerogear-dev] UPS: deviceType semantics
In-Reply-To: <5637BBAE.8050904@redhat.com>
References: <5637BBAE.8050904@redhat.com>
Message-ID: <CALD3Fd3PGsT4kvvoBi9+euy7HSPvjerD3Ga8yD1wFbsQf_GzAA@mail.gmail.com>

On Mon, Nov 2, 2015 at 2:38 PM, Ron Smeral <rsmeral at redhat.com> wrote:

> Hi all,
>
> I noticed the "deviceType" field in UPS seems to be used inconsistently
> between Server and the SDKs, and is perhaps underspecified.
>
> The docs only say this much:
> https://aerogear.org/docs/unifiedpush/client-registration/
> * "deviceType: The device type of the device or the user agent."
> - what does "device type of the device" mean? "Type" in what sense?
>
> https://aerogear.org/docs/unifiedpush/push-message-format/
> * "deviceType: A list of raw device types that should receive the message
> (e.g. Coupon only for iPad and AndroidTablets). The deviceType needs to be
> stored when the device is registering itself with the server."
> - what's a "raw device type"?
> - "needs to be stored" - who needs to do that? Store where?
>
>
> When trying to use the Sender API, the obvious question is: what's the
> list of possible values? The docs don't answer that.
>
> which Sender API, the node.js one or the the Java one.  i'd imagine both
are lacking  :)

> Another missing piece of information:
> * Is the deviceType an arbitrary string set by the user during
> registration?
> * Or, is it somehow automatically set by the client SDKs?
>
> After a bit of digging through the SDKs and APIs, I can see this (not
> necessarily 100% correct):
>
> * The Sender API accepts arbitrary values
>
> * Android SDK - has deviceType in model, sets to "ANDROID" by default
> * Windows SDK - doesn't even have deviceType in model
> * iOS SDK - has deviceType in model, doesn't set to any default value
>
> * Cordova Android - doesn't set, so uses "ANDROID"
> * Cordova WP8 - not in model, not set
> * Cordova iOS - sets UIDevice.model (I can't really read ObjC, just a
> guess by looking at the code)
>
>
> Can we come up with clearer semantics for the deviceType field?
>
> Thanks,
> Ron
>
> --
> Ron Smeral
> Technical Writer, FeedHenry
> Red Hat
> Brno
> _______________________________________________
> 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/20151102/4c32d4a3/attachment.html 

From matzew at apache.org  Tue Nov  3 02:57:44 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 3 Nov 2015 08:57:44 +0100
Subject: [aerogear-dev] UPS: deviceType semantics
In-Reply-To: <5637BBAE.8050904@redhat.com>
References: <5637BBAE.8050904@redhat.com>
Message-ID: <CAAg5f2TOs0UMCTB8Dxm-Om3BzgbCrdhSm_pEnZBstpJZU8j88A@mail.gmail.com>

Hi Ron,

thanks for the mail - let me try to bring some light into the dark

On Mon, Nov 2, 2015 at 8:38 PM, Ron Smeral <rsmeral at redhat.com> wrote:

> Hi all,
>
> I noticed the "deviceType" field in UPS seems to be used inconsistently
> between Server and the SDKs, and is perhaps underspecified.
>
> The docs only say this much:
> https://aerogear.org/docs/unifiedpush/client-registration/
> * "deviceType: The device type of the device or the user agent."
> - what does "device type of the device" mean? "Type" in what sense?
>


like here:
https://github.com/aerogear/aerogear-push-ios-demo/blob/master/PushTest/AGAppDelegate.m#L82

the iOS API read the type of the device (eg. iPod, iPad, iPhone) etc.

It's stored on the server's metadata. Presented to the user, on the admin
UI, when browsing the registered devices for a Variant. Below is an example
from our users doc:
https://aerogear.org/docs/unifiedpush/ups_userguide/index/#_importing_device_metadata


>
> https://aerogear.org/docs/unifiedpush/push-message-format/
> * "deviceType: A list of raw device types that should receive the message
> (e.g. Coupon only for iPad and AndroidTablets). The deviceType needs to be
> stored when the device is registering itself with the server."
> - what's a "raw device type"?
> - "needs to be stored" - who needs to do that? Store where?
>

This API is to actually sent the message to the registered devices - device
type here is a filter.
Example: you have a generic iOS variant, and have a few iPods, a few iPhone
and a few iPads, this filter allows you to just sent messages to all
iPhones, by specifiying iphone.



>
>
> When trying to use the Sender API, the obvious question is: what's the
> list of possible values? The docs don't answer that.
>

here is our current version of the doc:
https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html#POST


but we have a new online in a few days (after the 1.1.0.Finall is out)


>
> Another missing piece of information:
> * Is the deviceType an arbitrary string set by the user during
> registration?
>

usually that's done by the application (develoiper), not the directly the
end user of the phone


> * Or, is it somehow automatically set by the client SDKs?
>

yeah :-) but not enforced


>
> After a bit of digging through the SDKs and APIs, I can see this (not
> necessarily 100% correct):
>
> * The Sender API accepts arbitrary values
>
> * Android SDK - has deviceType in model, sets to "ANDROID" by default
> * Windows SDK - doesn't even have deviceType in model
> * iOS SDK - has deviceType in model, doesn't set to any default value
>
> * Cordova Android - doesn't set, so uses "ANDROID"
> * Cordova WP8 - not in model, not set
> * Cordova iOS - sets UIDevice.model (I can't really read ObjC, just a
> guess by looking at the code)
>
>
> Can we come up with clearer semantics for the deviceType field?
>

Looks like on Windows it is missing - perhaps we should add that.
On Android, I agree the SDK should not set any default here - but I am not
sure if there is an equivalent API around like UIDevice, which would the
app developer allow to specifiy the actual device type.

Mind filing a few JIRAs against: AGDROID, AGWIN to get the functionality
baked into the native SDKs, and against AGCORDOVA to get this into there as
well, once the native bits are done.

Great find, Ron!


>
> Thanks,
> Ron
>
> --
> Ron Smeral
> Technical Writer, FeedHenry
> Red Hat
> Brno
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151103/aafa60ac/attachment.html 

From matzew at apache.org  Tue Nov  3 05:49:16 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 3 Nov 2015 11:49:16 +0100
Subject: [aerogear-dev] Parent 0.2.17 -> staging repo
Message-ID: <CAAg5f2SVBaooBdN1PZ43SssTB4=V-Wj1Y+hzaC4fNBmNQVQ7Zg@mail.gmail.com>

Ahoy!

A new release of aerogear-parent was staged at:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7059/

This is basically an alignment of the httpcomponents dependencies, as
described in here:
https://github.com/aerogear/aerogear-parent/pull/52

I'm considering to release it on Thursday. If you want
the release to be postoned to another day, let me know.

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151103/441a193b/attachment.html 

From avibelli at redhat.com  Tue Nov  3 06:21:04 2015
From: avibelli at redhat.com (Andrea Vibelli)
Date: Tue, 3 Nov 2015 04:21:04 -0700 (MST)
Subject: [aerogear-dev] Parent 0.2.17 -> staging repo
In-Reply-To: <CAAg5f2SVBaooBdN1PZ43SssTB4=V-Wj1Y+hzaC4fNBmNQVQ7Zg@mail.gmail.com>
References: <CAAg5f2SVBaooBdN1PZ43SssTB4=V-Wj1Y+hzaC4fNBmNQVQ7Zg@mail.gmail.com>
Message-ID: <1446549664969-12205.post@n5.nabble.com>

Hello Matt, 
I have no concerns with this new parent release, thanks a lot for this.

Andrea


Matthias Wessendorf wrote
> Ahoy!
> 
> A new release of aerogear-parent was staged at:
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7059/
> 
> This is basically an alignment of the httpcomponents dependencies, as
> described in here:
> https://github.com/aerogear/aerogear-parent/pull/52
> 
> I'm considering to release it on Thursday. If you want
> the release to be postoned to another day, let me know.
> 
> -- 
> Matthias Wessendorf
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Parent-0-2-17-staging-repo-tp12204p12205.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From kpiwko at redhat.com  Tue Nov  3 07:06:29 2015
From: kpiwko at redhat.com (Karel Piwko)
Date: Tue, 3 Nov 2015 13:06:29 +0100
Subject: [aerogear-dev] Parent 0.2.17 -> staging repo
In-Reply-To: <1446549664969-12205.post@n5.nabble.com>
References: <CAAg5f2SVBaooBdN1PZ43SssTB4=V-Wj1Y+hzaC4fNBmNQVQ7Zg@mail.gmail.com>
	<1446549664969-12205.post@n5.nabble.com>
Message-ID: <CAPXQee718qZD2fqJjCwcBk=22ZKFpaYBo7LKF1yXey7JwYP9qg@mail.gmail.com>

I have no concerns for this releases neither.

Karel

On Tue, Nov 3, 2015 at 12:21 PM, Andrea Vibelli <avibelli at redhat.com> wrote:

> Hello Matt,
> I have no concerns with this new parent release, thanks a lot for this.
>
> Andrea
>
>
> Matthias Wessendorf wrote
> > Ahoy!
> >
> > A new release of aerogear-parent was staged at:
> >
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7059/
> >
> > This is basically an alignment of the httpcomponents dependencies, as
> > described in here:
> > https://github.com/aerogear/aerogear-parent/pull/52
> >
> > I'm considering to release it on Thursday. If you want
> > the release to be postoned to another day, let me know.
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
> > _______________________________________________
> > aerogear-dev mailing list
>
> > aerogear-dev at .jboss
>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Parent-0-2-17-staging-repo-tp12204p12205.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> 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/20151103/c64aedc7/attachment.html 

From matzew at apache.org  Wed Nov  4 04:02:12 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 4 Nov 2015 10:02:12 +0100
Subject: [aerogear-dev] Parent 0.2.17 -> staging repo
In-Reply-To: <CAPXQee718qZD2fqJjCwcBk=22ZKFpaYBo7LKF1yXey7JwYP9qg@mail.gmail.com>
References: <CAAg5f2SVBaooBdN1PZ43SssTB4=V-Wj1Y+hzaC4fNBmNQVQ7Zg@mail.gmail.com>
	<1446549664969-12205.post@n5.nabble.com>
	<CAPXQee718qZD2fqJjCwcBk=22ZKFpaYBo7LKF1yXey7JwYP9qg@mail.gmail.com>
Message-ID: <CAAg5f2R5w0SUy32JPkTTfMZzJpXYP8Jb2+y1X64X1GVicCS3EQ@mail.gmail.com>

clicked the btn ;-)

On Tue, Nov 3, 2015 at 1:06 PM, Karel Piwko <kpiwko at redhat.com> wrote:

> I have no concerns for this releases neither.
>
> Karel
>
> On Tue, Nov 3, 2015 at 12:21 PM, Andrea Vibelli <avibelli at redhat.com>
> wrote:
>
>> Hello Matt,
>> I have no concerns with this new parent release, thanks a lot for this.
>>
>> Andrea
>>
>>
>> Matthias Wessendorf wrote
>> > Ahoy!
>> >
>> > A new release of aerogear-parent was staged at:
>> >
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7059/
>> >
>> > This is basically an alignment of the httpcomponents dependencies, as
>> > described in here:
>> > https://github.com/aerogear/aerogear-parent/pull/52
>> >
>> > I'm considering to release it on Thursday. If you want
>> > the release to be postoned to another day, let me know.
>> >
>> > --
>> > Matthias Wessendorf
>> >
>> > blog: http://matthiaswessendorf.wordpress.com/
>> > sessions: http://www.slideshare.net/mwessendorf
>> > twitter: http://twitter.com/mwessendorf
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>>
>> > aerogear-dev at .jboss
>>
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Parent-0-2-17-staging-repo-tp12204p12205.html
>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151104/29253d13/attachment.html 

From matzew at apache.org  Wed Nov  4 05:01:01 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 4 Nov 2015 11:01:01 +0100
Subject: [aerogear-dev] jekyll issue, on site generation (on a mac)
Message-ID: <CAAg5f2TerG29POGBzUF5-CV6FPVw=P-NkfKnDk0K8o11fod5Wg@mail.gmail.com>

Hi,

can one try to generate the site, on a mac ?

I am getting:

Liquid Exception: "\xEF" from ASCII-8BIT to UTF-8 in
getstarted/demos/index.html
jekyll 2.5.2 | Error:  "\xEF" from ASCII-8BIT to UTF-8


I am on this ruby version:
ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin13.0]


Or am I the only person, seeing this ?

Thanks,
Matthias


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151104/5156207f/attachment.html 

From dpassos at redhat.com  Wed Nov  4 06:25:01 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Wed, 4 Nov 2015 09:25:01 -0200
Subject: [aerogear-dev] jekyll issue, on site generation (on a mac)
In-Reply-To: <CAAg5f2TerG29POGBzUF5-CV6FPVw=P-NkfKnDk0K8o11fod5Wg@mail.gmail.com>
References: <CAAg5f2TerG29POGBzUF5-CV6FPVw=P-NkfKnDk0K8o11fod5Wg@mail.gmail.com>
Message-ID: <CADF=h2tjRFskd2iz1fhmKAQ==kbfmg5ymkzPKhO+CrXVjpn8Xg@mail.gmail.com>

Same here

On Wed, Nov 4, 2015 at 8:01 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> can one try to generate the site, on a mac ?
>
> I am getting:
>
> Liquid Exception: "\xEF" from ASCII-8BIT to UTF-8 in
> getstarted/demos/index.html
> jekyll 2.5.2 | Error:  "\xEF" from ASCII-8BIT to UTF-8
>
>
> I am on this ruby version:
> ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin13.0]
>
>
> Or am I the only person, seeing this ?
>
> Thanks,
> Matthias
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151104/0ca72fda/attachment.html 

From dpassos at redhat.com  Wed Nov  4 06:34:36 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Wed, 4 Nov 2015 09:34:36 -0200
Subject: [aerogear-dev] UPS: deviceType semantics
In-Reply-To: <CAAg5f2TOs0UMCTB8Dxm-Om3BzgbCrdhSm_pEnZBstpJZU8j88A@mail.gmail.com>
References: <5637BBAE.8050904@redhat.com>
	<CAAg5f2TOs0UMCTB8Dxm-Om3BzgbCrdhSm_pEnZBstpJZU8j88A@mail.gmail.com>
Message-ID: <CADF=h2vtOro7D6qXcChO3sn=YkRecY+5y3gbGVYbYMv2tP3n=w@mail.gmail.com>

On Tue, Nov 3, 2015 at 5:57 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi Ron,
>
> thanks for the mail - let me try to bring some light into the dark
>
> On Mon, Nov 2, 2015 at 8:38 PM, Ron Smeral <rsmeral at redhat.com> wrote:
>
>> Hi all,
>>
>> I noticed the "deviceType" field in UPS seems to be used inconsistently
>> between Server and the SDKs, and is perhaps underspecified.
>>
>> The docs only say this much:
>> https://aerogear.org/docs/unifiedpush/client-registration/
>> * "deviceType: The device type of the device or the user agent."
>> - what does "device type of the device" mean? "Type" in what sense?
>>
>
>
> like here:
>
> https://github.com/aerogear/aerogear-push-ios-demo/blob/master/PushTest/AGAppDelegate.m#L82
>
> the iOS API read the type of the device (eg. iPod, iPad, iPhone) etc.
>
> It's stored on the server's metadata. Presented to the user, on the admin
> UI, when browsing the registered devices for a Variant. Below is an example
> from our users doc:
>
> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#_importing_device_metadata
>
>
>>
>> https://aerogear.org/docs/unifiedpush/push-message-format/
>> * "deviceType: A list of raw device types that should receive the message
>> (e.g. Coupon only for iPad and AndroidTablets). The deviceType needs to be
>> stored when the device is registering itself with the server."
>> - what's a "raw device type"?
>> - "needs to be stored" - who needs to do that? Store where?
>>
>
> This API is to actually sent the message to the registered devices -
> device type here is a filter.
> Example: you have a generic iOS variant, and have a few iPods, a few
> iPhone and a few iPads, this filter allows you to just sent messages to all
> iPhones, by specifiying iphone.
>
>
>
>>
>>
>> When trying to use the Sender API, the obvious question is: what's the
>> list of possible values? The docs don't answer that.
>>
>
> here is our current version of the doc:
>
> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html#POST
>
>
> but we have a new online in a few days (after the 1.1.0.Finall is out)
>
>
>>
>> Another missing piece of information:
>> * Is the deviceType an arbitrary string set by the user during
>> registration?
>>
>
> usually that's done by the application (develoiper), not the directly the
> end user of the phone
>
>
>> * Or, is it somehow automatically set by the client SDKs?
>>
>
> yeah :-) but not enforced
>
>
>>
>> After a bit of digging through the SDKs and APIs, I can see this (not
>> necessarily 100% correct):
>>
>> * The Sender API accepts arbitrary values
>>
>> * Android SDK - has deviceType in model, sets to "ANDROID" by default
>> * Windows SDK - doesn't even have deviceType in model
>> * iOS SDK - has deviceType in model, doesn't set to any default value
>>
>> * Cordova Android - doesn't set, so uses "ANDROID"
>> * Cordova WP8 - not in model, not set
>> * Cordova iOS - sets UIDevice.model (I can't really read ObjC, just a
>> guess by looking at the code)
>>
>>
>> Can we come up with clearer semantics for the deviceType field?
>>
>
> Looks like on Windows it is missing - perhaps we should add that.
> On Android, I agree the SDK should not set any default here - but I am not
> sure if there is an equivalent API around like UIDevice, which would the
> app developer allow to specifiy the actual device type.
>

You are right, we don't have API like UIDevice. To check if it's a tablet
or a phone we need to check the screen size
http://developer.android.com/guide/practices/screens_support.html#DeclaringTabletLayouts


> Mind filing a few JIRAs against: AGDROID, AGWIN to get the functionality
> baked into the native SDKs, and against AGCORDOVA to get this into there as
> well, once the native bits are done.
>
> Great find, Ron!
>
>
>>
>> Thanks,
>> Ron
>>
>> --
>> Ron Smeral
>> Technical Writer, FeedHenry
>> Red Hat
>> Brno
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151104/47c623d6/attachment-0001.html 

From matzew at apache.org  Wed Nov  4 06:41:00 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 4 Nov 2015 12:41:00 +0100
Subject: [aerogear-dev] UPS: deviceType semantics
In-Reply-To: <CADF=h2vtOro7D6qXcChO3sn=YkRecY+5y3gbGVYbYMv2tP3n=w@mail.gmail.com>
References: <5637BBAE.8050904@redhat.com>
	<CAAg5f2TOs0UMCTB8Dxm-Om3BzgbCrdhSm_pEnZBstpJZU8j88A@mail.gmail.com>
	<CADF=h2vtOro7D6qXcChO3sn=YkRecY+5y3gbGVYbYMv2tP3n=w@mail.gmail.com>
Message-ID: <CAAg5f2TjM5NKOsjD1BbNXmN83iht3=LsU135KYkb1Ga0nEqnXQ@mail.gmail.com>

On Wed, Nov 4, 2015 at 12:34 PM, Daniel Passos <dpassos at redhat.com> wrote:

>
>
> On Tue, Nov 3, 2015 at 5:57 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi Ron,
>>
>> thanks for the mail - let me try to bring some light into the dark
>>
>> On Mon, Nov 2, 2015 at 8:38 PM, Ron Smeral <rsmeral at redhat.com> wrote:
>>
>>> Hi all,
>>>
>>> I noticed the "deviceType" field in UPS seems to be used inconsistently
>>> between Server and the SDKs, and is perhaps underspecified.
>>>
>>> The docs only say this much:
>>> https://aerogear.org/docs/unifiedpush/client-registration/
>>> * "deviceType: The device type of the device or the user agent."
>>> - what does "device type of the device" mean? "Type" in what sense?
>>>
>>
>>
>> like here:
>>
>> https://github.com/aerogear/aerogear-push-ios-demo/blob/master/PushTest/AGAppDelegate.m#L82
>>
>> the iOS API read the type of the device (eg. iPod, iPad, iPhone) etc.
>>
>> It's stored on the server's metadata. Presented to the user, on the admin
>> UI, when browsing the registered devices for a Variant. Below is an example
>> from our users doc:
>>
>> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#_importing_device_metadata
>>
>>
>>>
>>> https://aerogear.org/docs/unifiedpush/push-message-format/
>>> * "deviceType: A list of raw device types that should receive the
>>> message (e.g. Coupon only for iPad and AndroidTablets). The deviceType
>>> needs to be stored when the device is registering itself with the server."
>>> - what's a "raw device type"?
>>> - "needs to be stored" - who needs to do that? Store where?
>>>
>>
>> This API is to actually sent the message to the registered devices -
>> device type here is a filter.
>> Example: you have a generic iOS variant, and have a few iPods, a few
>> iPhone and a few iPads, this filter allows you to just sent messages to all
>> iPhones, by specifiying iphone.
>>
>>
>>
>>>
>>>
>>> When trying to use the Sender API, the obvious question is: what's the
>>> list of possible values? The docs don't answer that.
>>>
>>
>> here is our current version of the doc:
>>
>> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html#POST
>>
>>
>> but we have a new online in a few days (after the 1.1.0.Finall is out)
>>
>>
>>>
>>> Another missing piece of information:
>>> * Is the deviceType an arbitrary string set by the user during
>>> registration?
>>>
>>
>> usually that's done by the application (develoiper), not the directly the
>> end user of the phone
>>
>>
>>> * Or, is it somehow automatically set by the client SDKs?
>>>
>>
>> yeah :-) but not enforced
>>
>>
>>>
>>> After a bit of digging through the SDKs and APIs, I can see this (not
>>> necessarily 100% correct):
>>>
>>> * The Sender API accepts arbitrary values
>>>
>>> * Android SDK - has deviceType in model, sets to "ANDROID" by default
>>> * Windows SDK - doesn't even have deviceType in model
>>> * iOS SDK - has deviceType in model, doesn't set to any default value
>>>
>>> * Cordova Android - doesn't set, so uses "ANDROID"
>>> * Cordova WP8 - not in model, not set
>>> * Cordova iOS - sets UIDevice.model (I can't really read ObjC, just a
>>> guess by looking at the code)
>>>
>>>
>>> Can we come up with clearer semantics for the deviceType field?
>>>
>>
>> Looks like on Windows it is missing - perhaps we should add that.
>> On Android, I agree the SDK should not set any default here - but I am
>> not sure if there is an equivalent API around like UIDevice, which would
>> the app developer allow to specifiy the actual device type.
>>
>
> You are right, we don't have API like UIDevice. To check if it's a tablet
> or a phone we need to check the screen size
>
> http://developer.android.com/guide/practices/screens_support.html#DeclaringTabletLayouts
>

wow - sounds like an advanced API :-)


But serious... in that case... why not just leave the default to ANDROID,
as it is today. I see zero reason to really change that at all...

-M




>
>
>
>> Mind filing a few JIRAs against: AGDROID, AGWIN to get the functionality
>> baked into the native SDKs, and against AGCORDOVA to get this into there as
>> well, once the native bits are done.
>>
>> Great find, Ron!
>>
>>
>>>
>>> Thanks,
>>> Ron
>>>
>>> --
>>> Ron Smeral
>>> Technical Writer, FeedHenry
>>> Red Hat
>>> Brno
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> -- Passos
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151104/240e102c/attachment.html 

From edewit at redhat.com  Wed Nov  4 08:37:02 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Wed, 4 Nov 2015 14:37:02 +0100
Subject: [aerogear-dev] jekyll issue, on site generation (on a mac)
In-Reply-To: <CADF=h2tjRFskd2iz1fhmKAQ==kbfmg5ymkzPKhO+CrXVjpn8Xg@mail.gmail.com>
References: <CAAg5f2TerG29POGBzUF5-CV6FPVw=P-NkfKnDk0K8o11fod5Wg@mail.gmail.com>
	<CADF=h2tjRFskd2iz1fhmKAQ==kbfmg5ymkzPKhO+CrXVjpn8Xg@mail.gmail.com>
Message-ID: <CAO2B-fbi2LZX9g6KFQgQcqgkk8SwnXG-p+xJ16zhyPL_XjLo=g@mail.gmail.com>

must be something in this file (getstarted/demos/index.html) encoded wrong?

On Wed, Nov 4, 2015 at 12:25 PM, Daniel Passos <dpassos at redhat.com> wrote:

> Same here
>
> On Wed, Nov 4, 2015 at 8:01 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> can one try to generate the site, on a mac ?
>>
>> I am getting:
>>
>> Liquid Exception: "\xEF" from ASCII-8BIT to UTF-8 in
>> getstarted/demos/index.html
>> jekyll 2.5.2 | Error:  "\xEF" from ASCII-8BIT to UTF-8
>>
>>
>> I am on this ruby version:
>> ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin13.0]
>>
>>
>> Or am I the only person, seeing this ?
>>
>> Thanks,
>> Matthias
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> -- Passos
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151104/8720a2f5/attachment.html 

From thradec at gmail.com  Thu Nov  5 02:57:04 2015
From: thradec at gmail.com (=?UTF-8?B?VG9tw6HFoSBIcmFkZWM=?=)
Date: Thu, 5 Nov 2015 08:57:04 +0100
Subject: [aerogear-dev] verification of JMS workflow
Message-ID: <CAF_jaDTX3wTyZYUGmq=JXV2haO+0r9X2H3PaJxodQcz=zAWstg@mail.gmail.com>

Hi all

I did some testing of JMS workflow used in UPS during sending
notifications. I can confirm, that suggested blocking strategy, as
protection against OOM errors, works as expected. However in worst scenario
could cause blocking 6 of 20 threads (from MDBs pool). So I would suggest
using different approach, with more optimal resource usage, some options
were discussed already with Lukas.

Regards
Tomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151105/c8363627/attachment.html 

From matzew at apache.org  Thu Nov  5 03:22:41 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 5 Nov 2015 09:22:41 +0100
Subject: [aerogear-dev] verification of JMS workflow
In-Reply-To: <CAF_jaDTX3wTyZYUGmq=JXV2haO+0r9X2H3PaJxodQcz=zAWstg@mail.gmail.com>
References: <CAF_jaDTX3wTyZYUGmq=JXV2haO+0r9X2H3PaJxodQcz=zAWstg@mail.gmail.com>
Message-ID: <CAAg5f2R06FWcXiOq83oXsHtpqOuUTB_wmtd0xh9Yq-j8O5yC8A@mail.gmail.com>

awesome, great to hear -

For the 1.1.x (mainly 1.1.1 first ;-)) let's see if we can provide an
optimized strategy. Lukas was already hinting this on IRC.

Tomas, thanks for the updates and the testing effort!

On Thu, Nov 5, 2015 at 8:57 AM, Tom?? Hradec <thradec at gmail.com> wrote:

> Hi all
>
> I did some testing of JMS workflow used in UPS during sending
> notifications. I can confirm, that suggested blocking strategy, as
> protection against OOM errors, works as expected. However in worst scenario
> could cause blocking 6 of 20 threads (from MDBs pool). So I would suggest
> using different approach, with more optimal resource usage, some options
> were discussed already with Lukas.
>
> Regards
> Tomas
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151105/087cb70c/attachment-0001.html 

From lfryc at redhat.com  Thu Nov  5 04:43:01 2015
From: lfryc at redhat.com (Lukas Fryc)
Date: Thu, 5 Nov 2015 10:43:01 +0100
Subject: [aerogear-dev] verification of JMS workflow
In-Reply-To: <CAAg5f2R06FWcXiOq83oXsHtpqOuUTB_wmtd0xh9Yq-j8O5yC8A@mail.gmail.com>
References: <CAF_jaDTX3wTyZYUGmq=JXV2haO+0r9X2H3PaJxodQcz=zAWstg@mail.gmail.com>
	<CAAg5f2R06FWcXiOq83oXsHtpqOuUTB_wmtd0xh9Yq-j8O5yC8A@mail.gmail.com>
Message-ID: <CAAnALH=6XOk0eP1c-sPBx_ywR63WBZ5CPGzw+SjbVo5Jg9sCvw@mail.gmail.com>

I've updated the related issue to track the idea:
https://issues.jboss.org/browse/AGPUSH-1521

On Thu, Nov 5, 2015 at 9:22 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> awesome, great to hear -
>
> For the 1.1.x (mainly 1.1.1 first ;-)) let's see if we can provide an
> optimized strategy. Lukas was already hinting this on IRC.
>
> Tomas, thanks for the updates and the testing effort!
>
> On Thu, Nov 5, 2015 at 8:57 AM, Tom?? Hradec <thradec at gmail.com> wrote:
>
>> Hi all
>>
>> I did some testing of JMS workflow used in UPS during sending
>> notifications. I can confirm, that suggested blocking strategy, as
>> protection against OOM errors, works as expected. However in worst scenario
>> could cause blocking 6 of 20 threads (from MDBs pool). So I would suggest
>> using different approach, with more optimal resource usage, some options
>> were discussed already with Lukas.
>>
>> Regards
>> Tomas
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Luk?? Fry?
Software Engineer
Red Hat Mobile | AeroGear.org, FeedHenry.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151105/8ace8ac4/attachment.html 

From rsmeral at redhat.com  Thu Nov  5 07:33:19 2015
From: rsmeral at redhat.com (Ron Smeral)
Date: Thu, 5 Nov 2015 13:33:19 +0100
Subject: [aerogear-dev] UPS: deviceType semantics
In-Reply-To: <CAAg5f2TOs0UMCTB8Dxm-Om3BzgbCrdhSm_pEnZBstpJZU8j88A@mail.gmail.com>
References: <5637BBAE.8050904@redhat.com>
	<CAAg5f2TOs0UMCTB8Dxm-Om3BzgbCrdhSm_pEnZBstpJZU8j88A@mail.gmail.com>
Message-ID: <563B4C8F.3070208@redhat.com>

Hi Matthias, 

thanks for the explanation, let me clarify my intentions :)

All of what you describe is mostly clear to me. I was trying to point at the fact that it might not be clear to a new user.

I'll try to rephrase:
I see two major problems with the *design*:

1) We say "deviceType is the raw type of the device", but in reality, it currently is "a completely arbitrary string where you can stuff anything on registration and then filter by it when sending a notification". 

2) Since we do have the "deviceType" field as part of the model, it should be there for a reason. So then, what's its purpose - what is a "device type"? Is it the form factor - tablet, phone? Is it the OS - "Android Lollipop", "iOS 7"? Or is it the model - "iPhone", "iPod", "Nexus", "Galaxy"? Something else?

So again, I think we should either:
* decide on what the field actually means, and document an enumeration of possible values, and have the SDKs always set the value automatically (possibly overridable),
* OR just get rid of the field (and let the developer set some arbitrary array/object of values on registration, to use for filtering when sending).

On 3.11.2015 08:57, Matthias Wessendorf wrote:
> Hi Ron,
> 
> thanks for the mail - let me try to bring some light into the dark
> 
> On Mon, Nov 2, 2015 at 8:38 PM, Ron Smeral <rsmeral at redhat.com <mailto:rsmeral at redhat.com>> wrote:
> 
>     Hi all,
> 
>     I noticed the "deviceType" field in UPS seems to be used inconsistently between Server and the SDKs, and is perhaps underspecified.
> 
>     The docs only say this much:
>     https://aerogear.org/docs/unifiedpush/client-registration/
>     * "deviceType: The device type of the device or the user agent."
>     - what does "device type of the device" mean? "Type" in what sense?
> 
> 
> 
> like here:
> https://github.com/aerogear/aerogear-push-ios-demo/blob/master/PushTest/AGAppDelegate.m#L82
> 
> the iOS API read the type of the device (eg. iPod, iPad, iPhone) etc.
> 
> It's stored on the server's metadata. Presented to the user, on the admin UI, when browsing the registered devices for a Variant. Below is an example from our users doc:
> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#_importing_device_metadata
>  
> 
> 
>     https://aerogear.org/docs/unifiedpush/push-message-format/
>     * "deviceType: A list of raw device types that should receive the message (e.g. Coupon only for iPad and AndroidTablets). The deviceType needs to be stored when the device is registering itself with the server."
>     - what's a "raw device type"?
>     - "needs to be stored" - who needs to do that? Store where?
> 
> 
> This API is to actually sent the message to the registered devices - device type here is a filter.
> Example: you have a generic iOS variant, and have a few iPods, a few iPhone and a few iPads, this filter allows you to just sent messages to all iPhones, by specifiying iphone.
> 
>  
> 
> 
> 
>     When trying to use the Sender API, the obvious question is: what's the list of possible values? The docs don't answer that.
> 
> 
> here is our current version of the doc:
> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html#POST
> 
> 
> but we have a new online in a few days (after the 1.1.0.Finall is out)
>  
> 
> 
>     Another missing piece of information:
>     * Is the deviceType an arbitrary string set by the user during registration?
> 
> 
> usually that's done by the application (develoiper), not the directly the end user of the phone
>  
> 
>     * Or, is it somehow automatically set by the client SDKs?
> 
> 
> yeah :-) but not enforced
>  
> 
> 
>     After a bit of digging through the SDKs and APIs, I can see this (not necessarily 100% correct):
> 
>     * The Sender API accepts arbitrary values
> 
>     * Android SDK - has deviceType in model, sets to "ANDROID" by default
>     * Windows SDK - doesn't even have deviceType in model
>     * iOS SDK - has deviceType in model, doesn't set to any default value
> 
>     * Cordova Android - doesn't set, so uses "ANDROID"
>     * Cordova WP8 - not in model, not set
>     * Cordova iOS - sets UIDevice.model (I can't really read ObjC, just a guess by looking at the code)
> 
> 
>     Can we come up with clearer semantics for the deviceType field?
> 
> 
> Looks like on Windows it is missing - perhaps we should add that.
> On Android, I agree the SDK should not set any default here - but I am not sure if there is an equivalent API around like UIDevice, which would the app developer allow to specifiy the actual device type.  
> 
> Mind filing a few JIRAs against: AGDROID, AGWIN to get the functionality baked into the native SDKs, and against AGCORDOVA to get this into there as well, once the native bits are done.
> 

I will happily file some JIRAs and make documentation PRs, *once we are clear on what the deviceType really is*.

> Great find, Ron!
>  
> 
> 
>     Thanks,
>     Ron
> 
>     --
>     Ron Smeral
>     Technical Writer, FeedHenry
>     Red Hat
>     Brno
>     _______________________________________________
>     aerogear-dev mailing list
>     aerogear-dev at lists.jboss.org <mailto:aerogear-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> 
> -- 
> Matthias Wessendorf
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 

-- 
Ron Smeral
Technical Writer, FeedHenry
Red Hat
Brno


From matzew at apache.org  Thu Nov  5 07:45:18 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 5 Nov 2015 13:45:18 +0100
Subject: [aerogear-dev] UPS: deviceType semantics
In-Reply-To: <563B4C8F.3070208@redhat.com>
References: <5637BBAE.8050904@redhat.com>
	<CAAg5f2TOs0UMCTB8Dxm-Om3BzgbCrdhSm_pEnZBstpJZU8j88A@mail.gmail.com>
	<563B4C8F.3070208@redhat.com>
Message-ID: <CAAg5f2RoCGf7vQEbAD2uhDXLy_LKVxJ7evVF2vnmSX-UcwC3fQ@mail.gmail.com>

On Thu, Nov 5, 2015 at 1:33 PM, Ron Smeral <rsmeral at redhat.com> wrote:

> Hi Matthias,
>
> thanks for the explanation, let me clarify my intentions :)
>
> All of what you describe is mostly clear to me. I was trying to point at
> the fact that it might not be clear to a new user.
>
> I'll try to rephrase:
> I see two major problems with the *design*:
>
> 1) We say "deviceType is the raw type of the device", but in reality, it
> currently is "a completely arbitrary string where you can stuff anything on
> registration and then filter by it when sending a notification".
>

Ok


>
> 2) Since we do have the "deviceType" field as part of the model, it should
> be there for a reason. So then, what's its purpose - what is a "device
> type"? Is it the form factor - tablet, phone? Is it the OS - "Android
> Lollipop", "iOS 7"? Or is it the model - "iPhone", "iPod", "Nexus",
> "Galaxy"? Something else?
>

the model - and, well mainly introduced for iOS. I am sure it's not really
used at all


>
> So again, I think we should either:
> * decide on what the field actually means, and document an enumeration of
> possible values, and have the SDKs always set the value automatically
> (possibly overridable),
>

updating the documenation sounds best - I doubt it makes sense to touch the
SDKs here (e.g. for iOS we need UIKit dependency etc.) -1 on doing that
automatically.
We can show, in the app how to send the UIDevice metadata (like we do).

Thats enough


> * OR just get rid of the field (and let the developer set some arbitrary
> array/object of values on registration, to use for filtering when sending).
>
> On 3.11.2015 08:57, Matthias Wessendorf wrote:
> > Hi Ron,
> >
> > thanks for the mail - let me try to bring some light into the dark
> >
> > On Mon, Nov 2, 2015 at 8:38 PM, Ron Smeral <rsmeral at redhat.com <mailto:
> rsmeral at redhat.com>> wrote:
> >
> >     Hi all,
> >
> >     I noticed the "deviceType" field in UPS seems to be used
> inconsistently between Server and the SDKs, and is perhaps underspecified.
> >
> >     The docs only say this much:
> >     https://aerogear.org/docs/unifiedpush/client-registration/
> >     * "deviceType: The device type of the device or the user agent."
> >     - what does "device type of the device" mean? "Type" in what sense?
> >
> >
> >
> > like here:
> >
> https://github.com/aerogear/aerogear-push-ios-demo/blob/master/PushTest/AGAppDelegate.m#L82
> >
> > the iOS API read the type of the device (eg. iPod, iPad, iPhone) etc.
> >
> > It's stored on the server's metadata. Presented to the user, on the
> admin UI, when browsing the registered devices for a Variant. Below is an
> example from our users doc:
> >
> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#_importing_device_metadata
> >
> >
> >
> >     https://aerogear.org/docs/unifiedpush/push-message-format/
> >     * "deviceType: A list of raw device types that should receive the
> message (e.g. Coupon only for iPad and AndroidTablets). The deviceType
> needs to be stored when the device is registering itself with the server."
> >     - what's a "raw device type"?
> >     - "needs to be stored" - who needs to do that? Store where?
> >
> >
> > This API is to actually sent the message to the registered devices -
> device type here is a filter.
> > Example: you have a generic iOS variant, and have a few iPods, a few
> iPhone and a few iPads, this filter allows you to just sent messages to all
> iPhones, by specifiying iphone.
> >
> >
> >
> >
> >
> >     When trying to use the Sender API, the obvious question is: what's
> the list of possible values? The docs don't answer that.
> >
> >
> > here is our current version of the doc:
> >
> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html#POST
> >
> >
> > but we have a new online in a few days (after the 1.1.0.Finall is out)
> >
> >
> >
> >     Another missing piece of information:
> >     * Is the deviceType an arbitrary string set by the user during
> registration?
> >
> >
> > usually that's done by the application (develoiper), not the directly
> the end user of the phone
> >
> >
> >     * Or, is it somehow automatically set by the client SDKs?
> >
> >
> > yeah :-) but not enforced
> >
> >
> >
> >     After a bit of digging through the SDKs and APIs, I can see this
> (not necessarily 100% correct):
> >
> >     * The Sender API accepts arbitrary values
> >
> >     * Android SDK - has deviceType in model, sets to "ANDROID" by default
> >     * Windows SDK - doesn't even have deviceType in model
> >     * iOS SDK - has deviceType in model, doesn't set to any default value
> >
> >     * Cordova Android - doesn't set, so uses "ANDROID"
> >     * Cordova WP8 - not in model, not set
> >     * Cordova iOS - sets UIDevice.model (I can't really read ObjC, just
> a guess by looking at the code)
> >
> >
> >     Can we come up with clearer semantics for the deviceType field?
> >
> >
> > Looks like on Windows it is missing - perhaps we should add that.
> > On Android, I agree the SDK should not set any default here - but I am
> not sure if there is an equivalent API around like UIDevice, which would
> the app developer allow to specifiy the actual device type.
> >
> > Mind filing a few JIRAs against: AGDROID, AGWIN to get the functionality
> baked into the native SDKs, and against AGCORDOVA to get this into there as
> well, once the native bits are done.
> >
>
> I will happily file some JIRAs and make documentation PRs, *once we are
> clear on what the deviceType really is*.
>
> > Great find, Ron!
> >
> >
> >
> >     Thanks,
> >     Ron
> >
> >     --
> >     Ron Smeral
> >     Technical Writer, FeedHenry
> >     Red Hat
> >     Brno
> >     _______________________________________________
> >     aerogear-dev mailing list
> >     aerogear-dev at lists.jboss.org <mailto:aerogear-dev at lists.jboss.org>
> >     https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
> --
> Ron Smeral
> Technical Writer, FeedHenry
> Red Hat
> Brno
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151105/81e6c350/attachment-0001.html 

From edewit at redhat.com  Thu Nov  5 08:35:14 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 5 Nov 2015 14:35:14 +0100
Subject: [aerogear-dev] UPS: deviceType semantics
In-Reply-To: <563B4C8F.3070208@redhat.com>
References: <5637BBAE.8050904@redhat.com>
	<CAAg5f2TOs0UMCTB8Dxm-Om3BzgbCrdhSm_pEnZBstpJZU8j88A@mail.gmail.com>
	<563B4C8F.3070208@redhat.com>
Message-ID: <CAO2B-fYzuLuH0bO1kJcULAxSm_Mz-21yQnPQ1_WE=ghx5fRODA@mail.gmail.com>

>
> * OR just get rid of the field (and let the developer set some arbitrary
> array/object of values on registration, to use for filtering when sending).
>
> Well the user can do that with categories and alias and if you want to use
deviceType for your own purpose you can do that as well.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151105/bfec976b/attachment.html 

From matzew at apache.org  Tue Nov 10 04:49:06 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 Nov 2015 10:49:06 +0100
Subject: [aerogear-dev] Staging of UnifiedPush Java Sender 1.1.0.Final
In-Reply-To: <CAD_dpu3Ct-vTBo0xPn8n=XbuynL8HeoxB9J+54vXTH3ok4F19A@mail.gmail.com>
References: <CAD_dpu3Ct-vTBo0xPn8n=XbuynL8HeoxB9J+54vXTH3ok4F19A@mail.gmail.com>
Message-ID: <CAAg5f2SnWG-u9Lsb5FQF=MDK4WRswDVDmEihWiHRG2H=SGVRGA@mail.gmail.com>

this has been canceled

On Mon, Aug 10, 2015 at 2:51 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Hi Team !
>
> I'm happy to announce that the Java Sender 1.1.0.Final has been staged.
>
> Please test the staged release :
>
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6292
>
> On Thursday I'd like to press the magic button to release it to the wild
>
> Thanks !
>
> Sebi
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151110/4d32baf6/attachment.html 

From matzew at apache.org  Tue Nov 10 04:49:23 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 Nov 2015 10:49:23 +0100
Subject: [aerogear-dev] Staging of UnifiedPush Java Sender 1.1.0.Final
In-Reply-To: <CAAg5f2SnWG-u9Lsb5FQF=MDK4WRswDVDmEihWiHRG2H=SGVRGA@mail.gmail.com>
References: <CAD_dpu3Ct-vTBo0xPn8n=XbuynL8HeoxB9J+54vXTH3ok4F19A@mail.gmail.com>
	<CAAg5f2SnWG-u9Lsb5FQF=MDK4WRswDVDmEihWiHRG2H=SGVRGA@mail.gmail.com>
Message-ID: <CAAg5f2StoLCCPkQK_xZaPxX3vU=5khiORfM6U-R7P1tJ0ttmEQ@mail.gmail.com>

here is the new staging repo:

https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7104/



On Tue, Nov 10, 2015 at 10:49 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> this has been canceled
>
> On Mon, Aug 10, 2015 at 2:51 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Hi Team !
>>
>> I'm happy to announce that the Java Sender 1.1.0.Final has been staged.
>>
>> Please test the staged release :
>>
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6292
>>
>> On Thursday I'd like to press the magic button to release it to the wild
>>
>> Thanks !
>>
>> Sebi
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151110/33fbcff9/attachment.html 

From matzew at apache.org  Tue Nov 10 07:11:26 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 Nov 2015 13:11:26 +0100
Subject: [aerogear-dev] Remove deprecated repos?
Message-ID: <CAAg5f2SBHOu1K1Ok-3X6Kp-JTf+VgHtKZQibGYVjodmk0Wo84g@mail.gmail.com>

Hi,

looking over our repos, for some stats and page views, I noticed a few that
are deprecated, since a quite a while

https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart
https://github.com/aerogear/aerogear-simplepush-quickstart
https://github.com/aerogear/aerogear-aerodoc-backend
https://github.com/aerogear/aerogear-security-hawk
https://github.com/aerogear/aerogear-android-todo
https://github.com/aerogear/aerogear-security-picketlink
https://github.com/aerogear/aerogear-security
https://github.com/aerogear/aerogear-security-shiro
https://github.com/aerogear/aerogear-jaxrs-demo
https://github.com/aerogear/TODO

Also, very much out of date (no?) are the following:

https://github.com/aerogear/aerogear-security-picketbox
https://github.com/aerogear/kitchensink-aerogear-js


What's the plan here? Just remove them, or keep it... and just leave as is.

Thanks,
Matthias


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151110/56fe0a9e/attachment.html 

From lholmqui at redhat.com  Tue Nov 10 08:45:05 2015
From: lholmqui at redhat.com (Luke Holmquist)
Date: Tue, 10 Nov 2015 08:45:05 -0500
Subject: [aerogear-dev] Remove deprecated repos?
In-Reply-To: <CAAg5f2SBHOu1K1Ok-3X6Kp-JTf+VgHtKZQibGYVjodmk0Wo84g@mail.gmail.com>
References: <CAAg5f2SBHOu1K1Ok-3X6Kp-JTf+VgHtKZQibGYVjodmk0Wo84g@mail.gmail.com>
Message-ID: <CALD3Fd1ak9539fgKUZ=iY5uyvDRyiKSZ_r5x60mpFocRLnE5cA@mail.gmail.com>

On Tue, Nov 10, 2015 at 7:11 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> looking over our repos, for some stats and page views, I noticed a few
> that are deprecated, since a quite a while
>
> https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart
> https://github.com/aerogear/aerogear-simplepush-quickstart
>
these 2 have been in the js cookbook for sometime so i think we just get
rid of them


> https://github.com/aerogear/aerogear-aerodoc-backend
> https://github.com/aerogear/aerogear-security-hawk
> https://github.com/aerogear/aerogear-android-todo
> https://github.com/aerogear/aerogear-security-picketlink
> https://github.com/aerogear/aerogear-security
> https://github.com/aerogear/aerogear-security-shiro
> https://github.com/aerogear/aerogear-jaxrs-demo
> https://github.com/aerogear/TODO
>

> Also, very much out of date (no?) are the following:
>
> https://github.com/aerogear/aerogear-security-picketbox
> https://github.com/aerogear/kitchensink-aerogear-js
>
this can probably also be removed also.

>
>
>
> What's the plan here? Just remove them, or keep it... and just leave as
> is.
>

i vote for getting rid of them(maybe make private first),  i some of these
are showing very outdated patterns that we no longer use.

>
> Thanks,
> Matthias
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151110/44f1518a/attachment-0001.html 

From matzew at apache.org  Wed Nov 11 05:41:06 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 11 Nov 2015 11:41:06 +0100
Subject: [aerogear-dev] Staging of UnifiedPush Java Sender 1.1.0.Final
In-Reply-To: <CAAg5f2StoLCCPkQK_xZaPxX3vU=5khiORfM6U-R7P1tJ0ttmEQ@mail.gmail.com>
References: <CAD_dpu3Ct-vTBo0xPn8n=XbuynL8HeoxB9J+54vXTH3ok4F19A@mail.gmail.com>
	<CAAg5f2SnWG-u9Lsb5FQF=MDK4WRswDVDmEihWiHRG2H=SGVRGA@mail.gmail.com>
	<CAAg5f2StoLCCPkQK_xZaPxX3vU=5khiORfM6U-R7P1tJ0ttmEQ@mail.gmail.com>
Message-ID: <CAAg5f2Rd=836HN5C7T5PkqQ4wqePcMprX0pWG6W4hf7TxRo8Kw@mail.gmail.com>

shipped

On Tue, Nov 10, 2015 at 10:49 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> here is the new staging repo:
>
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7104/
>
>
>
> On Tue, Nov 10, 2015 at 10:49 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> this has been canceled
>>
>> On Mon, Aug 10, 2015 at 2:51 PM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> Hi Team !
>>>
>>> I'm happy to announce that the Java Sender 1.1.0.Final has been staged.
>>>
>>> Please test the staged release :
>>>
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6292
>>>
>>> On Thursday I'd like to press the magic button to release it to the wild
>>>
>>> Thanks !
>>>
>>> Sebi
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151111/847dc82a/attachment.html 

From matzew at apache.org  Fri Nov 13 08:34:09 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 13 Nov 2015 14:34:09 +0100
Subject: [aerogear-dev] Remove deprecated repos?
In-Reply-To: <CALD3Fd1ak9539fgKUZ=iY5uyvDRyiKSZ_r5x60mpFocRLnE5cA@mail.gmail.com>
References: <CAAg5f2SBHOu1K1Ok-3X6Kp-JTf+VgHtKZQibGYVjodmk0Wo84g@mail.gmail.com>
	<CALD3Fd1ak9539fgKUZ=iY5uyvDRyiKSZ_r5x60mpFocRLnE5cA@mail.gmail.com>
Message-ID: <CAAg5f2TxWcDe4ZgawyRTsQ2emyzZdPqxD1zmWGahd3Def0Pa=Q@mail.gmail.com>

so...

[] private first
[] delete right away
[] keep repo as is

Please send your feedback!

On Tuesday, 10 November 2015, Luke Holmquist <lholmqui at redhat.com> wrote:

>
>
> On Tue, Nov 10, 2015 at 7:11 AM, Matthias Wessendorf <matzew at apache.org
> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>
>> Hi,
>>
>> looking over our repos, for some stats and page views, I noticed a few
>> that are deprecated, since a quite a while
>>
>> https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart
>> https://github.com/aerogear/aerogear-simplepush-quickstart
>>
> these 2 have been in the js cookbook for sometime so i think we just get
> rid of them
>
>
>> https://github.com/aerogear/aerogear-aerodoc-backend
>> https://github.com/aerogear/aerogear-security-hawk
>> https://github.com/aerogear/aerogear-android-todo
>> https://github.com/aerogear/aerogear-security-picketlink
>> https://github.com/aerogear/aerogear-security
>> https://github.com/aerogear/aerogear-security-shiro
>> https://github.com/aerogear/aerogear-jaxrs-demo
>> https://github.com/aerogear/TODO
>>
>
>> Also, very much out of date (no?) are the following:
>>
>> https://github.com/aerogear/aerogear-security-picketbox
>> https://github.com/aerogear/kitchensink-aerogear-js
>>
> this can probably also be removed also.
>
>>
>>
>>
>> What's the plan here? Just remove them, or keep it... and just leave as
>> is.
>>
>
> i vote for getting rid of them(maybe make private first),  i some of these
> are showing very outdated patterns that we no longer use.
>
>>
>> Thanks,
>> Matthias
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151113/c37f233b/attachment.html 

From corinnekrych at gmail.com  Fri Nov 13 08:42:34 2015
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 13 Nov 2015 14:42:34 +0100
Subject: [aerogear-dev] Remove deprecated repos?
In-Reply-To: <CAAg5f2TxWcDe4ZgawyRTsQ2emyzZdPqxD1zmWGahd3Def0Pa=Q@mail.gmail.com>
References: <CAAg5f2SBHOu1K1Ok-3X6Kp-JTf+VgHtKZQibGYVjodmk0Wo84g@mail.gmail.com>
	<CALD3Fd1ak9539fgKUZ=iY5uyvDRyiKSZ_r5x60mpFocRLnE5cA@mail.gmail.com>
	<CAAg5f2TxWcDe4ZgawyRTsQ2emyzZdPqxD1zmWGahd3Def0Pa=Q@mail.gmail.com>
Message-ID: <CAL8vO=exbrenUfiZiC4Ubm0DCOGOo0WQCA_2NpvKGAcz-QZL6w@mail.gmail.com>

[x] delete right away

Could I add to the list:
https://github.com/aerogear/aerogear-otp-ios-demo
https://github.com/aerogear/aerogear-crypto-ios-demo

Both demo app are now part of ios-cookbook repo.

++
Corinne

On 13 November 2015 at 14:34, Matthias Wessendorf <matzew at apache.org> wrote:

> so...
>
> [] private first
> [] delete right away
> [] keep repo as is
>
> Please send your feedback!
>
>
> On Tuesday, 10 November 2015, Luke Holmquist <lholmqui at redhat.com> wrote:
>
>>
>>
>> On Tue, Nov 10, 2015 at 7:11 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> looking over our repos, for some stats and page views, I noticed a few
>>> that are deprecated, since a quite a while
>>>
>>> https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart
>>> https://github.com/aerogear/aerogear-simplepush-quickstart
>>>
>> these 2 have been in the js cookbook for sometime so i think we just get
>> rid of them
>>
>>
>>> https://github.com/aerogear/aerogear-aerodoc-backend
>>> https://github.com/aerogear/aerogear-security-hawk
>>> https://github.com/aerogear/aerogear-android-todo
>>> https://github.com/aerogear/aerogear-security-picketlink
>>> https://github.com/aerogear/aerogear-security
>>> https://github.com/aerogear/aerogear-security-shiro
>>> https://github.com/aerogear/aerogear-jaxrs-demo
>>> https://github.com/aerogear/TODO
>>>
>>
>>> Also, very much out of date (no?) are the following:
>>>
>>> https://github.com/aerogear/aerogear-security-picketbox
>>> https://github.com/aerogear/kitchensink-aerogear-js
>>>
>> this can probably also be removed also.
>>
>>>
>>>
>>>
>>> What's the plan here? Just remove them, or keep it... and just leave as
>>> is.
>>>
>>
>> i vote for getting rid of them(maybe make private first),  i some of
>> these are showing very outdated patterns that we no longer use.
>>
>>>
>>> Thanks,
>>> Matthias
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>
> --
> Sent from Gmail Mobile
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151113/be367f65/attachment.html 

From lholmqui at redhat.com  Fri Nov 13 08:57:03 2015
From: lholmqui at redhat.com (Luke Holmquist)
Date: Fri, 13 Nov 2015 08:57:03 -0500
Subject: [aerogear-dev] Remove deprecated repos?
In-Reply-To: <CAL8vO=exbrenUfiZiC4Ubm0DCOGOo0WQCA_2NpvKGAcz-QZL6w@mail.gmail.com>
References: <CAAg5f2SBHOu1K1Ok-3X6Kp-JTf+VgHtKZQibGYVjodmk0Wo84g@mail.gmail.com>
	<CALD3Fd1ak9539fgKUZ=iY5uyvDRyiKSZ_r5x60mpFocRLnE5cA@mail.gmail.com>
	<CAAg5f2TxWcDe4ZgawyRTsQ2emyzZdPqxD1zmWGahd3Def0Pa=Q@mail.gmail.com>
	<CAL8vO=exbrenUfiZiC4Ubm0DCOGOo0WQCA_2NpvKGAcz-QZL6w@mail.gmail.com>
Message-ID: <CALD3Fd2B4P8rZGM7W_5cQrsKj3czaWPM_KpF6cqWhxP-GaPQCA@mail.gmail.com>

[X] delete right away


i probably have forks of them all anyway  :)

On Fri, Nov 13, 2015 at 8:42 AM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> [x] delete right away
>
> Could I add to the list:
> https://github.com/aerogear/aerogear-otp-ios-demo
> https://github.com/aerogear/aerogear-crypto-ios-demo
>
> Both demo app are now part of ios-cookbook repo.
>
> ++
> Corinne
>
> On 13 November 2015 at 14:34, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> so...
>>
>> [] private first
>> [] delete right away
>> [] keep repo as is
>>
>> Please send your feedback!
>>
>>
>> On Tuesday, 10 November 2015, Luke Holmquist <lholmqui at redhat.com> wrote:
>>
>>>
>>>
>>> On Tue, Nov 10, 2015 at 7:11 AM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> looking over our repos, for some stats and page views, I noticed a few
>>>> that are deprecated, since a quite a while
>>>>
>>>> https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart
>>>> https://github.com/aerogear/aerogear-simplepush-quickstart
>>>>
>>> these 2 have been in the js cookbook for sometime so i think we just get
>>> rid of them
>>>
>>>
>>>> https://github.com/aerogear/aerogear-aerodoc-backend
>>>> https://github.com/aerogear/aerogear-security-hawk
>>>> https://github.com/aerogear/aerogear-android-todo
>>>> https://github.com/aerogear/aerogear-security-picketlink
>>>> https://github.com/aerogear/aerogear-security
>>>> https://github.com/aerogear/aerogear-security-shiro
>>>> https://github.com/aerogear/aerogear-jaxrs-demo
>>>> https://github.com/aerogear/TODO
>>>>
>>>
>>>> Also, very much out of date (no?) are the following:
>>>>
>>>> https://github.com/aerogear/aerogear-security-picketbox
>>>> https://github.com/aerogear/kitchensink-aerogear-js
>>>>
>>> this can probably also be removed also.
>>>
>>>>
>>>>
>>>>
>>>> What's the plan here? Just remove them, or keep it... and just leave as
>>>> is.
>>>>
>>>
>>> i vote for getting rid of them(maybe make private first),  i some of
>>> these are showing very outdated patterns that we no longer use.
>>>
>>>>
>>>> Thanks,
>>>> Matthias
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>
>> --
>> Sent from Gmail Mobile
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151113/656c4d2b/attachment-0001.html 

From lfryc at redhat.com  Mon Nov 16 14:51:01 2015
From: lfryc at redhat.com (Lukas Fryc)
Date: Mon, 16 Nov 2015 20:51:01 +0100
Subject: [aerogear-dev] verification of JMS workflow
In-Reply-To: <CAAnALH=6XOk0eP1c-sPBx_ywR63WBZ5CPGzw+SjbVo5Jg9sCvw@mail.gmail.com>
References: <CAF_jaDTX3wTyZYUGmq=JXV2haO+0r9X2H3PaJxodQcz=zAWstg@mail.gmail.com>
	<CAAg5f2R06FWcXiOq83oXsHtpqOuUTB_wmtd0xh9Yq-j8O5yC8A@mail.gmail.com>
	<CAAnALH=6XOk0eP1c-sPBx_ywR63WBZ5CPGzw+SjbVo5Jg9sCvw@mail.gmail.com>
Message-ID: <CAAnALHkU4i4j_=w1ZvMNH8wcSz+NLhWBFFfXstwS83tvvC7XYA@mail.gmail.com>

I've discussed this further with Tomas and he told me he successfully
tested that our impl does not exceed given (configured) memory limits.

You have to switch the queue settings to: address-full-policy=BLOCK
(default is PAGE, which can cause exceeding the disk space and perhaps slow
down the node if there are really lot of recipients. which is, well, not
ideal) :-).
The best option would be to use address-full-policy=FAIL. I believe this
will fail transaction and the queue will try to redeliver, but still have
to get to confirming that. (This can be configured to exponential back-off
and try to deliver so many times that it really does its job (such as try
to redeliver after 5 seconds, but repeat that e.g. up to 2 hours, then fail
the message finally as non-deliverable)).

On Thu, Nov 5, 2015 at 10:43 AM, Lukas Fryc <lfryc at redhat.com> wrote:

> I've updated the related issue to track the idea:
> https://issues.jboss.org/browse/AGPUSH-1521
>
> On Thu, Nov 5, 2015 at 9:22 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> awesome, great to hear -
>>
>> For the 1.1.x (mainly 1.1.1 first ;-)) let's see if we can provide an
>> optimized strategy. Lukas was already hinting this on IRC.
>>
>> Tomas, thanks for the updates and the testing effort!
>>
>> On Thu, Nov 5, 2015 at 8:57 AM, Tom?? Hradec <thradec at gmail.com> wrote:
>>
>>> Hi all
>>>
>>> I did some testing of JMS workflow used in UPS during sending
>>> notifications. I can confirm, that suggested blocking strategy, as
>>> protection against OOM errors, works as expected. However in worst scenario
>>> could cause blocking 6 of 20 threads (from MDBs pool). So I would suggest
>>> using different approach, with more optimal resource usage, some options
>>> were discussed already with Lukas.
>>>
>>> Regards
>>> Tomas
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Luk?? Fry?
> Software Engineer
> Red Hat Mobile | AeroGear.org, FeedHenry.org
>



-- 
Luk?? Fry?
Software Engineer
Red Hat Mobile | AeroGear.org, FeedHenry.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151116/a663df09/attachment.html 

From matzew at apache.org  Mon Nov 16 15:40:31 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 16 Nov 2015 21:40:31 +0100
Subject: [aerogear-dev] verification of JMS workflow
In-Reply-To: <CAAnALHkU4i4j_=w1ZvMNH8wcSz+NLhWBFFfXstwS83tvvC7XYA@mail.gmail.com>
References: <CAF_jaDTX3wTyZYUGmq=JXV2haO+0r9X2H3PaJxodQcz=zAWstg@mail.gmail.com>
	<CAAg5f2R06FWcXiOq83oXsHtpqOuUTB_wmtd0xh9Yq-j8O5yC8A@mail.gmail.com>
	<CAAnALH=6XOk0eP1c-sPBx_ywR63WBZ5CPGzw+SjbVo5Jg9sCvw@mail.gmail.com>
	<CAAnALHkU4i4j_=w1ZvMNH8wcSz+NLhWBFFfXstwS83tvvC7XYA@mail.gmail.com>
Message-ID: <CAAg5f2Tmm5KLY3Yow9Q=drr92mvBQJcN8K1mM-Xsnz48ZbtcWQ@mail.gmail.com>

Lukas, Tomas,

good input, on the different settings - can you of you send a PR against
our aerogear.org repo, so that we have this documented in our user guide
for configuration?

On Mon, Nov 16, 2015 at 8:51 PM, Lukas Fryc <lfryc at redhat.com> wrote:

> I've discussed this further with Tomas and he told me he successfully
> tested that our impl does not exceed given (configured) memory limits.
>
> You have to switch the queue settings to: address-full-policy=BLOCK
> (default is PAGE, which can cause exceeding the disk space and perhaps slow
> down the node if there are really lot of recipients. which is, well, not
> ideal) :-).
> The best option would be to use address-full-policy=FAIL. I believe this
> will fail transaction and the queue will try to redeliver, but still have
> to get to confirming that. (This can be configured to exponential back-off
> and try to deliver so many times that it really does its job (such as try
> to redeliver after 5 seconds, but repeat that e.g. up to 2 hours, then fail
> the message finally as non-deliverable)).
>
> On Thu, Nov 5, 2015 at 10:43 AM, Lukas Fryc <lfryc at redhat.com> wrote:
>
>> I've updated the related issue to track the idea:
>> https://issues.jboss.org/browse/AGPUSH-1521
>>
>> On Thu, Nov 5, 2015 at 9:22 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> awesome, great to hear -
>>>
>>> For the 1.1.x (mainly 1.1.1 first ;-)) let's see if we can provide an
>>> optimized strategy. Lukas was already hinting this on IRC.
>>>
>>> Tomas, thanks for the updates and the testing effort!
>>>
>>> On Thu, Nov 5, 2015 at 8:57 AM, Tom?? Hradec <thradec at gmail.com> wrote:
>>>
>>>> Hi all
>>>>
>>>> I did some testing of JMS workflow used in UPS during sending
>>>> notifications. I can confirm, that suggested blocking strategy, as
>>>> protection against OOM errors, works as expected. However in worst scenario
>>>> could cause blocking 6 of 20 threads (from MDBs pool). So I would suggest
>>>> using different approach, with more optimal resource usage, some options
>>>> were discussed already with Lukas.
>>>>
>>>> Regards
>>>> Tomas
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Luk?? Fry?
>> Software Engineer
>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>
>
>
>
> --
> Luk?? Fry?
> Software Engineer
> Red Hat Mobile | AeroGear.org, FeedHenry.org
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151116/270a2015/attachment.html 

From lfryc at redhat.com  Wed Nov 18 06:26:39 2015
From: lfryc at redhat.com (Lukas Fryc)
Date: Wed, 18 Nov 2015 12:26:39 +0100
Subject: [aerogear-dev] verification of JMS workflow
In-Reply-To: <CAAg5f2Tmm5KLY3Yow9Q=drr92mvBQJcN8K1mM-Xsnz48ZbtcWQ@mail.gmail.com>
References: <CAF_jaDTX3wTyZYUGmq=JXV2haO+0r9X2H3PaJxodQcz=zAWstg@mail.gmail.com>
	<CAAg5f2R06FWcXiOq83oXsHtpqOuUTB_wmtd0xh9Yq-j8O5yC8A@mail.gmail.com>
	<CAAnALH=6XOk0eP1c-sPBx_ywR63WBZ5CPGzw+SjbVo5Jg9sCvw@mail.gmail.com>
	<CAAnALHkU4i4j_=w1ZvMNH8wcSz+NLhWBFFfXstwS83tvvC7XYA@mail.gmail.com>
	<CAAg5f2Tmm5KLY3Yow9Q=drr92mvBQJcN8K1mM-Xsnz48ZbtcWQ@mail.gmail.com>
Message-ID: <CAAnALHnc854jzowd10E2eFKEWrzR4cQkdvUc5kzn=eYbnjsyAw@mail.gmail.com>

There is an issue covering that: https://issues.jboss.org/browse/AGPUSH-1420

Should we schedule it for 1.1.1?

On Mon, Nov 16, 2015 at 9:40 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Lukas, Tomas,
>
> good input, on the different settings - can you of you send a PR against
> our aerogear.org repo, so that we have this documented in our user guide
> for configuration?
>
> On Mon, Nov 16, 2015 at 8:51 PM, Lukas Fryc <lfryc at redhat.com> wrote:
>
>> I've discussed this further with Tomas and he told me he successfully
>> tested that our impl does not exceed given (configured) memory limits.
>>
>> You have to switch the queue settings to: address-full-policy=BLOCK
>> (default is PAGE, which can cause exceeding the disk space and perhaps slow
>> down the node if there are really lot of recipients. which is, well, not
>> ideal) :-).
>> The best option would be to use address-full-policy=FAIL. I believe this
>> will fail transaction and the queue will try to redeliver, but still have
>> to get to confirming that. (This can be configured to exponential back-off
>> and try to deliver so many times that it really does its job (such as try
>> to redeliver after 5 seconds, but repeat that e.g. up to 2 hours, then fail
>> the message finally as non-deliverable)).
>>
>> On Thu, Nov 5, 2015 at 10:43 AM, Lukas Fryc <lfryc at redhat.com> wrote:
>>
>>> I've updated the related issue to track the idea:
>>> https://issues.jboss.org/browse/AGPUSH-1521
>>>
>>> On Thu, Nov 5, 2015 at 9:22 AM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> awesome, great to hear -
>>>>
>>>> For the 1.1.x (mainly 1.1.1 first ;-)) let's see if we can provide an
>>>> optimized strategy. Lukas was already hinting this on IRC.
>>>>
>>>> Tomas, thanks for the updates and the testing effort!
>>>>
>>>> On Thu, Nov 5, 2015 at 8:57 AM, Tom?? Hradec <thradec at gmail.com> wrote:
>>>>
>>>>> Hi all
>>>>>
>>>>> I did some testing of JMS workflow used in UPS during sending
>>>>> notifications. I can confirm, that suggested blocking strategy, as
>>>>> protection against OOM errors, works as expected. However in worst scenario
>>>>> could cause blocking 6 of 20 threads (from MDBs pool). So I would suggest
>>>>> using different approach, with more optimal resource usage, some options
>>>>> were discussed already with Lukas.
>>>>>
>>>>> Regards
>>>>> Tomas
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Luk?? Fry?
>>> Software Engineer
>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>
>>
>>
>>
>> --
>> Luk?? Fry?
>> Software Engineer
>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Luk?? Fry?
Software Engineer
Red Hat Mobile | AeroGear.org, FeedHenry.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151118/3bdbd703/attachment-0001.html 

From matzew at apache.org  Wed Nov 18 06:39:18 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 18 Nov 2015 12:39:18 +0100
Subject: [aerogear-dev] verification of JMS workflow
In-Reply-To: <CAAnALHnc854jzowd10E2eFKEWrzR4cQkdvUc5kzn=eYbnjsyAw@mail.gmail.com>
References: <CAF_jaDTX3wTyZYUGmq=JXV2haO+0r9X2H3PaJxodQcz=zAWstg@mail.gmail.com>
	<CAAg5f2R06FWcXiOq83oXsHtpqOuUTB_wmtd0xh9Yq-j8O5yC8A@mail.gmail.com>
	<CAAnALH=6XOk0eP1c-sPBx_ywR63WBZ5CPGzw+SjbVo5Jg9sCvw@mail.gmail.com>
	<CAAnALHkU4i4j_=w1ZvMNH8wcSz+NLhWBFFfXstwS83tvvC7XYA@mail.gmail.com>
	<CAAg5f2Tmm5KLY3Yow9Q=drr92mvBQJcN8K1mM-Xsnz48ZbtcWQ@mail.gmail.com>
	<CAAnALHnc854jzowd10E2eFKEWrzR4cQkdvUc5kzn=eYbnjsyAw@mail.gmail.com>
Message-ID: <CAAg5f2Q+6qr9xbB-V9CcaXO_XmnVWRO-0cgaovZYpoV3_PbRYQ@mail.gmail.com>

+1

On Wed, Nov 18, 2015 at 12:26 PM, Lukas Fryc <lfryc at redhat.com> wrote:

> There is an issue covering that:
> https://issues.jboss.org/browse/AGPUSH-1420
>
> Should we schedule it for 1.1.1?
>
> On Mon, Nov 16, 2015 at 9:40 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Lukas, Tomas,
>>
>> good input, on the different settings - can you of you send a PR against
>> our aerogear.org repo, so that we have this documented in our user guide
>> for configuration?
>>
>> On Mon, Nov 16, 2015 at 8:51 PM, Lukas Fryc <lfryc at redhat.com> wrote:
>>
>>> I've discussed this further with Tomas and he told me he successfully
>>> tested that our impl does not exceed given (configured) memory limits.
>>>
>>> You have to switch the queue settings to: address-full-policy=BLOCK
>>> (default is PAGE, which can cause exceeding the disk space and perhaps slow
>>> down the node if there are really lot of recipients. which is, well, not
>>> ideal) :-).
>>> The best option would be to use address-full-policy=FAIL. I believe this
>>> will fail transaction and the queue will try to redeliver, but still have
>>> to get to confirming that. (This can be configured to exponential back-off
>>> and try to deliver so many times that it really does its job (such as try
>>> to redeliver after 5 seconds, but repeat that e.g. up to 2 hours, then fail
>>> the message finally as non-deliverable)).
>>>
>>> On Thu, Nov 5, 2015 at 10:43 AM, Lukas Fryc <lfryc at redhat.com> wrote:
>>>
>>>> I've updated the related issue to track the idea:
>>>> https://issues.jboss.org/browse/AGPUSH-1521
>>>>
>>>> On Thu, Nov 5, 2015 at 9:22 AM, Matthias Wessendorf <matzew at apache.org>
>>>> wrote:
>>>>
>>>>> awesome, great to hear -
>>>>>
>>>>> For the 1.1.x (mainly 1.1.1 first ;-)) let's see if we can provide an
>>>>> optimized strategy. Lukas was already hinting this on IRC.
>>>>>
>>>>> Tomas, thanks for the updates and the testing effort!
>>>>>
>>>>> On Thu, Nov 5, 2015 at 8:57 AM, Tom?? Hradec <thradec at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi all
>>>>>>
>>>>>> I did some testing of JMS workflow used in UPS during sending
>>>>>> notifications. I can confirm, that suggested blocking strategy, as
>>>>>> protection against OOM errors, works as expected. However in worst scenario
>>>>>> could cause blocking 6 of 20 threads (from MDBs pool). So I would suggest
>>>>>> using different approach, with more optimal resource usage, some options
>>>>>> were discussed already with Lukas.
>>>>>>
>>>>>> Regards
>>>>>> Tomas
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Luk?? Fry?
>>>> Software Engineer
>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>
>>>
>>>
>>>
>>> --
>>> Luk?? Fry?
>>> Software Engineer
>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Luk?? Fry?
> Software Engineer
> Red Hat Mobile | AeroGear.org, FeedHenry.org
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151118/ef16548a/attachment.html 

From Romain.Javornik at saint-gobain.com  Thu Nov 19 05:22:48 2015
From: Romain.Javornik at saint-gobain.com (Javornik, Romain)
Date: Thu, 19 Nov 2015 10:22:48 +0000
Subject: [aerogear-dev] Problem on migrating to 1.1.0-Final
Message-ID: <144EA958C5BCB144849B6DF3DD05867C83008D@EXMB1EU12.za.if.atcsg.net>

Hello,

I don't really know if this is the right email address for asking question but I give it a try, please redirect me if I'm wrong !




------ Problem in the UnifiedPush Server User Guide ------

Before explaining my problem I want to tell you that something isn't clear enough from my point of view in your migration guide (https://aerogear.org/docs/unifiedpush/ups_userguide/index/#migration-guide).

On the part where you explain the database migration for mysql you write :
            MySQL
Inside of the extracted zip file, there is a liquibase-mysql-example.properties, copy that to liquibase.properties.
cp liquibase-mysql-example.properties liquibase.properties
Once done, you need to edit the new file to match your database name and credentials.

The problem with this is that you can't choose the version you want to upgrade to.
Since I have "changeLogFile=liquibase/master.xml" in my liquidbase.properties, the only upgrade I was able to make was to the 1.0.0-Final and I'm on the 1.0.2.
I had to open the ups-migrator.jar (wich wasn't really userfriendly) to see what was my option. And then I was able to go the version I want (exemple -> "changeLogFile=liquibase/1.1.0-Final/releasechanges.xml")

To conclude I think that just a small explanation in the migration guide will make everything more clear.





------ My migration problem ------

I'm currently using AerogearPush Server 1.0.2 and I want to go to the 1.1.0-Final version.

I download the last package (1.1.0-Final) on this page https://aerogear.org/getstarted/downloads

Like explain above I had some trouble make it work to move to the version I wanted.
Right now in 1.0.2 I can use the Migrator Tool to make sure that my 1.0.2 Mysql database is good and to upgrade it to 1.0.3.

But I can't go the 1.1.0-Final, I join to this email the error I get from the Migrator Tool.

Can you please tell me where the problem might come from or if you have any solution ?



Best Regards,
Romain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151119/a970f044/attachment-0001.html 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: error_log_MigrationTool.txt
Url: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151119/a970f044/attachment-0001.txt 

From matzew at apache.org  Thu Nov 19 09:25:00 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 19 Nov 2015 15:25:00 +0100
Subject: [aerogear-dev] Problem on migrating to 1.1.0-Final
In-Reply-To: <144EA958C5BCB144849B6DF3DD05867C83008D@EXMB1EU12.za.if.atcsg.net>
References: <144EA958C5BCB144849B6DF3DD05867C83008D@EXMB1EU12.za.if.atcsg.net>
Message-ID: <CAAg5f2QrEA5YpUWMRea3mi9JHnOC-6mTBwJPwJEk+BAh36Cbbw@mail.gmail.com>

Hi Romain,

unfortunately I don't think the 1.0.2 -> 1.1.0.Final really works. I think
you have to go to 1.0.3 first, before being able to run the migration
towards 1.1.0.Final.




On Thu, Nov 19, 2015 at 11:22 AM, Javornik, Romain <
Romain.Javornik at saint-gobain.com> wrote:

> Hello,
>
>
>
> I don?t really know if this is the right email address for asking question
> but I give it a try, please redirect me if I?m wrong !
>
>
>
>
>
>
>
>
>
> ------ Problem in the UnifiedPush Server User Guide ------
>
>
>
> Before explaining my problem I want to tell you that something isn?t clear
> enough from my point of view in your migration guide (
> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#migration-guide
> ).
>
>
>
> On the part where you explain the database migration for mysql you write :
>             MySQL
>
> Inside of the extracted zip file, there is a
> liquibase-mysql-example.properties, copy that to liquibase.properties.
>
> cp liquibase-mysql-example.properties liquibase.properties
>
> Once done, you need to edit the new file to match your database name and
> credentials.
>
>
>
> The problem with this is that you can?t choose the version you want to
> upgrade to.
>
> Since I have ?changeLogFile=liquibase/master.xml? in my
> liquidbase.properties, the only upgrade I was able to make was to the
> 1.0.0-Final and I?m on the 1.0.2.
>
> I had to open the ups-migrator.jar (wich wasn?t really userfriendly) to
> see what was my option. And then I was able to go the version I want
> (exemple -> ?changeLogFile=liquibase/1.1.0-Final/releasechanges.xml?)
>
>
>
> To conclude I think that just a small explanation in the migration guide
> will make everything more clear.
>
>
>
>
>
>
>
>
>
>
>
> ------ My migration problem ------
>
>
>
> I?m currently using AerogearPush Server 1.0.2 and I want to go to the
> 1.1.0-Final version.
>
>
>
> I download the last package (1.1.0-Final) on this page
> https://aerogear.org/getstarted/downloads
>
>
>
> Like explain above I had some trouble make it work to move to the version
> I wanted.
>
> Right now in 1.0.2 I can use the Migrator Tool to make sure that my 1.0.2
> Mysql database is good and to upgrade it to 1.0.3.
>
>
>
> But I can?t go the 1.1.0-Final, I join to this email the error I get from
> the Migrator Tool.
>
>
>
> Can you please tell me where the problem might come from or if you have
> any solution ?
>
>
>
>
>
>
>
> Best Regards,
>
> Romain
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151119/4be89605/attachment.html 

From matzew at apache.org  Thu Nov 19 09:44:21 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 19 Nov 2015 15:44:21 +0100
Subject: [aerogear-dev] Remove deprecated repos?
In-Reply-To: <CAAg5f2SBHOu1K1Ok-3X6Kp-JTf+VgHtKZQibGYVjodmk0Wo84g@mail.gmail.com>
References: <CAAg5f2SBHOu1K1Ok-3X6Kp-JTf+VgHtKZQibGYVjodmk0Wo84g@mail.gmail.com>
Message-ID: <CAAg5f2QAA4BbPpf_9qSCmo0q_pKcuOs759xnR87bucjXWSBM-A@mail.gmail.com>

So... I thought about this a bit.

all the listed aerogear-security-* repos did push releases out to maven
central. Even we are no longer doing anything there, the stuff is available
and it might be used. Therefore, let's just keep the repos, incase users
need to fork/patch it.

It does not hurt to have these repos, right ?

Regarding the TODO, SP quickstarts and the kitchensink, I think it's fine
to make delete them.... I think :-))


On Tue, Nov 10, 2015 at 1:11 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> looking over our repos, for some stats and page views, I noticed a few
> that are deprecated, since a quite a while
>
> https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart
> https://github.com/aerogear/aerogear-simplepush-quickstart
> https://github.com/aerogear/aerogear-aerodoc-backend
> https://github.com/aerogear/aerogear-security-hawk
> https://github.com/aerogear/aerogear-android-todo
> https://github.com/aerogear/aerogear-security-picketlink
> https://github.com/aerogear/aerogear-security
> https://github.com/aerogear/aerogear-security-shiro
> https://github.com/aerogear/aerogear-jaxrs-demo
> https://github.com/aerogear/TODO
>
> Also, very much out of date (no?) are the following:
>
> https://github.com/aerogear/aerogear-security-picketbox
> https://github.com/aerogear/kitchensink-aerogear-js
>
>
> What's the plan here? Just remove them, or keep it... and just leave as is.
>
> Thanks,
> Matthias
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151119/a0096385/attachment.html 

From lholmqui at redhat.com  Thu Nov 19 09:51:45 2015
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 19 Nov 2015 09:51:45 -0500
Subject: [aerogear-dev] Remove deprecated repos?
In-Reply-To: <CAAg5f2QAA4BbPpf_9qSCmo0q_pKcuOs759xnR87bucjXWSBM-A@mail.gmail.com>
References: <CAAg5f2SBHOu1K1Ok-3X6Kp-JTf+VgHtKZQibGYVjodmk0Wo84g@mail.gmail.com>
	<CAAg5f2QAA4BbPpf_9qSCmo0q_pKcuOs759xnR87bucjXWSBM-A@mail.gmail.com>
Message-ID: <CALD3Fd0Upo7eSp-oks9m_eewf1WuSZcm3Aj=UAQ2BQRkE0y4eQ@mail.gmail.com>

yea,  makes sense.  probably anything that we pushed to a "release place"
should probably stay

On Thu, Nov 19, 2015 at 9:44 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> So... I thought about this a bit.
>
> all the listed aerogear-security-* repos did push releases out to maven
> central. Even we are no longer doing anything there, the stuff is available
> and it might be used. Therefore, let's just keep the repos, incase users
> need to fork/patch it.
>
> It does not hurt to have these repos, right ?
>
> Regarding the TODO, SP quickstarts and the kitchensink, I think it's fine
> to make delete them.... I think :-))
>
>
> On Tue, Nov 10, 2015 at 1:11 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> looking over our repos, for some stats and page views, I noticed a few
>> that are deprecated, since a quite a while
>>
>> https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart
>> https://github.com/aerogear/aerogear-simplepush-quickstart
>> https://github.com/aerogear/aerogear-aerodoc-backend
>> https://github.com/aerogear/aerogear-security-hawk
>> https://github.com/aerogear/aerogear-android-todo
>> https://github.com/aerogear/aerogear-security-picketlink
>> https://github.com/aerogear/aerogear-security
>> https://github.com/aerogear/aerogear-security-shiro
>> https://github.com/aerogear/aerogear-jaxrs-demo
>> https://github.com/aerogear/TODO
>>
>> Also, very much out of date (no?) are the following:
>>
>> https://github.com/aerogear/aerogear-security-picketbox
>> https://github.com/aerogear/kitchensink-aerogear-js
>>
>>
>> What's the plan here? Just remove them, or keep it... and just leave as
>> is.
>>
>> Thanks,
>> Matthias
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151119/cd8e865f/attachment-0001.html 

From paroo at inspeero.com  Sat Nov 21 03:30:46 2015
From: paroo at inspeero.com (Pratik Aroo)
Date: Sat, 21 Nov 2015 14:00:46 +0530
Subject: [aerogear-dev] AeroGear Push Notification
Message-ID: <113a839193299abdfdf5bcf825d23a4a@inspeero.com>

Hi,

I am using aerogear UPS on openshit, I wanted to know if Push 
notification can be sent to specific device by its Device Token, if yes 
then can you provide an demo code for the same. Thanks


Regards,
Pratik A.

From matzew at apache.org  Mon Nov 23 05:44:10 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 23 Nov 2015 11:44:10 +0100
Subject: [aerogear-dev] AeroGear Push Notification
In-Reply-To: <113a839193299abdfdf5bcf825d23a4a@inspeero.com>
References: <113a839193299abdfdf5bcf825d23a4a@inspeero.com>
Message-ID: <CAAg5f2RZMKR=JLpr1VMo1Ec6appX8=TgzRNPGWaPpDj7NuMURQ@mail.gmail.com>

Hi,

not directly, but you could use (on the client) the given device-token (or
registrationID) and use that as the alias. Here is a snippet for iOS/Swift
to perform that in the device registration:

...
clientInfo = deviceToken
...

the full example (expect the above line) for iOS is here:
https://github.com/aerogear/aerogear-ios-push#push-registration

and on the sender API, use the actual alias filed, when sending.

Note you also need to store the device token in that case, so that your app
can use it when the send is triggered

HTH,
Matthias


On Sat, Nov 21, 2015 at 9:30 AM, Pratik Aroo <paroo at inspeero.com> wrote:

> Hi,
>
> I am using aerogear UPS on openshit, I wanted to know if Push
> notification can be sent to specific device by its Device Token, if yes
> then can you provide an demo code for the same. Thanks
>
>
> Regards,
> Pratik A.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151123/ab862ecc/attachment.html 

From matzew at apache.org  Mon Nov 23 05:44:35 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 23 Nov 2015 11:44:35 +0100
Subject: [aerogear-dev] AeroGear Push Notification
In-Reply-To: <CAAg5f2RZMKR=JLpr1VMo1Ec6appX8=TgzRNPGWaPpDj7NuMURQ@mail.gmail.com>
References: <113a839193299abdfdf5bcf825d23a4a@inspeero.com>
	<CAAg5f2RZMKR=JLpr1VMo1Ec6appX8=TgzRNPGWaPpDj7NuMURQ@mail.gmail.com>
Message-ID: <CAAg5f2Stn_j2e4CF1ehCcgWKGrEdHH1p2csVi4v+YaooWTofWw@mail.gmail.com>

clientInfo.alias that is ;)

On Mon, Nov 23, 2015 at 11:44 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> not directly, but you could use (on the client) the given device-token (or
> registrationID) and use that as the alias. Here is a snippet for iOS/Swift
> to perform that in the device registration:
>
> ...
> clientInfo = deviceToken
>
clientInfo.alias that is ;)

> ...
>
> the full example (expect the above line) for iOS is here:
> https://github.com/aerogear/aerogear-ios-push#push-registration
>
> and on the sender API, use the actual alias filed, when sending.
>
> Note you also need to store the device token in that case, so that your
> app can use it when the send is triggered
>
> HTH,
> Matthias
>
>
> On Sat, Nov 21, 2015 at 9:30 AM, Pratik Aroo <paroo at inspeero.com> wrote:
>
>> Hi,
>>
>> I am using aerogear UPS on openshit, I wanted to know if Push
>> notification can be sent to specific device by its Device Token, if yes
>> then can you provide an demo code for the same. Thanks
>>
>>
>> Regards,
>> Pratik A.
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151123/620d80a6/attachment.html 

From Romain.Javornik at saint-gobain.com  Tue Nov 24 08:08:26 2015
From: Romain.Javornik at saint-gobain.com (Javornik, Romain)
Date: Tue, 24 Nov 2015 13:08:26 +0000
Subject: [aerogear-dev] Problem on migrating to 1.1.0-Final
In-Reply-To: <CAAg5f2QrEA5YpUWMRea3mi9JHnOC-6mTBwJPwJEk+BAh36Cbbw@mail.gmail.com>
References: <144EA958C5BCB144849B6DF3DD05867C83008D@EXMB1EU12.za.if.atcsg.net>
	<CAAg5f2QrEA5YpUWMRea3mi9JHnOC-6mTBwJPwJEk+BAh36Cbbw@mail.gmail.com>
Message-ID: <144EA958C5BCB144849B6DF3DD05867C8323AC@EXMB1EU12.za.if.atcsg.net>

Hello Matthias,

I try to do a step by step like you suggest.

The migration of the database between 1.0.2 and 1.03 worked perfectly, but I can?t deploy  unifiedpush-server-as7.war

2015-11-24 11:45:45,457 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment unifiedpush-server-as7.war in 20ms
2015-11-24 11:45:45,458 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"unifiedpush-server as7.war#unifiedpush-default\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"unifiedpush-server-as7.war#unifiedpush-default\": javax.persistence.Persisten
ceException: [PersistenceUnit: unifiedpush-default] Unable to build EntityManagerFactory
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: unifiedpush-default] Unable to build EntityManagerFactory
    Caused by: org.hibernate.HibernateException: Wrong column type in unifiedpush_tmp.VariantMetricInformation for column deliveryStatus. Found: bit, expected: boolean"

I?m currently trying to make some change in the type of the column deliveryStatus to see if it make a difference.

Best Regards,
Romain

De : aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] De la part de Matthias Wessendorf
Envoy? : jeudi 19 novembre 2015 15:25
? : AeroGear Developer Mailing List
Objet : Re: [aerogear-dev] Problem on migrating to 1.1.0-Final

Hi Romain,

unfortunately I don't think the 1.0.2 -> 1.1.0.Final really works. I think you have to go to 1.0.3 first, before being able to run the migration towards 1.1.0.Final.




On Thu, Nov 19, 2015 at 11:22 AM, Javornik, Romain <Romain.Javornik at saint-gobain.com<mailto:Romain.Javornik at saint-gobain.com>> wrote:
Hello,

I don?t really know if this is the right email address for asking question but I give it a try, please redirect me if I?m wrong !




------ Problem in the UnifiedPush Server User Guide ------

Before explaining my problem I want to tell you that something isn?t clear enough from my point of view in your migration guide (https://aerogear.org/docs/unifiedpush/ups_userguide/index/#migration-guide).

On the part where you explain the database migration for mysql you write :
            MySQL
Inside of the extracted zip file, there is a liquibase-mysql-example.properties, copy that to liquibase.properties.
cp liquibase-mysql-example.properties liquibase.properties
Once done, you need to edit the new file to match your database name and credentials.

The problem with this is that you can?t choose the version you want to upgrade to.
Since I have ?changeLogFile=liquibase/master.xml? in my liquidbase.properties, the only upgrade I was able to make was to the 1.0.0-Final and I?m on the 1.0.2.
I had to open the ups-migrator.jar (wich wasn?t really userfriendly) to see what was my option. And then I was able to go the version I want (exemple -> ?changeLogFile=liquibase/1.1.0-Final/releasechanges.xml?)

To conclude I think that just a small explanation in the migration guide will make everything more clear.





------ My migration problem ------

I?m currently using AerogearPush Server 1.0.2 and I want to go to the 1.1.0-Final version.

I download the last package (1.1.0-Final) on this page https://aerogear.org/getstarted/downloads

Like explain above I had some trouble make it work to move to the version I wanted.
Right now in 1.0.2 I can use the Migrator Tool to make sure that my 1.0.2 Mysql database is good and to upgrade it to 1.0.3.

But I can?t go the 1.1.0-Final, I join to this email the error I get from the Migrator Tool.

Can you please tell me where the problem might come from or if you have any solution ?



Best Regards,
Romain

_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151124/cf1af1d2/attachment-0001.html 

From matzew at apache.org  Tue Nov 24 08:40:53 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 24 Nov 2015 14:40:53 +0100
Subject: [aerogear-dev] Problem on migrating to 1.1.0-Final
In-Reply-To: <144EA958C5BCB144849B6DF3DD05867C8323AC@EXMB1EU12.za.if.atcsg.net>
References: <144EA958C5BCB144849B6DF3DD05867C83008D@EXMB1EU12.za.if.atcsg.net>
	<CAAg5f2QrEA5YpUWMRea3mi9JHnOC-6mTBwJPwJEk+BAh36Cbbw@mail.gmail.com>
	<144EA958C5BCB144849B6DF3DD05867C8323AC@EXMB1EU12.za.if.atcsg.net>
Message-ID: <CAAg5f2RD3W_QOGD4OTkuyPvEtBiP86gtjgOoyuW9r0RMA3mfEg@mail.gmail.com>

Hwllo,

I see "as7" - what version of JBoss are you using? We don't really support
the JBoss7.1 server anymore. We have support for WildFly 8 and 9. Bsides
that we have EAP_6.4.0 as one of the supported servers

On Tue, Nov 24, 2015 at 2:08 PM, Javornik, Romain <
Romain.Javornik at saint-gobain.com> wrote:

> Hello Matthias,
>
>
>
> I try to do a step by step like you suggest.
>
>
>
> The migration of the database between 1.0.2 and 1.03 worked perfectly, but
> I can?t deploy  unifiedpush-server-as7.war
>
>
>
> 2015-11-24 11:45:45,457 INFO  [org.jboss.as.server.deployment] (MSC
> service thread 1-1) JBAS015877: Stopped deployment
> unifiedpush-server-as7.war in 20ms
>
> 2015-11-24 11:45:45,458 ERROR [org.jboss.as.server.deployment.scanner]
> (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed
> and was rolled back. Steps that failed:" => {"Operation step-2" =>
> {"JBAS014671: Failed services" =>
> {"jboss.persistenceunit.\"unifiedpush-server as7.war#unifiedpush-default\""
> => "org.jboss.msc.service.StartException in service
> jboss.persistenceunit.\"unifiedpush-server-as7.war#unifiedpush-default\":
> javax.persistence.Persisten
>
> ceException: [PersistenceUnit: unifiedpush-default] Unable to build
> EntityManagerFactory
>
>     Caused by: javax.persistence.PersistenceException: [PersistenceUnit:
> unifiedpush-default] Unable to build EntityManagerFactory
>
>     Caused by: org.hibernate.HibernateException: Wrong column type in
> unifiedpush_tmp.VariantMetricInformation for column deliveryStatus. Found:
> bit, expected: boolean"
>
>
>
> I?m currently trying to make some change in the type of the column
> deliveryStatus to see if it make a difference.
>
>
>
> Best Regards,
>
> Romain
>
>
>
> *De :* aerogear-dev-bounces at lists.jboss.org [mailto:
> aerogear-dev-bounces at lists.jboss.org] *De l**a part de* Matthias
> Wessendorf
> *Envoy? :* jeudi 19 novembre 2015 15:25
> *? :* AeroGear Developer Mailing List
> *Objet :* Re: [aerogear-dev] Problem on migrating to 1.1.0-Final
>
>
>
> Hi Romain,
>
>
>
> unfortunately I don't think the 1.0.2 -> 1.1.0.Final really works. I think
> you have to go to 1.0.3 first, before being able to run the migration
> towards 1.1.0.Final.
>
>
>
>
>
>
>
>
>
> On Thu, Nov 19, 2015 at 11:22 AM, Javornik, Romain <
> Romain.Javornik at saint-gobain.com> wrote:
>
> Hello,
>
>
>
> I don?t really know if this is the right email address for asking question
> but I give it a try, please redirect me if I?m wrong !
>
>
>
>
>
>
>
>
>
> ------ Problem in the UnifiedPush Server User Guide ------
>
>
>
> Before explaining my problem I want to tell you that something isn?t clear
> enough from my point of view in your migration guide (
> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#migration-guide
> ).
>
>
>
> On the part where you explain the database migration for mysql you write :
>             MySQL
>
> Inside of the extracted zip file, there is a
> liquibase-mysql-example.properties, copy that to liquibase.properties.
>
> cp liquibase-mysql-example.properties liquibase.properties
>
> Once done, you need to edit the new file to match your database name and
> credentials.
>
>
>
> The problem with this is that you can?t choose the version you want to
> upgrade to.
>
> Since I have ?changeLogFile=liquibase/master.xml? in my
> liquidbase.properties, the only upgrade I was able to make was to the
> 1.0.0-Final and I?m on the 1.0.2.
>
> I had to open the ups-migrator.jar (wich wasn?t really userfriendly) to
> see what was my option. And then I was able to go the version I want
> (exemple -> ?changeLogFile=liquibase/1.1.0-Final/releasechanges.xml?)
>
>
>
> To conclude I think that just a small explanation in the migration guide
> will make everything more clear.
>
>
>
>
>
>
>
>
>
>
>
> ------ My migration problem ------
>
>
>
> I?m currently using AerogearPush Server 1.0.2 and I want to go to the
> 1.1.0-Final version.
>
>
>
> I download the last package (1.1.0-Final) on this page
> https://aerogear.org/getstarted/downloads
>
>
>
> Like explain above I had some trouble make it work to move to the version
> I wanted.
>
> Right now in 1.0.2 I can use the Migrator Tool to make sure that my 1.0.2
> Mysql database is good and to upgrade it to 1.0.3.
>
>
>
> But I can?t go the 1.1.0-Final, I join to this email the error I get from
> the Migrator Tool.
>
>
>
> Can you please tell me where the problem might come from or if you have
> any solution ?
>
>
>
>
>
>
>
> Best Regards,
>
> Romain
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151124/6c0df24f/attachment.html 

From Romain.Javornik at saint-gobain.com  Tue Nov 24 08:48:47 2015
From: Romain.Javornik at saint-gobain.com (Javornik, Romain)
Date: Tue, 24 Nov 2015 13:48:47 +0000
Subject: [aerogear-dev] Problem on migrating to 1.1.0-Final
In-Reply-To: <CAAg5f2RD3W_QOGD4OTkuyPvEtBiP86gtjgOoyuW9r0RMA3mfEg@mail.gmail.com>
References: <144EA958C5BCB144849B6DF3DD05867C83008D@EXMB1EU12.za.if.atcsg.net>
	<CAAg5f2QrEA5YpUWMRea3mi9JHnOC-6mTBwJPwJEk+BAh36Cbbw@mail.gmail.com>
	<144EA958C5BCB144849B6DF3DD05867C8323AC@EXMB1EU12.za.if.atcsg.net>
	<CAAg5f2RD3W_QOGD4OTkuyPvEtBiP86gtjgOoyuW9r0RMA3mfEg@mail.gmail.com>
Message-ID: <144EA958C5BCB144849B6DF3DD05867C8323FC@EXMB1EU12.za.if.atcsg.net>

Hello,

I?m currently on JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4), do you think it might be the reason of all my trouble ?

De : aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] De la part de Matthias Wessendorf
Envoy? : mardi 24 novembre 2015 14:41
? : AeroGear Developer Mailing List
Objet : Re: [aerogear-dev] Problem on migrating to 1.1.0-Final

Hwllo,

I see "as7" - what version of JBoss are you using? We don't really support the JBoss7.1 server anymore. We have support for WildFly 8 and 9. Bsides that we have EAP_6.4.0 as one of the supported servers

On Tue, Nov 24, 2015 at 2:08 PM, Javornik, Romain <Romain.Javornik at saint-gobain.com<mailto:Romain.Javornik at saint-gobain.com>> wrote:
Hello Matthias,

I try to do a step by step like you suggest.

The migration of the database between 1.0.2 and 1.03 worked perfectly, but I can?t deploy  unifiedpush-server-as7.war

2015-11-24 11:45:45,457 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment unifiedpush-server-as7.war in 20ms
2015-11-24 11:45:45,458 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"unifiedpush-server as7.war#unifiedpush-default\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"unifiedpush-server-as7.war#unifiedpush-default\": javax.persistence.Persisten
ceException: [PersistenceUnit: unifiedpush-default] Unable to build EntityManagerFactory
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: unifiedpush-default] Unable to build EntityManagerFactory
    Caused by: org.hibernate.HibernateException: Wrong column type in unifiedpush_tmp.VariantMetricInformation for column deliveryStatus. Found: bit, expected: boolean"

I?m currently trying to make some change in the type of the column deliveryStatus to see if it make a difference.

Best Regards,
Romain

De : aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org> [mailto:aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>] De la part de Matthias Wessendorf
Envoy? : jeudi 19 novembre 2015 15:25
? : AeroGear Developer Mailing List
Objet : Re: [aerogear-dev] Problem on migrating to 1.1.0-Final

Hi Romain,

unfortunately I don't think the 1.0.2 -> 1.1.0.Final really works. I think you have to go to 1.0.3 first, before being able to run the migration towards 1.1.0.Final.




On Thu, Nov 19, 2015 at 11:22 AM, Javornik, Romain <Romain.Javornik at saint-gobain.com<mailto:Romain.Javornik at saint-gobain.com>> wrote:
Hello,

I don?t really know if this is the right email address for asking question but I give it a try, please redirect me if I?m wrong !




------ Problem in the UnifiedPush Server User Guide ------

Before explaining my problem I want to tell you that something isn?t clear enough from my point of view in your migration guide (https://aerogear.org/docs/unifiedpush/ups_userguide/index/#migration-guide).

On the part where you explain the database migration for mysql you write :
            MySQL
Inside of the extracted zip file, there is a liquibase-mysql-example.properties, copy that to liquibase.properties.
cp liquibase-mysql-example.properties liquibase.properties
Once done, you need to edit the new file to match your database name and credentials.

The problem with this is that you can?t choose the version you want to upgrade to.
Since I have ?changeLogFile=liquibase/master.xml? in my liquidbase.properties, the only upgrade I was able to make was to the 1.0.0-Final and I?m on the 1.0.2.
I had to open the ups-migrator.jar (wich wasn?t really userfriendly) to see what was my option. And then I was able to go the version I want (exemple -> ?changeLogFile=liquibase/1.1.0-Final/releasechanges.xml?)

To conclude I think that just a small explanation in the migration guide will make everything more clear.





------ My migration problem ------

I?m currently using AerogearPush Server 1.0.2 and I want to go to the 1.1.0-Final version.

I download the last package (1.1.0-Final) on this page https://aerogear.org/getstarted/downloads

Like explain above I had some trouble make it work to move to the version I wanted.
Right now in 1.0.2 I can use the Migrator Tool to make sure that my 1.0.2 Mysql database is good and to upgrade it to 1.0.3.

But I can?t go the 1.1.0-Final, I join to this email the error I get from the Migrator Tool.

Can you please tell me where the problem might come from or if you have any solution ?



Best Regards,
Romain

_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151124/525cba4d/attachment-0001.html 

From matzew at apache.org  Tue Nov 24 09:01:46 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 24 Nov 2015 15:01:46 +0100
Subject: [aerogear-dev] Problem on migrating to 1.1.0-Final
In-Reply-To: <144EA958C5BCB144849B6DF3DD05867C8323FC@EXMB1EU12.za.if.atcsg.net>
References: <144EA958C5BCB144849B6DF3DD05867C83008D@EXMB1EU12.za.if.atcsg.net>
	<CAAg5f2QrEA5YpUWMRea3mi9JHnOC-6mTBwJPwJEk+BAh36Cbbw@mail.gmail.com>
	<144EA958C5BCB144849B6DF3DD05867C8323AC@EXMB1EU12.za.if.atcsg.net>
	<CAAg5f2RD3W_QOGD4OTkuyPvEtBiP86gtjgOoyuW9r0RMA3mfEg@mail.gmail.com>
	<144EA958C5BCB144849B6DF3DD05867C8323FC@EXMB1EU12.za.if.atcsg.net>
Message-ID: <CAAg5f2SNhYx3GG1neUg0ChfOV=JTJVBk4fNOFHw1+aFAMeVv1w@mail.gmail.com>

yeah, its using quite old hibernate too

On Tuesday, 24 November 2015, Javornik, Romain <
Romain.Javornik at saint-gobain.com> wrote:

> Hello,
>
>
>
> I?m currently on JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4), do you
> think it might be the reason of all my trouble ?
>
>
>
> *De :* aerogear-dev-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-dev-bounces at lists.jboss.org');>
> [mailto:aerogear-dev-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-dev-bounces at lists.jboss.org');>] *De
> la part de* Matthias Wessendorf
> *Envoy? :* mardi 24 novembre 2015 14:41
> *? :* AeroGear Developer Mailing List
> *Objet :* Re: [aerogear-dev] Problem on migrating to 1.1.0-Final
>
>
>
> Hwllo,
>
>
>
> I see "as7" - what version of JBoss are you using? We don't really support
> the JBoss7.1 server anymore. We have support for WildFly 8 and 9. Bsides
> that we have EAP_6.4.0 as one of the supported servers
>
>
>
> On Tue, Nov 24, 2015 at 2:08 PM, Javornik, Romain <
> Romain.Javornik at saint-gobain.com
> <javascript:_e(%7B%7D,'cvml','Romain.Javornik at saint-gobain.com');>> wrote:
>
> Hello Matthias,
>
>
>
> I try to do a step by step like you suggest.
>
>
>
> The migration of the database between 1.0.2 and 1.03 worked perfectly, but
> I can?t deploy  unifiedpush-server-as7.war
>
>
>
> 2015-11-24 11:45:45,457 INFO  [org.jboss.as.server.deployment] (MSC
> service thread 1-1) JBAS015877: Stopped deployment
> unifiedpush-server-as7.war in 20ms
>
> 2015-11-24 11:45:45,458 ERROR [org.jboss.as.server.deployment.scanner]
> (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed
> and was rolled back. Steps that failed:" => {"Operation step-2" =>
> {"JBAS014671: Failed services" =>
> {"jboss.persistenceunit.\"unifiedpush-server as7.war#unifiedpush-default\""
> => "org.jboss.msc.service.StartException in service
> jboss.persistenceunit.\"unifiedpush-server-as7.war#unifiedpush-default\":
> javax.persistence.Persisten
>
> ceException: [PersistenceUnit: unifiedpush-default] Unable to build
> EntityManagerFactory
>
>     Caused by: javax.persistence.PersistenceException: [PersistenceUnit:
> unifiedpush-default] Unable to build EntityManagerFactory
>
>     Caused by: org.hibernate.HibernateException: Wrong column type in
> unifiedpush_tmp.VariantMetricInformation for column deliveryStatus. Found:
> bit, expected: boolean"
>
>
>
> I?m currently trying to make some change in the type of the column
> deliveryStatus to see if it make a difference.
>
>
>
> Best Regards,
>
> Romain
>
>
>
> *De :* aerogear-dev-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-dev-bounces at lists.jboss.org');>
> [mailto:aerogear-dev-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-dev-bounces at lists.jboss.org');>] *De
> l**a part de* Matthias Wessendorf
> *Envoy? :* jeudi 19 novembre 2015 15:25
> *? :* AeroGear Developer Mailing List
> *Objet :* Re: [aerogear-dev] Problem on migrating to 1.1.0-Final
>
>
>
> Hi Romain,
>
>
>
> unfortunately I don't think the 1.0.2 -> 1.1.0.Final really works. I think
> you have to go to 1.0.3 first, before being able to run the migration
> towards 1.1.0.Final.
>
>
>
>
>
>
>
>
>
> On Thu, Nov 19, 2015 at 11:22 AM, Javornik, Romain <
> Romain.Javornik at saint-gobain.com
> <javascript:_e(%7B%7D,'cvml','Romain.Javornik at saint-gobain.com');>> wrote:
>
> Hello,
>
>
>
> I don?t really know if this is the right email address for asking question
> but I give it a try, please redirect me if I?m wrong !
>
>
>
>
>
>
>
>
>
> ------ Problem in the UnifiedPush Server User Guide ------
>
>
>
> Before explaining my problem I want to tell you that something isn?t clear
> enough from my point of view in your migration guide (
> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#migration-guide
> ).
>
>
>
> On the part where you explain the database migration for mysql you write :
>             MySQL
>
> Inside of the extracted zip file, there is a
> liquibase-mysql-example.properties, copy that to liquibase.properties.
>
> cp liquibase-mysql-example.properties liquibase.properties
>
> Once done, you need to edit the new file to match your database name and
> credentials.
>
>
>
> The problem with this is that you can?t choose the version you want to
> upgrade to.
>
> Since I have ?changeLogFile=liquibase/master.xml? in my
> liquidbase.properties, the only upgrade I was able to make was to the
> 1.0.0-Final and I?m on the 1.0.2.
>
> I had to open the ups-migrator.jar (wich wasn?t really userfriendly) to
> see what was my option. And then I was able to go the version I want
> (exemple -> ?changeLogFile=liquibase/1.1.0-Final/releasechanges.xml?)
>
>
>
> To conclude I think that just a small explanation in the migration guide
> will make everything more clear.
>
>
>
>
>
>
>
>
>
>
>
> ------ My migration problem ------
>
>
>
> I?m currently using AerogearPush Server 1.0.2 and I want to go to the
> 1.1.0-Final version.
>
>
>
> I download the last package (1.1.0-Final) on this page
> https://aerogear.org/getstarted/downloads
>
>
>
> Like explain above I had some trouble make it work to move to the version
> I wanted.
>
> Right now in 1.0.2 I can use the Migrator Tool to make sure that my 1.0.2
> Mysql database is good and to upgrade it to 1.0.3.
>
>
>
> But I can?t go the 1.1.0-Final, I join to this email the error I get from
> the Migrator Tool.
>
>
>
> Can you please tell me where the problem might come from or if you have
> any solution ?
>
>
>
>
>
>
>
> Best Regards,
>
> Romain
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>


-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151124/455018f2/attachment.html 

From spadovani at powowbox.com  Sat Nov 28 10:34:01 2015
From: spadovani at powowbox.com (spi100)
Date: Sat, 28 Nov 2015 08:34:01 -0700 (MST)
Subject: [aerogear-dev] [docker][aerogear-wildfly] Persistence unit
 'ag-push.war#unifiedpush-default' is not available
Message-ID: <1448724841522-12242.post@n5.nabble.com>

Hi, trying to install  the docker  aerogear-wildfly latest version. In the
log, I've got  " Unexpected problem gathering statistics:
java.lang.IllegalStateException: JBAS011477: Persistence unit
'ag-push.war#unifiedpush-default' is not available".

Seen on Mac OX (El Capitan) and Ubuntu 14.04.3 LTS

Has someone got any idea about this issue ?



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/docker-aerogear-wildfly-Persistence-unit-ag-push-war-unifiedpush-default-is-not-available-tp12242.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Mon Nov 30 04:38:32 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 30 Nov 2015 10:38:32 +0100
Subject: [aerogear-dev] [docker][aerogear-wildfly] Persistence unit
 'ag-push.war#unifiedpush-default' is not available
In-Reply-To: <1448724841522-12242.post@n5.nabble.com>
References: <1448724841522-12242.post@n5.nabble.com>
Message-ID: <CAAg5f2Qps1HFx4s1zEGjdx+yAEz5Y5OE6bYD80sf1d3YNH9hxg@mail.gmail.com>

Hello SPI100,

I there is a work-in-progress, see
https://github.com/aerogear/dockerfiles/pull/8/files

However, if you are interested in building the docker images yourself,
please excute the following steps:

1) clone https://github.com/matzew/dockerfiles
2) use the "Centos7_mysql" branch
3) cd into the "wildfly" folder, and execute -> "docker build -t
aerogear/wildfly ."
4) now, cd into the "unifiedpush-wildfly", and run "docker build -t
aerogear/unifiedpush-wildfly ."

After these images are locally built, you need to run two MySQL DBs and
finally the UPS, as described here:
https://github.com/matzew/dockerfiles/tree/Centos7_mysql/wildfly/unifiedpush-wildfly#running-the-image

Thanks for looking into this, I need to finish and finally land the above
mentioned PR :-)

HTH,
Matthias





On Sat, Nov 28, 2015 at 4:34 PM, spi100 <spadovani at powowbox.com> wrote:

> Hi, trying to install  the docker  aerogear-wildfly latest version. In the
> log, I've got  " Unexpected problem gathering statistics:
> java.lang.IllegalStateException: JBAS011477: Persistence unit
> 'ag-push.war#unifiedpush-default' is not available".
>
> Seen on Mac OX (El Capitan) and Ubuntu 14.04.3 LTS
>
> Has someone got any idea about this issue ?
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/docker-aerogear-wildfly-Persistence-unit-ag-push-war-unifiedpush-default-is-not-available-tp12242.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151130/d8f42ec4/attachment-0001.html 

From matzew at apache.org  Mon Nov 30 17:41:32 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 30 Nov 2015 23:41:32 +0100
Subject: [aerogear-dev] Worth to update Node.js build for UPS Admin?
Message-ID: <CAAg5f2QLsEnMNC01UaOLK1dCJW=W9+6FY1+8xFfmwSJ15zLT6w@mail.gmail.com>

Hi folks,

I was wondering if it makes sense to update the Node based build for the
Admin UI of the UPS to use a slightly newer version of Node.js

Currently we are using v0.10.31:
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/admin-ui/pom.xml#L60

I changed that line to v5.1.0 and, to be honest, as expected, it did not
work :-) But, surprisingly an update to something lower (e.g. 0.12.8) did
also not work :-(

That actually made we wonder if this might become a problem, sooner or
later, and if we should be updating the build to use a more modern Node/NPM
version for our build?

Any thoughts (or volunteers :-))
-Matthias

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151130/d68079b5/attachment.html 

From lholmqui at redhat.com  Mon Nov 30 20:53:36 2015
From: lholmqui at redhat.com (Luke Holmquist)
Date: Mon, 30 Nov 2015 20:53:36 -0500
Subject: [aerogear-dev] Worth to update Node.js build for UPS Admin?
In-Reply-To: <CAAg5f2QLsEnMNC01UaOLK1dCJW=W9+6FY1+8xFfmwSJ15zLT6w@mail.gmail.com>
References: <CAAg5f2QLsEnMNC01UaOLK1dCJW=W9+6FY1+8xFfmwSJ15zLT6w@mail.gmail.com>
Message-ID: <CALD3Fd2vATNHzUEt8oZRjNSPg2KEEJg7deQku6QZP+Omem=bCg@mail.gmail.com>

probably would be a good idea to try and update to the latest version.
JIRA? :)

without looking at the dependencies, i'd imagine that some of them need
updating since there were breaking changes going from 0.10 to 0.12

any stack trace for the error.

On Mon, Nov 30, 2015 at 5:41 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi folks,
>
> I was wondering if it makes sense to update the Node based build for the
> Admin UI of the UPS to use a slightly newer version of Node.js
>
> Currently we are using v0.10.31:
>
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/admin-ui/pom.xml#L60
>
> I changed that line to v5.1.0 and, to be honest, as expected, it did not
> work :-) But, surprisingly an update to something lower (e.g. 0.12.8) did
> also not work :-(
>
> That actually made we wonder if this might become a problem, sooner or
> later, and if we should be updating the build to use a more modern Node/NPM
> version for our build?
>
> Any thoughts (or volunteers :-))
> -Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151130/70c93df1/attachment.html 

From lholmqui at redhat.com  Mon Nov 30 20:54:14 2015
From: lholmqui at redhat.com (Luke Holmquist)
Date: Mon, 30 Nov 2015 20:54:14 -0500
Subject: [aerogear-dev] Worth to update Node.js build for UPS Admin?
In-Reply-To: <CALD3Fd2vATNHzUEt8oZRjNSPg2KEEJg7deQku6QZP+Omem=bCg@mail.gmail.com>
References: <CAAg5f2QLsEnMNC01UaOLK1dCJW=W9+6FY1+8xFfmwSJ15zLT6w@mail.gmail.com>
	<CALD3Fd2vATNHzUEt8oZRjNSPg2KEEJg7deQku6QZP+Omem=bCg@mail.gmail.com>
Message-ID: <CALD3Fd0guPo2BKKEwnE1PyTRieZHvB716Ps=uRhrNwd+GkOByQ@mail.gmail.com>

also reply !== volunteering  :) :)


On Mon, Nov 30, 2015 at 8:53 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> probably would be a good idea to try and update to the latest version.
> JIRA? :)
>
> without looking at the dependencies, i'd imagine that some of them need
> updating since there were breaking changes going from 0.10 to 0.12
>
> any stack trace for the error.
>
> On Mon, Nov 30, 2015 at 5:41 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi folks,
>>
>> I was wondering if it makes sense to update the Node based build for the
>> Admin UI of the UPS to use a slightly newer version of Node.js
>>
>> Currently we are using v0.10.31:
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/admin-ui/pom.xml#L60
>>
>> I changed that line to v5.1.0 and, to be honest, as expected, it did not
>> work :-) But, surprisingly an update to something lower (e.g. 0.12.8) did
>> also not work :-(
>>
>> That actually made we wonder if this might become a problem, sooner or
>> later, and if we should be updating the build to use a more modern Node/NPM
>> version for our build?
>>
>> Any thoughts (or volunteers :-))
>> -Matthias
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151130/bf2583b9/attachment.html