Hi Joel,

There are two different issues that have been brought up.  The installer 
program is required to use a mirror to download the latest release (4.16.1) per 
Apache policy.  The installer is failing to fetch the mirror information over 
HTTPS.  We have asked for help from the original developer of our HTTPS 
handling code.

So, as an alternative until that is fixed, I have suggested folks use Apache 
Ant.  One user wrote in to say that the Adobe AIR SDK would not download 
because Ant would not allow a redirection from HTTP to HTTPS, so I just updated 
the AIR 29 URL we download from to HTTPS so there won't be a switch.  So folks 
who have tried Apache Ant to install Apache Flex should try again.

But the installer program will not work for Flex 4.16.1 until we find a way to 
host the release some place without requiring a mirror lookup.  I think 
Justin's original reply on this thread was not quite right and led to confusion.

So, folks wanting to install Apache Flex 4.16.1 should use Ant for now.  But I 
think I've made other changes today so that you can use the installer program 
to Install 4.16.0 and earlier, but you may not be successful using the 
installer program with these older releases and Adobe AIR 28 and 29.  You may 
need to use older releases and older Adobe AIR SDKs.

Hopefully we will get this straightened out soon.

Thanks,
-Alex

On 5/31/18, 3:30 PM, "Joel Tan" <organet...@gmail.com> wrote:

    Hi Justin,
    
    > Look like Alex has updated that UTL to use https, you might want to try
    again.
    Have tried it but still the same timeout issue, I am using the same version
    of installer (3.3.1 Mac) to install, do I need to use the older versions of
    installer instead?
    
    Joel
    
    On Fri, Jun 1, 2018 at 6:21 AM, Justin Mclean <jus...@classsoftware.com>
    wrote:
    
    > Hi,
    >
    > > As what Justin has explained, it is due to the redirection from http to
    > > https issue, this mean even if I use the order version of the installer
    > > will still having the same problem.
    >
    > Look like Alex has updated that UTL to use https, you might want to try
    > again.
    >
    > Thanks,
    > Justin
    

Reply via email to