Yep indeed coordination is needed, let’s see how we progress on removing AFNetworking dep.
When releasing 1.5 we’ll go either:
0.8.2 => with AFNetworking 2.2.1
or 0.9.0 => without AFNetworking dep
Keep you posted (very soon) on that.
++
Corinne
On 18 Mar 2014, at 10:47, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
But until AG Push registration 0.9 is released , 0.8.1 do not work
with AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) )
Shouldn't it make sense to make a 0.8.2 release with an updated pod (what Corinne
mentionned in the second message) to "fill the gap" until 0.9 is released ?
On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych <corinnekrych(a)gmail.com> wrote:
True, eventually we will remove that dependency.
What about getting 1.5 out of the way and then release AG Push registration 0.9.0 without
AFNetworkin dependency?
sounds good to me!
++
Corinne
On 18 Mar 2014, at 09:53, Matthias Wessendorf <matzew(a)apache.org> wrote:
> Corinne,
>
> no AFN on that project, in the future:
>
https://issues.jboss.org/browse/AGPUSH-558
>
>
>
>
> On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych <corinnekrych(a)gmail.com>
wrote:
> Hello Sebi
>
> Actually PR are on their ways (as we test it) to set proper version, what you need
here
>
https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Po...
> is to upgrade to:
> platform :ios, ‘7.0'
> pod 'AFNetworking', ‘2.2.1'
>
> Note that we’ll support from ios 7.0
> Feel free to send the PR with Podfile update if the testing works for you.
>
> ++
> Thanks for the feedback,
> Corinne
>
> On 18 Mar 2014, at 09:44, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
>
> > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`-
`AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- `AFNetworking/Security`
required by `AFNetworking (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking
(2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`-
`AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- `AFNetworking/UIKit`
required by `AFNetworking (2.2.1)`- `AFNetworking/Serialization` required by
`AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` required by
`AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by
`AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` required by
`AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` required by
`AFNetworking/UIKit (2.2.1)
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)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(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev