Re: 4.16.0 Install issues

Be sure to test on Windows 7. It has an older version of PowerShell, so some things that work in newer versions may not work there. I had the unzip working on Windows 10 after a long day of wrapping my head around running PowerShell from AIR. The next morning, I discovered that I had to redo it

Re: 4.16.0 Install issues

I think that was the direction I was going to go. Thanks! On Fri, Jul 7, 2017 at 11:30 AM, Josh Tynjala wrote: > In addition to MD5, the code the installer uses to unzip files can also > cause Error #1000. > > I came up with a solution for that using PowerShell that I

Re: 4.16.0 Install issues

In addition to MD5, the code the installer uses to unzip files can also cause Error #1000. I came up with a solution for that using PowerShell that I posted on the mailing list:

Re: 4.16.0 Install issues

I'm looking at the 4.16.0 release package, not what is in the source tree. That's why I was asking at first if anybody was working on it to make sure it hadn't been tackled, or nobody was actively working on the fix. -Nick On Fri, Jul 7, 2017 at 11:12 AM, Alex Harui

Re: 4.16.0 Install issues

What version of installer.xml are you looking at? I just synced up the develop branch in flex-sdk and took a look at there are merge conflict markers in the file! Apparently, nobody has tried to install a nightly build of Flex SDK. But I think the version from the release branch has the right

Re: 4.16.0 Install issues

I installed the latest version of Java, but didn't touch the JCE (I have to keep the standard set on my machine and extend, per project because of some of the other projects I'm working on). Just using the net.url package within a quick java app seems grab the files from sourceforge with no

Re: 4.16.0 Install issues

It would be great if anyone who can will add to that jira any hint for someone who will be working on that. I have other things on my plate right now. Thanks, Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context:

Re: 4.16.0 Install issues

Cool! I missed seeing this JIRA. I took a quick look and didn't see spline conversion handling between TTF and CFF. I think it may not handle specifying a TTF file for embedAsCFF=true and vice versa. But maybe we can live without it. Any volunteers to take this on? -Alex On 7/6/17, 10:01

Re: 4.16.0 Install issues

Maybe I wasn't clear enough: I don't think the version of Ant will affect the SSL issues. The SSL issues should be solvable via the JCE upgrade: http://stackoverflow.com/questions/38203971/javax-net-ssl-sslhandshakeexcep tion-received-fatal-alert-handshake-failure/38264878#38264878 I'm not

Re: 4.16.0 Install issues

Nicholas Kwiatkowski-2 wrote > - Re-creating Fontkit. Chris Dutz said he might be able to work on it, > but I havent seen anything else to that affect. At ApacheCon somebody found a lib that maybe contains a working FontKit port. Piotr created a JIRA that contains the link [1] HTH, Olaf

Re: 4.16.0 Install issues

I remember reading about needing the latest ANT, so I installed 1.10.1 and 1.9.9 on my Windows 10 machine with the latest Java 8 install and still had the SSL errors. I just read through the threads where where there was a discussion about it. There were three things talked about : - Having

Re: 4.16.0 Install issues

Hi Nick, As for the font encoding we had discussion about that at ApacheCon [1] and I raised jira [2] [1] http://apache-flex-development.247.n4.nabble.com/ApacheCon-FlexJS-Summit-FlexJS-1-0-Discussion-Round-Summary-td61700.html [2] https://issues.apache.org/jira/browse/FLEX-35315 Piotr

Re: 4.16.0 Install issues

I'm not spending any time on the installer other than occasionally pondering if there is some other workaround we could deploy. I'm waiting on Adobe to put out a 64-bit native installer. IMO, that's the least work on our part, but not sure when Adobe will push that out. The SSL errors from

4.16.0 Install issues

Is anybody actually addressing the issues people have been reporting about the installer and/or ANT script for Flex SDK 4.16.0? Right now I see two major issues that are preventing even people who are familiar with the SDK from doing installs : - In the installer, selecting AIR 25.0 gives users

Re: 4.16.0 Install issues (was Re: [ANNOUNCE] Apache Flex 4.16.0 released)

You can use FP/AIR 23 and older then use one of the upgrade scripts. +1 for this approach. I think we should add these steps to a wiki page and keep it handy for folks who want this. In fact, simply copying over a different AIR SDK should work as well. Thanks, Om

Re: 4.16.0 Install issues (was Re: [ANNOUNCE] Apache Flex 4.16.0 released)

On 3/16/17, 12:25 PM, "Nicholas Kwiatkowski" wrote: >I think there is some reason to use very old versions of AIR ( < 4), but >between AIR 4 and 23 it should be ok. Do you know if it effects the old >ones (which still support some older OSs)? Probably. The

Re: 4.16.0 Install issues (was Re: [ANNOUNCE] Apache Flex 4.16.0 released)

I think there is some reason to use very old versions of AIR ( < 4), but between AIR 4 and 23 it should be ok. Do you know if it effects the old ones (which still support some older OSs)? -Nick On Thu, Mar 16, 2017 at 2:54 PM, Alex Harui wrote: > Adding dev@... > > I just

4.16.0 Install issues (was Re: [ANNOUNCE] Apache Flex 4.16.0 released)

Adding dev@... I just noticed that there is a bug in the installer.xml and the Installer will not install 4.16.0 on Mac with FP/AIR 23 and older. It will only work with FP/AIR 24 and newer. I haven't tried Windows, but it should be ok. I am hopeful very few people will want to install 4.16