Re: Making an new Apache Flex release
For Linux support, me and one of this mailing list figured how to run it, my self I was able to run it in Ubuntu and it explained here how it is done : http://saleh360.blogspot.com/2013/04/up-and-running-with-apache-flex-on.html?m=1 On May 10, 2013 11:44 PM, Alex Harui aha...@adobe.com wrote: On 5/5/13 10:11 PM, Justin Mclean jus...@classsoftware.com wrote: I thought this was working except for running just the TLF folder? It's more broken that that - there several project level builds are also broken if you try to build them on their own. I ran ant from in the textlayout, spark, mx, mobilecomponents, and mobiletheme folders and they all ran to completion. What errors are you getting? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Making an new Apache Flex release
Hi,
I ran ant from in the textlayout, spark, mx, mobilecomponents, and
mobiletheme folders and they all ran to completion. What errors are you
getting?
Run ant at frameworks get:
lean-external:
[echo] cleaning ${TLF_HOME}
BUILD FAILED
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/build.xml:232:
The following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/build.xml:216:
Basedir
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/${TLF_HOME}
does not exist
Run ant at frameworks/projects/textLayout get:
clean-external:
[echo] cleaning ${TLF_HOME}
BUILD FAILED
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/build.xml:216:
Basedir
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/${TLF_HOME}
does not exist
Think there was a couple of others as well.
Justin
Re: Making an new Apache Flex release
I'll go the long way round ;-) EdB On Mon, May 6, 2013 at 5:51 PM, Alex Harui aha...@adobe.com wrote: Nick is right, but I don't understand why you are getting these files to show up in rat. Are those 3 targets the equivalent of ant release? Otherwise, it isn't a fair test as the release target might otherwise delete those files (since they are binaries and shouldn't be in a source package). I know you want to save time, but let's make sure we are building a correct source package and not skipping an important step. -Alex On 5/6/13 8:16 AM, Nicholas Kwiatkowski nicho...@spoon.as wrote: I think we have a list of Excluded files so the RAT report ignores files that can't or shouldn't have the license header in them. According to my IDE, those files are listed on lines 1668:1701 in the build.xml (ANT builder). We don't add the license header to binaries such as SWF, because, well.. it breaks them ;P -Nick On Mon, May 6, 2013 at 10:56 AM, Erik de Bruin e...@ixsoftware.nl wrote: If I run: ant main ant source-package ant rat-check I get a rat.report with 5 unapproved licenses: /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/javascript/fabr idge/samples/EmptySwf.swf /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/javascript/fabr idge/samples/app.swf /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/localFonts.ser /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/macFonts.ser /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/winFonts.ser But these seem to be binaries (.swf) and empty files (.ser), so how (and why) do I add license header to these? What am I doing wrong/not understanding? EdB On Mon, May 6, 2013 at 4:48 PM, Erik de Bruin e...@ixsoftware.nl wrote: Never one to shy away from a daunting task, I've taken on the 'missing headers' issue... I can run 'ant release' successfully (after fixing the JavaCC URL) and get a nice 'rat.report'. I've fixed the headers in the 'experimental/bundles' property files that ant reports. Running 'ant release' takes 32 min. on my machine. Is there a 'shortcut' so I can refresh the source packages etc. and run 'ant rat-check' directly to get a fresh report? EdB On Mon, May 6, 2013 at 5:58 AM, Justin Mclean justinmcl...@mac.com wrote: Hi, Develop and trunk are drifting further apart and we have a fair number of bug fixes, support for newer version of AIR and FP, some new experimental components, so probably about time we started thinking about a release. The longer we leave it the harder it will be to make a release. So who can help me out here? There a few things that need to be fixed up before we can make a release. Can anyone put up their hand to try and fix these? - Get Jenkin/CI back up and working with Git - not essential but give up some confidence that things are still working. - Fix build issues re TLF and move to Git - Look into issue with list selection tesst failing (selection colour difference in bitmaps) - Fix a few missing headers (dead simple!) - Does anyone know what state the components in the experimental project are? I have no idea if any of these are in a releasable state or not. - Make sure all mustella test run on OS, windows and mobile (now that mobile tests work) with flash player 11.1 and 11.7 and AIR 3.7 - What state are the mustella AIR tests in? - Add linux as an officially supported platform for this release. Is there anything else we would like to see in a release? Do we have any committers or non committers with Linux experience who would like to see this happen? There's is probably only a small amount of work required to officially supporting Linux. There are also a number of critical and major JIRA issues that have been raised over the last few months (including some of the issues above) that it would be nice to try and fix before a release. Here's the blocker and critical ones (12 issues): https://issues.apache.org/jira/issues/?filter=12323979 And those plus major ones (158 issues): https://issues.apache.org/jira/issues/?filter=12323978 Is any existing committer or non committer willing to help out and try and fix one or two of the above bugs? Almost all of this issues are unassigned. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- 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 -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
RE: Making an new Apache Flex release
I do some bug work on those major / critical ones later. -Mark -Original Message- From: Justin Mclean [mailto:justinmcl...@mac.com] Sent: Sunday, May 05, 2013 11:59 PM To: dev@flex.apache.org Subject: Making an new Apache Flex release Hi, Develop and trunk are drifting further apart and we have a fair number of bug fixes, support for newer version of AIR and FP, some new experimental components, so probably about time we started thinking about a release. The longer we leave it the harder it will be to make a release. So who can help me out here? There a few things that need to be fixed up before we can make a release. Can anyone put up their hand to try and fix these? - Get Jenkin/CI back up and working with Git - not essential but give up some confidence that things are still working. - Fix build issues re TLF and move to Git - Look into issue with list selection tesst failing (selection colour difference in bitmaps) - Fix a few missing headers (dead simple!) - Does anyone know what state the components in the experimental project are? I have no idea if any of these are in a releasable state or not. - Make sure all mustella test run on OS, windows and mobile (now that mobile tests work) with flash player 11.1 and 11.7 and AIR 3.7 - What state are the mustella AIR tests in? - Add linux as an officially supported platform for this release. Is there anything else we would like to see in a release? Do we have any committers or non committers with Linux experience who would like to see this happen? There's is probably only a small amount of work required to officially supporting Linux. There are also a number of critical and major JIRA issues that have been raised over the last few months (including some of the issues above) that it would be nice to try and fix before a release. Here's the blocker and critical ones (12 issues): https://issues.apache.org/jira/issues/?filter=12323979 And those plus major ones (158 issues): https://issues.apache.org/jira/issues/?filter=12323978 Is any existing committer or non committer willing to help out and try and fix one or two of the above bugs? Almost all of this issues are unassigned. Thanks, Justin
Re: Making an new Apache Flex release
Never one to shy away from a daunting task, I've taken on the 'missing headers' issue... I can run 'ant release' successfully (after fixing the JavaCC URL) and get a nice 'rat.report'. I've fixed the headers in the 'experimental/bundles' property files that ant reports. Running 'ant release' takes 32 min. on my machine. Is there a 'shortcut' so I can refresh the source packages etc. and run 'ant rat-check' directly to get a fresh report? EdB On Mon, May 6, 2013 at 5:58 AM, Justin Mclean justinmcl...@mac.com wrote: Hi, Develop and trunk are drifting further apart and we have a fair number of bug fixes, support for newer version of AIR and FP, some new experimental components, so probably about time we started thinking about a release. The longer we leave it the harder it will be to make a release. So who can help me out here? There a few things that need to be fixed up before we can make a release. Can anyone put up their hand to try and fix these? - Get Jenkin/CI back up and working with Git - not essential but give up some confidence that things are still working. - Fix build issues re TLF and move to Git - Look into issue with list selection tesst failing (selection colour difference in bitmaps) - Fix a few missing headers (dead simple!) - Does anyone know what state the components in the experimental project are? I have no idea if any of these are in a releasable state or not. - Make sure all mustella test run on OS, windows and mobile (now that mobile tests work) with flash player 11.1 and 11.7 and AIR 3.7 - What state are the mustella AIR tests in? - Add linux as an officially supported platform for this release. Is there anything else we would like to see in a release? Do we have any committers or non committers with Linux experience who would like to see this happen? There's is probably only a small amount of work required to officially supporting Linux. There are also a number of critical and major JIRA issues that have been raised over the last few months (including some of the issues above) that it would be nice to try and fix before a release. Here's the blocker and critical ones (12 issues): https://issues.apache.org/jira/issues/?filter=12323979 And those plus major ones (158 issues): https://issues.apache.org/jira/issues/?filter=12323978 Is any existing committer or non committer willing to help out and try and fix one or two of the above bugs? Almost all of this issues are unassigned. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Making an new Apache Flex release
If I run: ant main ant source-package ant rat-check I get a rat.report with 5 unapproved licenses: /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/javascript/fabridge/samples/EmptySwf.swf /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/javascript/fabridge/samples/app.swf /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/localFonts.ser /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/macFonts.ser /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/winFonts.ser But these seem to be binaries (.swf) and empty files (.ser), so how (and why) do I add license header to these? What am I doing wrong/not understanding? EdB On Mon, May 6, 2013 at 4:48 PM, Erik de Bruin e...@ixsoftware.nl wrote: Never one to shy away from a daunting task, I've taken on the 'missing headers' issue... I can run 'ant release' successfully (after fixing the JavaCC URL) and get a nice 'rat.report'. I've fixed the headers in the 'experimental/bundles' property files that ant reports. Running 'ant release' takes 32 min. on my machine. Is there a 'shortcut' so I can refresh the source packages etc. and run 'ant rat-check' directly to get a fresh report? EdB On Mon, May 6, 2013 at 5:58 AM, Justin Mclean justinmcl...@mac.com wrote: Hi, Develop and trunk are drifting further apart and we have a fair number of bug fixes, support for newer version of AIR and FP, some new experimental components, so probably about time we started thinking about a release. The longer we leave it the harder it will be to make a release. So who can help me out here? There a few things that need to be fixed up before we can make a release. Can anyone put up their hand to try and fix these? - Get Jenkin/CI back up and working with Git - not essential but give up some confidence that things are still working. - Fix build issues re TLF and move to Git - Look into issue with list selection tesst failing (selection colour difference in bitmaps) - Fix a few missing headers (dead simple!) - Does anyone know what state the components in the experimental project are? I have no idea if any of these are in a releasable state or not. - Make sure all mustella test run on OS, windows and mobile (now that mobile tests work) with flash player 11.1 and 11.7 and AIR 3.7 - What state are the mustella AIR tests in? - Add linux as an officially supported platform for this release. Is there anything else we would like to see in a release? Do we have any committers or non committers with Linux experience who would like to see this happen? There's is probably only a small amount of work required to officially supporting Linux. There are also a number of critical and major JIRA issues that have been raised over the last few months (including some of the issues above) that it would be nice to try and fix before a release. Here's the blocker and critical ones (12 issues): https://issues.apache.org/jira/issues/?filter=12323979 And those plus major ones (158 issues): https://issues.apache.org/jira/issues/?filter=12323978 Is any existing committer or non committer willing to help out and try and fix one or two of the above bugs? Almost all of this issues are unassigned. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Making an new Apache Flex release
I think we have a list of Excluded files so the RAT report ignores files that can't or shouldn't have the license header in them. According to my IDE, those files are listed on lines 1668:1701 in the build.xml (ANT builder). We don't add the license header to binaries such as SWF, because, well.. it breaks them ;P -Nick On Mon, May 6, 2013 at 10:56 AM, Erik de Bruin e...@ixsoftware.nl wrote: If I run: ant main ant source-package ant rat-check I get a rat.report with 5 unapproved licenses: /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/javascript/fabridge/samples/EmptySwf.swf /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/javascript/fabridge/samples/app.swf /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/localFonts.ser /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/macFonts.ser /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/winFonts.ser But these seem to be binaries (.swf) and empty files (.ser), so how (and why) do I add license header to these? What am I doing wrong/not understanding? EdB On Mon, May 6, 2013 at 4:48 PM, Erik de Bruin e...@ixsoftware.nl wrote: Never one to shy away from a daunting task, I've taken on the 'missing headers' issue... I can run 'ant release' successfully (after fixing the JavaCC URL) and get a nice 'rat.report'. I've fixed the headers in the 'experimental/bundles' property files that ant reports. Running 'ant release' takes 32 min. on my machine. Is there a 'shortcut' so I can refresh the source packages etc. and run 'ant rat-check' directly to get a fresh report? EdB On Mon, May 6, 2013 at 5:58 AM, Justin Mclean justinmcl...@mac.com wrote: Hi, Develop and trunk are drifting further apart and we have a fair number of bug fixes, support for newer version of AIR and FP, some new experimental components, so probably about time we started thinking about a release. The longer we leave it the harder it will be to make a release. So who can help me out here? There a few things that need to be fixed up before we can make a release. Can anyone put up their hand to try and fix these? - Get Jenkin/CI back up and working with Git - not essential but give up some confidence that things are still working. - Fix build issues re TLF and move to Git - Look into issue with list selection tesst failing (selection colour difference in bitmaps) - Fix a few missing headers (dead simple!) - Does anyone know what state the components in the experimental project are? I have no idea if any of these are in a releasable state or not. - Make sure all mustella test run on OS, windows and mobile (now that mobile tests work) with flash player 11.1 and 11.7 and AIR 3.7 - What state are the mustella AIR tests in? - Add linux as an officially supported platform for this release. Is there anything else we would like to see in a release? Do we have any committers or non committers with Linux experience who would like to see this happen? There's is probably only a small amount of work required to officially supporting Linux. There are also a number of critical and major JIRA issues that have been raised over the last few months (including some of the issues above) that it would be nice to try and fix before a release. Here's the blocker and critical ones (12 issues): https://issues.apache.org/jira/issues/?filter=12323979 And those plus major ones (158 issues): https://issues.apache.org/jira/issues/?filter=12323978 Is any existing committer or non committer willing to help out and try and fix one or two of the above bugs? Almost all of this issues are unassigned. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Making an new Apache Flex release
Nick is right, but I don't understand why you are getting these files to show up in rat. Are those 3 targets the equivalent of ant release? Otherwise, it isn't a fair test as the release target might otherwise delete those files (since they are binaries and shouldn't be in a source package). I know you want to save time, but let's make sure we are building a correct source package and not skipping an important step. -Alex On 5/6/13 8:16 AM, Nicholas Kwiatkowski nicho...@spoon.as wrote: I think we have a list of Excluded files so the RAT report ignores files that can't or shouldn't have the license header in them. According to my IDE, those files are listed on lines 1668:1701 in the build.xml (ANT builder). We don't add the license header to binaries such as SWF, because, well.. it breaks them ;P -Nick On Mon, May 6, 2013 at 10:56 AM, Erik de Bruin e...@ixsoftware.nl wrote: If I run: ant main ant source-package ant rat-check I get a rat.report with 5 unapproved licenses: /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/javascript/fabr idge/samples/EmptySwf.swf /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/javascript/fabr idge/samples/app.swf /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/localFonts.ser /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/macFonts.ser /Users/erik/Documents/ApacheFlex/git/flex-sdk/temp/frameworks/winFonts.ser But these seem to be binaries (.swf) and empty files (.ser), so how (and why) do I add license header to these? What am I doing wrong/not understanding? EdB On Mon, May 6, 2013 at 4:48 PM, Erik de Bruin e...@ixsoftware.nl wrote: Never one to shy away from a daunting task, I've taken on the 'missing headers' issue... I can run 'ant release' successfully (after fixing the JavaCC URL) and get a nice 'rat.report'. I've fixed the headers in the 'experimental/bundles' property files that ant reports. Running 'ant release' takes 32 min. on my machine. Is there a 'shortcut' so I can refresh the source packages etc. and run 'ant rat-check' directly to get a fresh report? EdB On Mon, May 6, 2013 at 5:58 AM, Justin Mclean justinmcl...@mac.com wrote: Hi, Develop and trunk are drifting further apart and we have a fair number of bug fixes, support for newer version of AIR and FP, some new experimental components, so probably about time we started thinking about a release. The longer we leave it the harder it will be to make a release. So who can help me out here? There a few things that need to be fixed up before we can make a release. Can anyone put up their hand to try and fix these? - Get Jenkin/CI back up and working with Git - not essential but give up some confidence that things are still working. - Fix build issues re TLF and move to Git - Look into issue with list selection tesst failing (selection colour difference in bitmaps) - Fix a few missing headers (dead simple!) - Does anyone know what state the components in the experimental project are? I have no idea if any of these are in a releasable state or not. - Make sure all mustella test run on OS, windows and mobile (now that mobile tests work) with flash player 11.1 and 11.7 and AIR 3.7 - What state are the mustella AIR tests in? - Add linux as an officially supported platform for this release. Is there anything else we would like to see in a release? Do we have any committers or non committers with Linux experience who would like to see this happen? There's is probably only a small amount of work required to officially supporting Linux. There are also a number of critical and major JIRA issues that have been raised over the last few months (including some of the issues above) that it would be nice to try and fix before a release. Here's the blocker and critical ones (12 issues): https://issues.apache.org/jira/issues/?filter=12323979 And those plus major ones (158 issues): https://issues.apache.org/jira/issues/?filter=12323978 Is any existing committer or non committer willing to help out and try and fix one or two of the above bugs? Almost all of this issues are unassigned. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- 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: Making an new Apache Flex release
On 5/5/13 8:58 PM, Justin Mclean justinmcl...@mac.com wrote: Hi, Develop and trunk are drifting further apart and we have a fair number of bug fixes, support for newer version of AIR and FP, some new experimental components, so probably about time we started thinking about a release. The longer we leave it the harder it will be to make a release. So who can help me out here? I was wondering when you were going to come up for air. You and Mark have been on a great run. There a few things that need to be fixed up before we can make a release. Can anyone put up their hand to try and fix these? - Get Jenkin/CI back up and working with Git - not essential but give up some confidence that things are still working. - Fix build issues re TLF and move to Git I thought this was working except for running just the TLF folder? - Look into issue with list selection tesst failing (selection colour difference in bitmaps) - Fix a few missing headers (dead simple!) - Does anyone know what state the components in the experimental project are? I have no idea if any of these are in a releasable state or not. - Make sure all mustella test run on OS, windows and mobile (now that mobile tests work) with flash player 11.1 and 11.7 and AIR 3.7 - What state are the mustella AIR tests in? The apollo folder passed on Mac and Win a while back. You can't run in AIR mode on the other tests as there are bitmap compare failures due to rendering differences involving JPGs. - Add linux as an officially supported platform for this release. Is there anything else we would like to see in a release? I think there are a few bugs I need to resolve. Do we have any committers or non committers with Linux experience who would like to see this happen? There's is probably only a small amount of work required to officially supporting Linux. There are also a number of critical and major JIRA issues that have been raised over the last few months (including some of the issues above) that it would be nice to try and fix before a release. Here's the blocker and critical ones (12 issues): https://issues.apache.org/jira/issues/?filter=12323979 And those plus major ones (158 issues): https://issues.apache.org/jira/issues/?filter=12323978 Is any existing committer or non committer willing to help out and try and fix one or two of the above bugs? Almost all of this issues are unassigned. Thanks, Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Making an new Apache Flex release
Hi, I was wondering when you were going to come up for air. You and Mark have been on a great run. More to come - lots of little date, time and number and formatting issues still to look at. :-) I thought this was working except for running just the TLF folder? It's more broken that that - there several project level builds are also broken if you try to build them on their own. The apollo folder passed on Mac and Win a while back. So we should run this against AIR 3.7 and see if there's any differences? I think there are a few bugs I need to resolve. Any in particular? I listed the blocker and critical ones. Most are probably not easy to solve. I had a look at the TLF hyphen issue a while back and got nowhere. Thanks, Justin
Re: Making an new Apache Flex release
On 5/5/13 10:11 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, I was wondering when you were going to come up for air. You and Mark have been on a great run. More to come - lots of little date, time and number and formatting issues still to look at. :-) I thought this was working except for running just the TLF folder? It's more broken that that - there several project level builds are also broken if you try to build them on their own. The apollo folder passed on Mac and Win a while back. So we should run this against AIR 3.7 and see if there's any differences? If you want. I think there are a few bugs I need to resolve. Any in particular? I listed the blocker and critical ones. Most are probably not easy to solve. I had a look at the TLF hyphen issue a while back and got nowhere. I remember assigning a few to myself and proposed workarounds which I think the bug author approved, so I should probably fix those issues since we now have confirmation what the cause is. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
