Don was asking for it to be in the 3.2.x stream. The fix is pretty small so it should be doable for the next point release. -James Jong
On Dec 6, 2013, at 10:05 AM, Carlos Santana <[email protected]> wrote: > The fix is located in cordova-android repo and was landed after last > release 3.2.0, it was picked up by 3.3.x branch, like Steve already > mentioned is going to be in 3.3.0 next week. > > https://github.com/apache/cordova-android/commit/2f66ec60db8749bc442095560d5713b7bb718527 > > This is not a fix on Cordova CLI, the fix in platform android 3.3.0 > > hope this clarifies > > > > > > On Fri, Dec 6, 2013 at 9:40 AM, Michal Mocny <[email protected]> wrote: > >> Or maybe we didn't do a point release for android.. >> >> >> On Fri, Dec 6, 2013 at 9:36 AM, Michal Mocny <[email protected]> wrote: >> >>> I think I marked that fix version, and it was before we did an android >>> 3.2.x point release. I was under the impression that the fix did already >>> make it out in that point release and so we can update JIRA, but I guess >> I >>> should make sure first. >>> >>> Are you saying that the fix isn't in the latest point release, or just >>> pointing out the JIRA metadata is wrong? >>> >>> >>> On Fri, Dec 6, 2013 at 1:03 AM, Joe Bowser <[email protected]> wrote: >>> >>>> I blame Maven. Maven requires JAVA_HOME. (Yes, I had maven installed. >> I'm >>>> not proud of that.) >>>> On Dec 5, 2013 9:36 PM, "Steven Gill" <[email protected]> wrote: >>>> >>>>> It is a bug with Cordova android. We could have tried to do a 3.2.1 >> for >>>>> android but instead are focusing on getting 3.3.0 out next week. >>>>> >>>>> On Thursday, December 5, 2013, Don Coleman wrote: >>>>> >>>>>> I was hoping this fix was going to make 3.2.0-0.4.0 but it looks >> like >>>>> it's >>>>>> marked as 3.3 in JIRA. Would it be difficult to get this fix >>>>>> into 3.2.0-0.5.0? >>>>>> >>>>>> https://issues.apache.org/jira/browse/CB-5422 >>>>>> >>>>>> >>>>>> On Tue, Dec 3, 2013 at 12:08 PM, Marcel Kinard <[email protected] >>>>> <javascript:;>> >>>>>> wrote: >>>>>> >>>>>>> Yeah. It's really cool what works in Cordova, but it's also >>>> embarrasing >>>>>>> what gets broken. Running real end-to-end (in the generic sense) >>>> tests >>>>>> like >>>>>>> a real consumer in a real app-dev workflow should help us catch >> the >>>> bad >>>>>>> parts. I don't think we are exercising end-to-end without >> automated >>>> CI. >>>>>>> >>>>>>> On Dec 3, 2013, at 1:36 AM, Brian LeRoux <[email protected] >> <javascript:;>> >>>>>> wrote: >>>>>>> >>>>>>>> This is really a symptom of how badly we need to get CI running >>>>> again. >>>>>>> The >>>>>>>> hello world workflow being broken is completely unacceptable. >>>>>>> >>>>>> >>>>> >>>> >>> >>> >> > > > > -- > Carlos Santana > <[email protected]>
