Re: [CANCEL][DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-15 Thread Alex Harui
t;>> right >>>>> when you can unpack the source package and the characters match up. >>> Until >>>>> then, it isn't really worth putting out another RC. >>>>> >>>>> Good luck, >>>>> -Alex >>>

Re: [CANCEL][DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-15 Thread Harbs
; >>>> Good luck, >>>> -Alex >>>> >>>> From: Piotr Zarzycki >>> piotrzarzyck...@gmail.com>> >>>> Reply-To: "dev@flex.apache.org<mailto:dev@flex.apache.org>" < >>>> dev@flex.apache.org<

Re: [CANCEL][DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-15 Thread Maxim Solodovnik
gt;> -Alex > >> > >> From: Piotr Zarzycki >> piotrzarzyck...@gmail.com>> > >> Reply-To: "dev@flex.apache.org<mailto:dev@flex.apache.org>" < > >> dev@flex.apache.org<mailto:dev@flex.apache.org>> > >> Date: Tu

[CANCEL][DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-15 Thread Piotr Zarzycki
o:dev@flex.apache.org>> >> Date: Tuesday, November 14, 2017 at 10:06 AM >> To: "dev@flex.apache.org<mailto:dev@flex.apache.org>" < >> dev@flex.apache.org<mailto:dev@flex.apache.org>> >> Subject: Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-15 Thread Piotr Zarzycki
"dev@flex.apache.org<mailto:dev@flex.apache.org>" < > dev@flex.apache.org<mailto:dev@flex.apache.org>> > Date: Tuesday, November 14, 2017 at 10:06 AM > To: "dev@flex.apache.org<mailto:dev@flex.apache.org>" <mailto:dev@flex.apache.org>> > Subject

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-14 Thread OmPrakash Muppirala
On Tue, Nov 14, 2017 at 7:50 PM, Par Niclas Hedhman wrote: > > Alex, > it is called "Open SOURCE" and not "Binary with link to Source" for a > reason. Apache Software Foundation official only promise SOURCE releases. > Any convenience binaries are not required/expected. It is not kosher to so > c

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-14 Thread Justin Mclean
Hi, > Niclas, Where did I say it was "Binary with link to Source?” I would assume from your email here: > So, my assessment is: > 1) the binary artifacts are ok. No new problems. > 2) the source artifacts are not ok. There might be a workaround if we can > figure out how to convert the code p

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-14 Thread Alex Harui
Niclas, Where did I say it was "Binary with link to Source?" Do you truly understand the issues here or are you just falsely accusing me of something? This is the kind of behavior we are supposed to model? How about modeling constructive criticism instead. -Alex On 11/14/17, 7:50 PM, "Par Nic

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-14 Thread Par Niclas Hedhman
Alex, it is called "Open SOURCE" and not "Binary with link to Source" for a reason. Apache Software Foundation official only promise SOURCE releases. Any convenience binaries are not required/expected. It is not kosher to so called release (or make available) any binaries that are not built fro

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-14 Thread Alex Harui
lex From: Piotr Zarzycki mailto:piotrzarzyck...@gmail.com>> Reply-To: "dev@flex.apache.org<mailto:dev@flex.apache.org>" mailto:dev@flex.apache.org>> Date: Tuesday, November 14, 2017 at 10:06 AM To: "dev@flex.apache.org<mailto:dev@flex.apache.org>" mailto:dev@flex.apa

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-14 Thread Piotr Zarzycki
Hi Alex, I'm running out of time for today, but I just look into the: frameworks/tests/basicTests/spark/views/SortTests.mxml in my local repository on Windows I see exactly same as you pasted here: "海 (U+6D77)", "雨 (U+96E8)", "水 (U+6C34)", "川 (U+5DDD)"]); But when I unpack on my Windows RC2 sour

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-14 Thread Maxim Solodovnik
I can confirm (using Ubuntu 16.04 latest) LICENSE file has Windows line endings (which is OK if it was checked-out on Windows) both frameworks/locale/ja_JP/metadata.properties and frameworks/tests/basicTests/spark/views/SortTests.mxml files has invalid contents (encoding) I would suggest to creat

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Alex Harui
On 11/13/17, 11:34 PM, "Justin Mclean" wrote: >Hi, > >> The binaries are not created by first creating the source package, >> unpacking it and compiling it. You were a Flex SDK RM at least once, >>did >> you not understand what you were signing? > >Every time I made the release I made it from

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Alex Harui
Piotr, If you look at your repo's copy of frameworks/tests/basicTests/spark/views/SortTests.mxml, around line 43 you should see: "海 (U+6D77)", "雨 (U+96E8)", "水 (U+6C34)", "川 (U+5DDD)"]); Note the character before "(U+5DDD)". It should look like 1 curved line followed by 2 straight lines.

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Justin Mclean
Hi, > I just pushed RC2 [1]. Can you check whether you have the same problem ? > > [1] https://dist.apache.org/repos/dist/dev/flex/sdk/4.16.1/rc2/ Yes I can confirm that the scripts have execute bits. The files do not have the correct line endings (for instance look at LICENSE) Re UTF-8 it doe

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Justin Mclean
Hi, > The binaries are not created by first creating the source package, > unpacking it and compiling it. You were a Flex SDK RM at least once, did > you not understand what you were signing? Every time I made the release I made it from the source on my local machine on a clean tagged branch. I

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Alex Harui
If the RC build was run on files that weren't utf-8 encoded, the build would have failed, since the build runs checkintests and that's where it first notices the encoding differences. And then I would expect the binaries in the RC would be incorrect, which it appears they aren't. Files are being

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Maxim Solodovnik
I read through almost all emails, Unfortunately have not much time to contribute more :(( On Tue, Nov 14, 2017 at 2:23 PM, Piotr Zarzycki wrote: > Hi Maxim, > > Long time no see! :) Thanks for looking into that! > > Piotr > > > 2017-11-14 8:15 GMT+01:00 Maxim Solodovnik : > > > Just have tried t

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Piotr Zarzycki
Hi Maxim, Long time no see! :) Thanks for looking into that! Piotr 2017-11-14 8:15 GMT+01:00 Maxim Solodovnik : > Just have tried to run `bin/*` files under Ubuntu > Only errors related to missing environment variables are reported > > On Tue, Nov 14, 2017 at 2:01 PM, Piotr Zarzycki > > wrote

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Piotr Zarzycki
Alex, I understand what is all about with chmod as it was in FlexJS (not sure which file should be converted), but I would like to leave it as is now. Unfortunately I don't understand your last sentence: "I was hoping the source files would be valid on Windows, but I just checked and even there t

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Maxim Solodovnik
Just have tried to run `bin/*` files under Ubuntu Only errors related to missing environment variables are reported On Tue, Nov 14, 2017 at 2:01 PM, Piotr Zarzycki wrote: > Hi, > > I just pushed RC2 [1]. Can you check whether you have the same problem ? > > [1] https://dist.apache.org/repos/dist

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Piotr Zarzycki
Hi, I just pushed RC2 [1]. Can you check whether you have the same problem ? [1] https://dist.apache.org/repos/dist/dev/flex/sdk/4.16.1/rc2/ Piotr 2017-11-14 7:59 GMT+01:00 Justin Mclean : > Hi, > > I would guess that all the issue are git config issues. > > git config —list will give you a l

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Maxim Solodovnik
.gitattributes file might be created in git repo to unify settings ... On Tue, Nov 14, 2017 at 1:59 PM, Justin Mclean wrote: > Hi, > > I would guess that all the issue are git config issues. > > git config —list will give you a list of your settings. > > > I think I just verified that the binary

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Justin Mclean
Hi, I would guess that all the issue are git config issues. git config —list will give you a list of your settings. > I think I just verified that the binary artifacts are ok regarding the > non-ascii characters. I think that's because they are correct in the > repo, and were compiled into bund

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Alex Harui
On 11/13/17, 6:27 PM, "Justin Mclean" wrote: >Hi, > >> Is the DateChooser problem from your local build of the sources or from >> the RC binary artifacts? > >A local built from the compiled source bundled I've not tested the binary >yet but given it was made from the source release I would expe

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Alex Harui
I think I just verified that the binary artifacts are ok regarding the non-ascii characters. I think that's because they are correct in the repo, and were compiled into bundles from that repo source. I'm not sure when the files get screwed up. I think it is when Ant copies the files to the temp

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Justin Mclean
Hi, CCed to you just in case it doesn’t show up on the list as it tends to reject email with images. What it should look like: What 4.16.1 gives: There are other similar issues cause by the same issue as well. Code to replicate: http://ns.adobe.com/mxml/2009";

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Piotr Zarzycki
Hi Justin, Could you please post screenshot what is wrong cause I don't understand. - I wanted to compare results of tests between those two RCs. I will cut another RC, but not because of the issue above, but because I couldn't run sh script either on my Mac which is not good itself. I would like

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Justin Mclean
Hi, > Is the DateChooser problem from your local build of the sources or from > the RC binary artifacts? A local built from the compiled source bundled I've not tested the binary yet but given it was made from the source release I would expect it to show the same issues. Or are you saying that

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Alex Harui
Is the DateChooser problem from your local build of the sources or from the RC binary artifacts? I don't doubt that the locale files are not right, but I would have expected them to be compiled into bundles correctly on the RM's machine. -Alex On 11/13/17, 4:17 PM, "Justin Mclean" wrote: >Hi,

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Justin Mclean
Hi, > Which would effect the locale files i.e. the Chinese and Japanese and > probably French and other european language locales would be broken. Confirmed it’s an issue and I would also vote -1 binding because of that. To reproduce just view a DateChooser and you’ll see it has some ? in it’s

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Justin Mclean
Hi, > What is a problem with the release is that the files do not appear to be > UTF-8 encoded. Which would effect the locale files i.e. the Chinese and Japanese and probably French and other european language locales would be broken. And perhaps some of the keyboard handling code? Thanks,

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-13 Thread Alex Harui
I spent some time checking out the release. The line-ending problem is a non-issue. Prior releases are set up this way as well. The "release" target fixes up the line endings when building the binary kit. I think the main build does not so it doesn't inject changes into the sources in a repo.

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-12 Thread Justin Mclean
Hi, > Ok I got it, but I don't fully understand how changing line endings for > files check outed for sdk repository could change final .tar.gz file. Exact > this file has wrong line endings, or file after unpack have ? As I said the bash script contained in the .tar.gz have the wrong line ending

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-12 Thread Piotr Zarzycki
Hi, Ok I got it, but I don't fully understand how changing line endings for files check outed for sdk repository could change final .tar.gz file. Exact this file has wrong line endings, or file after unpack have ? Thanks, Piotr 2017-11-12 12:48 GMT+01:00 Justin Mclean : > Hi, > > > What do I n

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-12 Thread Justin Mclean
Hi, > What do I need to do in build.xml script in order to fix that or your > suggestion is to take this file and do something with it ? I’ve not build on windows for several years so not 100% sure sorry. When building on OSX I’ve not run into the issue. It may actually be a git setting issue

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-12 Thread Justin Mclean
Hi, > I don't understand actually .tar.gz source is used on Linux and OSX, the .zip on windows. Linux and OSX use different line endings and if you use DOS/windows style line ending in shell scripts they will not run > It was packaged by build.xml script on Windows 10. Does it make the > diff

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-12 Thread Piotr Zarzycki
Maybe I wasn't clear, but my questions are: What do I need to do in build.xml script in order to fix that or your suggestion is to take this file and do something with it ? I haven't change the type of compression. Piotr 2017-11-12 12:15 GMT+01:00 Piotr Zarzycki : > Hi, > > I don't understand a

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-12 Thread Piotr Zarzycki
Hi, I don't understand actually - It was packaged by build.xml script on Windows 10. Does it make the difference for your OSX ? What do you mean .sh files ? Piotr 2017-11-12 11:47 GMT+01:00 Justin Mclean : > Hi, > > Looks like the tar.gz file has been packaged / checked out with wrong line > en

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-12 Thread Justin Mclean
Hi, I’m also having issues downloading OSMF when trying t compile the SDK and I do have the international crypto set up. However it's only failing on on Java 1.7 and works on 1.8, on OSX if that helps anyone. Thanks, Justin

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-12 Thread Justin Mclean
Hi, Looks like the tar.gz file has been packaged / checked out with wrong line endings (i.e. dos ones). If you try to run any of the .sh files you get “: invalid option” on OSX. you can fix this by running dos2unix on the files but their may be other issues because of this. Thanks, Justin

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-11 Thread Piotr Zarzycki
Hi Om, Peter, Here you got link to old discussion about your problems with OSMF [1] [1] http://apache-flex-development.247.n4.nabble.com/source-forge-downloads-failing-tp59050p59220.html Thanks, Piotr 2017-11-10 23:02 GMT+01:00 Piotr Zarzycki : > Hi Peter, > > Somewhere on the dev list th

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-10 Thread Piotr Zarzycki
Hi Peter, Somewhere on the dev list there is a thread where problems with downloading SMF2 is described. It is because sourcfourge changed something in their policy. The solution was to download following java jars [1] and replace in your JDK. Let me know if you are using Java 8 or 7 ? [1] http:/

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-10 Thread Peter Ent
After getting the Approval script running and going through the license files, etc., the whole thing ended with: osmf-check: osmf-download: download-osmf-swc: [get] Getting: https://sourceforge.net/adobe/flexsdk/code/HEAD/tree/trunk/frameworks/libs/ OSMF2_0.swc?format=raw [get] To:

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-10 Thread Alex Harui
Hi Piotr, Yes, you are right. I looked in the wrong thread. Sorry about that, -Alex On 11/10/17, 8:34 AM, "Piotr Zarzycki" wrote: >Alex, > >In the VOTE thread I see the right command. I've checked many times that >email. > >Peter, > >Thanks for looking into that. I hope now it will work with A

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-10 Thread Peter Ent
I had actually tried the -Drc=1, but I mistakenly set the release.version to 4.16 So close. Script is running. —peter On 11/10/17, 11:34 AM, "Piotr Zarzycki" wrote: >Alex, > >In the VOTE thread I see the right command. I've checked many times that >email. > >Peter, > >Thanks for looking into t

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-10 Thread Piotr Zarzycki
Alex, In the VOTE thread I see the right command. I've checked many times that email. Peter, Thanks for looking into that. I hope now it will work with Alex's suggestion. Piotr On Fri, Nov 10, 2017, 17:26 Alex Harui wrote: > Peter, looks like you are missing the -Drc=1 parameter. > > I guess

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-10 Thread Alex Harui
Peter, looks like you are missing the -Drc=1 parameter. I guess Piotr was unable to use the releasecandidate.xml scripts because they would have put the right command-line in the vote thread emails. IMO, it would be better to get these scripts working so they save everybody time and hassle. -Alex

Re: [DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-10 Thread Peter Ent
I'm trying the AppoveSDK.xml script. When I do: ant -f ApproveSDK.xml -Drelease.version=4.16.1 I get the following: Buildfile: /Users/pent/Downloads/ApproveSDK.xml write-out-jars-list: [delete] Deleting: /Users/pent/Downloads/jars.txt install-rat.jar: install-rat.tasks.jar: install-rat:

[DISCUSS] Release Apache Flex SDK 4.16.1 - RC1*

2017-11-09 Thread Piotr Zarzycki
Hi Folks, This is discussion thread for Apache Flex SDK 4.16.1 RC1. Thanks, -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki *