Interesting. The log you posted doesn't show it running through the caching logic, and it just stops as if it didn't get a complete event.
Are you sure caching was on? Or did you turn on verbose logging late? -Alex On 3/7/14 5:55 AM, "Maurice Amsellem" <maurice.amsel...@systar.com> wrote: >I did another try disabling the download cache, and the installation >completes sucessfully. > >HTH. > >Maurice > >-----Message d'origine----- >De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] >Envoyé : vendredi 7 mars 2014 14:47 >À : dev@flex.apache.org >Objet : RE: [DISCUSS] Discuss Release Apache Flex SDK Installer 3.0 - RC4 > >I have tried Installer 3.0 RC4 with FlexJS Nightly / AIR 3.9 : > >I have used directories without spaces, including for download cache: >SDK target: D:\ApacheFlex\FlexJS\SDK >Installer cache: D:\Temp\flex_installer_cache Windows 7, fr > >Installer stops at guava downloading step (9th square) !! >Tried 3 times, always stops at the same step. > >Downloading guava directly from the browser works fine: >http://search.maven.org/remotecontent?filepath=com/google/guava/guava/15.0 >/guava-15.0.jar > >Here is the verbose install log: >https://www.dropbox.com/s/eiqzbvpuzxr67a3/FLEXJS_install_log_KO.txt > >Maurice > >-----Message d'origine----- >De : Kessler CTR Mark J [mailto:mark.kessler....@usmc.mil] >Envoyé : vendredi 7 mars 2014 13:26 >À : dev@flex.apache.org >Objet : RE: [DISCUSS] Discuss Release Apache Flex SDK Installer 3.0 - RC4 > >How about just a busy indicator then while it's loading. It doesn't >require a language and is a universal graphic. > >-Mark > >-----Original Message----- >From: Alex Harui [mailto:aha...@adobe.com] >Sent: Thursday, March 06, 2014 7:40 PM >To: dev@flex.apache.org >Subject: Re: [DISCUSS] Discuss Release Apache Flex SDK Installer 3.0 - RC4 > > > >On 3/6/14 4:06 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > >>>> So, if we're going to do an RC5, what do we want to do about the >> >>> >>jumping: >>> >> >>> >> 1) nothing >>> >> 2) don't show any window at all (visible=false) until the strings >>>are in >>> >> and the window is position. This could make start up seem slower. >>> >> 3) don't reposition the window. >>> >> 4) other ideas? >>> >> >>> > >>> >Can we load the strings after the window center's itself on the >>>screen? >>> Also possible, but then the screen appears blank for a bit, then the >>> strings appear. >>> >>> Thoughts? >>> -Alex >>> >>> >>It appears blank initially anyways before the jump. At least if we >>center >>it right away, there wont be a jump. I think having it blank for a few >>seconds is okay. >> >>Maybe would could have all the dropdowns show a default label of >>"Loading..." so that it does not appear blank. >Interesting idea, but that will be in English since we are waiting to load >the default localized strings. Maybe I'll look into putting up a busy >cursor. > >-Alex >
