OK, I think I have fashioned a workaround, but it is past my bedtime here, so I need someone to finish it.
If you look at our website and the recent changes, I added a bunch of properties to flex.a.o/installer/properties/en_US.properties, then copied it to flex.a.o/installer/properties/sdk/en_US.properties The new properties override the properties in the 4.13 install script and the install seemed to work for me. There is a bug in the install script where the log still says it is downloading from opensource.adobe.com even though it is actually downloading from sourceforge. So, assuming AIR urls are working, folks using en_US to install should now be un-blocked. If someone can copy these same properties into the other language files and put those files in the flex.a.o/installer/properties/sdk folder, that should cover most folks. In theory, we don't need .properties files in flex.a.o/installer/properties, but I didn't have time to test that. If there are issues, I'll try to look tomorrow morning. -Alex On 7/30/14 12:23 AM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >> Ok, while not a permanent solution, this [1] seems to indicate that JAR >>is >> 'optional'. > >The download isn't failing it asking for a user name and password before >it tries to download. It optional if you don't want to embed fonts :-) >but yes if you select only the required bits it shoudl work. I just gave >it a go but looks like the AIR urls are now offline as well - what are >they doing? > >A question to consider is should we somehow disable the installer until >the situation is fixed? But looks like Alex is on to it. > >Justin >
