Re: Flash Player end of life
Hi, > I would already be interested in how Adobe can make the flash player no > longer play SWF. I believe recent versions of the flash player have this feature built into them. I was pointed to this thread [1] which include info about how to change mmc.cfg to disable uninstalling and updating and add a white list. Something like this: EOLUninstallDisable=1 SilentAutoUpdateEnable=0 EnableAllowList=1 AutoUpdateDisable=1 ErrorReportingEnable=1 AllowListUrlPattern=http://localhost/ <http://localhost/> For more info on the options see chapter 4 in [2] > Also, in any case I believe that Adobe Air stays unaffected by this as well > - and it's terribly easy to migrate a Flex Web Application to a Flex > Desktop Application with Air. Does anybody know whether any of the EOL > actions also apply to the Air runtime? My understanding is that they do not. Thanks, Justin 1. https://community.adobe.com/t5/flash-player/adobe-flash-availability-after-2020/td-p/10929047?page=1 <https://community.adobe.com/t5/flash-player/adobe-flash-availability-after-2020/td-p/10929047?page=1> 2. https://www.adobe.com/content/dam/acom/en/devnet/flashplayer/articles/flash_player_admin_guide/pdf/latest/flash_player_32_0_admin_guide.pdf <https://www.adobe.com/content/dam/acom/en/devnet/flashplayer/articles/flash_player_admin_guide/pdf/latest/flash_player_32_0_admin_guide.pdf>
Flash Player end of life
Hi, I notice on [1] it states this: In December, Chrome 55 will make HTML5 the default experience, except for sites which only support Flash Which I assume means a URL ending .swf? And on [2] it states: Since Adobe is no longer supporting Flash Player after the EOL Date, Adobe will block Flash content from running in Flash Player beginning January 12, 2021 to help secure users’ systems. If this is correct? If so that give a very limited window for "sites which only support Flash” to work. Does anyone know anything different? Thanks, Justin 1. https://blog.google/products/chrome/flash-and-chrome/ 2. https://www.adobe.com/products/flashplayer/end-of-life.html
Re: [Vote] Release flex-dk-converter-maven-extension
Hi, +1 (binding) Generally to want to cancel the editing vote and create a new thread when voting on a new RC, otherwise is may not be clear what people are voting on. I checked RC2: - Signatures and hashes fine - LICENSE and NOTICE fine - No unexpected binary files - All source files have ASF headers - Can compile from source (ion OSX using Java 1.8 and Apache Maven 3.3.9) I didn’t check if this works, after compiling what the easiest way to do that? Thanks, Justin
Re: [Vote] Release flex-dk-converter-maven-extension
Hi, > Since this is not a flex-sdk release, we just want to release that piece of > code. In that case you need something to check (a release candidate) for people to vote on, otherwise it’s not a release. Thanks, Justin
Re: [Vote] Release flex-dk-converter-maven-extension
HI, Where’s the release candidate to vote on? Thanks, Justin
[JOB] Moonshine-IDE.com is hiring contractors to bring Apache Royale to version 1.0
Hi everyone, Unless I missed it, we got absolutely no bids by the original Friday May 3 deadline. I am disappointed, since I get the impression there are several of you on here who could make meaningful documentation impact with probably 5 hours of your time. Half of a Saturday or Sunday should be worth some $ and the knowledge of knowing you are helping bring Royale 1.0 into existence. Please, consider submitting a proposal even though the deadline is past. Please submit a proposal, which will make it worth your while professionally to dig in for a few hours. The community with thank you immensely, and you will get paid! I have posted the job to UpWork: https://www.upwork.com/ab/applicants/1124571121626791936/job-details Please spread the word again. Justin Hill === Subject: [JOB] Moonshine-IDE.com hiring contractors to bring Apache Royale to version 1.0 Royale helps modernize Flex applications AND provides a great way to revitalize the next generation Flex ecosystem as a viable alternative to Javascript solutions such as React, Angular, and Vue. Get paid to help bring Apache Royale to version 1.0! Prominic is the company developing the Moonshine IDE for Flex and Royale. Prominic is willing to pay developers to help bring Royale to market as 1.0. To apply: 1) join the d...@royale.apache.org mailing list 2) review the recent discussions on what needs to be fixed on Nabble: http://apache-royale-development.20373.n8.nabble.com 3) Submit to the d...@royale.apache.org mailing list your bid for assistance to the group by Friday May 3 The Moonshine-IDE.com team is willing to donate $2,500 USD in total over the next 30 days to anyone who can accomplish agreed upon tasks to help Royale release a 1.0 version. IF you who are willing to step up to the plate immediately (with a deliverable no later than May 26, 2019) to help with: * documentation (ASDoc style) * examples (code snippets that do things like Tour de Royale) * tutorials (well written, friendly, understandable, educational material) * a mini reproduction of the aforementioned Flex In a Week Series (great idea!) https://www.adobe.com/devnet/flex/videotraining.html * build automation * automated test cases * creation of a summary comparison table showing Royale relative to React, Vue, Angular * a longer write up of competitive articles detailed why Royale is important. BTW, one reason it can be important is because it is NOT controlled by giant companies. * a directory of consultants for hire: * OR anything else you would want to see in a 1.0 version of Royale THEN Please submit to this public group your commitment and cost. We will then do this democratically: deadline for bid submissions is 7 days from now -- Friday May 3. Folks on this mailing list should offer their thoughts and opinions on the bids. Carlos (or someone who knows Twitter enough to create another poll) will then do another Twitter vote poll for 3 days to see what folks think of the various proposals. Prominic alone will decide which bids it will pay for taking into consideration the discussion threads. Ideally multiple people will commit to doing something "small" for $500 each and Prominic can award 5 people the projects. The $2,500 USD total will be paid via PayPal. No exceptions. Please note that the work you do may not be accepted into the project repos. If your work is not accepted, Prominic will work with you and the project on next steps. Your work may end up on the Moonshine-IDE site or other places. Prominic cannot dictate production deadlines for an Apache project so If the 30 day and 60 day deadlines are not met, Prominic reserves the right to change the offer or its deadlines. Prominic is not the only business entity involved with Royale and encourages other business entities to make similar offers to help Royale mature to be your solution for building applications for web/mobile/desktop. IF within 30 days Apache Royale 1.0 is released to the public then the Moonshine-IDE.com team will again donate $2,500 for the month of June in an identical voting scenario (assuming this one works well) to bring home a 1.1 release. By 60 days from now, a new user who has never seen Royale before or programmed in ActionScript should be able to: 1) Arrive at the Apache Royale web page 2) Understand from the home page why they should care about the project if they come from React, Vue, Angular, Flex, or ActionScript worlds 3) Be able to within 5 mouse clicks (download button, install button, launch button, build button, run button) go from having nothing on their machine to having an IDE (we of course volunteer Moonshine but Visual Studio Code should
Get paid to help bring Apache Royale to version to 1.0 -- submit your bid for assistance to the group by Friday May 3
Royale helps modernize Flex applications AND provides a great alternative to revitalize the next generation Flex ecosystem as a viable alternative to Javascript solutions such as React, Angular, and Vue. Get paid to help bring Apache Royale to version 1.0! If you are interested in getting paid to help bring Royale to market as 1.0 then: 1) join the d...@royale.apache.org mailing list 2) review the recent discussions on what needs to be fixed on Nabble: http://apache-royale-development.20373.n8.nabble.com 3) Submit to the d...@royale.apache.org mailing list your bid for assistance to the group by Friday May 3 The Moonshine-IDE.com team is willing to donate $2,500 USD in total over the next 30 days to anyone who can accomplish what Alex and Carlos want to see happen to call it release 1.0. IF you who are willing to step up to the plate immediately (with a deliverable no later than May 26, 2019) to help with: * documentation (ASDoc style) * examples (code snippets that do things like Tour de Royale) * tutorials (well written, friendly, understandable, educational material) * a mini reproduction of the aforementioned Flex In a Week Series (great idea!) https://www.adobe.com/devnet/flex/videotraining.html * build automation * automated test cases * creation of a summary comparison table showing Royale relative to React, Vue, Angular * a longer write up of competitive articles detailed why Royale is important. BTW, one reason it can be important is because it is NOT controlled by giant companies. * a directory of consultants for hire: * OR anything else Alex and Carlos specifically need to be convinced to push to 1.0 release THEN Please submit to this public group your commitment and cost. We will then do this democratically: deadline for bid submissions is 7 days from now -- Friday May 3. Carlos (or someone who knows Twitter enough to create another poll) will then do another Twitter vote poll for 3 days to decide who gets the bids Ideally multiple people will commit to doing something "small" for $500 each and we can award 5 people the projects. The $2,500 USD total will be paid via PayPal. No exceptions. IF within 30 days Apache Royale 1.0 is released to the public then the Moonshine-IDE.com team will again donate $2,500 for the month of June in an identical voting scenario (assuming this one works well) to bring home a 1.1 release. By 60 days from now, a new user who has never seen Royale before or programmed in ActionScript should be able to: 1) Arrive at the Apache Royale web page 2) Understand from the home page why they should care about the project if they come from React, Vue, Angular, Flex, or ActionScript worlds 3) Be able to within 5 mouse clicks (download button, install button, launch button, build button, run button) go from having nothing on their machine to having an IDE (we of course volunteer Moonshine but Visual Studio Code should be a goal for this, too) on their machine with a successful build of their first "hello world". No command line nonsense. No learning NPM, Git, downloading 20 required packages. See Royale website. Want to try it. 5 clicks later build your Hello World. If the above 3 goals are met, then the Moonshine-IDE.com team will run a 3rd donation round of $2,500 for the month of July in a manner to the description above to bring home a 1.2 release, to be published no later than the end of July 2019 for the awards to be paid. Hopefully this helps motivate the team. Thank you, Justin Hill
Re: [Vote] Moving JIRA issues and Confluence Wiki to GitHub
Hi, +0 I see little reason to change and split where you need to look at things in two places. I assume that JIRA and Confluence will not be made read only? Thanks, Justin
Re: Enabling GitHub "Issues" and "Wiki" for flex repositories
Hi, > I think it would be easier and more transparent for folks to handle future > development (if it will happen) by using GitHub. i’m that sure that it is. JIRA has a number of significant benefits over GitHub issues including better searching and querying. (Yes I use both). Do we know if it possible it import all historical JIRA issues (open and closed) into git issues? And if we do what if anything do we loose? Don’t forget the old Adobe issues are also in JIRA and having a history of which bugs have been resolved or not is very useful. Thanks, Justin
Re: [2/2] git commit: [flex-utilities] [refs/heads/develop] - switch to AIR 30 so we can use TLSSocket against TLS1.2. Replace the as3crypto TLSSocket with our own that uses AIR 30 SecureSocket
Hi, I don’t believe this is the correct way to handle this ie by replacing the 3rd party headers with ASF even though changes have been made. Can you point me to the original code? Changes to 3rd party files are generally made under the original license and changes need to be major before adding an ASF header. You might want to read this [1] that come up on the incubator general list recently about the same issue. Also are you including the full text of the BSD license anywhere (perhaps it’s in another check in and I missed it) as that is required by the BSD license? Thanks, Justin 1. https://lists.apache.org/thread.html/111ce40196f4f81c9b394fc7399298f72f7afc8d3cc144ed0f6320cc@%3Cgeneral.incubator.apache.org%3E
Re: Installer is Timing Out.
Hi, Do we really want to go with a service that states "this is a free service, so there are no uptime or support guarantees.". I not sure we even have an issue with downloading the binary connivance releases so why do we need to move them from where they currently are? Justin On Tue, Jun 12, 2018 at 12:05 PM, OmPrakash Muppirala wrote: > Rawgit might be a good option for us: https://rawgit.com/ > > If no one has objections, I can set this up. > > Thanks, > Om > > On Mon, Jun 11, 2018, 5:12 PM Alex Harui wrote: > > > Also, I think if we can find a volunteer to host the entire binary folder > > (and thus pay the bandwidth costs) that will solve the problem without > > requiring an update to the installer. > > > > My 2 cents, > > -Alex > > > > On 6/11/18, 5:05 PM, "Alex Harui" wrote: > > > > Hmm. Are you proposing a new release of the installer? The location > > of the apache-flex-sdk-installer-config.xml is supposed to be > > release-specific. Each release can have its own version in case we need > to > > change steps in the release, so I don't think we want to hardcode it to > the > > URL you are using for testing. > > > > Did you say that if you use https to access this file on our website > > that it also fails? I find that really interesting if you are also > saying > > that the install does complete if we use https to download some of the > > artifacts like AIR29. Can you verify that this is only an issue for > > hitting apache.org sites via HTTPS and make sure your AIR29 didn't come > > out of the download cache? > > > > If it is an HTTPS for apache.org only, I think we want to understand > > why and build a really small test case to show Infra. Because if they > made > > a config change on apache.org/dist, if one of the other places we > > download from make the same change we will be stuck again. > > > > Thoughts? > > -Alex > > > > On 6/11/18, 1:25 PM, "Piotr Zarzycki" > > wrote: > > > > I simply placed link here [1]. > > > > APACHE_FLEX_BIN_INSTALLER_URL = > > " > > https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fflex.apache.org%2Finstaller%2Fapache-flex-sdk- > installer-config.xml=02%7C01%7Caharui%40adobe.com% > 7Ceda63602f32e4a98d35f08d5cfd97c84%7Cfa7b1b5a7b34438794aed2c178de > cee1%7C0%7C0%7C636643455386260834=8%2FKeViaRU2QlsM%2BDVqI9% > 2B5VwFRaoR3cYywVPiD8iiI4%3D=0 > > " > > > > > > [1] > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbit.ly% > 2F2JC5dcX=02%7C01%7Caharui%40adobe.com%7Ceda63602f32e4a98d35f08d5cfd9 > 7c84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1% > 7C636643455386260834=k3wKVwi2OH9dwPoTXlvYz4gKQnNs85 > II6JxH7GUSMPE%3D=0 > > > > pon., 11 cze 2018 o 22:10 Alex Harui > > napisał(a): > > > > > But what code knew to start looking at the website instead of > > dist? > > > Didn't something else need to change? I'm trying to understand > > all of the > > > pieces. > > > > > > -Alex > > > > > > On 6/11/18, 12:34 PM, "Piotr Zarzycki" < > > piotrzarzyck...@gmail.com> wrote: > > > > > > Alex, > > > > > > When we are trying to read following file [1], we are > > getting time out > > > in > > > installer. I moved that file to our website [2] and locally > > tested > > > installer. - I got positive results. It's started to work. > > > > > > [1] > > > > > > > > https://na01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fwww.apache.org%2Fdist%2Fflex%2F4.16.1% > 2Fbinaries%2Fapache-flex-sdk-installer-config.xml=02% > 7C01%7Caharui%40adobe.com%7C8cf556e5bf954296e05908d5cfd26258% > 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636643424854057105= > WaA3FpmHKJuhJI5Dpvxy6gfIBXOYBNg862fzTpLSucQ%3D=0 > > > [2] > > > > > https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fflex.apache.org%2Finstaller%2Fapache-flex-sdk- > installer-config.xml=02%7C01%7Caharui%40adobe.com% > 7C8cf556e5bf954296e05908d5cfd26258%7Cfa7b1b5a7b34438794aed2c178de > cee1%7C0%7C0%7C636643424854057105=nRM0G2Vsc3uVg9sg3SEiF% > 2FnKzmO34dUJACfhl47MbEc%3D=0 > > > > > > Thanks, > > > Piotr > > >
Re: Installer is Timing Out.
No I'm not suggesting that. AFAIK it's only the config text file that Prior wants to host. On Mon., 11 Jun. 2018, 8:47 am Alex Harui, wrote: > Justin, > > Are you suggesting that we distribute a binary artifact from our project > website? Do other projects do that? > > -Alex > > On 6/10/18, 10:27 PM, "Justin Mclean" wrote: > > Hi, > > > I'm talking about that file [1]. What kind of security issues do you > > exactly see if I move that file on my server ? > > Well if someone changed the paths in those files, our users could > unwitting be made to download walware or other stuff. Risk is probably low > but I have no details on the server this file is going on, for instance it > it a dedicated server or one that contains shared hosts for instance. What > other services are running on this server? How is the file uloaded/updated > on that server? What security is in place to stop others modifying that > file? If it located in Poland is that going to cause performance issues for > people outside of Europe? What happens if the server falls overs can > someone on the PMC restart it? Will the rest of the PMC have access to this > server? Might be best to answer on the private list if you don’t want > details about your server made public. > > Perhaps a better solution would be to host them on the Apache Flex > website as currently we do for [1] which the installer gets. Is it too hard > to have a > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflex.apache.org%2Finstaller%2FXXX%2Fsdk-installer-config-4.0.xml=02%7C01%7Caharui%40adobe.com%7Cbe3b60c824884a383f7d08d5cf5c1704%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636642916791710330=CUrCENwFIuMoAtvJnjoNXT9o41rbsXGXojcwa5QH%2Bys%3D=0, > were XXX if the flex version number as well? Given the issue is only with > 4.16.0 and 4.16.1that’s only two files we would need to host there. That > way access and security are handled by ASF infrastructure and we don’t have > to worry about them. > > Thanks, > Justin > > 1. > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflex.apache.org%2Finstaller%2Fsdk-installer-config-4.0.xml=02%7C01%7Caharui%40adobe.com%7Cbe3b60c824884a383f7d08d5cf5c1704%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636642916791710330=2ld9NbW8Uar2ARRbaXv14uQ1cNN2U2ZIxWjqpnJdqX0%3D=0 > > > >
Re: Installer is Timing Out.
Hi, > I'm talking about that file [1]. What kind of security issues do you > exactly see if I move that file on my server ? Well if someone changed the paths in those files, our users could unwitting be made to download walware or other stuff. Risk is probably low but I have no details on the server this file is going on, for instance it it a dedicated server or one that contains shared hosts for instance. What other services are running on this server? How is the file uloaded/updated on that server? What security is in place to stop others modifying that file? If it located in Poland is that going to cause performance issues for people outside of Europe? What happens if the server falls overs can someone on the PMC restart it? Will the rest of the PMC have access to this server? Might be best to answer on the private list if you don’t want details about your server made public. Perhaps a better solution would be to host them on the Apache Flex website as currently we do for [1] which the installer gets. Is it too hard to have a http://flex.apache.org/installer/XXX/sdk-installer-config-4.0.xml, were XXX if the flex version number as well? Given the issue is only with 4.16.0 and 4.16.1that’s only two files we would need to host there. That way access and security are handled by ASF infrastructure and we don’t have to worry about them. Thanks, Justin 1. http://flex.apache.org/installer/sdk-installer-config-4.0.xml
Re: Installer is Timing Out.
Hi, Which file are the going to host (it's a little unclear from you email). There are some security concerns here I think. Justin On Sat., 9 Jun. 2018, 4:00 pm Piotr Zarzycki, wrote: > I did tests with moved file to my server and everything went fine. I just > have enough to fighting with changing something on the Apache servers. I > will wait a bit for some other PMCs voices. I hope they will be positive. > > Thanks, > Piotr > > sob., 9 cze 2018 o 01:10 Alex Harui napisał(a): > > > I think you can, or even some company like the folks behind Moonshine. I > > cannot think of any restrictions against doing that. > > > > My 2 cents, > > -Alex > > > > On 6/8/18, 1:12 AM, "Piotr Zarzycki" wrote: > > > > Hi PMCs, > > > > What if I store problematic file on my server ? Can I do that without > > breaking some Apache policies ? > > > > Thanks, > > Piotr > > > > wt., 5 cze 2018 o 08:34 Alex Harui > > napisał(a): > > > > > See: > > > > > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Fc8abaa83b83c260e899517e32baf6dfe5d4de6524eb2b2a3ffcdff31%40%253Cdev.flex.apache.org%253E=02%7C01%7Caharui%40adobe.com%7Ca63ca9106c7c4948ff8f08d5cd1785b2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636640423293428892=t7oRNB2z1H3F3CYvh7eQ%2FhV60Ws3D0HtJWTRm83mVp4%3D=0 > > > > > > HTH, > > > -Alex > > > > > > On 6/4/18, 9:35 PM, "joho" wrote: > > > > > > I am getting an SSL Error when running "ant -f installer.xml" > > > > > > Has one else encountered a similar error? > > > > > > > > /Users/dev/Downloads/apache-flex-sdk-4.16.1-bin/installer.xml:927: The > > > following error occurred while executing this line: > > > > > /Users/dev/Downloads/apache-flex-sdk-4.16.1-bin/installer.xml:967: > > > javax.net.ssl.SSLException: Received fatal alert: > > protocol_version > > > at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) > > > at sun.security.ssl.Alerts.getSSLException(Alerts.java:154) > > > at > > > sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1979) > > > at > > > sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1086) > > > at > > > > > > > > > sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332) > > > at > > > > > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1359) > > > at > > > > > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343) > > > at > > > > > > > > sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) > > > at > > > > > > > > > sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) > > > at > > > > > > > > > sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153) > > > at > > > > > org.apache.tools.ant.taskdefs.Get$GetThread.openConnection(Get.java:737) > > > at > > org.apache.tools.ant.taskdefs.Get$GetThread.get(Get.java:650) > > > at > > org.apache.tools.ant.taskdefs.Get$GetThread.run(Get.java:640) > > > > > > > > > > > > -- > > > Sent from: > > > > > > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-development.247.n4.nabble.com%2F=02%7C01%7Caharui%40adobe.com%7Ca4325be303b444a5dd7f08d5ca9dc763%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636637701363988747=%2B93MVlqQ5kXO%2FDTra2kET9XmZa7YrDIoK3q0%2B8YiiCo%3D=0 > > > > > > > > > > > > > -- > > > > Piotr Zarzycki > > > > Patreon: * > > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7Ca63ca9106c7c4948ff8f08d5cd1785b2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636640423293428892=YU7GFQofMlK26Adym0qmxQ8tJHb%2BD1GW9p2PWGknGpk%3D=0 > > < > > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7Ca63ca9106c7c4948ff8f08d5cd1785b2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636640423293428892=YU7GFQofMlK26Adym0qmxQ8tJHb%2BD1GW9p2PWGknGpk%3D=0 > > >* > > > > > > > > -- > > Piotr Zarzycki > > Patreon: *https://www.patreon.com/piotrzarzycki > <https://www.patreon.com/piotrzarzycki>* >
Re: Installer is Timing Out.
Hi, > I just debug it and it looks like there is some problem with parsing > in MirrorURLUtil - fetchMirrorFromCGIResult. We go following web page [1]. > What actually should be parsed out of it ? Yes you’re seeing what I saw, that’s the full HTML rather than XML result returned. I’m guessing It may be inconsistent depending on where you are. I’ve not looked at the code in detail but I'm wondering does it make two requests to that URL? If it makes two requests A and B and A returns HTML and B returns XML it may be that we may have a timing issue. For fast connections A gets results right away and then B get results straight away, but for slower requests A result could occur after B results return. In one case: Call A is made Call A returns a lot of HTML Call B is made Call B returns short XML In the other case: Cal A is made Call B is made Call B returns short XML Call A returns a lot of HTML No idea if this is the case but just suggesting it as a possible explanation that seems to fit what is going on. Thanks, Justin
Re: Installer is Timing Out.
Hi, > The worst thing that I have seen the same as Alex - that there is a problem > with https, not parsing itself. If it is an https issue like this (one of the possible mirrors that can be returned) https://apache.melbourneitmirror.net/flex/4.16.1/binaries/apache-flex-sdk-installer-config.xml <https://apache.melbourneitmirror.net/flex/4.16.1/binaries/apache-flex-sdk-installer-config.xml> I can’t see how we could easily solve it as it likely at the mirrors end. (Open that URL in a browser and see what you get.) It may be that SSL in not supported on all Apache mirrors, perhaps on purpose?? Has anyone asked infra? I have no idea if this is the case or not and a quick search of teh documentation doesn’t mention https and mirrors. I know that the KEY files and hashes need to checked via SSL and not placed on mirrors, but all mirror examples use http not https and there is this JIRA which suggests that https requests need to redirect and return 301s. [1] (which is moved permanently) Thanks, Justin 1. https://issues.apache.org/jira/browse/INFRA-13442
Re: Installer is Timing Out.
Hi, > I think you've proposed multiple causes. One is that the cgi isn't returning > the right thing, the other was that fetching apache-flex-installer-config.xml > over https was failing. > Which one or both are you claiming to be the issue? Well you were saying that https was the issue and fetching the apache-flex-installer-config.xml file via https seems to fail via curl or in the browser is failing. The older SDK that are working don’t use https to get the config file. Try for instance this via curl or https: https://apache.melbourneitmirror.net/flex/4.16.1/binaries/apache-flex-sdk-installer-config.xml But the first issue you will run into is the cgi not returning the right thing and that would explain the timeout. > If I just use my browser to hit: > http://flex.apache.org/single-mirror-url--xml.cgi > I am getting the expected single line back. Can some other folks hit this > link above? You should get a single line of text, not even an HTML page. > Same with using CURL. I only get one line of text back. I get the HTML page: MacBook-Pro:~ justinmclean$curl -v http://flex.apache.org/single-mirror-url--xml.cgi * Trying 40.79.78.1... * TCP_NODELAY set * Connected to flex.apache.org (40.79.78.1) port 80 (#0) > GET /single-mirror-url--xml.cgi HTTP/1.1 > Host: flex.apache.org > User-Agent: curl/7.54.0 > Accept: */* > < HTTP/1.1 200 OK < Date: Fri, 01 Jun 2018 07:28:59 GMT < Server: Apache/2.4.18 (Ubuntu) < Vary: Host,Accept-Encoding < Transfer-Encoding: chunked < Content-Type: text/html < https://www.apache.org/dyn/closer.cgi; /> etc ect * Connection #0 to host flex.apache.org left intact MacBook-Pro:~ justinmclean$ If I run the installer in the debugger it also returns the whole page and the mirror URL ends up as that html content as well with a few letters off the start and end. Thanks, Justin
Re: Installer is Timing Out.
Hi,
> That doesn't sound like what I saw when I debugged into it last week, but if
> you are right, then it sounds like you can prepare a fix for it.
I’ve run into through a reverse proxy to record the installers traffic and also
though the debugger and both match. Perhaps there was also a different issue
last week or we also have another issue that occurs after this step. But note
that the call to that cgi script is http call not a https call when made by the
installer. I’ve include the response to the cgi script below as seen by the
reverse proxy. You’ll can also see that 5K is a lot bigger than the expected
response should be.
Sorry I’m running back to back courses on the weekend and all next week (inter
state) and then off to Berlin for The Apache Roadshow the week after so I'm not
sure when I’ll have time over the next couple of weeks to fix it. It should
just be a simple mater of changing the cgi script / web site config to produce
what that installer expects and there no need to change the installer code or
make a new release of the installer. This could be probably easily tested by
briefly putting up a hard coded response in replace of that cgi script to see
if the current installer works with that.
Thanks,
Justin
Reverse proxy request:
http://flex.apache.org/single-mirror-url--xml.cgi
Complete
200 OK
Total size: 5.14 KB (5268 bytes)
72.6% (gzip)
Reverse proxy response:
https://www.apache.org/dyn/closer.cgi; />
Apache Download Mirrors
Toggle navigation
HomeDyn
About
Overview
Members
Process
Sponsorship
Glossary
FAQ
Code of Conduct
Contact
Projects
People
http://people.apache.org/;>Overview
http://people.apache.org/committer-index.html;>Committers
Meritocracy
Roles
Code of Conduct
http://planet.apache.org/;>Planet Apache
Get
Involved
Overview
http://community.apache.org/;>Community Development
Code of Conduct
http://helpwanted.apache.org/;>Help
Wanted
http://www.apachecon.com/;>ApacheCon
Download
Support Apache
Sponsorship
Donations
Buy
Stuff
Thanks
http://apache.org/foundation/contributing.html; title="Support
Apache">
(function() {
var cx = '005703438322411770421:5mgshgrgx2u';
var gcse = document.createElement('script');
gcse.type = 'text/javascript';
gcse.async = true;
gcse.src = (document.location.protocol == 'https:' ? 'https:' : 'http:') +
'//cse.google.com/cse.js?cx=' + cx;
var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(gcse, s);
})();
The Apache Way
https://community.apache.org/contributors/;>Contribute
ASF Sponsors
/* The following code is added by mdx_elementid.py
It was originally lifted from <a rel="nofollow" href="http://subversion.apache.org/style/site.css">http://subversion.apache.org/style/site.css</a> */
/*
* Hide class="elementid-permalink", except when an enclosing heading
* has the :hover property.
*/
.headerlink, .elementid-permalink {
visibility: hidden;
}
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }
We suggest the following mirror
site for your download:
http://ap
Re: Installer Issue: Host binaries elsewhere?
Hi, As mentioned in the other thread is issue is not SSL released but is released to our mirror CGI script. http://flex.apache.org/single-mirror-url--xml.cgi <http://flex.apache.org/single-mirror-url--xml.cgi> looks to be returning too much information and the installer’s code (in MirrorURLUtil) isn’t correctly parsing the mirror’s URL out of the info returned. It ends up with an invalid URL which times out when the installer tries to call it. Thanks, Justin
Re: Installer is Timing Out.
Hi,
> 1. The page structure has changed and it failing to correctly parse the
> mirror URL out of the page so the URL it manufactures times out
And Ive confirmed (in the debugger) that exactly what is happening. This code
below in MirrorURLUtil.as is no longer parsing the correct mirror name out of
the content returned.
var result:String = _internetUtil.result;
_mirrorURL = (result.search("") != -1) ?
result.substring(3, result.length - 4) :
result;
Issue being I think that the cgi script is returning full page of HTML which is
not what this code expects.
Thanks,
Justin
Re: Installer is Timing Out.
Hi, > It’s the https call to the mirror to get the XML installer config file that > is failing. And it could be failing for one of two reasons, Which I don't think has been 100% determined, 1. The page structure has changed and it failing to correctly parse the mirror URL out of the page so the URL it manufactures times out 2. It's a https issues The first option seem more likely to me. Has anyone looked at that? Thanks, Justin
Re: Installer is Timing Out.
Hi, > 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. The http call to the single mirror CGI script to get the mirror information works. It’s the https call to the mirror to get the XML installer config file that is failing. Thanks,. Justin
Re: Installer is Timing Out.
Hi, > 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. I don’t believe this is only an AIR HTTPS issue. Try: curl -v http://apache.melbourneitmirror.net/flex/4.16.1/binaries/apache-flex-sdk-installer-config.xml (and you see it works) But: curl -v https://apache.melbourneitmirror.net/flex/4.16.1/binaries/apache-flex-sdk-installer-config.xml Will fail with: * Trying 202.124.241.168... * TCP_NODELAY set * Connected to apache.melbourneitmirror.net (202.124.241.168) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH * successfully set certificate verify locations: * CAfile: /etc/ssl/cert.pem CApath: none * TLSv1.2 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS alert, Server hello (2): * error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure * stopped the pause stream! * Closing connection 0 curl: (35) error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure So wouldn't the easy fix be just get the config file over http? Thanks, Justin
Re: Installer is Timing Out.
HI, > 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? The old XML config file is probably cached and you’re probably not seeing the new version. Thanks, Justin
Re: Installer Issue: Host binaries elsewhere?
Hi, > Looks like all download are failing either with a timeout or other error. It > doesn’t seem to be OS specific but it’s looks to be SDK version specific. I just tried it and I’m also getting a timeout. Given non 4.16 versions can be downloaded it looks to me tp be an issue with the configuration file or parking the mirror URL. I’ve run it though a proxy to see what call is failing but it doesn’t seem to show. Calls to: http://flex.apache.org/installer/sdk-installer-config-4.0.xml http://flex.apache.org/installer/properties/en_AU.properties http://flex.apache.org/single-mirror-url--xml.cgi Are all successful but it not making a call to the mirror contained within the page returned by the cgi script. I would guess it failing to parse that information from the cgi page. However it looks like the cause of that issue is that it not passing the file to download to the cgi scrip. Thanks, Justin
Re: Installer is Timing Out.
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
Re: Installer Issue: Host binaries elsewhere?
Hi, > As you hopefully know, lots of people are having trouble with the installer. > Can someone look to see if we've had any successful 4.16.1 installs in the > past week or two? Looks like all download are failing either with a timeout or other error. It doesn’t seem to be OS specific but it’s looks to be SDK version specific. From 14th May(and possibly earlier) onwards it looks like all 4.16.1 and 4.1`6.0 are failing. /track-installer.html?failure=true=Apache Flex SDK 4.16.1=4.16.1=windows=3.3.1=Timeout 846 failures /track-installer.html?failure=true=Apache Flex SDK 4.16.1=4.16.1=mac=3.3.1=Timeout 377 failures /track-installer.html?failure=true=Apache Flex SDK 4.16.0=4.16.0=windows=3.3.1=Timeout 64 failures There was a small number of successful 4.15.0 downloads and I can see success for 4.13.0 and 4.14.1 as well. /track-installer.html?label=Apache Flex SDK 4.15.0=4.15.0=windows=3.3.1 /track-installer.html?label=Apache Flex SDK 4.15.0=4.15.0=mac=3.3.1 Thanks, Justin
Re: Installer is Timing Out.
Hi, > get-with-no-params: > [get] Getting: > http://airdownload.adobe.com/air/mac/download/29.0//AdobeAIRSDK.dmg?ts=201805311405 > [get] To: > /Users/oharkins/Documents/Adobe/ApachieFlex/test/apache-flex-sdk-4.16.1-bin/in/AdobeAIRSDK.dmg > [get] > http://airdownload.adobe.com/air/mac/download/29.0//AdobeAIRSDK.dmg?ts=201805311405 > permanently moved to > https://airdownload.adobe.com/air/mac/download/29.0/AdobeAIRSDK.dmg?ts=201805311405 The issue is is that a http URI is being requested and Adobe’s server is returning a 301 saying the file has moved and gives a https URI. > /Users/oharkins/Documents/Adobe/ApachieFlex/test/apache-flex-sdk-4.16.1-bin/installer.xml:967: > Redirection detected from http to https. Protocol switch unsafe, not allowed. And the redirection from http to https is not allowed by ant. That issue might be ant version specific. Hosting the binaries elsewhere is not going o fix this issue. Changing the URL from http: to https: may do. Here’s the curl output showing what is going on: curl -v http://airdownload.adobe.com/air/mac/download/29.0//AdobeAIRSDK.dmg * Trying 23.9.226.40... * TCP_NODELAY set * Connected to airdownload.adobe.com (23.9.226.40) port 80 (#0) > GET /air/mac/download/29.0//AdobeAIRSDK.dmg HTTP/1.1 > Host: airdownload.adobe.com > User-Agent: curl/7.54.0 > Accept: */* > < HTTP/1.1 301 Moved Permanently < Server: AkamaiGHost < Content-Length: 0 < Location: https://airdownload.adobe.com/air/mac/download/29.0/AdobeAIRSDK.dmg < Date: Thu, 31 May 2018 21:58:35 GMT < Connection: keep-alive Thanks, Justin
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC3*
Hi, > FYI, Yesterday (Sunday my time) I have moved binaries to different folder > - because there were in a wrong one in comparing to the previous release. > It ends up that I need to wait for the mirrors. I thought that after 24 > hours they will be available but they are not. You can check the status of the mirrors here [1] Have a look at the age histogram towards the bottom of the page. It looks like most of the mirrors are less than 10 hours behind, 24 is usually more than enough for just about all of the mirror to catch up. Thanks, Justin 1.https://www.apache.org/mirrors/
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC2*
Hi, > FWIW, I confirmed with the author that this code is Adobe-owned. Consider it > "donated". Thanks for confirming that. I’ve put back the headers and fixed up the LICENSE file to match the new information. Thanks, Justin
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC2*
Hi, > IMO, we'd be better off having these files donated to Apache so the header > does not need to change. There is no need to keep it as third-party since > the original author hasn't touched it in years. I'm pretty sure it is ok > for me to just say it is owned by Adobe and thus donated. We've done > this in the past without a whole SGA. It is just a couple of files. I’ve changed the headers IMO it better to comply with ASF legal policy than not to. If you want retroactively get them donated I believe you would need to confirm that Adobe does own the copyright and check on legal discuss if that’s OK. I’ll change the headers back to ASF ones for you if they need to be. I put the copyright as "Copyright 2011 Piotr Walczyszyn or Adobe” as although he was working for Adobe at the time this was his personal blog and I don’t know the what the terms of his contact with Adobe was or how employee/employer copyright ownership works under Polish copyright law. (He was based in Poland according to his blog.) Re "There is no need to keep it as third-party since the original author hasn't touched it in years.” I think you find that copyright lasts a little longer than that :-) I’ve no idea what it is in Poland but here (and the US) it’s life of the author + 70 years. Thanks, Justin
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC2*
Hi, You don’t need to assert copyright it exists the moment something is created. In this case copyright is with someone (the author or perhaps Adobe) not us but that’s OK as it Apache licensed. If a file is developed at the ASF it has the standard ASF header [1] but if it’s a 3rd party work it clearly states “3. Do not add the standard Apache License header to the top of third-party source files.” [2] Which is exactly what has happened here. Is everyone OK that we are not following ASF legal policy? Especially considering it's easy to fix? The ASF header states "Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.” Is this true for those files? Thanks, Justin 1. https://www.apache.org/legal/src-headers.html#headers 2. https://www.apache.org/legal/src-headers.html#3party
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC2*
Hi, So Alex as an Adobe employee you're happy that someone took Adobe licensed code (assuming that is the case) that wasn’t part of a grant to the ASF and added it to the code base with ASF headers? What do you think Adobe legal might say about this? No need to ask them I just asking you think what they might say. I’m guessing they may have a small issue with that. Thanks, Justin
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC2*
Hi, See here for where it originally come from. [1] Thanks, Justin 1. https://lists.apache.org/thread.html/f3fee0e5b9b8853f744a8a111a4e7e5d3d9a4960f570b02f6409bc06@1343037815@%3Cdev.flex.apache.org%3E
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC2*
Hi, > I think the author is an Adobe employee. It isn't clear he would own > copyright. I know I wouldn't if I had written it. AFAIK This code wasn’t part of Adobe’s donation to Apache but added later as it was Apache licensed. Thanks, Justin
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC2*
Hi, > If you can fix it that would be great. I’ve fixed the header. There is still an outstanding question re how to fix the license issue. It easy to fix either way just we need to agree on which way to do it. You could make another RC without that license fix but I think it would be better to fix it. Thanks, Justin
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC2*
Hi, Found a couple of other (very) minor issues (which are certainly not blockers): - This file had an incorrect ASF header [1] No objections if I fix it? - build.number also has 2 copyright statement in it with different dates. That probably should be fixed. - This file [2] has copyright 2014 and needs to be updated. Thanks, Justin 1. installer/sign_and_hash.sh 2. installer/src/InstallApacheFlex-app.xml
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC2*
Hi, > I’ve also tried the installer a couple of time and getting errors. And on the 3rd try it worked - but still not sure why the first two runs failed. Thanks, Justin
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC2*
Hi, I’ve also tried the installer a couple of time and getting errors. Running on OSX Sierra (and latest version of Air) I get the following: Installer version 3.3.1 (mac) Using Locale: en_AU Fetched the SDK download mirror URL from the CGI. SDK version Apache Flex SDK 4.16.1 AIR version 29.0 Flash Player version 29.0 Creating Apache Flex home Creating temporary directory Downloading Apache Flex SDK from: http://apache.melbourneitmirror.net/flex/4.16.1/binaries/apache-flex-sdk-4.16.1-bin.tar.gz Aborting Installation: http://flex.apache.org/track-installer.html?failure=true=Apache Flex SDK 4.16.1=4.16.1=mac=3.3.1=handleApacheFlexSDKDownload Error #3004 #3004 implies out of disk space but I have 30+ gigabytes free so not sure what the issue is. Mirror looks fine. Thanks, Justin 1. http://apache.melbourneitmirror.net/flex/4.16.1/binaries/
Re: [VOTE] Apache Flex SDK Installer 3.3.1 RC2
Hi, +0 because of license issues (see discussion) I checked: - signatures and hashes correct - NOTICE has incorrect year - LICENSE has an issue re the NativeApplicationUpdater - no unexpected binary files - one file is missing an ASF header [1] Also note that this file isn’t under version control so perhaps should not be in the release? - could compile from source Thanks, Justin 1. common/common.iml
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC2*
Hi, The NOTICE had the wrong year in it so I fixed that. We would need to curt another RC if we want correct in the release. The licensing for the NativeApplicationUpdater is a little odd. The LICENSE file states: "The NativeApplicationUpdater is available under Apache License 2.0. For details see installer/src/com/riaspace/“ But there are no details in that location and the files have ASF headers. The files probably should probably have a 3rd party Apache header or the LICENSE file mention who the original copyright holder was. The original author is [1]. Which solution do people prefer? Thanks, Justin 1. https://vimeo.com/14400178
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC2*
Hi, > Downloading 2.2.zip from: https://github.com/swfobject/swfobject/archive > [get] [IOErrorEvent type="ioError" bubbles=false cancelable=false > eventPhase=2 text="Error #2032" errorID=2032] It looks like the first https call is failing. Air us to use IE’s proxy settings (not 100% sure if it currently does) you might want to check what they are and if it correctly set up for https. You might also want to check windows firewall. Thanks, Justin
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC2*
Hi, Error #2038 is fairly generic but it could be: - windows firewall is blocking that server/port - AIR apps used use IE proxy setting (not sure if that still is the case). You might what to check your IE proxy settings for SSL and see that they are correct. Thanks, Justin
Re: Change to SHA1 signatures
Hi, > Is this a massive change to our build script ? It’s a minor change and/or can be done manually. Thanks, Justin
Re: ApacheFlexBuild Nightly Build Server
Hi, I changed the jenkins job to only run on windows boxes (of which there are 4) and it is working so that gets rid of those minor issues. Note that you need to specify the windows version of ant and java in the job to get it working. It’s currently not running the checkin tests but that should be possible to set up and what I’ll take a look at next.. And I also need to test the build to confirm that it’s working correctly but the build log look good to me. [1] Anyone want to explore any of the other options? Thanks, Justin 1, https://builds.apache.org/job/Apache%20Flex%20SDK/31/console
Re: ApacheFlexBuild Nightly Build Server
Hi, One other minor thing is that it’s not running rat but that should be easy to fix. Thanks, Justin
Re: ApacheFlexBuild Nightly Build Server
Hi, > As a temporary measure it should be easy enough to set up a build on > builds.apache.org that makes the release package but doesn’t run the checkin > tests. After a few minor changes to the build scripts to get the release to compile on Linux I have it set up and running here. [1] This produces a convenience binary but will have a have a couple of minor difference to one made on windows or OSX. The major one being the checking tests are not run during the build process. Minor things include it’s missing support for flash integration in flex, automation of the flash flex kit as both of these are not supported on Linux and it’s missing the asdocs/documentation for the mobile themes. If you’re setting this up yourself somewhere a few thing that may help: - TLF needs to be copied for it build. Currently this is slow between slave machines. There may be a better way to do it. - You need to run with an unlimited security version of java - The setup is basically run ant -f jenkins.xml followed by ant release.notests - A couple of environment variables need to be set like so AIR_HOME=$WORKSPACE/air/AIR\ Integration\ Kit/ PLAYERGLOBAL_HOME=$WORKSPACE/lib/player/ TLF_HOME=$WORKSPACE/TLF/ ANT_HOME=/usr/share/ant - The release.notests doesn’t do a clean but the workspace is wiped on the start of the build It seems that BLAZEDS_HOME is no longer required to set? So far this is just a proof of concept and I not tested the Flex SDK it produces but I can’t see why their would be any major issues with it. Infra / builds.apache.org do also have windows machines and we can restrict the build to those, that means the minor issues above disappear, and that we should be able to get the checkin and mustella tests running. Thanks, Justin 1. https://builds.apache.org/job/Apache%20Flex%20SDK/lastSuccessfulBuild/
4.16.1 release merged into master
Hi, Looks like the last release wasn’t merged into master I just went ahead and did that. Thanks, Justin
Re: git commit: [flex-sdk] [refs/heads/develop] - testing if we can make a release build target without running the tests
Hi, > This is one of the commit which causes build fail. What's the plan to fix > that ? That commit wasn’t the issue it was the one after that. I’ve pushed a fix and things should be back to normal. Thanks, Justin
Re: git commit: [flex-sdk] [refs/heads/develop] - testing if we can make a release build target without running the tests
Hi, > This is one of the commit which causes build fail. What's the plan to fix > that ? Odd that change is working fine locally and I can’t see how that would break the build i.e. adding new target that isn’t used. I’ll look into it. Thanks, Justin
Re: ApacheFlexBuild Nightly Build Server
Hi, > We could copy the last good build somewhere. Unless changes are actually > committed to the Flex repos, there isn't going to be any difference > between one nightly build and another. As a temporary measure it should be easy enough to set up a build on builds.apache.org that makes the release package but doesn’t run the checkin tests. Thanks, Justin
Re: ApacheFlexBuild Nightly Build Server
Hi, > If someone wants to move the jobs to builds.a.o and deal with working with > Infra or joining > Infra and maintaining the builds as Infra requires updating versions of > things, that is a third option. I would be willing to do that. > But if that volunteer disappears, then Flex is back to where it is now. Exactly the same could be said for someone setting up an external box and infra is likely to be around a lot longer than any external box. > Justin, the Flex PMC does have access to apacheflexbuilds. I never claimed they didn't, however the Flex PMC do not currently have access to the new server you have set up. I assume you will be shutting down the existing apache flex build server in the near future. Do you have a timeframe for that? > And if Flex wants to use the Royale CI server they will be given access there > as well. Well that is good to know and look forward to that happening if the Flex PMC decides to move the builds onto this new box. > Stop with the FUD. There is no FUD here, stop with the accusatiions. Thanks, Justin
Re: ApacheFlexBuild Nightly Build Server
Hi, > Yep we have FlexJS and Royale [1], but this is Maven build and we need to > have also ANT. Jenkins can run ant builds as well. > All PMCs have access to the build server Currently the Flex PMC doesn’t have access to the server AFAIK. Please email the login details to the Flex private list. Thanks, Justin
Re: ApacheFlexBuild Nightly Build Server
Hi, > There are some choices: > 1) Some other PMC member get an Azure VM and move the jobs there > 2) Run Flex jobs on the new Royale VM. There is a 3rd option and that is to run it on builds.apache.org. We did have this working at one point and I can’t see why it wouldn’t be possible to do so again. The FlexJS builds were running on builds.apache.org [1] so I don’t see why the Royale builds couldn’t be there as well. What’s the requirement to run them on a seperate VM? (But that is up to the Royale PMC to decide.) > For #2, we would need a volunteer or two to move the jobs. Moving the Flex nightly builds to a machine where not all of the Flex PMC has access is probably not the best option IMO. Thanks, Justin 1.https://builds.apache.org/job/FlexJS%20Pipeline/
Re: [DRAFT] Apache Flex SDK Installer 3.3.0 Released
Hi, Some minor suggested changes: > --- start draft announcement - > The Apache Flex community is pleased to announce the release of Apache Flex > SDK Installer 3.3.0 > > Apache Flex SDK Installer 3.3 is an update to Apache Flex SDK Installer > 2.2. 3.2 rather than 2.2 I think? > This update provide fix for out of memory exception when user download > Apache Flex SDK with Adobe Air greater than 23 on Windows platform. Suggestion: “This update provides a fix for an out of memory exception when user downloads the Apache Flex SDK with Adobe AIR versions greater than 23 on the Windows platform.” > Known Issue: > On Windows platform user need to uninstall previous version of installer, > before install the newest one. Suggestion: “On the windows platform the user will need to uninstall the previous version of the installer before installing the newest version.” Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC2*
Hi, > Btw your example failed for me with error [2], so I moved formatter > to declarations - Didn't you have such error ? No error here. Not checked but I think that only happens if you use a s:Application rather than an mx:Application. Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC2*
Hi, > Please raise jira issue. Will do. > I'm going to move forward with release, cause it’s existing issue and it's > probably with us for a long time. Does any user > raise that problem ? No user has raised an issue for pound sign not showing that I could find. BTW I’ve used en_GB in the last couple of years and didn’t run into the issue but I can’t recall what version of the SDK that was. Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC2*
Hi, > I have so far more +1 than -1 so I can release it, but wondering how to fix > it for the next release. For a release you need at least 3 +1 binding votes and more +1’s than -1’s. Currently by my count there’s two +2 and one -1. Piotr you could vote +1 and make this a release. However given this problem just been found I’d suggest waiting 24 hours to see if any other PMC members vote or change their minds. Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC2*
Hi, > Please raise jira issue. I'm going to move forward with release, cause it's > existing issue and it's probably with us for a long time. AFAIKS this is not an existing issue but a new issue. Looking at the comparison of 4.16.0 to what's in version control they match. 4.16.1 doesn’t match what in version control. Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC2*
Hi, > My suggestion is to vote +1 and ship this release since this is not a new > issue. And I'd suggest fixing this before making a release. But if the release gets three +1 votes and more +1’s than -1’s then that’s a release. > I think there are code page issues in the source files. Volunteers can > work it out later for the next release. Let's get our users a release > that more of them can use. IMO, releases do not have to be perfect. More of them can use? Not so sure about that. From Google Analysis (for the past year) 60% or so of our users use a locale other than en_US. How many would be effected by this encoding issue? I’m not sure as I’m don’t know all locales that have an issue but en_GB is 5% of users. Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC2*
Hi, > Perhaps the SharedResources.properties has been incorrectly converted to > UTF-8 when it actually should be ISO-8859? (The pound sign is character 163.) > Perhaps we have a mix of text encodings for resource files? Answer yes and it’s a bit of a mess. In version control we have resource files with: ASCII text ASCII text, with CRLF line terminators ASCII text, with CRLF, LF line terminators ASCII text, with no line terminators ASCII text, with very long lines ISO-8859 text SVG XML document UTF-8 Unicode (with BOM) text UTF-8 Unicode (with BOM) text, with CRLF line terminators UTF-8 Unicode text UTF-8 Unicode text, with CRLF line terminators UTF-8 Unicode text, with very long lines UTF-8 Unicode text, with very long lines, with CRLF line terminators directory In the 4.16.1 RC we have: ASCII text, with CRLF line terminators ASCII text, with no line terminators ASCII text, with very long lines, with CRLF line terminators SVG XML document UTF-8 Unicode (with BOM) text, with CRLF line terminators UTF-8 Unicode text, with CRLF line terminators UTF-8 Unicode text, with very long lines, with CRLF line terminators directory So some conversion has gone on and that is going to explain the differences. Note that some of the files also have the BOM (byte order mark). One of the ISO-8859 files just happened to contain the en_GB currency symbol. Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC2*
Hi, > It looks like this was also a problem in 4.16.0. Can you confirm? Doesn’t look like it from a quick look but I’ve not tried to compile against it (yet). 4.16.1 vs VC gives: diff -w -r *src ~/flex-sdk | grep currencySymbol < currencySymbol= > currencySymbol=? 4.16.0 vs VC gives no differences. Also the file types match 4.16.0 and what’s in version control (but it's not UTF-8): 4.16.1 RC: $file apache-flex-sdk-4.16.1-src/frameworks/projects/framework/bundles/en_GB/SharedResources.properties UTF-8 Unicode text, with CRLF line terminators VC: $file /Users/justinmclean/flex-sdk/frameworks/projects/framework/bundles/en_GB/SharedResources.properties ISO-8859 text 4.16.0: file /Users/justinmclean/Documents/ApacheFlex4.16/frameworks/projects/framework/bundles/en_GB/SharedResources.properties ISO-8859 text Perhaps the SharedResources.properties has been incorrectly converted to UTF-8 when it actually should be ISO-8859? (The pound sign is character 163.) Perhaps we have a mix of text encodings for resource files? Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC2*
Hi, > diff -w -r > apache-flex-sdk-4.16.1-src/frameworks/projects/framework/bundles/en_GB/SharedResources.properties > > /Users/justinmclean/flex-sdk/frameworks/projects/framework/bundles/en_GB/SharedResources.properties > 39c39 > < currencySymbol=� > --- >> currencySymbol= Just confirmed this is an issue and here's some example code to test it. To test compile with the en_GB locale. http://www.adobe.com/2006/mxml; layout="absolute" applicationComplete="format()"> The currency symbol will show as a question mark in a black diamond in the text input field. If you need a screen shot just ask. Thanks, Justin
Re: [VOTE] Release Apache Flex SDK 4.16.1 - RC2
Hi, -1 binding because of locale issues. I checked: - hashes and signatures correct - LICENSE and NOTICE good - no unexpected binary files - all source file has ASF header where needed - can compile from source Tried a few simple tests and while most worked but we are still having locale issues. For instance when in en_GB the pound sign incorrectly shows as a question mark in a black dimond. Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC2*
Hi, Looks like we may still have some unicode issues. Some that are likely to cause issues: Comparing the source release to a clean checked out repo: file apache-flex-sdk-4.16.1-src/licenseParts/saxon9-NOTICES/UNICODE.txt apache-flex-sdk-4.16.1-src/licenseParts/saxon9-NOTICES/UNICODE.txt: ISO-8859 text, with CRLF line terminators That that probably not a an issue but is is likely to cause locale issues: diff -w -r apache-flex-sdk-4.16.1-src/frameworks/projects/apache/bundles/fr_FR/apache.properties /Users/justinmclean/flex-sdk/frameworks/projects/apache/bundles/fr_FR/apache.properties 21c21 < invalidCharPostcodeError=Le code postal contient des caract�res invalides. --- > invalidCharPostcodeError=Le code postal contient des caractres invalides. diff -w -r apache-flex-sdk-4.16.1-src/frameworks/projects/framework/bundles/en_GB/SharedResources.properties /Users/justinmclean/flex-sdk/frameworks/projects/framework/bundles/en_GB/SharedResources.properties 39c39 < currencySymbol=� --- > currencySymbol= diff -w -r apache-flex-sdk-4.16.1-src/modules/debugger/src/java/flex/tools/debugger/cli/fdbhelp_fi.txt /Users/justinmclean/flex-sdk/modules/debugger/src/java/flex/tools/debugger/cli/fdbhelp_fi.txt < M��ritt�m�t�n komento. Sy�tt�m�ll� 'help' n�et luettelon kaikista --- > Mrittmtn komento. Syttmll 'help' net > luettelon kaikista Thanks, Justin
Re: [Discuss] Release Apache Flex SDK Installer 3.3 - RC3*
HI, > Windows installs were successful with AIR/Flash 24 and later? Yes quite a number have work. For 24, 25 and 26 more worked than got error 1000. > I didn’t think that was possible with the 4.16.0 install script. From google analytics looking at only windows install successes: Apache Flex SDK 4.16.0 AIR 22.0 installs 95 Apache Flex SDK 4.16.0 AIR 23.0 installs 137 Apache Flex SDK 4.16.0 AIR 24.0 installs 260 Apache Flex SDK 4.16.0 AIR 25.0 installs 1,609 Apache Flex SDK 4.16.0 AIR 26.0 installs 1,093 Apache Flex SDK 4.16.0 AIR 27.0 installs 593 Thanks, Justin
Re: [Discuss] Release Apache Flex SDK Installer 3.3 - RC3*
Hi, > It's occurring 100% on Win 7 or Win 10 from your statistics ? Hard to tell as we don’t directly log that and google analytics is not giving that info up. Given the number of distinct users I would guess it’s a mix but more likely more windows 10 than 7. Thanks, Justin
Re: [Discuss] Release Apache Flex SDK Installer 3.3 - RC3*
Hi, > Not only with installer 3.3 but also with installer 3.2. It doesn't occur > often. I think on Windows 7 it may work. JFYI It's occurring 100% of the time with 3.3 (from a small sample of 42 anyway), with 3.2 over the last few month I can find 6 of the same errors out of 2000 odd working installs of 4.16.0 on windows. Thanks, Justin
Re: [Discuss] Release Apache Flex SDK Installer 3.3 - RC3*
Hi, > Tests never too much! :) However I explained it in several places that we > have this issue from your email. [1] Which has been fixed in 4.16.1. This > is the only reason why I'm trying to release new SDK. So just to be clear 4.16.0 will fail to work on windows with the 3.3 installer? Perhaps we may need to remove 4.16.0 from the list of SDKs on windows? We’re currently getting just under 2000 installs via the installer of 4.16 a month btw. Thanks, Justin
Re: [Discuss] Release Apache Flex SDK Installer 3.3 - RC3*
Hi,
JFYI May be another issue with the new installer.
I got sent this off line:
(paths edited to remove user name)
Installer version 3.3.0 (windows)
Using Locale: en_US
Fetched the SDK download mirror URL from the CGI.
SDK version Apache Flex SDK 4.16.0
AIR version 27.0
Flash Player version 27.0
Creating Apache Flex home
Creating temporary directory
Downloading Apache Flex SDK from:
http://apache.mirror.cdnetworks.com/flex/4.16.0/binaries/apache-flex-sdk-4.16.0-bin.zip
Verifying Apache Flex SDK MD5 Signature
The Apache Flex SDK MD5 Signature of the downloaded files matches the
reference. The file is valid.
Uncompressing: ...apache-flex-sdk-4.16.0-bin.zip
Finished uncompressing: ...apache-flex-sdk-4.16.0-bin.zip
Downloading Adobe AIR Runtime Kit for Windows from:
http://airdownload.adobe.com/air/win/download/27.0//AdobeAIRSDK.zip
Validating download: ...4.16.0_AIR27.0/in/AdobeAIRSDK.zip
Finished uncompressing: ...4.16.0_AIR27.0/in/AdobeAIRSDK.zip
Should unzip: ${shouldUnzip}
Mounting dmg
Exec task failed: /usr/bin/hdiutil
Installation aborted:
http://flex.apache.org/track-installer.html?failure=true=Apache Flex SDK
4.16.0=4.16.0=windows=3.3.0==Exec%20task%20failed%3A%20/usr/bin/hdiutil
Note it’s installer 3.3 (i.e. the new one) on windows / SDK 4.16.0 and AIR
version 27 but it’s trying to run " /usr/bin/hdiutil” which is OSX/unix.
At a guess it’s looking like ${shouldUnzip} is not being set so it’s think it’s
on OSX and trying to mount the dmg file which doesn’t exist.
Looking in google analytics I see 42 instances of this error from 31` different
users. (about 30% of 3.3.0 requests) There’s no working installs of 4.16.0 on
windows at all in the logs just 4.16.1.
The also a few of the same errors (9) on OSX
/track-installer.html?failure=true=Apache Flex SDK
4.16.0=4.16.0=mac=3.3.0==Exec task
failed: /usr/bin/hdiutil
But some successes as well so not 100% sure what’s happening there. Of 130
attempts to install FlexSDK using 3.3 only around 30 have worked.
We may want to do some more testing before releasing it?
Thanks,
Justin
Re: [Discuss] Release Apache Flex SDK Installer 3.3 - RC3*
Hi, > Validating download: > d:\Users\kangmin\Desktop\4.16.0_AIR27.0/in/AdobeAIRSDK.zip > - directory delimiter error? > Error #1000 This is an out of memory error, the new installer which is just about to be released should fix this. Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*
Hi, > Niclas, Where did I say it was "Binary with link to Source?” I would assume from your email here: > So, my assessment is: > 1) the binary artifacts are ok. No new problems. > 2) the source artifacts are not ok. There might be a workaround if we can > figure out how to convert the code page on those files. > 3) Would be nice to fix the executable bit on the scripts, but not a new > problem either. > So, the vast majority of our users may not hit this problem since they > consume the binary artifacts and not the source artifacts. I'll leave it > up to Piotr as to whether he wants to roll another RC that picks up > changes. i.e. That you were good to release the working binary and broken source artefacts together. I did also raise this as a issue , although perhaps in a less direct way. > Either way it's the source that’s the offical release and it seems unusual to > release a broken source release even if the binary did work. Given there’s going to be another RC perhaps it would be better to not waste energy arguing about this? Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*
Hi, > I just pushed RC2 [1]. Can you check whether you have the same problem ? > > [1] https://dist.apache.org/repos/dist/dev/flex/sdk/4.16.1/rc2/ Yes I can confirm that the scripts have execute bits. The files do not have the correct line endings (for instance look at LICENSE) Re UTF-8 it doesn’t look like the resource files are UTF-8 file --mime frameworks/locale/ja_JP/metadata.properties frameworks/locale/ja_JP/metadata.properties: text/plain; charset=unknown-8bit In the 4.15 release SDK I get: file --mime frameworks/locale/ja_JP/metadata.properties frameworks/locale/ja_JP/metadata.properties: text/plain; charset=utf-8 Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*
Hi, > The binaries are not created by first creating the source package, > unpacking it and compiling it. You were a Flex SDK RM at least once, did > you not understand what you were signing? Every time I made the release I made it from the source on my local machine on a clean tagged branch. I understood 100% what I was signing (for instance see [1][2]) and write most of the scripts to do help make builds [3][4] and contributed a lot to the wiki on the instructions on how the build the SDK. [4] I was a Flex SDK RM 1/2 dozen times probably more and more than a dozen releases in this project. So I have no idea why you would say “did you not understand what you were signing?” and IMO that was uncalled for. > I'm not sure there is a workaround to convert those files back > to UTF8 or not. Even if you did find a way it would likely change the md5s and make the signatures invalid as converting to UTF8 modifies the file by adding a byte order mark at the front of the file. Thanks, Justin 1. http://www.apache.org/legal/release-policy.html#owned-controlled-hardware <http://www.apache.org/legal/release-policy.html#owned-controlled-hardware> 2. http://www.apache.org/legal/release-policy.html#compiled-packages <http://www.apache.org/legal/release-policy.html#compiled-packages> 3. https://github.com/apache/flex-sdk/commits/develop/build <https://github.com/apache/flex-sdk/commits/develop/build> 4. https://github.com/apache/flex-sdk/commit/0d69cbea6cea4f70872b8e40436894bcec400adc#diff-b0da275520918e23dd615e2a747528f1 4. https://cwiki.apache.org/confluence/display/FLEX/The+SDK+Release+Manager's+Guide
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*
Hi, I would guess that all the issue are git config issues. git config —list will give you a list of your settings. > I think I just verified that the binary artifacts are ok regarding the > non-ascii characters. I think that's because they are correct in the > repo, and were compiled into bundles from that repo source. I'm not sure > when the files get screwed up. When they are checked out I think that’’s happening. I notice I have in my config: core.precomposeunicode=false Re the newline issue I have: core.autocrlf=false > I also ran installer.xml in the binary artifact and found that the scripts > aren't executable. I looked in the build.xml and installer.xml and do not > see any calls to chmod that would fix that, like there is in the FlexJS > versions of those files. There are some indications from the archives > that this also has been a problem for as far back as 4.12. Again git will preserve the execute bit of a file I remember doing this ages ago for the .sh files in question And I think you need this set to preserve it n checkout. core.filemode=true Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*
Hi, CCed to you just in case it doesn’t show up on the list as it tends to reject email with images. What it should look like: What 4.16.1 gives: There are other similar issues cause by the same issue as well. Code to replicate: http://ns.adobe.com/mxml/2009; xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx"> You need to compile with the right locale i.e. try a not english one. Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*
Hi, > Is the DateChooser problem from your local build of the sources or from > the RC binary artifacts? A local built from the compiled source bundled I've not tested the binary yet but given it was made from the source release I would expect it to show the same issues. Or are you saying that the binary artefact was not made from the code in the source release? Either way it's the source that’s the offical release and it seems unusual to release a broken source release even if the binary did work. Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*
Hi, > Which would effect the locale files i.e. the Chinese and Japanese and > probably French and other european language locales would be broken. Confirmed it’s an issue and I would also vote -1 binding because of that. To reproduce just view a DateChooser and you’ll see it has some ? in it’s display when using the Chinese and Japanese locales where other characters should be. Thanks, Justin
Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*
Hi, > What is a problem with the release is that the files do not appear to be > UTF-8 encoded. Which would effect the locale files i.e. the Chinese and Japanese and probably French and other european language locales would be broken. And perhaps some of the keyboard handling code? Thanks, Justin
Re: [Discuss] Release Apache Flex SDK Installer 3.3 - RC1*
Hi, > So solution is that the header should be copied from your [1] to [2] ? I think the best way to sort this would be to re-add the BSD header or a least a pointer to it in a comment and the BSD file to LICENSE. [1] Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
Re: [Discuss] Release Apache Flex SDK Installer 3.3 - RC1*
Hi, I’m seeing a number of failures: For version 4.16.0 / FP 23.0 - I though it could be a bad mirror? Installer version 3.3.0 (mac) Using Locale: en_AU Fetched the SDK download mirror URL from the CGI. SDK version Apache Flex SDK 4.16.0 AIR version 23.0 Flash Player version 23.0 Creating Apache Flex home Creating temporary directory Downloading Apache Flex SDK from: http://mirror.ventraip.net.au/apache/flex/4.16.0/binaries/apache-flex-sdk-4.16.0-bin.tar.gz Aborting Installation: http://flex.apache.org/track-installer.html?failure=true=Apache Flex SDK 4.16.0=4.16.0=mac=3.3.0=handleApacheFlexSDKDownload Error #3004 Verifying Apache Flex SDK MD5 Signature Error #3003 So I tried an older version in the archive and it also failed Installer version 3.3.0 (mac) Using Locale: en_AU Fetched the SDK download mirror URL from the CGI. SDK version Apache Flex SDK 4.10.0 AIR version 23.0 Flash Player version 23.0 Creating Apache Flex home Creating temporary directory Downloading Apache Flex SDK from: http://archive.apache.org/dist/flex/4.10.0/binaries/apache-flex-sdk-4.10.0-bin.tar.gz Aborting Installation: http://flex.apache.org/track-installer.html?failure=true=Apache Flex SDK 4.10.0=4.10.0=mac=3.3.0=handleApacheFlexSDKDownload Error #3004 Verifying Apache Flex SDK MD5 Signature Error #3003 Thanks, Justin
Re: [Discuss] Release Apache Flex SDK Installer 3.3 - RC1*
Hi, A few other questions. Is there any reason the installer is defaulting to version 23 of AIR/Flash rather than a later version? Looks like the CONTRIBUTORS file was not updated. Is seem a little odd that the BSD licensed file here [1] has been copied into our repo with an ASF header. There’s been some modification as mentioned in NOTICE but I don’t think that changes the original copyright or license of the file. Thanks, Justin 1. https://github.com/mikechambers/as3corelib/blob/master/src/com/adobe/crypto/MD5Stream.as 2. https://github.com/apache/flex-utilities/blob/develop/flex-installer/ant_on_air/src/org/apache/flex/crypto/MD5Stream.as
Re: [LAST CALL] Apache Flex SDK 4.16.1
Hi, > Is it not enough if that file has header with those license information ? It’s enough to satisfy the MIT license conditions but not quite enough for ASF policy. [1] Adding it to LICENSE also make it clear to any users that their’s MIT licensed software included without them looking for it / accidentally coming across it. Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
Re: [LAST CALL] Apache Flex SDK 4.16.1
Hi, I’ve not had a chance to look at this in full but a quick inspection shows that License is missing this MIT licensed file (copyright Dave Gandy). [1] Thanks, Justin 1. apache-flex-sdk-4.16.1-src/frameworks/projects/flatspark/src/flatspark/utils/AwesomeUtils.as
Re: [LAST CALL] Apache Flex SDK Installer 3.3
Hi, I took a quick look and looks like there’s a couple of things that need to be fixed: - there are things bundled that perhaps should’t be i.e. ant_on_air/tests/temp - NOTICE has wrong year I’m currently travelling and may not be able to look at it again for several days. Thanks, Justin
Re: [LAST CALL] Apache Flex SDK Installer 3.3
Hi, > I don't understand. Under the link which I provided you don't see sources > packaged to zip? Sorry the link you provided was being unresponsive for me and I thought we also have a build on Apache’s build servers but was unable to find it. Thanks, Justin
Re: [LAST CALL] Apache Flex SDK Installer 3.3
Hi, Id there a source release anyway we can check I’m not seeing one at builds.apacge.org - but could of missed it. Thanks, Justin
Re: [3/4] git commit: [flex-asjs] [refs/heads/develop] - Allow drag and drop item renderers to be more that simpkle labels.
Hi, > Possibly. Which part adds overhead in your opinion? In that it a feature that not all users may use that's being implemented by conditional logic so it adds to both run time and possibly size cost. While that cost would be small in the past on the Flex list code similar to this has been called out as not PAYG and it’s been suggested to move it to a new class. It may however be that PAYG is now less strict and that adding new features in this way is now acceptable? Thanks, Justin
Re: [07/13] git commit: [flex-asjs] [refs/heads/release0.8.0] - give up on trying to use FlexBox for full-screen 3-pane views. FlexBox seems more happy stretching to content size instead of clipping a
Hi, > The compiler, the language, and the Flash runtime are all designed to > prevent you from making silly mistakes, so I think the best practice is t > define data classes. I've even considered adding a warning that detects > use of plain object. . Sonar Cube can do that for you - for instance are what it reports on the SDK: https://builds.apache.org/analysis/component_issues/index?id=org.apache.flex.flexjs.framework%3Aflexjs-framework-parent#resolved=false|rules=flex%3AS1434 thanks, Justin
Re: [RESULT][VOTE] What should be the new Project Name for Proposed fork of FlexJS?
Hi, > Spreadsheet with VOTES. Royale has a two points less, but still this is our > choose [1]. > > [1] > https://docs.google.com/spreadsheets/d/1kOvPBUgkxcdIksEWOgKhzipy5EPR0eDz8JrlB2aDTCo/edit?usp=sharing So looks like there's 14 voters their not 13? Was Tom missed in the first count? The total votes (14*6 == 84) still doesn’t tally with the total votes in that spreadsheet i.e. 82 with 3 people only placing 2 votes it still seems off by one? Given the top 4 choices are separated by 1 vote in that spreadsheet that may be important and change the result. Thanks, Justin
Re: [RESULT][VOTE] What should be the new Project Name for Proposed fork of FlexJS?
Hi, > Even if we’re off by one, Royale is the clear winner. (I get 18 votes as > well.) I’m not seeing 18 votes for Royale would you mind listing them out. Thanks, Justin
Re: [RESULT][VOTE] What should be the new Project Name for Proposed fork of FlexJS?
Hi, I think you may need to double check the count. > Royale 18 > Limber (Limbr) 13 > Bead (Beads)11 > Braid 10 > Arise 9 > Boja 8 > Bend 3 > Crown2 > Action1 > Strand0 > Boinga 0 If 13 voted this should add up to 13*(3+2+1) = 78 the above only adds up to 75 so there seems to be a missing vote or two. I think only one person didn’t give 3 votes which would make 77? From a quick count I’m seeing different totals to you. Do you mind putting in it in a google spreadsheet so people can double check the results. Thanks, Justin
Re: [VOTE] What should be the new Project Name for Proposed fork of FlexJS?
Hi, 1. Bead 2. Braid 3.Royale Thanks, Justin
Re: [VOTE] Should the Project Name of the Proposed Fork be FlexJS?
Hi, I can see there good reasons for a name change and also a good number for not changing the name. I wouldn’t underestimate the effort needed to change the name and the impact this would have on current users. It’s not an easy to decide but I’m more on the yes side than no side but it’s not a particularly strongly held view. Yes (binding) Thanks, Justin
Re: [DISCUSS] Name of the FlexJS Fork
Hi everyone, I am not someone with an official vote, but I wanted to express my concern about ditching the FlexJS name. The largest possible market for adoption of a new "javascript" solution is to go after those who have stuck with Flex. There are FAR too many javascript solutions on the market right now. If the vote is to change the name, this will: -- confuse the people who have been patiently waiting for FlexJS to get to 1.0 so they can dive in. -- get lost in the noise of all of the other far more well popularized javascript frameworks like Angular, React, etc. -- lose the feeling, however small it may be, that those who came from the Flex background can expect to have some of their knowledge recycled. These are 3 critical aspects in terms of raising awareness and having a potentially devoted following of one technology (Flex) star to transition and champion to a new one (FlexJS). If we lose that, then we effectively have to target against ALL javascript frameworks, most notably ones that are heavily entrenched already and supported by giant company resources like Google and Facebook. I am strongly opposed to a name change. I think this would be a huge mistake. On top of that, picking a new name and gaining awareness of it is HARD. It should be reason enough for the Apache powers-that-be to approve a project change to avoid being stuck with a huge legacy Flex bugbase that Adobe donated, and instead start fresh with our 1.0 name. If that cannot be achieved, then at a bare minimum we should seek to keep the name FlexJS. Regarding targeting something other than Javascript -- like SWF or AIR -- I realize the debug aspect benefits are important, but all this is going to do is confuse people. I have read about HaXe a dozen times, and I never understand what it does because apparently it does too much. A swiss army knife is a lot more confusing to use then a fixed head screwdriver. Please, we have spent SO much time trying to get to 1.0 -- lets get FOCUSED on delivering what everyone outside of the community of active participants here has been waiting on, which is a future direction for their Flex efforts. Thank you, Justin Hill http://Prominic.NET | Skype: JustinProminic My Apache Flex community contribution is working on the open source Moonshine-IDE.com for FlexJS.
Re: [VOTE] Fork FlexJS from Apache Flex
Hi, -1 binding as there are still outstanding questions in the discussion thread and the committer/PMC lists have not been amended. While I’m not against a FlexJS becoming it’s own project seperate from the Flex SDK and there’s probably good reasons from a marketing point of view there seem's to be no real technical reason to do so. There also hasn’t been any real discussion on the list about about the pros and cons about this other that what in the proposal. It seems a little rushed to me. The proposal currently omits several people that IMO should be on the PMC and committer list - myself included. The usual process is to ask existing PMC and committers if they want to be on the new PMC and AFAIK this hasn’t been done. It also includes 1/2 dozen people who have not made any contributions for 1+ year which on it’s own is not an issue (as they are already committers/PMC members) but seems odd when combined with the obvious omissions. Thanks, Justin PS I’m just about to board a 24 flight and spend 2 week travelling so will only have limited access and time to respond to anything on this list.
Re: FlexPMD Download Links not working
Hi, You can also use the Sonar Cube IntelliJ plug to show you issues without setting up Sonar Cube. Thanks, Justin
Re: FlexPMD Download Links not working
Hi, Sonar Cube is very easy to set up and run locally and reports issues on AS files. (It doesn't parse MXML files however.) You can see some results here [1] Thanks, Justin 1. https://builds.apache.org/analysis/overview?id=20942
Re: [DISCUSS} Fork FlexJS from Apache Flex
Hi, As a long standing Flex PMC and committer (5 1/2 years) with a large number of contributions in code [1] (and also elsewhere) I’d like to be added as a PMC and committer to this proposal. I’ve also made a number of contributions directly to FlexJS [2], reviewed releases, spoken at conferences on FlexJS and more receintly created the website for the FlexJS summit held at the last ApacheCon [3] and have been working on a FlexJS application. Thanks, Justin 1. https://github.com/apache/flex-sdk/graphs/contributors 2. https://github.com/apache/flex-asjs/graphs/contributors 3. https://us.apacheflexjs.org
Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.
Hi, > I think if booleans could fail even non-strict equality checks when they > are not initialized, then we should always initialize booleans, like we > currently do with int and uint. +1 > I would still like the see the compiler initialize everything by default so > that ActionScript behaves like ActionScript. I think we're making a mistake > by making non-initialization the default. Maybe I'll convince others > eventually. No need to convince me less bugs and no implicit casting is a better thing. Thanks, Justin
