On 5/20/14 12:06 AM, "OmPrakash Muppirala" wrote:
>
>> >
>> >I can add the console log tracking right away if you are okay with
>> >releasing that as 3.0.1. Works?
>> Any concerns the log gets too long or is too different so it is hard to
>> track? I was going to try to add some status string
On May 19, 2014 11:59 PM, "Alex Harui" wrote:
>
>
>
> On 5/19/14 11:35 PM, "OmPrakash Muppirala" wrote:
>
> >On May 19, 2014 11:28 PM, "Alex Harui" wrote:
> >>
> >> I believe we don't know if the failure rate is lower with 2.7. It
could
> >> simply be the same, especially if folks are getting a
On 5/19/14 11:35 PM, "OmPrakash Muppirala" wrote:
>On May 19, 2014 11:28 PM, "Alex Harui" wrote:
>>
>> I believe we don't know if the failure rate is lower with 2.7. It could
>> simply be the same, especially if folks are getting as far as antlr,
>>gcc,
>> or some other third-party download b
On May 19, 2014 11:28 PM, "Alex Harui" wrote:
>
> I believe we don't know if the failure rate is lower with 2.7. It could
> simply be the same, especially if folks are getting as far as antlr, gcc,
> or some other third-party download before it fails.
I meant bringing the old Installer back for
I believe we don't know if the failure rate is lower with 2.7. It could
simply be the same, especially if folks are getting as far as antlr, gcc,
or some other third-party download before it fails. That's the funny
part, for all of these failures, we are not getting as many complaints as
I would
Should we perhaps revert back to the earlier version of the Installer while
we investigate this? Or are you sure that debugging and fixing FlexJS
installs would take care if the 4.12.1 SDK installation as well.
Thanks,
Om
On May 19, 2014 9:06 PM, "Alex Harui" wrote:
> At least two folks are cur
At least two folks are currently struggling to get FlexJS installed
properly.
In the next installer we should try to provide more info on where it
failed. If you have time to work on that, please do, otherwise I will get
around to it.
-Alex
On 5/19/14 12:25 AM, "Christofer Dutz" wrote:
>I thi
I think the problems I was having were related to the Website contianing the
BlazeDS libs being insanely slow (Using the browser the page took up to 10
Minutes to show).
This problem should have an effect on any installation. Also have I noticed
this poor performance beeng the regular mode of op
