Re: [DISCUSS] Apache Flex SDK Installer 2.0 - RC2
Nick, If you are planning to work on more locale strings, I strongly suggest that you check out this AIR app that Roland created. You can find it attached to the JIRA issue here [1] It will make your life much easier. Please feel free to provide feedback on the app as well. Thanks, Om [1] https://issues.apache.org/jira/browse/FLEX-0 On Fri, Jan 4, 2013 at 7:02 AM, Nick Tsitlakidis ni...@perfectedz.comwrote: I always thought that some parts cant or shouldn't be translated in applications. One of these cases I think is the software licenses because there is room for a lot of errors in this kind of translations. That's why I didn't translate these. Anyway, it looks like I'm wrong since there are translations for the other locales so I'll check them out. I thought other locales had them in English as well. On Fri, Jan 4, 2013 at 4:41 PM, Carol Frampton cfram...@adobe.com wrote: minor issues with current code For the Portuguese locale, the BROWSE button is SELEC. and the NEXT button is PROX. In RuntimeLocale.as I see content[BTN_LABEL_BROWSE]= ; content[BTN_LABEL_NEXT]=PROX.; For the Greek locale, the text for the license agreements are in English. I think the whole license agreement selection window is still confusing but good enough for now. Carol On 1/3/13 8 :11PM, Om bigosma...@gmail.com wrote: The source and binary kits for both Mac and Windows are available here: http://people.apache.org/~bigosmallm/installapacheflex_2.0_RC2/ * Issues fixed in RC2: * 1. Fixed issue where changing languages caused selections to be cleared 2. While changing languages, buttons will automatically enlarge to fit all the text 3. More translations made possible by Roland and Nick 4. Fixed README, RELEASE_NOTES, RELEASE_GUIDE and build.properties files for more accuracy. Issues fixed in RC1: 1. UI of the components selection and license screen has been fixed to use just checkboxes for selection 2. All the various locales have been enabled. 3. By default, Apache Flex SDK Installer 2.0 downloads Adobe Flash Player 11.1 and Adobe AIR SDK 3.4. If you want to change it to any other supported combination, you save a copy of the config file found at: http://incubator.apache.org/flex/sdk-installer-config-2.0.xml, modify the download urls to point to the required versions. Then run the app from command line mode with the optional command line parameter: -config=path to config file Thanks, Om Justin -- Nick Tsitlakidis, CEO and Software Architect at Perfect Edge LTD. www.perfectedz.com
Re: svn commit: r1428687 - /incubator/flex/utilities/trunk/installer/RELEASE_GUIDE
Thanks! I was looking for this a while ago but forgot about it. Do you mind if I moved it into utilities/build directory? That seems like a more appropriate location for this script . Om On Fri, Jan 4, 2013 at 12:50 PM, Carol Frampton cfram...@adobe.com wrote: Justin, This seems rather complicated. The Apache script sign_and_hash.sh just needs to be run on the files in the release directory. We have a copy of the script in the sdk/trunk/build directory. cd release ./path/to/sign_and_hash.sh Carol On 1/3/13 7 :43PM, jmcl...@apache.org jmcl...@apache.org wrote: Author: jmclean Date: Fri Jan 4 00:43:22 2013 New Revision: 1428687 URL: http://svn.apache.org/viewvc?rev=1428687view=rev Log: change version 2.0.0 to 2.0.1 Modified: incubator/flex/utilities/trunk/installer/RELEASE_GUIDE Modified: incubator/flex/utilities/trunk/installer/RELEASE_GUIDE URL: http://svn.apache.org/viewvc/incubator/flex/utilities/trunk/installer/RELE ASE_GUIDE?rev=1428687r1=1428686r2=1428687view=diff == --- incubator/flex/utilities/trunk/installer/RELEASE_GUIDE (original) +++ incubator/flex/utilities/trunk/installer/RELEASE_GUIDE Fri Jan 4 00:43:22 2013 @@ -48,18 +48,18 @@ This step cd release -gpg --armor --output apache-flex-sdk-installer-2.0.0-bin.exe.asc --detach-sig apache-flex-sdk-installer-2.0.0-bin.exe (on Windows) -gpg --armor --output apache-flex-sdk-installer-2.0.0-bin.dmg.asc --detach-sig apache-flex-sdk-installer-2.0.0-bin.dmg (on Mac) -gpg --armor --output apache-flex-sdk-installer-2.0.0-src.tar.gz.asc --detach-sig apache-flex-sdk-installer-2.0.0-src.tar.gz -gpg --armor --output apache-flex-sdk-installer-2.0.0-src.zip.asc --detach-sig apache-flex-sdk-installer-2.0.0-src.zip +gpg --armor --output apache-flex-sdk-installer-2.0.1-bin.exe.asc --detach-sig apache-flex-sdk-installer-2.0.1-bin.exe (on Windows) +gpg --armor --output apache-flex-sdk-installer-2.0.1-bin.dmg.asc --detach-sig apache-flex-sdk-installer-2.0.1-bin.dmg (on Mac) +gpg --armor --output apache-flex-sdk-installer-2.0.1-src.tar.gz.asc --detach-sig apache-flex-sdk-installer-2.0.1-src.tar.gz +gpg --armor --output apache-flex-sdk-installer-2.0.1-src.zip.asc --detach-sig apache-flex-sdk-installer-2.0.1-src.zip -This step creates the release artifacts InstallApacheFlex.exe.asc, apache-flex-sdk-installer-2.0.0-src.tar.gz.asc and apache-flex-sdk-installer-2.0.0-src.zip.asc +This step creates the release artifacts InstallApacheFlex.exe.asc, apache-flex-sdk-installer-2.0.1-src.tar.gz.asc and apache-flex-sdk-installer-2.0.1-src.zip.asc 6. Run: -gpg --print-md MD5 apache-flex-sdk-installer-2.0.0-bin.exe apache-flex-sdk-installer-2.0.0-bin.exe.md5 (On Windows) -gpg --print-md MD5 apache-flex-sdk-installer-2.0.0-bin.dmg apache-flex-sdk-installer-2.0.0-bin.dmg.md5 (On Mac) -gpg --print-md MD5 apache-flex-sdk-installer-2.0.0-src.tar.gz apache-flex-sdk-installer-2.0.0-src.tar.gz.md5 -gpg --print-md MD5 apache-flex-sdk-installer-2.0.0-src.zip apache-flex-sdk-installer-2.0.0-src.zip.md5 +gpg --print-md MD5 apache-flex-sdk-installer-2.0.1-bin.exe apache-flex-sdk-installer-2.0.1-bin.exe.md5 (On Windows) +gpg --print-md MD5 apache-flex-sdk-installer-2.0.1-bin.dmg apache-flex-sdk-installer-2.0.1-bin.dmg.md5 (On Mac) +gpg --print-md MD5 apache-flex-sdk-installer-2.0.1-src.tar.gz apache-flex-sdk-installer-2.0.1-src.tar.gz.md5 +gpg --print-md MD5 apache-flex-sdk-installer-2.0.1-src.zip apache-flex-sdk-installer-2.0.1-src.zip.md5 7. In the /installer directory, run: ant rat-report
Re: svn commit: r1428687 - /incubator/flex/utilities/trunk/installer/RELEASE_GUIDE
I meant to say: */utilities/trunk/build* On Fri, Jan 4, 2013 at 1:49 PM, Om bigosma...@gmail.com wrote: Thanks! I was looking for this a while ago but forgot about it. Do you mind if I moved it into utilities/build directory? That seems like a more appropriate location for this script . Om On Fri, Jan 4, 2013 at 12:50 PM, Carol Frampton cfram...@adobe.comwrote: Justin, This seems rather complicated. The Apache script sign_and_hash.sh just needs to be run on the files in the release directory. We have a copy of the script in the sdk/trunk/build directory. cd release ./path/to/sign_and_hash.sh Carol On 1/3/13 7 :43PM, jmcl...@apache.org jmcl...@apache.org wrote: Author: jmclean Date: Fri Jan 4 00:43:22 2013 New Revision: 1428687 URL: http://svn.apache.org/viewvc?rev=1428687view=rev Log: change version 2.0.0 to 2.0.1 Modified: incubator/flex/utilities/trunk/installer/RELEASE_GUIDE Modified: incubator/flex/utilities/trunk/installer/RELEASE_GUIDE URL: http://svn.apache.org/viewvc/incubator/flex/utilities/trunk/installer/RELE ASE_GUIDE?rev=1428687r1=1428686r2=1428687view=diff == --- incubator/flex/utilities/trunk/installer/RELEASE_GUIDE (original) +++ incubator/flex/utilities/trunk/installer/RELEASE_GUIDE Fri Jan 4 00:43:22 2013 @@ -48,18 +48,18 @@ This step cd release -gpg --armor --output apache-flex-sdk-installer-2.0.0-bin.exe.asc --detach-sig apache-flex-sdk-installer-2.0.0-bin.exe (on Windows) -gpg --armor --output apache-flex-sdk-installer-2.0.0-bin.dmg.asc --detach-sig apache-flex-sdk-installer-2.0.0-bin.dmg (on Mac) -gpg --armor --output apache-flex-sdk-installer-2.0.0-src.tar.gz.asc --detach-sig apache-flex-sdk-installer-2.0.0-src.tar.gz -gpg --armor --output apache-flex-sdk-installer-2.0.0-src.zip.asc --detach-sig apache-flex-sdk-installer-2.0.0-src.zip +gpg --armor --output apache-flex-sdk-installer-2.0.1-bin.exe.asc --detach-sig apache-flex-sdk-installer-2.0.1-bin.exe (on Windows) +gpg --armor --output apache-flex-sdk-installer-2.0.1-bin.dmg.asc --detach-sig apache-flex-sdk-installer-2.0.1-bin.dmg (on Mac) +gpg --armor --output apache-flex-sdk-installer-2.0.1-src.tar.gz.asc --detach-sig apache-flex-sdk-installer-2.0.1-src.tar.gz +gpg --armor --output apache-flex-sdk-installer-2.0.1-src.zip.asc --detach-sig apache-flex-sdk-installer-2.0.1-src.zip -This step creates the release artifacts InstallApacheFlex.exe.asc, apache-flex-sdk-installer-2.0.0-src.tar.gz.asc and apache-flex-sdk-installer-2.0.0-src.zip.asc +This step creates the release artifacts InstallApacheFlex.exe.asc, apache-flex-sdk-installer-2.0.1-src.tar.gz.asc and apache-flex-sdk-installer-2.0.1-src.zip.asc 6. Run: -gpg --print-md MD5 apache-flex-sdk-installer-2.0.0-bin.exe apache-flex-sdk-installer-2.0.0-bin.exe.md5 (On Windows) -gpg --print-md MD5 apache-flex-sdk-installer-2.0.0-bin.dmg apache-flex-sdk-installer-2.0.0-bin.dmg.md5 (On Mac) -gpg --print-md MD5 apache-flex-sdk-installer-2.0.0-src.tar.gz apache-flex-sdk-installer-2.0.0-src.tar.gz.md5 -gpg --print-md MD5 apache-flex-sdk-installer-2.0.0-src.zip apache-flex-sdk-installer-2.0.0-src.zip.md5 +gpg --print-md MD5 apache-flex-sdk-installer-2.0.1-bin.exe apache-flex-sdk-installer-2.0.1-bin.exe.md5 (On Windows) +gpg --print-md MD5 apache-flex-sdk-installer-2.0.1-bin.dmg apache-flex-sdk-installer-2.0.1-bin.dmg.md5 (On Mac) +gpg --print-md MD5 apache-flex-sdk-installer-2.0.1-src.tar.gz apache-flex-sdk-installer-2.0.1-src.tar.gz.md5 +gpg --print-md MD5 apache-flex-sdk-installer-2.0.1-src.zip apache-flex-sdk-installer-2.0.1-src.zip.md5 7. In the /installer directory, run: ant rat-report
Re: svn commit: r1428687 - /incubator/flex/utilities/trunk/installer/RELEASE_GUIDE
So, should I just make a copy under utilities/trunk/installer? On Fri, Jan 4, 2013 at 2:11 PM, Justin Mclean jus...@classsoftware.comwrote: I'd leave it where it is each imo you should be able to build each project from its own trunk and not have to check out multiple trunks
Re: svn commit: r1428687 - /incubator/flex/utilities/trunk/installer/RELEASE_GUIDE
BTW, this script does not work for me on windows (cygwin) This is what I get: $ ./sign_and_hash.sh ./sign_and_hash.sh: line 48: $'\r': command not found ./sign_and_hash.sh: line 49: $'\r': command not found ./sign_and_hash.sh: line 50: syntax error near unexpected token `$'do\r'' '/sign_and_hash.sh: line 50: `for file in *; do On Fri, Jan 4, 2013 at 2:13 PM, Om bigosma...@gmail.com wrote: So, should I just make a copy under utilities/trunk/installer? On Fri, Jan 4, 2013 at 2:11 PM, Justin Mclean jus...@classsoftware.comwrote: I'd leave it where it is each imo you should be able to build each project from its own trunk and not have to check out multiple trunks
Re: svn commit: r1428687 - /incubator/flex/utilities/trunk/installer/RELEASE_GUIDE
Yup, that fixed it. Thanks! On Fri, Jan 4, 2013 at 2:40 PM, Alex Harui aha...@adobe.com wrote: That's a line ending issue. Run dos2unix on it. On 1/4/13 2:24 PM, Om bigosma...@gmail.com wrote: BTW, this script does not work for me on windows (cygwin) This is what I get: $ ./sign_and_hash.sh ./sign_and_hash.sh: line 48: $'\r': command not found ./sign_and_hash.sh: line 49: $'\r': command not found ./sign_and_hash.sh: line 50: syntax error near unexpected token `$'do\r'' '/sign_and_hash.sh: line 50: `for file in *; do On Fri, Jan 4, 2013 at 2:13 PM, Om bigosma...@gmail.com wrote: So, should I just make a copy under utilities/trunk/installer? On Fri, Jan 4, 2013 at 2:11 PM, Justin Mclean jus...@classsoftware.comwrote: I'd leave it where it is each imo you should be able to build each project from its own trunk and not have to check out multiple trunks -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
Fixed RELEASE_NOTES and the issue that Carol raised with losing selections while changing languages. Thanks, Om On Wed, Jan 2, 2013 at 2:06 PM, Nick Tsitlakidis ni...@perfectedz.comwrote: Having a quick look it seems there are places where translation doesn't exist. For example the next button keeps the NEXT as the label. Also the Select installation directory doesn't change. I'll make a list of the changes I think you should do (whether it is capitalization or translation) and you can choose what fits in your schedule. Sounds good? On Wed, Jan 2, 2013 at 11:44 PM, Nick Tsitlakidis ni...@perfectedz.com wrote: damn, sorry for posting on the other thread. I got confused with all the emails. Sure I can, I'll let you know first thing in the morning (it's midnight here at the moment) On Wed, Jan 2, 2013 at 11:32 PM, Alex Harui aha...@adobe.com wrote: Hi Nick, The truncation issues might have to wait, but can you tell use where the incorrect capitalization is so we can try to fix it? Thanks, -Alex On 1/2/13 7:32 AM, Nick Tsitlakidis ni...@perfectedz.com wrote: Following Carol's comments, using the Greek locale also has some inconsistencies. For example incorrect capitalization and problems with truncation as well. Other than that, using the installer in a clean system (no other version of the installer existing) worked great. On Wed, Jan 2, 2013 at 5:03 PM, Carol Frampton cfram...@adobe.com wrote: Just gave this a try. Here are my comments regarding the installation and use: 1. When I tried to install it I got that there is something wrong AIR error which is really unhelpful but I knew it meant I had to uninstall the old installer first. Why can't the old installer and the new installer co-exist since they are each installing a different version of Flex? 2. As Justin said, the DISCLAIMER needs to be removed. 3. Depending on the locale, the text in some of the buttons is truncated which looks bad. For example, try French. 4. When I switch the language in the middle of checking all the license agreements, whatever I've already checked is cleared. Carol On 1/1/13 1 :23AM, Om bigosma...@gmail.com wrote: This is version 2.0 of Apache Flex SDK Installer. This version lets users download the Apache Flex SDK 4.9 and its required dependencies. https://people.apache.org/~bigosmallm/installapacheflex_2.0_RC1/ Significant improvements over previous version: 1. UI of the components selection and license screen has been fixed to use just checkboxes for selection 2. All the various locales have been enabled. 3. By default, Apache Flex SDK Installer 2.0 downloads Adobe Flash Player 11.1 and Adobe AIR SDK 3.4. If you want to change it to any other supported combination, you save a copy of the config file found at: http://incubator.apache.org/flex/sdk-installer-config-2.0.xml, modify the download urls to point to the required versions. Then run the app from command line mode with the optional command line parameter: -config=path to config file Please take it for a spin and let us know your feedback. We would like to put up a vote asap and release this right away! Thanks, Om -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Nick Tsitlakidis, CEO and Software Architect at Perfect Edge LTD. www.perfectedz.com -- Nick Tsitlakidis, CEO and Software Architect at Perfect Edge LTD. www.perfectedz.com
Re: Installer Button Truncation
Yes please :-) Om On Thu, Jan 3, 2013 at 3:34 PM, Alex Harui aha...@adobe.com wrote: Hey Om, After looking at Nick¹s greek translations, I got motivated enough to code up a way to get the buttons to grow in a nice way (at least to my eyes). I just finished it and can check it in. Do you want it for RC2? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Installer Button Truncation
Looks very nice! Thanks for this fix. Justin, are you ready to cut an RC2? Om On Thu, Jan 3, 2013 at 3:41 PM, Alex Harui aha...@adobe.com wrote: OK, it's in. Rev 1428672. On 1/3/13 3:36 PM, Om bigosma...@gmail.com wrote: Yes please :-) Om On Thu, Jan 3, 2013 at 3:34 PM, Alex Harui aha...@adobe.com wrote: Hey Om, After looking at Nick¹s greek translations, I got motivated enough to code up a way to get the buttons to grow in a nice way (at least to my eyes). I just finished it and can check it in. Do you want it for RC2? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Installer Button Truncation
On Thu, Jan 3, 2013 at 4:10 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Justin, are you ready to cut an RC2? Can do if the satellite uplink is up for it. ;-) Justin Cool. I have bumped up the build.number, etc. and checked it in. All you have to do is sync up and do ant release. Once you let me know, I will put all the artifacts together and start a new [DISCUSS] thread. Thanks, Om
[DISCUSS] Apache Flex SDK Installer 2.0 - RC2
The source and binary kits for both Mac and Windows are available here: http://people.apache.org/~bigosmallm/installapacheflex_2.0_RC2/ * Issues fixed in RC2: * 1. Fixed issue where changing languages caused selections to be cleared 2. While changing languages, buttons will automatically enlarge to fit all the text 3. More translations made possible by Roland and Nick 4. Fixed README, RELEASE_NOTES, RELEASE_GUIDE and build.properties files for more accuracy. Issues fixed in RC1: 1. UI of the components selection and license screen has been fixed to use just checkboxes for selection 2. All the various locales have been enabled. 3. By default, Apache Flex SDK Installer 2.0 downloads Adobe Flash Player 11.1 and Adobe AIR SDK 3.4. If you want to change it to any other supported combination, you save a copy of the config file found at: http://incubator.apache.org/flex/sdk-installer-config-2.0.xml, modify the download urls to point to the required versions. Then run the app from command line mode with the optional command line parameter: -config=path to config file Thanks, Om Justin
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On Jan 1, 2013 11:44 PM, Alex Harui aha...@adobe.com wrote: On 1/1/13 11:30 PM, Om bigosma...@gmail.com wrote: On Tue, Jan 1, 2013 at 11:23 PM, Alex Harui aha...@adobe.com wrote: On 1/1/13 11:09 PM, Om bigosma...@gmail.com wrote: On Jan 1, 2013 10:42 PM, Alex Harui aha...@adobe.com wrote: Ok, here is my logic: -From [1], a release is anything that is published beyond the group that owns it.. Putting the config.xml on the site to be consumed by one of our binaries makes it part of a release and requires a vote before it happens. I still don't agree with this logic. The config xml is placed on our website which is completely under our control. Which means that we don't really 'release' it. We are taking something from SVN and consuming it in a binary distribution that we've deployed to our site and telling the world to use it. We consume a lot of resources from the website - the flex sdk, the md5, the mirror url cgi script (which IS code). We dont release any of those in the source kit for the Installer. How is the config xml any different? We also consume a host of external dependencies like flash player, air sdk, etc. According to your logic, we cannot do this because we cannot 'release' those files. It is in our SVN with the rest of our code and dictates what the code does. None of the other things you listed do both. I don't see these two conditions in the Apache release guide. It is your interpretation of what it says, which I don't agree with. In any case, what exactly do you mean by 'dictate'? Please explain how that makes it source? Why is the mirror cgi script not considered to being 'dictating' the app? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On Jan 2, 2013 6:37 AM, Carol Frampton cfram...@adobe.com wrote: flex/utilities/trunk/installer/build.properties needs updating FLEX_HOME_MAC still points to 4.8.0 and FLEX_HOME_WIN points to ApacheFlex4.9.0 (I'm not sure where this name comes from but the formatting seems odd - I dislike names with spaces but given the rest of the path why not Apache Flex 4.9.0?) #Flex Locations FLEX_HOME_WIN=C:/Program Files (x86)/Adobe/Adobe Flash Builder 4.6/sdks/ApacheFlex4.9.0/ FLEX_HOME_MAC=/Applications/Adobe Flash Builder 4.6/sdks/4.8.0/ Carol That is how I have named the directory for 4.9 on my machine. You are free to name it however you want and update build.properties before running ant. In any case, one cannot guarantee that the path would be same across computers. Thanks, Om
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On Jan 2, 2013 7:04 AM, Carol Frampton cfram...@adobe.com wrote: Just gave this a try. Here are my comments regarding the installation and use: 1. When I tried to install it I got that there is something wrong AIR error which is really unhelpful but I knew it meant I had to uninstall the old installer first. Why can't the old installer and the new installer co-exist since they are each installing a different version of Flex? Did you try to install the RC or did you install from what you built yourself? The latter should give the problem you mentioned since you would be signing with a temp generated certificate. 2. As Justin said, the DISCLAIMER needs to be removed. 3. Depending on the locale, the text in some of the buttons is truncated which looks bad. For example, try French. 4. When I switch the language in the middle of checking all the license agreements, whatever I've already checked is cleared. Carol On 1/1/13 1 :23AM, Om bigosma...@gmail.com wrote: This is version 2.0 of Apache Flex SDK Installer. This version lets users download the Apache Flex SDK 4.9 and its required dependencies. https://people.apache.org/~bigosmallm/installapacheflex_2.0_RC1/ Significant improvements over previous version: 1. UI of the components selection and license screen has been fixed to use just checkboxes for selection 2. All the various locales have been enabled. 3. By default, Apache Flex SDK Installer 2.0 downloads Adobe Flash Player 11.1 and Adobe AIR SDK 3.4. If you want to change it to any other supported combination, you save a copy of the config file found at: http://incubator.apache.org/flex/sdk-installer-config-2.0.xml, modify the download urls to point to the required versions. Then run the app from command line mode with the optional command line parameter: -config=path to config file Please take it for a spin and let us know your feedback. We would like to put up a vote asap and release this right away! Thanks, Om
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On Jan 2, 2013 8:06 AM, Carol Frampton cfram...@adobe.com wrote: On 1/2/13 10 :44AM, Om bigosma...@gmail.com wrote: On Jan 2, 2013 6:37 AM, Carol Frampton cfram...@adobe.com wrote: flex/utilities/trunk/installer/build.properties needs updating FLEX_HOME_MAC still points to 4.8.0 and FLEX_HOME_WIN points to ApacheFlex4.9.0 (I'm not sure where this name comes from but the formatting seems odd - I dislike names with spaces but given the rest of the path why not Apache Flex 4.9.0?) #Flex Locations FLEX_HOME_WIN=C:/Program Files (x86)/Adobe/Adobe Flash Builder 4.6/sdks/ApacheFlex4.9.0/ FLEX_HOME_MAC=/Applications/Adobe Flash Builder 4.6/sdks/4.8.0/ Carol That is how I have named the directory for 4.9 on my machine. You are free to name it however you want and update build.properties before running ant. In any case, one cannot guarantee that the path would be same across computers. I realize this but what we ship should at least point to 4.9.0 or something to that effect so people aren't confused. I do have to set FLEX_HOME to build which I don't like to have to do but that is a different issue. Source files in svn should not never have something particular to one person's machine. I'd prefer to see both paths set to 4.9.0 or Apache Flex 4.9.0. Carol I don't understand why, but I have no problems if you make this change. Thanks, Om
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
We don't 'release' the installer badge, but it consumes the same exact config xml. Are you saying that we need to release the source for the badge as well? IMO, absolutely. Did we not do this in the prior version? Then we really messed up that release. I thought the same source created the badge installer, but it got packaged differently before posting on the site. We discussed this in the past and decided not to officially release the badge. It was also decided to include a link to this disclaimer [1] in the badge [1] http://incubator.apache.org/flex/installerbadge/disclaimer.html
Re: [MENTORS] Release Policy
Thanks Greg. Alex, I think it is pretty clear from Greg's response on how we want to proceed. Do you have any more clarifications, or can we go ahead with the [VOTE] for RC1? Thanks, Om On Wed, Jan 2, 2013 at 8:34 AM, Greg Reddin gred...@gmail.com wrote: On Wed, Jan 2, 2013 at 10:14 AM, Alex Harui aha...@adobe.com wrote: As you may have seen, there is a long thread going on about the installer and its deployment of a .xml file on the Apache Flex website. The main question is: Is this .xml file considered “source material” and therefore does it require a vote before being pushed to the Apache Flex website? I haven't completely followed the discussion, but here's my opinion, assuming I understand everything correctly: The XML file is similar to a properties file or other config file that is shipped with a product. We ship one out with the release so people using the release will have an example, but, for the most part, they are expected to change it if they want to configure the installer to do something different than its out of the box configuration. If this understanding is correct, then it must be voted on before being released - i.e. included in a distribution that is an official Apache release. Things pushed to the website do not need to be voted on normally. The website is not an official Apache release. It is updated by checking things into a Subversion tree. It is peer-reviewed in the same manner that source code is when it is checked in. If a committer objects to a commit he/she can veto the commit and offer an alternative. If the community can't reach consensus about what should be committed then a vote may be required. I've never seen this happen. I've only rarely seen someone veto a commit. Usually the reason is obvious and there is no argument. I'm sure somewhere at Apache there has been a disputed commit that was hard to work out on a dev list, but I have not been part of that process. So, just in case the above didn't answer your questions, see below: The follow-up questions are: 1) Can such a file even be pushed to the Apache Flex website or can it only live in the dist folder? Yes it can be pushed to the site. The one is the dist folder would act as an example. The two files are different files which go through different review processes before being published: one as part of a release, the other to the website. 2) Why does website content not require a vote before publishing (or is it supposed to)? Because it's not a release. It's peer-reviewed just like source code, but it's not released. 3) If not, what is the “line” that defines what requires a vote? Is it that it is human-readable content? If it's released it requires a vote. If not it does not - unless consensus cannot be reached about what the content should be. Greg Thanks for your thoughts on this matter. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
[DISCUSS] Continuing discussion on Installer 2.0 RC1
On Wed, Jan 2, 2013 at 12:53 PM, Alex Harui aha...@adobe.com wrote: On 1/2/13 12:18 PM, Om bigosma...@gmail.com wrote: Thanks Greg. Alex, I think it is pretty clear from Greg's response on how we want to proceed. Do you have any more clarifications, or can we go ahead with the [VOTE] for RC1? Yes, it is good to learn that publishing on the site is not considered a release and you can publish the xml file on the site without a vote. You can start a vote for RC1 if you want, but I think we should fix up a few of the issues folks have brought up so far. The ones I saw are: 1) the name of the default value for FLEX_HOME_MAC folder. Can you or Carol fix this and check it in? 2) Greek locale capitalization (I think we'll probably have to live with truncation issues in this version like prior versions) Truncated labels automatically show tooltips. So we are not a lot of functionality. But I do agree it doesnt look too good. I am loathe to changing the size of buttons. Maybe someone can make the text's font size to scale down automatically based on content? Bonus: This would be a very nice feature addition to the Flex SDK :-) 3) remove DISCLAIMER file This was removed a while ago by Justin - rev 1427021 [ http://svn.apache.org/viewvc?view=revisionrevision=1427021] 4) Examine the checkbox issue Carol brought up about changing locales after checking some of the boxes. If it will be risky/painful, it can probably be deferred. I will take a look at this tonight. I actually haven't looked at RC1 myself. I will do that next. Also, I still don't like the fact that someone running the installer sometime in the future can potentially have a different version installed, and I still don't like having the incubator URLs. I wish we could get our final URLs before sending out this release. I am okay with waiting if we know that the timeframe is in the order of days and not weeks/months. Thanks, Om
Re: [DISCUSS] Continuing discussion on Installer 2.0 RC1
On Wed, Jan 2, 2013 at 1:42 PM, Nick Tsitlakidis ni...@perfectedz.comwrote: I can spend some time with the installer tomorrow and make some notes on what needs to change for the Greek locale if you guys plan to spend time and have it fixed in this release. If not I'll add it in my todo list for next week. Nick, If you can take a look asap, that would be great. We are probably going to have a couple more RCs and it would be nice to fix as many issues as possible for Installer 2.0. Thanks, Om On Wed, Jan 2, 2013 at 11:31 PM, Alex Harui aha...@adobe.com wrote: On 1/2/13 1:04 PM, Om bigosma...@gmail.com wrote: On Wed, Jan 2, 2013 at 12:53 PM, Alex Harui aha...@adobe.com wrote: On 1/2/13 12:18 PM, Om bigosma...@gmail.com wrote: Thanks Greg. Alex, I think it is pretty clear from Greg's response on how we want to proceed. Do you have any more clarifications, or can we go ahead with the [VOTE] for RC1? Yes, it is good to learn that publishing on the site is not considered a release and you can publish the xml file on the site without a vote. You can start a vote for RC1 if you want, but I think we should fix up a few of the issues folks have brought up so far. The ones I saw are: 1) the name of the default value for FLEX_HOME_MAC folder. Can you or Carol fix this and check it in? I'll do it. Carol is out rest of today I think. 2) Greek locale capitalization (I think we'll probably have to live with truncation issues in this version like prior versions) Truncated labels automatically show tooltips. So we are not a lot of functionality. But I do agree it doesnt look too good. I am loathe to changing the size of buttons. Maybe someone can make the text's font size to scale down automatically based on content? Bonus: This would be a very nice feature addition to the Flex SDK :-) Scaling font size would make it unreadable in many cases. I think the SDK feature you are supposed to use is constraint columns. I think the visual designers are probably ok having buttons grow to fit the text, but they want two buttons on top of each other to grow to the size of the larger button. But I just want us to get the capitalization right in this release. Let's see if we can get someone to tell us what to change. I wish we could get our final URLs before sending out this release. I am okay with waiting if we know that the timeframe is in the order of days and not weeks/months. I guess the best plan is to make an RC2 soon with the non-final URLs and be prepared to cancel the vote if we get our final URLs on Monday next week. I think the issue is that the board secretaries are still out on holiday and don't have final minutes for infra to use to build out the TLP stuff. Thanks, Om -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Nick Tsitlakidis, CEO and Software Architect at Perfect Edge LTD. www.perfectedz.com
Re: [DISCUSS] Continuing discussion on Installer 2.0 RC1
On Wed, Jan 2, 2013 at 2:43 PM, Alex Harui aha...@adobe.com wrote: Om, Made the change to build.properties and fixed some typo's in the release notes. I think RELEASE_NOTES typically also have lists of bugs fixed or improvements made. Can you add that to the release notes? Will do! Thanks, Om
Re: alternatives to flash builder
Since we are having this discussion on flex-dev, here is something every Apache Flex committer needs to know :-) IntelliJ IDEA is available for free for open source developers [1] I just got my free license and am getting my feet wet with IntelliJ. Few things that struck me immediately: 1. UML support is built in. 2. Code analysis (via Flex PMD?) available built in 3. Works great with Apache Flex 4.9 4. Very primitive UI Design View available as an add-on. It in fact, seems to be an AIR app that talks back to the IDE. Lots of scope for improvement with this feature, though. Thanks, Om [1] http://www.jetbrains.com/idea/buy/buy.jsp#openSource On Wed, Jan 2, 2013 at 9:34 AM, Frédéric THOMAS webdoubl...@hotmail.comwrote: After a long time tweaking, building Flex / Maven project using eclipse/FB, I prefer to use Intellij also because it doesn't need any m2e like tools to map the maven config to the IDE project configuration files, which anyway doesn't work for Flex under FB, with IntelliJ, there is no differences between the Maven config and the IDE project configuration files, there is no double config which too often is source of conflicts between what you configured and what is built by FB. - Fred -Original Message- From: Alain Ekambi [mailto:jazzmatad...@gmail.com] Sent: Wednesday, January 02, 2013 6:02 PM To: flex-dev@incubator.apache.org Subject: Re: alternatives to flash builder We use basic eclipse with the gwt plugin. All free in java. Nothing beats that :) On Jan 2, 2013 5:39 PM, Nick Tsitlakidis ni...@perfectedz.com wrote: Never tried FDT but I love IntelliJ. It certainly needs some time so you can understand it's concepts but I think you will be greatly rewarded because of its features. It's coding assist tools are from another world (if you like that sort of assistance). There is also UML support that directly talks to your Flex classes and other small surprises all over the IDE that makes the development really fun. I sound like I advertise it, I know, but I was using Flash Builder before and when I made the switch I never looked back. That being said, there are some small features that aren't supported by Intellij and you can find them in FB, but the team at Jetbrains is taking feedback VERY seriously so they always push new functionality. On Wed, Jan 2, 2013 at 5:17 PM, aYo ~ a...@binitie.com wrote: Every time I try intelliJ there is some error or the other. I'd love to try it but installing it has been a bitch on Linux and Windows for me On Jan 2, 2013 3:11 PM, Tianzhen Lin tang...@usa.net wrote: Most recent switch to Flash Builder 4.7 was nothing but disappointment. I don't know if it happens to anyone, FB 4.7 hangs on me many times, and it uses substantially more CPU power, and I have to restart it at least once every hour, when the hang up happens at the wrong time, my workspace would be broken and I would have to rebuild the workspace. It went so bad that eventually I had to switch back to FB 4.6. Furthermore, I submitted a serial # request to update 4.7, the ticket was closed and Adobe made not contact with me. I started to worry if I could rely on Adobe for any future Flex development My projects generally are broken down to a few library projects and one Flex project. While FlashDevelop is my favorite choice of AS3 IDE, the lacking of multiple-project support makes it inconvenient for me to use FD for serious development I have not tried FDT or IntelliJ IDEA, and I would love to hear anyone with experience of both providing some insights on their pro's and con's. Tangent -Original Message- From: Jaydeep Tank [mailto:jaydeep.t...@gmail.com] Sent: Wednesday, January 02, 2013 3:25 AM To: flex-dev@incubator.apache.org Subject: Re: alternatives to flash builder Hi, You ca use open source FlashDevelop IDE with Apache Flex SDK. http://www.flashdevelop.org/ Regards, Jaydeep Tank On 2 January 2013 13:48, Thomas Wawra twa...@gmail.com wrote: hi, are there alternatives to flash builder? thanks best regards thomas -- Nick Tsitlakidis, CEO and Software Architect at Perfect Edge LTD. www.perfectedz.com
[LAZY] Planning to commit Installer Locale Editor to SVN
Thanks Roland! If no one has objections, I would like to commit this to /flex/utilities/trunk/installerlLocaleEditor I think this will make life so much easier for people contributing other locales to the Installer. Also, I dont think we need to officially release this app. Developers can just check it out of svn and use it. Thanks, Om On Sat, Dec 29, 2012 at 4:10 AM, Roland Zwaga (JIRA) j...@apache.orgwrote: [ https://issues.apache.org/jira/browse/FLEX-0?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13540885#comment-13540885] Roland Zwaga commented on FLEX-0: - Hey Om, glad you like it. I just made some slight changes and added some sorting options for the translation keys. I've attached a new zip with the source and an installer. If you have any more suggestions please let me know. I think its pretty much finished now, but maybe you have some smart ideas :) cheers, Roland An easier way of managing the locales for the InstallApache application --- Key: FLEX-0 URL: https://issues.apache.org/jira/browse/FLEX-0 Project: Apache Flex Issue Type: Improvement Components: InstallApacheFlex Reporter: Roland Zwaga Priority: Minor Labels: InstallApacheFlex, utility Fix For: InstallApacheFlex 1.1 Attachments: RuntimeLocale.as Right now updating the translation for an existing locale, or creating a new locale for the InstallApache application involves quite a bit of copy/pasting. While the list of locales grows this problem will grow with it, IMHO. To try and combat this complexity I've created a small AIR application which is capable of loading, parsing and editing the RuntimeLocale.as (which contains all of the locale data) file of the InstallApache project. I'll attach both an FXP export of the FlashBuilder project as well as an AIR installer for the application. Should folks find the app useful I'll be happy to donate the code to Apache Flex. A huge credit goes out to Michael Schmalle who created the asblocks library (https://github.com/teotigraphix/as3-commons-asblocks) which takes care of the parsing and editing of actionscript source files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
The config is not part of the source. There is only a reference to its url in the installer app. The installer was designed with this scenario in mind. A copy is included as a convenience to the developer who uses it. In that sense it is more like a .properties file. We need to be able to change the sdk version without having to push an update to the installer. Bundling the config xml with the source or binary will cause issues . Thanks, Om On Jan 1, 2013 12:06 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, Apache only officially releases (and we are voting on) a source distribution for the installer. Would a run time loaded config file be really considered part of that source? Basically it's the same as the build.properties for the Flex SDK. While the build.properties is part of the source release kit you generally need to edit and change the values in it. The XML file is not compiled into the source it can also be changed/edited by the user to install other versions of the SDK or AIR. A typical version of it is included in the source (just like build.properties) see sdk-insaller-config-2.0.xml in the root src directory. Would you consider the disclaimer page to be part of the source? It's on the wiki and linked to by the application. Or the cgi scipt it uses to get the mirror? Where exactly do you draw the line? Either way when a vote is called for it only requires three more +1 than -1 votes and I don't see this as a reason for voting -1. Justin
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On Jan 1, 2013 8:22 AM, Alex Harui aha...@adobe.com wrote: On 1/1/13 1:29 AM, Om bigosma...@gmail.com wrote: The config is not part of the source. There is only a reference to its url in the installer app. The installer was designed with this scenario in mind. A copy is included as a convenience to the developer who uses it. In that sense it is more like a .properties file. We need to be able to change the sdk version without having to push an update to the installer. Bundling the config xml with the source or binary will cause issues . First, let me start off with saying that this kind of issue is a pain point for me as well. Unfortunately, Apache doesn't release just binaries. I have definitely considered launching my own company to handle the stuff that Apache doesn't do very well, like binary distributions. AFAIK, the app cannot run without this file. We author it, it lives in our SVN, etc., so it is source. The definition for binary distro is a compiled version of the source kit. I don't think you can remove files from the source distro in making it. The app will compile and run just fine even without the config xml being present in the source or binary distro. It is NOT source. Like the Flex SDK, .md5 file, the config xml is just another set of bytes that get loaded during runtime to be processed. The config xml does not get compiled into the binary distro. BTW, I'm not very familiar with .htaccess redirects, but I know we have to clear our builds from the incubator's dist folder when we get our final dist folder. Would redirects still work for fetching the old incubator release? If we just change the url for the flex sdk in the config xml that lives on our website, there is no need for redirects. How does the UI handle choosing which version to download? Justin went to all of this work to allow different player versions. We don't want to lock folks down to the latest Flex version. You can pass a config xml with any combination of FP and AIR sdk via the command line, using the -config option. Thanks, Om
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
The installer badge swf shares the config.xml, so the claim that it does not contribute to the content of our website is not true. The next release will first be locally tested by developers by pointing to a local copy of the config. Once we are happy with the installation process.com we switch it to point to to the one on the website and test locally. . This is how we test Release Candidates every time. We have had no problems so far. When we are ready to promote the installer release, that is when we update the config xml on the website. Also, in this case, because we started bundling TLF, we introduced a new sdk-installer-config-2.0.xml. This prevents us from affecting current installations. This was my and Erik's design as to how the Installer should work and update as new Flex SDKs are released. You are free to propose your ideas to solve these design issues. But none of your questions have anything to do with whether config.xml is source or not. I still maintain that it is not. Thanks, Om On Jan 1, 2013 10:49 AM, Dave Fisher dave2w...@comcast.net wrote: On Jan 1, 2013, at 10:25 AM, Alex Harui wrote: OK, so this looks like a recent change. It seems to me the issues are: 1) Is it ok to take a .xml file from SVN and publish it on the web without a vote? Especially since it does not contribute to the content of our web site. 2) Is this a correct implementation? I'm wondering how would we test the next release. As soon as you replace/update that .xml file so we can test the next installer we are forcing everyone to suddenly start taking the next version. I understand you are saying we don't need to test the installer ever again, but I think we'd need to at least run it ourselves. 3) Is it reasonable to suddenly have the .xml file cause a different version to install to the customer's computer? I think the answer is no to all 3. Or did I miss a thread and the mentors approved #1? Not by me. I agree with no to all 3. Flex is now a TLP and the Flex PMC has to decide. This is a suggestion, but it seems to me that parts of the installer configuration file belongs with the Apache Flex 4.9 release, and the rest belongs with the installer. BTW - all parts of releases need to be on the project's area on dist - this is official. Everything on dist gets copied to archives automatically. I think that there can be two configuration files for the installer. (1) Flex release installation configurations which include the range of supported Flash Player, etc. (2) Flex installer configurations which point to the installation configuration patterns. I think that this would decouple the two threads of release, make the configuration clearly part of a release and most importantly avoid the semantic game and edge cases about what is a release. With the 4.10 (or whatever release) the installer could be programmed to go to archives for older releases and configurations. HTH, Dave -Alex On 1/1/13 9:43 AM, Om bigosma...@gmail.com wrote: On Jan 1, 2013 8:22 AM, Alex Harui aha...@adobe.com wrote: On 1/1/13 1:29 AM, Om bigosma...@gmail.com wrote: The config is not part of the source. There is only a reference to its url in the installer app. The installer was designed with this scenario in mind. A copy is included as a convenience to the developer who uses it. In that sense it is more like a .properties file. We need to be able to change the sdk version without having to push an update to the installer. Bundling the config xml with the source or binary will cause issues . First, let me start off with saying that this kind of issue is a pain point for me as well. Unfortunately, Apache doesn't release just binaries. I have definitely considered launching my own company to handle the stuff that Apache doesn't do very well, like binary distributions. AFAIK, the app cannot run without this file. We author it, it lives in our SVN, etc., so it is source. The definition for binary distro is a compiled version of the source kit. I don't think you can remove files from the source distro in making it. The app will compile and run just fine even without the config xml being present in the source or binary distro. It is NOT source. Like the Flex SDK, .md5 file, the config xml is just another set of bytes that get loaded during runtime to be processed. The config xml does not get compiled into the binary distro. BTW, I'm not very familiar with .htaccess redirects, but I know we have to clear our builds from the incubator's dist folder when we get our final dist folder. Would redirects still work for fetching the old incubator release? If we just change the url for the flex sdk in the config xml that lives on our website, there is no need for redirects. How does the UI handle choosing which version to download? Justin went
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On Jan 1, 2013 9:49 PM, Alex Harui aha...@adobe.com wrote: On 1/1/13 2:18 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: Wouldn't we want to keep the config file on our website / SVN? It seems to me that placing the config file on any of the DISTS would be disasterious, as this contains the MD5 checksum that the app verifies to make sure the release wasn't tampered by the dist... Interesting point. Anybody know wny we don't fetch the MD5 from the apache.org DIST (sans Mirror as recommended by Apache). The app is hardcoded to look at the apache site for the MD5 file. We don't get it from any mirrors. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On Jan 1, 2013 10:42 PM, Alex Harui aha...@adobe.com wrote: Ok, here is my logic: -From [1], a release is anything that is published beyond the group that owns it.. Putting the config.xml on the site to be consumed by one of our binaries makes it part of a release and requires a vote before it happens. I still don't agree with this logic. The config xml is placed on our website which is completely under our control. Which means that we don't really 'release' it. We don't 'release' the installer badge, but it consumes the same exact config xml. Are you saying that we need to release the source for the badge as well? -Also from [1], All releases are in the form of the source materials needed to make changes to the software being released.. The config file gets changed with each release and therefore IMO it is considered source materials even though it is not source code. Not necessarily. We can ship Installer 3.0 with only UI improvements. No need to update the config xml in that case. -From [2], The role of the PMC from a Foundation perspective is oversight. The main role of the PMC is not code and not coding - but to ensure that all legal issues are addressed, that procedure is followed, and that each and every release is the product of the community as a whole. That is key to our litigation protection mechanisms. and later However those on the PMC are kept to a higher standard. As the PMC, and the chair in particular, are eyes and ears of the ASF Board, it is you that we rely on and need to trust to provide legal oversight. The board has the faculty to terminate a PMC at any time by resolution. As much as we want to get this release out the door, the fact is it is more important to make sure we are following policy. It is unfortunate that various logistical issues have prevented us from getting our final dist folder. But here we are and we have to work with Apache policy. [1] http://www.apache.org/dev/release#what [2] http://www.apache.org/foundation/how-it-works.html#pmc On 1/1/13 1:44 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Would you consider the disclaimer page to be part of the source? The DISCLAIMER file is in the source kit for incubating releases. I was referring to the disclaimer link in the application not the DISCLAIMER file. I don't think it is an issue if we pull up existing web pages, but IMO it is an issue to be publishing source materials on the site without a vote. Source kits are (potentially filtered) dumps of what is in SVN. And that correct with the installer, there's a source kit which someone can take and compile the application. I'm pretty sure Apache regulations would override any vote. What regulation exactly? Can you point to me page that state that you can't load XML files outside of it's SVN trunk? This is potentially a legal issue What is the legal issue here? The installer will be voted on and distributed in the normal Apache Way (apache.org/dist). The XML file is also in SVN at svn.apage.org that only Apache committers can access and change. The installer will only download official Apache releases that have been voted on and placed in apache.org/dist. I guess worse case a committer could modify the file XML file in SVN to download another Apache binary kit but I think we would notice that and fix. Thanks, Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On Tue, Jan 1, 2013 at 11:23 PM, Alex Harui aha...@adobe.com wrote: On 1/1/13 11:09 PM, Om bigosma...@gmail.com wrote: On Jan 1, 2013 10:42 PM, Alex Harui aha...@adobe.com wrote: Ok, here is my logic: -From [1], a release is anything that is published beyond the group that owns it.. Putting the config.xml on the site to be consumed by one of our binaries makes it part of a release and requires a vote before it happens. I still don't agree with this logic. The config xml is placed on our website which is completely under our control. Which means that we don't really 'release' it. We are taking something from SVN and consuming it in a binary distribution that we've deployed to our site and telling the world to use it. We consume a lot of resources from the website - the flex sdk, the md5, the mirror url cgi script (which IS code). We dont release any of those in the source kit for the Installer. How is the config xml any different? We also consume a host of external dependencies like flash player, air sdk, etc. According to your logic, we cannot do this because we cannot 'release' those files.
Re: Prepping for Installer 2.0 RC1
On Sun, Dec 30, 2012 at 9:37 PM, Alex Harui aha...@adobe.com wrote: Not sure. Any chance you are pointing at AIR SDK 3.1 somehow? Yes, that was it. I had an environment variable pointing to AIR SDK 3.1. Changing that fixed it. Installer 2.0 compiles and runs fine with AIR 3.4 via the build.xml. Justin, any luck with your issue? Thanks, Om On 12/30/12 4:37 PM, Om bigosma...@gmail.com wrote: BTW, the app compiles and runs fine with Apache Flex 4.9/AIR 3.4 when I run it from Flash Builder 4.6. On Sun, Dec 30, 2012 at 4:34 PM, Om bigosma...@gmail.com wrote: This is the error I am getting when I run ant release. Error in *bold* I googled this issue, it looks like quite a few folks have this issue with AIR 3.4. I have not been able to find out what is happening. Any ideas? C:\p\flex_os\workspace\flexroot\utilities\trunk\installerant release Buildfile: C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\build.xml clean: [delete] Deleting directory C:\p\flex_os\workspace\flexroot\utilities\trunk\i nstaller\build [delete] Deleting directory C:\p\flex_os\workspace\flexroot\utilities\trunk\i nstaller\libs [delete] Deleting directory C:\p\flex_os\workspace\flexroot\utilities\trunk\i nstaller\release createDirs: [echo] [echo] [echo] Execute the update-version target once, and only once, when you modifiy this app. [echo] This will increment the version number to allow the app to b e updated by the AIR installer. [echo] [echo] [mkdir] Created dir: C:\p\flex_os\workspace\flexroot\utilities\trunk\install er\build [mkdir] Created dir: C:\p\flex_os\workspace\flexroot\utilities\trunk\install er\release update-version-in-xml-files: [echo] version in InstallApacheFlex-app.xml will be 2.0.0 init: certificate: check-as3commons.swc: get-as3commons.swc: [mkdir] Created dir: C:\p\flex_os\workspace\flexroot\utilities\trunk\install er\libs [get] Getting: http://projects.yoolab.org/maven/content/repositories/relea ses/org/as3commons/as3commons-zip/1.0.0-alpha.1/as3commons-zip-1.0.0-alpha.1. swc [get] To: C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\libs\a s3commons-zip-1.0.0-alpha.1.swc [get] ... [get] Getting: http://projects.yoolab.org/maven/content/repositories/relea ses/org/as3commons/as3commons-zip/1.0.0-alpha.1/as3commons-zip-1.0.0-alpha.1. swc .md5 [get] To: C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\libs\a s3commons-zip-1.0.0-alpha.1.swc.md5 [get] . [delete] Deleting: C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\ libs\as3commons-zip-1.0.0-alpha.1.swc.md5 compile: [mxmlc] Loading configuration file C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\ApacheFlex4.9.0\frameworks\air-config.xml [mxmlc] C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\build\Inst allApacheFlex.swf (1511233 bytes) abortBuild: *packageair:* * [java] C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\src\Instal* *lApacheFlex-app.xml: error 102: Invalid namespace http://ns.adobe.com/air/applic* *ation/3.4* BUILD FAILED C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\build.xml:291: Java re turned: 12 Total time: 11 seconds On Sun, Dec 30, 2012 at 3:39 PM, Om bigosma...@gmail.com wrote: On Sun, Dec 30, 2012 at 3:36 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, I am using Apache Flex 4.8 to build the installer. Which means AIR 3.1, right? I think we should be using AF 4.9/AIR 3.4 - be nice if the SDK and installer were in sync. Justin Makes sense. i will get on it now. Mind posting what errors you are seeing? Om -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Prepping for Installer 2.0 RC1
Great! So you mind tagging trunk with 2.0 RC1? Thanks, Om On Dec 31, 2012 5:21 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Justin, any luck with your issue? Yep sorted. Made a few minor mods to the build files and notes as well (see checkins). Here you go one dmg and associated files: https://people.apache.org/~jmclean/Apache%20Flex%20Installer%20RC1/ Thanks, Justin
Re: Prepping for Installer 2.0 RC1
On Dec 31, 2012 6:01 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Great! So you mind tagging trunk with 2.0 RC1? You might have to do it I got an SVN error. May because of my slow connection. I tried twice same error. svn: '/repos/asf/!svn/bc/1427276/incubator/flex/utilities/trunk' path not found: 404 Not Found (https://svn.apache.org) I also running the installer here, it's still downloading (about an hour so far it's a slow connection) but no issues. It defaulted to my Australian locale and it went though and downloaded 4.9 SDK and in the process of downloaded AIR 3.4. The MD5 check passed. To be put on the to do/improvement list but no need to stop the installer from being released: There a very minor visual issue in the install log window - part of the logo shows under the log window. Usability wise I still find the red/green check boxes annoying (and I'm not red/green colour blind). Can't we just use normal check boxes? Fixing these issues is in my to-do list. Should I give it a go before we cut an RC? I have a few hours available before I go out partying for the new year. Thanks, Justin
Re: Prepping for Installer 2.0 RC1
I have fixed those issues and checked it in. Please give it a run through and see everything works as it should. I have also created a tag for the RC: apache-flex-sdk-installer-2.0.0-RC1 Ready to start a [DISCUSS] Release Candidate 1 thread when you are. Thanks, Om On Mon, Dec 31, 2012 at 6:20 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Fixing these issues is in my to-do list. Should I give it a go before we cut an RC? Up to you. I don't think they are required for a RC as it works fine without those minor changes. I have a few hours available before I go out partying for the new year. Been there done that, it's afternoon on the 1st here. :-) Have fun. Justin
[DISCUSS] Apache Flex SDK Installer 2.0 RC1
This is version 2.0 of Apache Flex SDK Installer. This version lets users download the Apache Flex SDK 4.9 and its required dependencies. https://people.apache.org/~bigosmallm/installapacheflex_2.0_RC1/ Significant improvements over previous version: 1. UI of the components selection and license screen has been fixed to use just checkboxes for selection 2. All the various locales have been enabled. 3. By default, Apache Flex SDK Installer 2.0 downloads Adobe Flash Player 11.1 and Adobe AIR SDK 3.4. If you want to change it to any other supported combination, you save a copy of the config file found at: http://incubator.apache.org/flex/sdk-installer-config-2.0.xml, modify the download urls to point to the required versions. Then run the app from command line mode with the optional command line parameter: -config=path to config file Please take it for a spin and let us know your feedback. We would like to put up a vote asap and release this right away! Thanks, Om
Re: Prepping for Installer 2.0 RC1
On Sat, Dec 29, 2012 at 2:18 PM, Justin Mclean jus...@classsoftware.comwrote: HI, I am ready to put out an RC1 for voting. I need a committer with a Mac to build and sign a .dmg file for the Mac installer. I can do that if needed. Have you tagged RC1 in some way or should I just use trunk? Justin Trunk is good to go. I have created the source kits and windows binary kit. We just need the Mac binaries now. As described here [1], I will send you the .p12 file and the password file you need to sign the official binary in two private emails. Just follow the steps in the RELEASE_GUIDE to cut a release build. Once you have the artifacts build, upload it to some location in your people.apache.org site and I will download them and put it in my people.a.o site along with the rest of the artifacts Thanks, Om [1] https://issues.apache.org/jira/browse/FLEX-33186
Re: Prepping for Installer 2.0 RC1
On Dec 30, 2012 1:40 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Trunk is good to go. Any reason we're working in trunk and not develop? Seems a little inconsistent. We decided to work on trunk for the installer since it has low traffic. And this decision was made before the rules for sdk branching were decided upon. In any case, I don't see a need for a develop branch for the installer. I have created the source kits and windows binary kit. We just need the Mac binaries now. Just sync up SVN and I'll have a go at making one now. Great. I am available in case you run into any issues. Thanks, Justin
Re: Prepping for Installer 2.0 RC1
On Dec 30, 2012 2:34 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Looks like something isn't quite right in the build file on OSX. [mxmlc] command line: Error: unable to open '/Users/justinmclean/Documents/Adobe Flash Builder 4.6/Apache Flex Installer/../common/src' Any idea why the .. is in there? Justin Are you sure you have checked out utilities/trunk/common/ as well?
Re: Prepping for Installer 2.0 RC1
On Sun, Dec 30, 2012 at 3:01 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Are you sure you have checked out utilities/trunk/common/ as well? Nope as that's not included in the build instructions. It says to check out source and just run this: ant build [-DFLEX_HOME=/path/to/apache/flex/sdk] [-DAIR_HOME=/path/to/air/sdk] How/where does this need to be check out? I assume there an environment variable you need to point at it? Justin RELEASE_GUIDE says: 1. Check out the code from https://svn.apache.org/repos/asf/incubator/flex/utilities/trunk You might want to change it to say check out https://svn.apache.org/repos/asf/incubator/flex/utilities/trunk/installerand https://svn.apache.org/repos/asf/incubator/flex/utilities/trunk/common. After the last release, more stuff (mavenizer, etc. ) was added to utitlities/trunk. You dont need that for building the installer.
Re: Prepping for Installer 2.0 RC1
On Sun, Dec 30, 2012 at 3:18 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Are you sure you have checked out utilities/trunk/common/ as well? OK it wasn't clear to me that you need to check out all of the utilities trunk rather than just the installer directory. We'll need to add instructions to the README on how to checkout the project. README is for folks who get the source distro. No need to talk about checkout directions. RELEASE_GUIDE has the required instructions. What version of AIR are you using to compile the application? I'm getting an error with AIR 3.4. I am using Apache Flex 4.8 to build the installer. Which means AIR 3.1, right?
Re: Prepping for Installer 2.0 RC1
On Sun, Dec 30, 2012 at 3:36 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, I am using Apache Flex 4.8 to build the installer. Which means AIR 3.1, right? I think we should be using AF 4.9/AIR 3.4 - be nice if the SDK and installer were in sync. Justin Makes sense. i will get on it now. Mind posting what errors you are seeing? Om
Re: Prepping for Installer 2.0 RC1
This is the error I am getting when I run ant release. Error in *bold* I googled this issue, it looks like quite a few folks have this issue with AIR 3.4. I have not been able to find out what is happening. Any ideas? C:\p\flex_os\workspace\flexroot\utilities\trunk\installerant release Buildfile: C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\build.xml clean: [delete] Deleting directory C:\p\flex_os\workspace\flexroot\utilities\trunk\i nstaller\build [delete] Deleting directory C:\p\flex_os\workspace\flexroot\utilities\trunk\i nstaller\libs [delete] Deleting directory C:\p\flex_os\workspace\flexroot\utilities\trunk\i nstaller\release createDirs: [echo] [echo] [echo] Execute the update-version target once, and only once, when you modifiy this app. [echo] This will increment the version number to allow the app to b e updated by the AIR installer. [echo] [echo] [mkdir] Created dir: C:\p\flex_os\workspace\flexroot\utilities\trunk\install er\build [mkdir] Created dir: C:\p\flex_os\workspace\flexroot\utilities\trunk\install er\release update-version-in-xml-files: [echo] version in InstallApacheFlex-app.xml will be 2.0.0 init: certificate: check-as3commons.swc: get-as3commons.swc: [mkdir] Created dir: C:\p\flex_os\workspace\flexroot\utilities\trunk\install er\libs [get] Getting: http://projects.yoolab.org/maven/content/repositories/relea ses/org/as3commons/as3commons-zip/1.0.0-alpha.1/as3commons-zip-1.0.0-alpha.1.swc [get] To: C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\libs\a s3commons-zip-1.0.0-alpha.1.swc [get] ... [get] Getting: http://projects.yoolab.org/maven/content/repositories/relea ses/org/as3commons/as3commons-zip/1.0.0-alpha.1/as3commons-zip-1.0.0-alpha.1.swc .md5 [get] To: C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\libs\a s3commons-zip-1.0.0-alpha.1.swc.md5 [get] . [delete] Deleting: C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\ libs\as3commons-zip-1.0.0-alpha.1.swc.md5 compile: [mxmlc] Loading configuration file C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\ApacheFlex4.9.0\frameworks\air-config.xml [mxmlc] C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\build\Inst allApacheFlex.swf (1511233 bytes) abortBuild: *packageair:* * [java] C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\src\Instal* *lApacheFlex-app.xml: error 102: Invalid namespace http://ns.adobe.com/air/applic* *ation/3.4* BUILD FAILED C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\build.xml:291: Java re turned: 12 Total time: 11 seconds On Sun, Dec 30, 2012 at 3:39 PM, Om bigosma...@gmail.com wrote: On Sun, Dec 30, 2012 at 3:36 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, I am using Apache Flex 4.8 to build the installer. Which means AIR 3.1, right? I think we should be using AF 4.9/AIR 3.4 - be nice if the SDK and installer were in sync. Justin Makes sense. i will get on it now. Mind posting what errors you are seeing? Om
Re: Prepping for Installer 2.0 RC1
BTW, the app compiles and runs fine with Apache Flex 4.9/AIR 3.4 when I run it from Flash Builder 4.6. On Sun, Dec 30, 2012 at 4:34 PM, Om bigosma...@gmail.com wrote: This is the error I am getting when I run ant release. Error in *bold* I googled this issue, it looks like quite a few folks have this issue with AIR 3.4. I have not been able to find out what is happening. Any ideas? C:\p\flex_os\workspace\flexroot\utilities\trunk\installerant release Buildfile: C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\build.xml clean: [delete] Deleting directory C:\p\flex_os\workspace\flexroot\utilities\trunk\i nstaller\build [delete] Deleting directory C:\p\flex_os\workspace\flexroot\utilities\trunk\i nstaller\libs [delete] Deleting directory C:\p\flex_os\workspace\flexroot\utilities\trunk\i nstaller\release createDirs: [echo] [echo] [echo] Execute the update-version target once, and only once, when you modifiy this app. [echo] This will increment the version number to allow the app to b e updated by the AIR installer. [echo] [echo] [mkdir] Created dir: C:\p\flex_os\workspace\flexroot\utilities\trunk\install er\build [mkdir] Created dir: C:\p\flex_os\workspace\flexroot\utilities\trunk\install er\release update-version-in-xml-files: [echo] version in InstallApacheFlex-app.xml will be 2.0.0 init: certificate: check-as3commons.swc: get-as3commons.swc: [mkdir] Created dir: C:\p\flex_os\workspace\flexroot\utilities\trunk\install er\libs [get] Getting: http://projects.yoolab.org/maven/content/repositories/relea ses/org/as3commons/as3commons-zip/1.0.0-alpha.1/as3commons-zip-1.0.0-alpha.1.swc [get] To: C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\libs\a s3commons-zip-1.0.0-alpha.1.swc [get] ... [get] Getting: http://projects.yoolab.org/maven/content/repositories/relea ses/org/as3commons/as3commons-zip/1.0.0-alpha.1/as3commons-zip-1.0.0-alpha.1.swc .md5 [get] To: C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\libs\a s3commons-zip-1.0.0-alpha.1.swc.md5 [get] . [delete] Deleting: C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\ libs\as3commons-zip-1.0.0-alpha.1.swc.md5 compile: [mxmlc] Loading configuration file C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\ApacheFlex4.9.0\frameworks\air-config.xml [mxmlc] C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\build\Inst allApacheFlex.swf (1511233 bytes) abortBuild: *packageair:* * [java] C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\src\Instal* *lApacheFlex-app.xml: error 102: Invalid namespace http://ns.adobe.com/air/applic* *ation/3.4* BUILD FAILED C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\build.xml:291: Java re turned: 12 Total time: 11 seconds On Sun, Dec 30, 2012 at 3:39 PM, Om bigosma...@gmail.com wrote: On Sun, Dec 30, 2012 at 3:36 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, I am using Apache Flex 4.8 to build the installer. Which means AIR 3.1, right? I think we should be using AF 4.9/AIR 3.4 - be nice if the SDK and installer were in sync. Justin Makes sense. i will get on it now. Mind posting what errors you are seeing? Om
Re: Prepping for Installer 2.0 RC1
On Dec 30, 2012 5:10 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, I'm getting a different error: packagenative: [java] SDK is missing file /Users/justinmclean/Documents/air/mac/AdobeAIRSDK/lib/nai/bin/naip BUILD FAILED /Users/justinmclean/Documents/Adobe Flash Builder 4.6/Apache Flex Utilities/installer/build.xml:203: Java returned: 5 Looking at that directory I have 2 exe files - which can't run on OSX. ls /Users/justinmclean/Documents/air/mac/AdobeAIRSDK/lib/nai/bin/ naip.exenais.exe Thanks, Justin Does it compile in Flash Builder? How did you create the flex sdk for flash builder? Using the script or the installer?
Re: Prepping for Installer 2.0 RC1
On Dec 30, 2012 5:48 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Does it compile in Flash Builder? No it fails as well looks like there's hard coded paths in the project files. /Applications/Adobe Flash Builder 4.6/sdks/4.8.0 does not exist. You are expected to change that in build.properties file. How did you create the flex sdk for flash builder? Using the script or the installer? The make IDE script from the binary distribution, it downloaded http://airdownload.adobe.com/air/mac/download/3.4/AdobeAIRSDK.tbz2 to add into the SDK. Justin Do you want build it using the installer to see if that problem occurs there as well? Either that or manually copy required dependencies to eliminate any doubts. Om
Re: Apache Flex 4.9 release on web site
Please do not make any changes to the installer config. I plan to create a new version of the config xml for v2. The new config changes will break the installer v1 and we don't want that. The badge would also have to be updated to look for the new config xml. The plan is to wait for 4.9 to be promoted to a release before we cut the first RC for installer v2. Thanks, Om On Dec 27, 2012 7:27 AM, Alex Harui aha...@adobe.com wrote: The xml file for the installer will need to be changed then we will need a separate vote on its release. I think we need to hold off on its release until we get our TLP dist folder. We could release twice (sooner for the incubator URL) and again when we get our dist folder, but I'm hoping that we get our dist folder soon. On 12/27/12 6:29 AM, Erik de Bruin e...@ixsoftware.nl wrote: Yes, I believe there was. But to my knowledge the 'interface' in the XML file hasn't been altered, so the change I indicated will need to implemented anyway. EdB On Thu, Dec 27, 2012 at 3:26 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: ok. Was there a new version of the installer that was being produced? I thought I remember one being worked on (although, I'd admit I wasn't paying very good attention to it). -Nick On Thu, Dec 27, 2012 at 8:46 AM, Erik de Bruin e...@ixsoftware.nl wrote: In sdk-installer-config.xml the line: file name=ApacheFlexSDK path=incubator/flex/4.8.0-incubating/binaries/ file=apache-flex-sdk-4.8.0-incubating-bin.zip / Needs to be updated to point to the latest SDK. That should be enough to update both the Installer and InstallerBadge functionality. EdB On Thu, Dec 27, 2012 at 2:41 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: But otherwise -- it looks good to me. I made a few quick changes on the index to add the date of the release. I'm showing that about 90% of the dists have the images now. From experience, it took the full 24 hours for all of them to get it. We should publish the pages then. Do you know if the SDK installer is good to go as well? Is there anything we need to do to get that page on the website updated? -Nick On Thu, Dec 27, 2012 at 8:34 AM, Nicholas Kwiatkowski nicho...@spoon.as wrote: Did you push those changes in the CMS? I don't see them on the staging server yet. I do see them in SVN, though. I can take care of that for you, if you wish. -Nick On Thu, Dec 27, 2012 at 1:32 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, I've added some information to the web site for the 4.9 release, if someone could review and make it live I'd appreciate it. Paged edited include index, download and timeline. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Flex 4.9 announcement and the installer
On Dec 27, 2012 5:04 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Do we want to hold off on making an official release announcement (on various lists etc etc) until we have an installer that supports 4.9? I assume that's the way most people are going to install it. Justin +1 I will try to work on the installer v2 RC very soon. Thanks, Om
Re: Flex 4.9 announcement and the installer
On Dec 27, 2012 5:43 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, I will try to work on the installer v2 RC very soon. I forgot we will have to vote on the installer (before releasing it) so it's realistically going to be a week or more before we can officially announce 4.9 if we go down this path. That is correct. Perhaps we just announce it now and say new installer coming soon? Thanks, Justin I vote for announcing both at the same time. The extra time would probably help us with settling the release locations. Thanks, Om
Re: undated built release notes
On Dec 25, 2012 8:30 PM, Alex Harui aha...@adobe.com wrote: On 12/25/12 8:26 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, I've updated; https://cwiki.apache.org/confluence/display/FLEX/Release+Guide+for+the+SDK In particular to take into account the develop and release branches. This a slight issue with tagging the release as the release is built from the release branch, but I assume we would want to tag the trunk after the release branch has been merged with it. In theory there should be no changes in the trunk, but it seems there been a few occasions when people have checked stuff into the trunk accidentally or otherwise so we're likely to get a conflict or two so what end up getting tagged by not actually be what was released. The whole point of having seperate release, develop and trunk branch was that trunk is the last good know release. Any suggestions of how to improve this process? Well, we should be vetoing any checkins to trunk. But I think folks aren't quite sure how to revert (it is sort of a pain in SVN) and some things didn't get reverted. I know there's sort of a rule about not reverting someone else's changes, but I think it is ok in this case. If you can, verify that the change that went into trunk did actually end up in develop, then revert it out of trunk. +1 to selectively reverting from trunk as a special case this time. The better approach would be revert trunk to the 4.8 tag before merging the 4.9 branch. Thanks, Om Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
[DISCUSS] [VOTE] Apache Flex 4.9 RC7
Justin, I dont see your PGP key here [1] According to this page [2], the release manager's public key should be present on that page for users to verify the artifacts. Thanks, Om [1] http://www.apache.org/dist/incubator/flex/KEYS [2] http://incubator.apache.org/flex/download.html -- Forwarded message -- From: Justin Mclean jus...@classsoftware.com Date: Sun, Dec 23, 2012 at 9:15 PM Subject: [VOTE] Apache Flex 4.9 RC7 To: flex-dev@incubator.apache.org Hi, This is a Apache Flex 4.9.0 release candidate 7. Please see the RELEASE_NOTES and the README. Fixed in this release candidate: - Fix minor issue with 2 files failing rat license test - Minor changes to README The release candidate can be found here; http://people.apache.org/~jmclean/Apache%20Flex%204.9.0%20Release%20Candidate%207/ Before voting please review the section,What are the ASF requirements on approving a release?, at: http://www.apache.org/dev/release.html#approving-a-release Please vote to approve this release: +1 Approve the release -1 Veto the release (please provide specific comments to why) This vote will be open for at least 72 hours or as long as needed given it's the holidays. The vote passes if there is: - At least 3 +1 votes from the PMC - More positive votes than negative votes When voting please indicate what platform and IDE you compiled and tested the SDK with. Please put all discussion about this release in a DISCUSSION thread not this VOTE thread. Thanks, Justin PS Brought to you over a satellite link and made with solar power :-)
Re: [VOTE] Apache Flex 4.9 RC7
+1 (Binding) PGP signatures for src kit and binaries look good. ant main build successful Tested binary kit with Installer v2 (with FP 11.1 and AIR 3.4) Flash Builder 4.6 recognizes it as a valid SDK Smoke test projects for Flex and AIR projects compile and run fine Thanks, Om On Mon, Dec 24, 2012 at 8:46 AM, Nicholas Kwiatkowski nicho...@spoon.aswrote: +1 See remarks in Discuss thread. -Nick
Re: [DISCUSS][VOTE] APACHE FLEX 4.9 RC6
On Dec 23, 2012 1:12 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, Rat-check failed with two issues. I'm fixing that now and running rat again (takes about an hour). I also fixed a minor issue in the README since we're going to have to re-kit again. It does look like it related to as_docs, at a guess the en_US locale is hard coded in the clean and that may be causing an issue. You didn't happen to compile for another locale did you? I think in that case these file would be left about if you compiled for en_US then another locale. Do you really think this is an issue that should stop a release? They are 2 generated XML files, they are not in source control regenerating the asdocs will create them. Generated files can be excluded from the rat report. But if we are going to sign the asdoc package, then any changes to the package has to be signed again which works need a new RC. Thanks, Om Thanks, Justin
Re: [DISCUSS][VOTE] APACHE FLEX 4.9 RC6
On Dec 23, 2012 8:31 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, I'll give RC7 a whirl tomorrow if I get a chance before heading out for the holiday. Thanks + enjoy. Here's hoping I'll not be making RC8 on christmas day (tomorrow for me) :-) Justin I don't see a vote thread for RC7. It would be better if we have discussion about RC7 in its own thread. Thanks, Om
Re: [VOTE] Apache Flex 4.9 Release Candidate 4
And oh, the swfobject issue I had in earlier RCs have gone away now. Not sure what fixed that. On Sat, Dec 22, 2012 at 12:39 AM, Om bigosma...@gmail.com wrote: I tested with the installer and Flex 4.9 RC6 looks good to me. I switched up the sdk-installer-config.xml file to point to RC6 in case anyone else wants to test. Thanks, Om On Fri, Dec 21, 2012 at 7:46 PM, Alex Harui aha...@adobe.com wrote: We'll try to make RC6 work. I am downloading it now. On 12/21/12 7:39 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, What's your last day before you take off? Satellite internet connection up and running, it's slow but working (0.3 Mbps down/0.1 Mbps up and 1 second ping time) so as long as I don't have to upload too many new RCs should be OK. Thanks, Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [FalconJx] New JavaScript runtime format prototype
Obligatory xkcd reference ;-) http://xkcd.com/386/ On Dec 21, 2012 12:26 AM, Erik de Bruin e...@ixsoftware.nl wrote: Frank, I was writing a very long and detailed reply to your very long and detailed reply to my ... (ad infinitum, it seems), debunking or countering most of your claims, when I realised that I don't want to spend my time that way. I call for a truce while we investigate the merits and pitfalls of both approaches in real life examples and against a realistic work flow. I'm going to help Mike with FalconJx so we have something to work with. I'm going to continue to investigate the best way forward after we have the language-translation-thing done and need to figure out which approach is best for creating the AS and JS UI frameworks. That might be Alex's FlexJS, but it also might be something completely different. For now, it's Xmas time! Happy partying :-) EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [jira] [Updated] (FLEX-33326) RuntimeLocale.as for the Apache Flex Installer needs to be updated for the French language
Frederic, please commit it into SVN yourself? That would be a much easier workflow. Thanks Om On Dec 21, 2012 6:51 AM, Frédéric THOMAS (JIRA) j...@apache.org wrote: [ https://issues.apache.org/jira/browse/FLEX-33326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] Frédéric THOMAS updated FLEX-33326: --- Attachment: FLEX-33326.patch I have attached a patch that provides the necessary translations. RuntimeLocale.as for the Apache Flex Installer needs to be updated for the French language -- Key: FLEX-33326 URL: https://issues.apache.org/jira/browse/FLEX-33326 Project: Apache Flex Issue Type: Improvement Components: InstallApacheFlex Affects Versions: InstallApacheFlex 1.1 Reporter: Frédéric THOMAS Assignee: Frédéric THOMAS Priority: Minor Attachments: FLEX-33326.patch RuntimeLocale.as for the Apache Flex Installer needs to be updated for the French language -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Apache Flex 4.9 RC5
On Dec 21, 2012 2:01 PM, Alex Harui aha...@adobe.com wrote: You might already be gone, but I don't think you updated the signature files? They are not matching so the installer is failing. If I don't hear from you by tonight my time, I'll try to cut an RC6. Did you update the sdk-installer-config.xml in the src folder to point to RC5? Did you confirm by downloading the binaries manually and verifying that the signature doesn't match? Om On 12/20/12 2:59 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, In the binary kit, frameworks/build.xml does not build cleanly. I've fixed, tested and checked in changes that fix this issue (rename blank.properties to experimental.properties). I don't think this is a major enough issue to stop the current vote so I've just replaced the binary packages in RC5. Thanks, Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Installer language selection issue
On Dec 21, 2012 2:10 PM, Alex Harui aha...@adobe.com wrote: Om, Do you have any objections if I re-arrange that to require the use of file:// URLs to speed up testing? Then we'll always be using the same code paths. I will also use file:// to skip the mirror lookup. I am not sure if I understand. Can you please rephrase? Or you could just check in your intended changes and I could review the code directly. BTW, I guess we have to finalize the vote and post the SDK to its final home before making the final RC for the installer so its sources can point to the right place? That would certainly make our lives easier. Thanks, Om On 12/20/12 2:55 PM, Om bigosma...@gmail.com wrote: On Thu, Dec 20, 2012 at 2:44 PM, Chema Balsas jbal...@gmail.com wrote: Hi, I've been digging around the installer, and I think I've found the issue with the languages... I'm not very comfortable with the code, so I want to ask before breaking anything ;) The problem seems to come from ViewResourceConstants.as, line 191 if(n1) messageStringsContentLocalized = ... This never happens, as the localeChain is initialized inside selectDefaultLanguage() as resourceManager.localeChain = [ userLocale ]; It's also worth noting that if all the strings are not in the locale, an error is thrown. Shouldn't we have a base locale to inherit from? Urls for instance don't usually need translation, so they could default in general to the root locale. A possible fix is to append the root locale en_US when initializing localeChain, like resourceManager.localeChain = [ userLocale, en_US ]; This seems to fix all problems and I can see the existing es_ES strings and the default en_US strings for the missing ones. It's been a while since I've worked around these, so maybe this is not the solution at all... let me know what you think and how should this be addressed. Cheers, Chema I think your analysis makes sense. Please go ahead and make the changes as you mentioned. I can help test your changes. Thanks, Om 2012/12/20 Chema Balsas jbal...@gmail.com Hi, I checked the submitted patch, and it does fix the issue of the license agreements box to appear empty. However, I also can't see the labels for the Browse, Next and Install Log. Was this known before? If you change the locale back and forth in the dropdown, then all texts are shown correctly. 2012/12/20 Alex Harui aha...@adobe.com I will try to get to it tonight. It would be nice if you could add a hook at startup (maybe command-line option or reading from the .xml file) that overrides the language/locale default it picks up from the player/os. That would enable us to simulate what folks in different countries will experience. That would enable to you verify that the patch worked yourself. Last time we went through this, I had to stop in the debugger and zap the variable by hand. It would make it easier to test if we could override in some way. On 12/20/12 1:04 PM, Om bigosma...@gmail.com wrote: Bump... The more people who can help test the Installer with other languages, the better it would be for us to make a confident release. Please take a look when you get a chance. Source code is available here: https://svn.apache.org/repos/asf/incubator/flex/utilities/trunk Thanks, Om On Thu, Dec 20, 2012 at 12:46 AM, Om bigosma...@gmail.com wrote: Commit 1424368 (hopefully) fixes this issue. Stefan Horochovec had provided this patch a while ago and attached it to the JIRA bug: https://issues.apache.org/jira/browse/FLEX-33223 Can you please test it and see if the issue is gone? Thanks, Om On Wed, Dec 19, 2012 at 12:22 PM, Chema Balsas jbal...@gmail.com wrote: Hi, I was checking the installer, and was starting to add a translation for the es_ES locale. After compiling and launching it, There are lots of buttons with empty labels. If you select a different locale and then back to spanish, then the labels appear. I remember reading something like this before the previous version was released... is this the same issue? Is it supposed to be fixed before this version is released? Cheers, Chema 2012/12/19 Alex Harui aha...@adobe.com -Original Message- From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of Om Sent: Wednesday, December 19, 2012 9:36 AM To: flex-dev@incubator.apache.org Subject: Re: [VOTE] Apache Flex 4.9 Release Candidate 4 1. Would there be value in adding drop downs that let users switch between FP swc versions and AIR sdk versions? I would say no. I wouldn't want to take the time to test this additional functionality. Could the two URLs it will hit (based on the answer to #2) be stored in an external .XML file? That would make it easier to folks to use different
Installer language selection issue
Commit 1424368 (hopefully) fixes this issue. Stefan Horochovec had provided this patch a while ago and attached it to the JIRA bug: https://issues.apache.org/jira/browse/FLEX-33223 Can you please test it and see if the issue is gone? Thanks, Om On Wed, Dec 19, 2012 at 12:22 PM, Chema Balsas jbal...@gmail.com wrote: Hi, I was checking the installer, and was starting to add a translation for the es_ES locale. After compiling and launching it, There are lots of buttons with empty labels. If you select a different locale and then back to spanish, then the labels appear. I remember reading something like this before the previous version was released... is this the same issue? Is it supposed to be fixed before this version is released? Cheers, Chema 2012/12/19 Alex Harui aha...@adobe.com -Original Message- From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of Om Sent: Wednesday, December 19, 2012 9:36 AM To: flex-dev@incubator.apache.org Subject: Re: [VOTE] Apache Flex 4.9 Release Candidate 4 1. Would there be value in adding drop downs that let users switch between FP swc versions and AIR sdk versions? I would say no. I wouldn't want to take the time to test this additional functionality. Could the two URLs it will hit (based on the answer to #2) be stored in an external .XML file? That would make it easier to folks to use different versions and for us to update an already released installer if Adobe goes and moves things around again. Yes, we load all the download urls from an external config file: http://incubator.apache.org/flex/sdk-installer-config.xml My thinking is that we will have a different config for each FP/AIR combination we want to support. Just show a simple dropdown at the launch of the app (default to 11.4/3.4). Depending on what the user selects, we grab the corresponding config url. A pretty straightforward implementation. But this could wait until Installer 2.5 if we dont want to hold up Flex 4.9 release. Thanks, Om I just built and ran the installer from sources on Win7. FB4.7 accepted the results as a new SDK. I created a new Flex project and it showed up in IE8 and FF15. I didn't see any warnings or errors. So, I would say we don't take the time to test all of the permutations of configs. Adobe is not open next week so I will be working from home and testing the installer is slow because of the internet speeds I get at home, so the less downloading I need to do, the better. Alex Harui Apache Flex Team http://blogs.adobe.com/aharui
Re: Installer language selection issue
Bump... The more people who can help test the Installer with other languages, the better it would be for us to make a confident release. Please take a look when you get a chance. Source code is available here: https://svn.apache.org/repos/asf/incubator/flex/utilities/trunk Thanks, Om On Thu, Dec 20, 2012 at 12:46 AM, Om bigosma...@gmail.com wrote: Commit 1424368 (hopefully) fixes this issue. Stefan Horochovec had provided this patch a while ago and attached it to the JIRA bug: https://issues.apache.org/jira/browse/FLEX-33223 Can you please test it and see if the issue is gone? Thanks, Om On Wed, Dec 19, 2012 at 12:22 PM, Chema Balsas jbal...@gmail.com wrote: Hi, I was checking the installer, and was starting to add a translation for the es_ES locale. After compiling and launching it, There are lots of buttons with empty labels. If you select a different locale and then back to spanish, then the labels appear. I remember reading something like this before the previous version was released... is this the same issue? Is it supposed to be fixed before this version is released? Cheers, Chema 2012/12/19 Alex Harui aha...@adobe.com -Original Message- From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of Om Sent: Wednesday, December 19, 2012 9:36 AM To: flex-dev@incubator.apache.org Subject: Re: [VOTE] Apache Flex 4.9 Release Candidate 4 1. Would there be value in adding drop downs that let users switch between FP swc versions and AIR sdk versions? I would say no. I wouldn't want to take the time to test this additional functionality. Could the two URLs it will hit (based on the answer to #2) be stored in an external .XML file? That would make it easier to folks to use different versions and for us to update an already released installer if Adobe goes and moves things around again. Yes, we load all the download urls from an external config file: http://incubator.apache.org/flex/sdk-installer-config.xml My thinking is that we will have a different config for each FP/AIR combination we want to support. Just show a simple dropdown at the launch of the app (default to 11.4/3.4). Depending on what the user selects, we grab the corresponding config url. A pretty straightforward implementation. But this could wait until Installer 2.5 if we dont want to hold up Flex 4.9 release. Thanks, Om I just built and ran the installer from sources on Win7. FB4.7 accepted the results as a new SDK. I created a new Flex project and it showed up in IE8 and FF15. I didn't see any warnings or errors. So, I would say we don't take the time to test all of the permutations of configs. Adobe is not open next week so I will be working from home and testing the installer is slow because of the internet speeds I get at home, so the less downloading I need to do, the better. Alex Harui Apache Flex Team http://blogs.adobe.com/aharui
Re: [VOTE] Apache Flex 4.9 RC5
On Thu, Dec 20, 2012 at 1:02 PM, Carol Frampton cfram...@adobe.com wrote: And if you decide to rekit I think you should mention in the README that although we have graduated we are still using incubator urls - which will redirect after we've been moved. Carol Why bother releasing as 'incubating' after we have graduated. Can we wait until our top level domain is up and running before we release? I am sure we are not going to get enough testing done with most of us gone for the holidays. Om
Re: Installer language selection issue
On Thu, Dec 20, 2012 at 2:44 PM, Chema Balsas jbal...@gmail.com wrote: Hi, I've been digging around the installer, and I think I've found the issue with the languages... I'm not very comfortable with the code, so I want to ask before breaking anything ;) The problem seems to come from ViewResourceConstants.as, line 191 if(n1) messageStringsContentLocalized = ... This never happens, as the localeChain is initialized inside selectDefaultLanguage() as resourceManager.localeChain = [ userLocale ]; It's also worth noting that if all the strings are not in the locale, an error is thrown. Shouldn't we have a base locale to inherit from? Urls for instance don't usually need translation, so they could default in general to the root locale. A possible fix is to append the root locale en_US when initializing localeChain, like resourceManager.localeChain = [ userLocale, en_US ]; This seems to fix all problems and I can see the existing es_ES strings and the default en_US strings for the missing ones. It's been a while since I've worked around these, so maybe this is not the solution at all... let me know what you think and how should this be addressed. Cheers, Chema I think your analysis makes sense. Please go ahead and make the changes as you mentioned. I can help test your changes. Thanks, Om 2012/12/20 Chema Balsas jbal...@gmail.com Hi, I checked the submitted patch, and it does fix the issue of the license agreements box to appear empty. However, I also can't see the labels for the Browse, Next and Install Log. Was this known before? If you change the locale back and forth in the dropdown, then all texts are shown correctly. 2012/12/20 Alex Harui aha...@adobe.com I will try to get to it tonight. It would be nice if you could add a hook at startup (maybe command-line option or reading from the .xml file) that overrides the language/locale default it picks up from the player/os. That would enable us to simulate what folks in different countries will experience. That would enable to you verify that the patch worked yourself. Last time we went through this, I had to stop in the debugger and zap the variable by hand. It would make it easier to test if we could override in some way. On 12/20/12 1:04 PM, Om bigosma...@gmail.com wrote: Bump... The more people who can help test the Installer with other languages, the better it would be for us to make a confident release. Please take a look when you get a chance. Source code is available here: https://svn.apache.org/repos/asf/incubator/flex/utilities/trunk Thanks, Om On Thu, Dec 20, 2012 at 12:46 AM, Om bigosma...@gmail.com wrote: Commit 1424368 (hopefully) fixes this issue. Stefan Horochovec had provided this patch a while ago and attached it to the JIRA bug: https://issues.apache.org/jira/browse/FLEX-33223 Can you please test it and see if the issue is gone? Thanks, Om On Wed, Dec 19, 2012 at 12:22 PM, Chema Balsas jbal...@gmail.com wrote: Hi, I was checking the installer, and was starting to add a translation for the es_ES locale. After compiling and launching it, There are lots of buttons with empty labels. If you select a different locale and then back to spanish, then the labels appear. I remember reading something like this before the previous version was released... is this the same issue? Is it supposed to be fixed before this version is released? Cheers, Chema 2012/12/19 Alex Harui aha...@adobe.com -Original Message- From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of Om Sent: Wednesday, December 19, 2012 9:36 AM To: flex-dev@incubator.apache.org Subject: Re: [VOTE] Apache Flex 4.9 Release Candidate 4 1. Would there be value in adding drop downs that let users switch between FP swc versions and AIR sdk versions? I would say no. I wouldn't want to take the time to test this additional functionality. Could the two URLs it will hit (based on the answer to #2) be stored in an external .XML file? That would make it easier to folks to use different versions and for us to update an already released installer if Adobe goes and moves things around again. Yes, we load all the download urls from an external config file: http://incubator.apache.org/flex/sdk-installer-config.xml My thinking is that we will have a different config for each FP/AIR combination we want to support. Just show a simple dropdown at the launch of the app (default to 11.4/3.4). Depending on what the user selects, we grab the corresponding config url. A pretty straightforward implementation. But this could wait until Installer 2.5 if we dont want to hold up Flex 4.9 release. Thanks, Om I just built and ran
Re: Build failed in Jenkins: Flex_SDK_build #402
On Thu, Dec 20, 2012 at 3:43 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Fairly certain clean and not a super-clean, looking at the script it does the following: ant clean main source-release Yup, this is what is running: [Flex_SDK_build] $ cmd.exe /C 'f:\hudson\tools\ant\apache-ant-1.7.0\bin\ant.bat -file build.xml -Dbuild.number=1424735 -Dbuild.noprompt= clean main source-release exit %%ERRORLEVEL%%' Each Jenkins runs is in it own workspace so I think that's why it downloads each time, the SVN source code is shared however. Not 100% sure. We have the Discard Old Builds option selected. Should we try keeping old builds? That should help with download issues, perhaps? Thanks, Om
OneClickMustella 0.1 - take it for a spin
OneClickMustella can now: 1. Run a webserver, listen on port 80 (or any other port you like) 2. Open and run commands via terminal (Windows only for now) 3. Invoke svn status to get a list of changed files 4. Create the dependencyDB of classes 5 Generate changes.txt which contains the tests required to be run for the current set of files that have been changed 6. Run the mini_run.bat with various options such as -all, -failures, -rerun, -changes, etc. This is just the first cut. Lots of hacks, treat this as a POC. More coming... This most probably wont work on a Mac. But it should be quite easy to make it work. The source code can be found here: https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/develop/mustella/utilities/OneClickMustella Steps to test: a. Make a change to a file, ex. develop\frameworks\projects\spark\src\spark\components.RichText.as b. Open OneClickMustella c. Select Flex SDK path d. Select path to Shell - typically C:\Windows\System32\cmd.exe (This is where it wont work for Macs yet. Someone take this up?) e. Click on Start Web Server button f. Click on Generate DB button g. On the right side, click Get Modifiied Files button h. In the Test Chooser panel, you should see the list get populated. Then click Compute Tests i. Click Run on changes button You should see the tests run and the console output in the text area on the right. In a while, you should also see the FP debugger player popping up and run tests. Sit back and enjoy the test run. In the end, you should see a tests success or failure message. As you will see, the UI is quite bad. I will worry about that later :-) This whole thing now runs end to end and I wanted to quickly share it with the team. More coming... Thanks, Om
Re: [VOTE] Apache Flex 4.9 Release Candidate 4
1. Would there be value in adding drop downs that let users switch between FP swc versions and AIR sdk versions? I would say no. I wouldn't want to take the time to test this additional functionality. Could the two URLs it will hit (based on the answer to #2) be stored in an external .XML file? That would make it easier to folks to use different versions and for us to update an already released installer if Adobe goes and moves things around again. Yes, we load all the download urls from an external config file: http://incubator.apache.org/flex/sdk-installer-config.xml My thinking is that we will have a different config for each FP/AIR combination we want to support. Just show a simple dropdown at the launch of the app (default to 11.4/3.4). Depending on what the user selects, we grab the corresponding config url. A pretty straightforward implementation. But this could wait until Installer 2.5 if we dont want to hold up Flex 4.9 release. Thanks, Om
Re: [VOTE] Apache Flex 4.9 Release Candidate 4
I remember there was a fix submitted as a patch. I am not sure if that was committed. Erik, do you remember what happened to that patch? Om On Dec 19, 2012 12:22 PM, Chema Balsas jbal...@gmail.com wrote: Hi, I was checking the installer, and was starting to add a translation for the es_ES locale. After compiling and launching it, There are lots of buttons with empty labels. If you select a different locale and then back to spanish, then the labels appear. I remember reading something like this before the previous version was released... is this the same issue? Is it supposed to be fixed before this version is released? Cheers, Chema 2012/12/19 Alex Harui aha...@adobe.com -Original Message- From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of Om Sent: Wednesday, December 19, 2012 9:36 AM To: flex-dev@incubator.apache.org Subject: Re: [VOTE] Apache Flex 4.9 Release Candidate 4 1. Would there be value in adding drop downs that let users switch between FP swc versions and AIR sdk versions? I would say no. I wouldn't want to take the time to test this additional functionality. Could the two URLs it will hit (based on the answer to #2) be stored in an external .XML file? That would make it easier to folks to use different versions and for us to update an already released installer if Adobe goes and moves things around again. Yes, we load all the download urls from an external config file: http://incubator.apache.org/flex/sdk-installer-config.xml My thinking is that we will have a different config for each FP/AIR combination we want to support. Just show a simple dropdown at the launch of the app (default to 11.4/3.4). Depending on what the user selects, we grab the corresponding config url. A pretty straightforward implementation. But this could wait until Installer 2.5 if we dont want to hold up Flex 4.9 release. Thanks, Om I just built and ran the installer from sources on Win7. FB4.7 accepted the results as a new SDK. I created a new Flex project and it showed up in IE8 and FF15. I didn't see any warnings or errors. So, I would say we don't take the time to test all of the permutations of configs. Adobe is not open next week so I will be working from home and testing the installer is slow because of the internet speeds I get at home, so the less downloading I need to do, the better. Alex Harui Apache Flex Team http://blogs.adobe.com/aharui
Re: We need your help testing Flex 4.9 with various Flash Player versions
Thanks Erik, Fred, Alex and Nick who have volunteered so far! Others, there are still a lot of combinations available for testing. If you haven't had a chance to dig into Apache Flex and get your environment set up, this is a great time to start :-) Just to be clear, we should all be testing on the* 4.9 release branch*: https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/release4.9 And let us stick to *en_US *for now. It seems that other locales cannot be tested easily. More on that later. Thanks, Om On Tue, Dec 18, 2012 at 12:18 AM, Erik de Bruin e...@ixsoftware.nl wrote: On it, starting with 10.2 on OS X. EdB On Tue, Dec 18, 2012 at 1:05 AM, Om bigosma...@gmail.com wrote: Justin has been working hard on getting Flex 4.9 into shape for a release. He has also made it possible to easily switch between different versions of Flash Player while compiling the SDK. This is where you come in. Before we release, it would be great if we can compile and run the Mustella test suite against each version of the Flash Player we want to support. Here are the detailed instructions on how to switch between Flash Player versions before compiling the SDK: How to compile Flex for different versions of Flash Player: https://cwiki.apache.org/confluence/display/FLEX/Compiling+Apache+Flex+for+different+Locales+and+different+versions+of+the+Flash+Player How to run Mustella: https://cwiki.apache.org/confluence/display/FLEX/Mustella+Overview To make it easier to track the progress of testing, there is also a table that shows which version/platform has been tested. Please take a look at the pages, follow the steps, compile and then run Mustella for as many versions as you can. A complete run of Mustella takes hours, so it would be better to plan for an overnight run Please keep in mind that you dont need to be a committer to help out with this very important step before our next release. If you want to help, you can directly edit the Wiki to add your name into the corresponding row (if you have write access to the Wiki) or you can reply to this thread and I will add your name to the woki (if you dont have write access to the Wiki) Please feel free to respond with questions, if any. Thanks, Om -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: We need your help testing Flex 4.9 with various Flash Player versions
In theory, yes. But the RCs are changing so fast that it is hard to keep track of. Since the next RC is going to be cut from the release branch, I think testing the release branch should be fine. Om On Dec 18, 2012 9:35 AM, Alex Harui aha...@adobe.com wrote: On 12/18/12 12:37 AM, Om bigosma...@gmail.com wrote: Just to be clear, we should all be testing on the* 4.9 release branch*: Shouldn't we really be testing the RC? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [VOTE] Apache Flex 4.9 Release Candidate 4
On Tue, Dec 18, 2012 at 8:35 AM, Carol Frampton cfram...@adobe.com wrote: -1 The SDK is almost there but now that the README mentions the installer I will vote -1 until the installer is ready to go out at the same time. The installer is ready. I posted about it here: http://markmail.org/message/ka5vmji5advcq7c7 Thanks, Om
Re: We need your help testing Flex 4.9 with various Flash Player versions
On Tue, Dec 18, 2012 at 10:49 AM, Alex Harui aha...@adobe.com wrote: On 12/18/12 10:32 AM, Om bigosma...@gmail.com wrote: On Tue, Dec 18, 2012 at 10:06 AM, Alex Harui aha...@adobe.com wrote: On 12/18/12 9:50 AM, Om bigosma...@gmail.com wrote: In theory, yes. But the RCs are changing so fast that it is hard to keep track of. Since the next RC is going to be cut from the release branch, I think testing the release branch should be fine. Actually, I think I am going to claim that the only correct procedure is to test the actual RC. That ensures that nothing went wrong in the packaging. Otherwise, how can you really vote on the RC? I guess you can bin-diff the files in the RC vs the release branch and show that there are no differences, but that seems like an extra and slow step. I disagree. This excercise has NOTHING to with any Release Candidate. The 'correct' approach is to first test on all different combinations, ensure that everything works as we want to claim and then cut a release. I would go as far as stopping any new RCs before we get all these test scenarios completed. OK, I guess I missed a decision somewhere. I thought this exercise was to approve the RC. If Justin withdraws the RC vote, then I will know you are right. But frankly, I think we should just test the RC and vote on it and get it out the door. If we want to just get it out the door (I am not sure why we'd want to do it that way), we should update the README to not say we support these other flash player versions. Once an RC is cut, individuals are free to test on whatever platform/flash player version/AIR version they want and indicate that in their +1 or -1 vote for the RC. And because the RC does not have its own copy of the mustella tests, you have to use the recipe I described below if you plan to test the RC with mustella. Sounds like a bad idea. We dont lock the develop branch. What if someone changes the tests in develop that make it incompatible with the code in the RC that was cut. Also, right now I think that there might be some changes to mustella in the develop branch that haven't been sync'd over to release 4.9. Step 0 in the future should be to run mustella on the develop branch before cutting the release branch. Then let us all switch to testing the develop branch first on various combinations before cutting the release branch. If Justin agrees to this plan, I will try to sync up the release branch's mustella tests. It will take a while as I will need to make sure that mustella change aren't tied to develop branch checkins. And I'll have to run the mini_run -all on the release branch overnight. I would say that it is up to him (Justin, your thoughts?) I am all for releasing sooner than later, but we need to follow the steps in the right order. I would say the right order is: a) Test with all versions of runtimes we want to support - on the develop branch b) Fix issues as necessary c) If we decide that a certain version of flash player is too costly to support indicate that we dont support it in the README (hopefully we drop the older versions first) d) Cut a release branch c) Test release branch with preferred version (ex. FP 11.4 + AIR 3.4) d) Cut an RC e) Folks test src and binary kits with real projects (and not necessarily Mustella tests) and whatever runtimes they want to work with. My recipe (on Win, will try to run Mac tonight): -Download the RC. -Unzip to a folder (c:\apacheflex4.9) -Change the build.properties if you are trying different player version -Setup the required environment variables -Make sure FLASHPLAYER_DEBUGGER environment variable is pointing to right player if you are using a different player version -run ant main checkintests -Set FLEX_HOME environment variable to the folder (FLEX_HOME=c:/apacheflex4.9). Note the forward slash for Cygwin. -Change to develop branch's mustella folder -Uncomment and edit local.properties to point sdk.dir to c:/apacheflex4.9 -run ./mini_run.sh -all -run ./mini_run.sh -failures -rerun You are mixing source trees here (downloaded apache 4.9 vs. develop branch) I am not sure what the intent is. The RC does not contain the full mustella suite (not very useful to most folks) so you need to be able to redirect a branch's mustella run against an external set of SWCs and compiler. If we want to do this, we should not test against the mustella tests in develop, but agains the mustella tests in the release branch. The release branch is more protected than the develop branch. This should prevent spurious test failures or false positives. Also, the RC is baked with a version of flash player. The FlashPlayer is not in the RC. But I assume you are talking about the swf-version in the library.swfs in the SWCs and the default value set in build.properties and flex-config.xml
Re: Apache Flex 4.9 Release Candidate 3
On Tue, Dec 18, 2012 at 1:58 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Which is useful, but somewhat disturbing information as it potentially increases the number of possible rendering environments. I don't think we can possible test every combination here that's: OS version (at least 2) x compile for FP (x8) x run in FP versions (x8) x supported locales (x22) x AIR (x5) = 14000+ combinations :-) I think we decided that we will test only en_US because that is what we have baselines for. And it makes logical sense to tie a FP runtime to its corresponding AIR runtime (ex. 11.4 goes with AIR 3.4) With these assumptions, the number of combinations would be more like: OS version (at least 2) x compile for FP/AIR (x8) = 16 combinations. More manageable, IMHO. Thanks, Om
Re: We need your help testing Flex 4.9 with various Flash Player versions
On Dec 18, 2012 2:27 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, I would say that it is up to him (Justin, your thoughts?) I am all for releasing sooner than later, but we need to follow the steps in the right order. Given that most users of the SDK are going to use the default of FP 11.1/AIR 3.4 we needs test that on windows/OSX, everything else is nice to have. I think you mean 11.4/3.4, right? I don't think we need to drop support for older versions of the flash player, just state that they have not been fully tested and that there may be some unknown issues. Do you want to take a stab at modifying the README reflecting this sentiment? Thanks, Justin
Re: [VOTE] Apache Flex 4.9 Release Candidate 4
On Dec 18, 2012 2:34 PM, Alex Harui aha...@adobe.com wrote: On 12/18/12 11:15 AM, Om bigosma...@gmail.com wrote: On Tue, Dec 18, 2012 at 8:35 AM, Carol Frampton cfram...@adobe.com wrote: -1 The SDK is almost there but now that the README mentions the installer I will vote -1 until the installer is ready to go out at the same time. The installer is ready. I posted about it here: http://markmail.org/message/ka5vmji5advcq7c7 I see. I was waiting for you to create an RC. Can you do that? There two questions I would like resolved before embarking on the RC quest: 1. Would there be value in adding drop downs that let users switch between FP swc versions and AIR sdk versions? 2. What are the default FP swc version and AIR sdk version that the installer should download?
Fwd: Jenkins build is back to normal : Flex_SDK_checkin_tests #25
Checkintests now pass on Jenkins! It was the absence of mm.cfg and the flashplayer trust files on the build machine that was causing the build to fail. I will start tweaking the two jobs to make them more efficient soon. Thanks, Om -- Forwarded message -- From: Apache Jenkins Server jenk...@builds.apache.org Date: Tue, Dec 18, 2012 at 4:13 PM Subject: Jenkins build is back to normal : Flex_SDK_checkin_tests #25 To: jus...@classsoftware.com, bigosma...@gmail.com, jmcl...@apache.org, cframp...@apache.org, cherre...@apache.org, ftho...@apache.org, p...@apache.org, aha...@apache.org, que...@apache.org, bdelacre...@apache.org See https://builds.apache.org/job/Flex_SDK_checkin_tests/25/changes
Re: [VOTE] Apache Flex 4.9 Release Candidate 4
On Tue, Dec 18, 2012 at 4:31 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Compiles on OSX, make SDK for both FB6 and FB7 with no issues. Tested against a few small projects and one large project with no obvious issues. However it a -1 from me as RC4 currently fails to compile with other locales (issue with experimental and apache projects). Anyone have anything to add re this RC or should I close this vote and make another RC later today (my time)? Thanks, Justin I still have the swfobject.js issue with web based flex applications. If someone could take a look at that, it would be good. Thanks, Om
Re: [VOTE] Apache Flex 4.9 Release Candidate 4
On Tue, Dec 18, 2012 at 4:42 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, I still have the swfobject.js issue with web based flex applications. If someone could take a look at that, it would be good. I've not see that issue nor can I reproduce it here. I tested several web based applications. How are you packaging up RC4 into a SDK? Using the Installer :-)
Re: [VOTE] Apache Flex 4.9 Release Candidate 4
On Tue, Dec 18, 2012 at 4:57 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Using the Installer :-) Well that would be likely a bug with the installer :-) makeApacheFlexForFlashBuilder.sh runs the swfobject-download target in the framework/download.xml file, that downloads http://swfobject.googlecode.com/files/swfobject_2_2.zip and extracts swfobject/expressInstall.swf and swfobject/swfobject.js to the templates directory. Does the installer do that? Thanks, Justin Yup it does. I see that all the files are there after the install. Not sure what to make of the errors. Can you try the installer (from utilitis/installer/trunk) and see if you can repro it?
Re: Checkintests on Jenkins
''On Tue, Dec 18, 2012 at 5:50 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, We have success! https://builds.apache.org/job/Flex_SDK_checkin_tests/27/console From now on the check in tests will run when a SVN checkin occurs (max once/hour) and once/day if no checkins. PRobably about time it mailed any failures to the dev mailing list so people are aware of any issues. There will be a few false positives as the machine is not 100% stable but it's worthing knowing that the build is broken or that the checkin test has failed. Justin Yup, finally we have a cron job that actually tests the shit we check in! The copy job was predicated on the presence of the string build timed out. I altered the job to add a search for passed or build timed out condition. Everything looks good now :-) Next up - getting the Mustella tests to work on Jenkins! Om
Re: Apache Flex 4.9 Release Candidate 3
On Tue, Dec 18, 2012 at 10:23 PM, Alex Harui aha...@adobe.com wrote: On 12/18/12 10:15 PM, Frédéric THOMAS webdoubl...@hotmail.com wrote: Hi, Adding else if (s.startsWith(Avertissement)) to the MustellaResultsParser.java makes the checkintests pass, thanks Alex, where am I suppose to check in that, in the develop or releaze4.9 branch ? The release4.9 branch, then merge it back to the develop branch if you have time. We'll do a giant merge after releasing if you don't have time. It sort of depends on how many folks you think will run checkintests against the develop branch in the near future. Well, we just enabled checkintests on Jenkins...
Re: Apache Flex 4.9 Release Candidate 3
On Tue, Dec 18, 2012 at 10:45 PM, Alex Harui aha...@adobe.com wrote: On 12/18/12 10:37 PM, Om bigosma...@gmail.com wrote: Well, we just enabled checkintests on Jenkins... Yeah, but it will run in english, so his fix is not required. Got it. Missed that part.
Re: svn commit: r1423770 - /incubator/flex/sdk/branches/release4.9/mustella/MustellaResultsParser.java
On Tue, Dec 18, 2012 at 11:37 PM, Justin Mclean jus...@classsoftware.comwrote: HI, It is for checkintests to pass in French OS. I think it is ok to take. Sadly not - I think it just broke the check in test for english. https://builds.apache.org/job/Flex_SDK_checkin_tests/28/console Justin BTW, this build did not copy the flashlog.txt into the workspace. I have fixed the Jenkins job to copy the flashlog.txt in case of a BUILD FAILED result as well now. If you want to see what happened, we can trigger a new build right away.
Re: Apache Flex 4.9 Release Candidate 3
I was thinking of adding a dropdown box for the various Flash Players swcs (11.1 through 11.5) and AIR SDK versions (3.1 through 3.5) - so that it is easy for users to chose the runtimes they want to target. Is it that simple, or should this selection happen during the compilation of the SDK? On Sun, Dec 16, 2012 at 11:12 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, I guess the folks would apreciate to be able to compile their last Flex/Air apps out of the box without the need to recompile the framework and use target-version Understand your concern, but IMO not everyone uses AIR, and I think those who do are used to configuring FB to work with various versions of AIR. Also I think we'd have a lot of complaints if we forced 4.9 SDK users to upgrade to FP 11.4 by default. Anyone have anything to add / or a different opinion? Thanks, Justin
Re: Apache Flex 4.9 Release Candidate 3
On Mon, Dec 17, 2012 at 12:10 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, I was thinking of adding a dropdown box for the various Flash Players swcs (11.1 through 11.5) and AIR SDK versions (3.1 through 3.5) - so that it is easy for users to chose the runtimes they want to target. Nice idea. Is it that simple, or should this selection happen during the compilation of the SDK? Well currently I believe the byte code generated is the same (unless we start using new flash player features). You'd need to update some of the config files. eg flex-sdk-description.xml Do you mean the name element in flex-sdk-description.xml? That looks pretty straightforward to change. What other stuff much be changed? Can we compile a list?
Re: Apache Flex 4.9 Release Candidate 3
On Mon, Dec 17, 2012 at 7:37 AM, Carol Frampton cfram...@adobe.com wrote: On 12/17/12 3 :00AM, Om bigosma...@gmail.com wrote: I was thinking of adding a dropdown box for the various Flash Players swcs (11.1 through 11.5) and AIR SDK versions (3.1 through 3.5) - so that it is easy for users to chose the runtimes they want to target. I would not do this unless you are prepared to do a mustella run with each of those combinations to make sure there aren't any issues before we release. Carol We need to do a mustella run for each version we support regardless of how we build the Installer. It says in the Release Notes [1] that Apache Flex SDK can be compiled for any version of the Flash Player from 10.2 to 11.5. Has this statement been verified? [1] http://people.apache.org/~jmclean/Apache%20Flex%204.9.0%20Release%20Candidate%203/RELEASE_NOTES
Re: Apache Flex 4.9 Release Candidate 3
On Mon, Dec 17, 2012 at 2:03 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Apache Flex SDK can be compiled for any version of the Flash Player from 10.2 to 11.5. Has this statement been verified? I have at various time compile the SDK for all versions mention in the README, but all of them haven;t been tested yet to my knowledge. Justin If you could publish the steps for compiling and testing against a particular version of the Flash Player, I (and hopefully a few others) can chip in and test all the versions. Thanks, Om
Re: Apache Flex 4.9 Release Candidate 3
On Mon, Dec 17, 2012 at 2:53 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Justin - If I understand what you did a while back, after changing those properties don't you have to rebuild frameworks so that the flex-config target in frameworks/build.xml fixes up the playerversion, swfversion and locale in flex-config.xml? Yep you change the properties then rebuild that correct. Thanks, Justin Sorry to do this, but can you please post a wiki page with detailed instructions (like I am a 5 year old)? Its hard to follow this thread :-) Thanks, Om
Re: Apache Flex 4.9 Release Candidate 3
Perfect! Thanks for this. I have updated the page with assignments. I will start a new thread calling for folks to help with the testing. Om On Mon, Dec 17, 2012 at 3:29 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Sorry to do this, but can you please post a wiki page with detailed instructions (like I am a 5 year old)? Its hard to follow this thread :-) Here you go: https://cwiki.apache.org/confluence/display/FLEX/Compiling+Apache+Flex+for+different+Locales+and+different+versions+of+the+Flash+Player Once you compile and tested a SDK please add it to the table at the bottom of the page. Thanks, Justin
Re: Apache Flex 4.9 Release Candidate 3
On Mon, Dec 17, 2012 at 5:28 PM, Nicholas Kwiatkowski nicho...@spoon.aswrote: I can't avoid it any longer ;P Karma always gets you in the end ;-) I can update the wiki for you in the meantime. Om
Re: Apache Flex 4.9 Release Candidate 3
I have updated the Installer to support Flex 4.9. I tested it with your RC3 and the downloads/installs work fine. Flash Builder 4.6 recognizes the SDK fine (I like it that the name of the SDK appears as Apache Flex 4.9.0 FP11.1 en_US - Nice touch!) My smoke test AIR project compiled and ran fine. My smoke test Flex project compiled fine, but the app did not show up in the browser (tried on IE8, Firefox 17.0.1) This is the browser error message: (From Firebug) ReferenceError: swfobject is not defined file:///C:/p/flex_os/workspace/SmokeTestWebProject/bin-debug/SmokeTest.html Line 69 The source code for the new version of the Installer is available here [1] Oh btw, I re-enabled the locale choosing functionality that we disabled for v1 release. If folks can start testing the various locales and fixing any related issues, that would be great. Thanks, Om [1] https://svn.apache.org/repos/asf/incubator/flex/utilities/trunk/installer On Sat, Dec 15, 2012 at 9:49 PM, Justin Mclean justinmcl...@gmail.comwrote: Hi, The release candidate can be found here; http://people.apache.org/~jmclean/Apache%20Flex%204.9.0%20Release%20Candidate%203/ Fixed in this release candidate: - Can compile on OSX with Java 1.7 - Make ide scripts now use AIR 3.4 rather than AIR 3.1 - Fix for TLF text truncation I've done some informal testing with this releases with several existing projects and found no obvious major issues. Two minor issues I've found: Looks like there some incompatibility with the make IDE build script and Flash Builder 4.7 (Flash Builder 4.6 is fine). De we have a exact list of FB 4.7 expects and where? With flex build number, the flex description file is correctly set with the SVN change number but isn't copied across to the source package flex description file. Justin
Re: Flash Builder issues and 4.9 release candidate
I think that we should at least support FB 4.6 and 4.7 with a Flex SDK release. We don't know if this would work with any other IDE. This version of the SDK would be pretty much useless if we don't support FB. Thanks, Om On Dec 13, 2012 11:25 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Currently with Apache Flex 4.9 RC2 we have teh following issues: - Flash Builder 4.6 and 4.7 not able to use the SDK if it compiled against Java 1.7 (on OSX not tested on windows) - Flash Builder 4.7 not recognising Apache Flex 4.9 RC While we may be able to work around these issues it's not certain. If we can't work around them should we go ahead and vote on a 4.9 release and just note the (current) limited FB support for Apache Flex in the README? Thanks, Justin
Re: Release target and Jenekins
On Thu, Dec 13, 2012 at 12:03 AM, Alex Harui aha...@adobe.com wrote: Ant main checkintests takes like 12 minutes for me. The checkintests take only the last two minutes or so. It sure seems like the player is hanging on the security exception dialog. I would see if there is a way to verify the trust file settings. This was the first time the sdk was built in that workspace, so it was downloading a lot of stuff. I am going to try it again and see if it does not time out at least. On 12/12/12 11:55 PM, Justin Mclean jus...@classsoftware.com wrote: Looks like it froze and didn't run any tests to me which was the issue I was having before. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Release target and Jenekins
On Thu, Dec 13, 2012 at 12:15 AM, Om bigosma...@gmail.com wrote: On Thu, Dec 13, 2012 at 12:03 AM, Alex Harui aha...@adobe.com wrote: Ant main checkintests takes like 12 minutes for me. The checkintests take only the last two minutes or so. It sure seems like the player is hanging on the security exception dialog. I would see if there is a way to verify the trust file settings. This was the first time the sdk was built in that workspace, so it was downloading a lot of stuff. I am going to try it again and see if it does not time out at least. Yup, that failed as well. Now that the sdk build problem is fixed, I will try to reproduce the flash player security error on my local machine. I have removed the reference to the mustella/tests directory from these two locations (from any and all cfg files): C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerTrust C:\Users\user\AppData\Roaming\Macromedia\Flash Player\#Security\FlashPlayerTrust I then proceeded to close all browsers and restarted the computer. And then I ran ant checkintests, the flash player is still opening up the tests and everything goes fine. The build is successful. What am I missing? How exactly can I repro the flash player not responding issue locally?
Re: Release target and Jenekins
On Thu, Dec 13, 2012 at 1:11 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Yeah, it seems like there is some secret place that the Global Settings are stored. You might want to run a dummy swf and see what the right-click global settings say are trusted locations. Can you add a trusted location via the command line/parameters to the debug player in any way? If that was possible, it would be a major security flaw :-)
Re: Release target and Jenekins
I believe that the mm.cfg file is missing on the windows slave. How would I get this added on to that server? Should I send an email to bui...@apache.org? Once we have that, we should at least get to know what is happening by looking at the flashlog.txt dump. Thanks, Om On Thu, Dec 13, 2012 at 1:15 PM, Om bigosma...@gmail.com wrote: On Thu, Dec 13, 2012 at 1:11 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Yeah, it seems like there is some secret place that the Global Settings are stored. You might want to run a dummy swf and see what the right-click global settings say are trusted locations. Can you add a trusted location via the command line/parameters to the debug player in any way? If that was possible, it would be a major security flaw :-)
Re: Release target and Jenekins
On Thu, Dec 13, 2012 at 1:19 PM, Om bigosma...@gmail.com wrote: I believe that the mm.cfg file is missing on the windows slave. How would I get this added on to that server? Should I send an email to bui...@apache.org? Once we have that, we should at least get to know what is happening by looking at the flashlog.txt dump. Thanks, Om Never mind. I have created this bug in JIRA [1] for this. Thanks, Om [1] https://issues.apache.org/jira/browse/INFRA-5652 On Thu, Dec 13, 2012 at 1:15 PM, Om bigosma...@gmail.com wrote: On Thu, Dec 13, 2012 at 1:11 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Yeah, it seems like there is some secret place that the Global Settings are stored. You might want to run a dummy swf and see what the right-click global settings say are trusted locations. Can you add a trusted location via the command line/parameters to the debug player in any way? If that was possible, it would be a major security flaw :-)
Apache Flex Community Revue December 2012
...is available here: http://www.spoon.as/2012/apache-flex-community-revue-december-2012/ Thanks, Om
Re: Flash Builder 4.6/4.7 and Apache Flex
On Dec 13, 2012 10:53 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Adobe nicely sent me my free FB 4.7 serial and looks like it expects a slightly different format for the SDK than we expect. 1. Compile from source code (RC2) 2. Run ide/fashbuilder/makeApacheFlexForFlashBuilder.sh to package up SDK that something FB can use. FB 4.6 recognised the packaged SDK however FB 4.7 doesn't. Is the makeApacheFlexForFlashBuilder.sh script up to date? Have I missed any other required steps? FB 4.7 gives the error Directory does not contain a Flex SDK. Anyone know exactly what FB 4.7 expects where? Thanks, Justin Did you try the installer with 4.8? Does it work with FB 4.7? I remember Carol mentioning that the scripts are out of date. Thanks, Om
Re: Release target and Jenekins
On Tue, Dec 11, 2012 at 11:50 PM, Alex Harui aha...@adobe.com wrote: Can we get the ant output in the console and the flashlog.txt? There is no flashlog.txt output since the file was not found. Here is the console output: Started by user jmclean Building remotely on windows1 in workspace f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests Location 'https://svn.apache.org/repos/asf/incubator/flex/trunk' does not exist Updating https://svn.apache.org/repos/asf/incubator/flex/trunk ERROR: Failed to update https://svn.apache.org/repos/asf/incubator/flex/trunk org.tmatesoft.svn.core.SVNException: svn: Target path '/incubator/flex/trunk' does not exist svn: REPORT of /repos/asf/!svn/vcc/default: 500 Internal Server Error ( https://svn.apache.org) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1284) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:830) at org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:564) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:401) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:136) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:788) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:769) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2309) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Unknown Source) Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: Target path '/incubator/flex/trunk' does not exist at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:146) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:89) at org.tmatesoft.svn.core.internal.io.dav.handlers.DAVErrorHandler.endElement(DAVErrorHandler.java:72) at org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.endElement(BasicDAVHandler.java:99) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:776) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:741) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readError(HTTPConnection.java:222) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.readError(HTTPRequest.java:290) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.java:213) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:379) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:292) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:283) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:271) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:283) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1282) ... 19 more Caused by:
Re: Release target and Jenekins
On Wed, Dec 12, 2012 at 12:28 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, There is no flashlog.txt output since the file was not found. The job timed out and as a result of that error occurred next. Justin This job is looking at https://svn.apache.org/repos/asf/incubator/flex/trunk which seems outdated. Can you try updating it to the correct location and try again?
Re: Release target and Jenekins
On Wed, Dec 12, 2012 at 12:57 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, This job is looking at https://svn.apache.org/repos/asf/incubator/flex/trunk which seems outdated. The Flex_SDK_build job is using: https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/develop It has the same issue when I tried 2 days ago, so that's not the issue. Justin After you changed the repo location for Flex_SDK_checkin_tests, there is a different error now. Looks like an issue with the paths (cant find compc, mxmlc, etc) I am trying to fix the paths now. https://builds.apache.org/job/Flex_SDK_checkin_tests/18/consoleText
Re: Test Release of Apache Flex 4.9
On Wed, Dec 12, 2012 at 12:19 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, I think the next installer should install just Apache Flex 4.9. Both the SDK and the installer should be released the same day. We could have a vote of the SDK release today, a vote for the installer is probably some time off and I'm not sure if anyone is working on it. Justin If we are going to have installer v.2 support only Flex 4.9, I will be able to get it working in the next week or so. Thanks, Om
Re: Release target and Jenekins
Good news. I ran the same job locally on my instance of Jenkins and I am
getting the same exact error . Will debug it on my machine by this
evening.
Thanks,
Om
On Wed, Dec 12, 2012 at 1:39 PM, Alex Harui aha...@adobe.com wrote:
BTW, the flashplayer trust folder might be in
%systemroot%\syswow64\macromed
On 12/12/12 1:31 PM, Alex Harui aha...@adobe.com wrote:
On 12/12/12 1:23 PM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
{sdk_folder}/build.xml - checkintests task
I'd give that a go first, but either is probably fine. Any automated
testing
we have is far better than none.
Yes, the one from the top level build.xml. It might call into sub-folder
targets, but the true test is getting it to work from the top-level.
Thanks,
Justin
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
