You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Gordon Smith <go...@adobe.com> on 2012/11/30 22:09:34 UTC
Falcon SDKSWCTests
@Cyril: Thanks for your help with introducing the compile-config.xml files so that we can more easily make Falcon JUnit tests that compile each SDK SWC.
Now that we have one such test - for compiling framework.swc - passing, would anybody like to work on investigating the status of other tests that compile rpc.swc, mx.swc, spark.swc, etc.? We need to figure out whether the SDK source code needs to change because Falcon is pickier than the old compiler, or whether Falcon has AS bugs that need to be fixed.
- Gordon
RE: Falcon SDKSWCTests
Posted by Gordon Smith <go...@adobe.com>.
I checked in the beginning of some feature tests for Falcon. Here are my checkin notes.
- Gordon
-------
Falcon: Added simple MXML feature tests for <Boolean>, <int>, <uint>, <Number>, <String>, <Class> and generic instance tags such as <Sprite>. They are not yet part of 'ant tests'.
These tests currently create an MXML file, compile it to a SWF with MXMLC, and check that it compiles cleanly. Soon I'll make the SWF run in Flash Player and check that the runtime asserts don't fire, so that we know that codegen is correct.
Such "feature tests" are intended to test one specific feature of MXML all the way through compilation and execution. By contrast, "unit tests" test only a particular class or subsystem, such as testing the MXML lexer to create MXML tokens, or testing how the MXML parser creates particular kinds of MXML nodes. Furthermore, "functional tests" test real-world situations involving multiple features working together. There are three distinct directories for these various kinds of Falcon tests.
Feature tests do not need to be as exhaustive as the unit tests. For example, suppose we have a complete set of parser tests for the <int> tag and know that ultimately an MXMLLiteralNode gets created with an appropriate int value in each case. Then we do not need to have feature tests for things like integer tags with whitspace around the integer text, or hex integer text, or empty int tags, etc. We can just do a few feature tests that make sure that MXMLLiteralNodes with int values codegen integer values in the VM.
-------
-----Original Message-----
From: Michael Schmalle [mailto:apache@teotigraphix.com]
Sent: Friday, November 30, 2012 1:36 PM
To: flex-dev@incubator.apache.org
Subject: RE: Falcon SDKSWCTests
Ok we'll meet again next week.
Mike
Quoting Gordon Smith <go...@adobe.com>:
> OK. I'm working on getting a few feature tests in place that test
> specific features of MXML by compiling to SWF and running in Flash
> Player. I'm starting with the simplest stuff like a <Boolean> tag. I
> started working on this two Fridays ago but that was the day that the
> Haxe discussion ended up taking all day, and then last Friday was a
> holiday.
>
> - Gordon
>
> -----Original Message-----
> From: Michael Schmalle [mailto:apache@teotigraphix.com]
> Sent: Friday, November 30, 2012 1:23 PM
> To: flex-dev@incubator.apache.org
> Subject: RE: Falcon SDKSWCTests
>
> Gordon,
>
> I entered bugs in JIRA for those, it's actually 2 tickets.
>
> I will fix them. The first one is tricky and a bad set of code I was
> scared to change without afterwords running mustella.
>
> I had to reformat my computer and haven't got mustella running again.
> Next week I can get on this. I am burnt out from all this js talk. :)
>
> I could go head and start looking at the other SWCs to I am sure Cyril
> will give them a go as well.
>
> Mike
>
>
> Quoting Gordon Smith <go...@adobe.com>:
>
>> Whoops, the frameworkSWC() compilation test doesn't pass. There are
>> still four warnings:
>>
>> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\fra
>> m
>> ework\src\mx\collections\ListCollectionView.as:1398
>> Warning: variable definition duplicates function parameter: events.
>> var events:Array = updatedItems[j].events;
>> ^
>>
>> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\fra
>> m
>> ework\src\mx\utils\SHA256.as:111
>> Warning: Initializer value 3144134277 for type 'int' must be between
>> -2147483648 and 2147483647 inclusive. An initial value of
>> -1150833019 will be used instead.
>> var h1:int = 0xbb67ae85;
>> ^
>>
>> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\fra
>> m
>> ework\src\mx\utils\SHA256.as:113
>> Warning: Initializer value 2773480762 for type 'int' must be between
>> -2147483648 and 2147483647 inclusive. An initial value of
>> -1521486534 will be used instead.
>> var h3:int = 0xa54ff53a;
>> ^
>>
>> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\fra
>> m
>> ework\src\mx\utils\SHA256.as:115
>> Warning: Initializer value 2600822924 for type 'int' must be between
>> -2147483648 and 2147483647 inclusive. An initial value of
>> -1694144372 will be used instead.
>> var h5:int = 0x9b05688c;
>> ^
>>
>> These are examples of Falcon being pickier (and more correct) than
>> the old compiler.
>>
>> Any volunteers to fix the source code so that this test passes?
>>
>> - Gordon
>>
>> -----Original Message-----
>> From: Gordon Smith [mailto:gosmith@adobe.com]
>> Sent: Friday, November 30, 2012 1:10 PM
>> To: flex-dev@incubator.apache.org
>> Subject: Falcon SDKSWCTests
>>
>> @Cyril: Thanks for your help with introducing the compile-config.xml
>> files so that we can more easily make Falcon JUnit tests that compile
>> each SDK SWC.
>>
>> Now that we have one such test - for compiling framework.swc -
>> passing, would anybody like to work on investigating the status of
>> other tests that compile rpc.swc, mx.swc, spark.swc, etc.? We need to
>> figure out whether the SDK source code needs to change because Falcon
>> is pickier than the old compiler, or whether Falcon has AS bugs that
>> need to be fixed.
>>
>> - Gordon
>>
>>
>
> --
> Michael Schmalle - Teoti Graphix, LLC
> http://www.teotigraphix.com
> http://blog.teotigraphix.com
>
>
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
RE: Falcon SDKSWCTests
Posted by Michael Schmalle <ap...@teotigraphix.com>.
Ok we'll meet again next week.
Mike
Quoting Gordon Smith <go...@adobe.com>:
> OK. I'm working on getting a few feature tests in place that test
> specific features of MXML by compiling to SWF and running in Flash
> Player. I'm starting with the simplest stuff like a <Boolean> tag. I
> started working on this two Fridays ago but that was the day that
> the Haxe discussion ended up taking all day, and then last Friday
> was a holiday.
>
> - Gordon
>
> -----Original Message-----
> From: Michael Schmalle [mailto:apache@teotigraphix.com]
> Sent: Friday, November 30, 2012 1:23 PM
> To: flex-dev@incubator.apache.org
> Subject: RE: Falcon SDKSWCTests
>
> Gordon,
>
> I entered bugs in JIRA for those, it's actually 2 tickets.
>
> I will fix them. The first one is tricky and a bad set of code I was
> scared to change without afterwords running mustella.
>
> I had to reformat my computer and haven't got mustella running again.
> Next week I can get on this. I am burnt out from all this js talk. :)
>
> I could go head and start looking at the other SWCs to I am sure
> Cyril will give them a go as well.
>
> Mike
>
>
> Quoting Gordon Smith <go...@adobe.com>:
>
>> Whoops, the frameworkSWC() compilation test doesn't pass. There are
>> still four warnings:
>>
>> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\fram
>> ework\src\mx\collections\ListCollectionView.as:1398
>> Warning: variable definition duplicates function parameter: events.
>> var events:Array = updatedItems[j].events;
>> ^
>>
>> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\fram
>> ework\src\mx\utils\SHA256.as:111
>> Warning: Initializer value 3144134277 for type 'int' must be between
>> -2147483648 and 2147483647 inclusive. An initial value of
>> -1150833019 will be used instead.
>> var h1:int = 0xbb67ae85;
>> ^
>>
>> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\fram
>> ework\src\mx\utils\SHA256.as:113
>> Warning: Initializer value 2773480762 for type 'int' must be between
>> -2147483648 and 2147483647 inclusive. An initial value of
>> -1521486534 will be used instead.
>> var h3:int = 0xa54ff53a;
>> ^
>>
>> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\fram
>> ework\src\mx\utils\SHA256.as:115
>> Warning: Initializer value 2600822924 for type 'int' must be between
>> -2147483648 and 2147483647 inclusive. An initial value of
>> -1694144372 will be used instead.
>> var h5:int = 0x9b05688c;
>> ^
>>
>> These are examples of Falcon being pickier (and more correct) than the
>> old compiler.
>>
>> Any volunteers to fix the source code so that this test passes?
>>
>> - Gordon
>>
>> -----Original Message-----
>> From: Gordon Smith [mailto:gosmith@adobe.com]
>> Sent: Friday, November 30, 2012 1:10 PM
>> To: flex-dev@incubator.apache.org
>> Subject: Falcon SDKSWCTests
>>
>> @Cyril: Thanks for your help with introducing the compile-config.xml
>> files so that we can more easily make Falcon JUnit tests that compile
>> each SDK SWC.
>>
>> Now that we have one such test - for compiling framework.swc -
>> passing, would anybody like to work on investigating the status of
>> other tests that compile rpc.swc, mx.swc, spark.swc, etc.? We need to
>> figure out whether the SDK source code needs to change because Falcon
>> is pickier than the old compiler, or whether Falcon has AS bugs that
>> need to be fixed.
>>
>> - Gordon
>>
>>
>
> --
> Michael Schmalle - Teoti Graphix, LLC
> http://www.teotigraphix.com
> http://blog.teotigraphix.com
>
>
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
RE: Falcon SDKSWCTests
Posted by Gordon Smith <go...@adobe.com>.
OK. I'm working on getting a few feature tests in place that test specific features of MXML by compiling to SWF and running in Flash Player. I'm starting with the simplest stuff like a <Boolean> tag. I started working on this two Fridays ago but that was the day that the Haxe discussion ended up taking all day, and then last Friday was a holiday.
- Gordon
-----Original Message-----
From: Michael Schmalle [mailto:apache@teotigraphix.com]
Sent: Friday, November 30, 2012 1:23 PM
To: flex-dev@incubator.apache.org
Subject: RE: Falcon SDKSWCTests
Gordon,
I entered bugs in JIRA for those, it's actually 2 tickets.
I will fix them. The first one is tricky and a bad set of code I was scared to change without afterwords running mustella.
I had to reformat my computer and haven't got mustella running again.
Next week I can get on this. I am burnt out from all this js talk. :)
I could go head and start looking at the other SWCs to I am sure Cyril will give them a go as well.
Mike
Quoting Gordon Smith <go...@adobe.com>:
> Whoops, the frameworkSWC() compilation test doesn't pass. There are
> still four warnings:
>
> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\fram
> ework\src\mx\collections\ListCollectionView.as:1398
> Warning: variable definition duplicates function parameter: events.
> var events:Array = updatedItems[j].events;
> ^
>
> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\fram
> ework\src\mx\utils\SHA256.as:111
> Warning: Initializer value 3144134277 for type 'int' must be between
> -2147483648 and 2147483647 inclusive. An initial value of
> -1150833019 will be used instead.
> var h1:int = 0xbb67ae85;
> ^
>
> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\fram
> ework\src\mx\utils\SHA256.as:113
> Warning: Initializer value 2773480762 for type 'int' must be between
> -2147483648 and 2147483647 inclusive. An initial value of
> -1521486534 will be used instead.
> var h3:int = 0xa54ff53a;
> ^
>
> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\fram
> ework\src\mx\utils\SHA256.as:115
> Warning: Initializer value 2600822924 for type 'int' must be between
> -2147483648 and 2147483647 inclusive. An initial value of
> -1694144372 will be used instead.
> var h5:int = 0x9b05688c;
> ^
>
> These are examples of Falcon being pickier (and more correct) than the
> old compiler.
>
> Any volunteers to fix the source code so that this test passes?
>
> - Gordon
>
> -----Original Message-----
> From: Gordon Smith [mailto:gosmith@adobe.com]
> Sent: Friday, November 30, 2012 1:10 PM
> To: flex-dev@incubator.apache.org
> Subject: Falcon SDKSWCTests
>
> @Cyril: Thanks for your help with introducing the compile-config.xml
> files so that we can more easily make Falcon JUnit tests that compile
> each SDK SWC.
>
> Now that we have one such test - for compiling framework.swc -
> passing, would anybody like to work on investigating the status of
> other tests that compile rpc.swc, mx.swc, spark.swc, etc.? We need to
> figure out whether the SDK source code needs to change because Falcon
> is pickier than the old compiler, or whether Falcon has AS bugs that
> need to be fixed.
>
> - Gordon
>
>
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
Re: Falcon SDKSWCTests
Posted by Cyrill Zadra <cy...@gmail.com>.
> I could go head and start looking at the other SWCs to I am sure Cyril will give them a go as well.
I continue to write some more test classes for the css package. So
that every class has at least a few tests. But after that I can work
on that.
Cyrill
On Fri, Nov 30, 2012 at 1:22 PM, Michael Schmalle
<ap...@teotigraphix.com> wrote:
> Gordon,
>
> I entered bugs in JIRA for those, it's actually 2 tickets.
>
> I will fix them. The first one is tricky and a bad set of code I was scared
> to change without afterwords running mustella.
>
> I had to reformat my computer and haven't got mustella running again. Next
> week I can get on this. I am burnt out from all this js talk. :)
>
> I could go head and start looking at the other SWCs to I am sure Cyril will
> give them a go as well.
>
> Mike
>
>
>
> Quoting Gordon Smith <go...@adobe.com>:
>
>> Whoops, the frameworkSWC() compilation test doesn't pass. There are still
>> four warnings:
>>
>>
>> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\framework\src\mx\collections\ListCollectionView.as:1398
>> Warning: variable definition duplicates function parameter: events.
>> var events:Array =
>> updatedItems[j].events;
>> ^
>>
>>
>> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\framework\src\mx\utils\SHA256.as:111
>> Warning: Initializer value 3144134277 for type 'int' must be between
>> -2147483648 and 2147483647 inclusive. An initial value of -1150833019 will
>> be used instead.
>> var h1:int = 0xbb67ae85;
>> ^
>>
>>
>> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\framework\src\mx\utils\SHA256.as:113
>> Warning: Initializer value 2773480762 for type 'int' must be between
>> -2147483648 and 2147483647 inclusive. An initial value of -1521486534 will
>> be used instead.
>> var h3:int = 0xa54ff53a;
>> ^
>>
>>
>> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\framework\src\mx\utils\SHA256.as:115
>> Warning: Initializer value 2600822924 for type 'int' must be between
>> -2147483648 and 2147483647 inclusive. An initial value of -1694144372 will
>> be used instead.
>> var h5:int = 0x9b05688c;
>> ^
>>
>> These are examples of Falcon being pickier (and more correct) than the old
>> compiler.
>>
>> Any volunteers to fix the source code so that this test passes?
>>
>> - Gordon
>>
>> -----Original Message-----
>> From: Gordon Smith [mailto:gosmith@adobe.com]
>> Sent: Friday, November 30, 2012 1:10 PM
>> To: flex-dev@incubator.apache.org
>> Subject: Falcon SDKSWCTests
>>
>> @Cyril: Thanks for your help with introducing the compile-config.xml files
>> so that we can more easily make Falcon JUnit tests that compile each SDK
>> SWC.
>>
>> Now that we have one such test - for compiling framework.swc - passing,
>> would anybody like to work on investigating the status of other tests that
>> compile rpc.swc, mx.swc, spark.swc, etc.? We need to figure out whether the
>> SDK source code needs to change because Falcon is pickier than the old
>> compiler, or whether Falcon has AS bugs that need to be fixed.
>>
>> - Gordon
>>
>>
>
> --
> Michael Schmalle - Teoti Graphix, LLC
> http://www.teotigraphix.com
> http://blog.teotigraphix.com
>
RE: Falcon SDKSWCTests
Posted by Michael Schmalle <ap...@teotigraphix.com>.
Gordon,
I entered bugs in JIRA for those, it's actually 2 tickets.
I will fix them. The first one is tricky and a bad set of code I was
scared to change without afterwords running mustella.
I had to reformat my computer and haven't got mustella running again.
Next week I can get on this. I am burnt out from all this js talk. :)
I could go head and start looking at the other SWCs to I am sure Cyril
will give them a go as well.
Mike
Quoting Gordon Smith <go...@adobe.com>:
> Whoops, the frameworkSWC() compilation test doesn't pass. There are
> still four warnings:
>
> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\framework\src\mx\collections\ListCollectionView.as:1398
> Warning: variable definition duplicates function parameter: events.
> var events:Array = updatedItems[j].events;
> ^
>
> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\framework\src\mx\utils\SHA256.as:111
> Warning: Initializer value 3144134277 for type 'int' must be between
> -2147483648 and 2147483647 inclusive. An initial value of
> -1150833019 will be used instead.
> var h1:int = 0xbb67ae85;
> ^
>
> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\framework\src\mx\utils\SHA256.as:113
> Warning: Initializer value 2773480762 for type 'int' must be between
> -2147483648 and 2147483647 inclusive. An initial value of
> -1521486534 will be used instead.
> var h3:int = 0xa54ff53a;
> ^
>
> D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\framework\src\mx\utils\SHA256.as:115
> Warning: Initializer value 2600822924 for type 'int' must be between
> -2147483648 and 2147483647 inclusive. An initial value of
> -1694144372 will be used instead.
> var h5:int = 0x9b05688c;
> ^
>
> These are examples of Falcon being pickier (and more correct) than
> the old compiler.
>
> Any volunteers to fix the source code so that this test passes?
>
> - Gordon
>
> -----Original Message-----
> From: Gordon Smith [mailto:gosmith@adobe.com]
> Sent: Friday, November 30, 2012 1:10 PM
> To: flex-dev@incubator.apache.org
> Subject: Falcon SDKSWCTests
>
> @Cyril: Thanks for your help with introducing the compile-config.xml
> files so that we can more easily make Falcon JUnit tests that
> compile each SDK SWC.
>
> Now that we have one such test - for compiling framework.swc -
> passing, would anybody like to work on investigating the status of
> other tests that compile rpc.swc, mx.swc, spark.swc, etc.? We need
> to figure out whether the SDK source code needs to change because
> Falcon is pickier than the old compiler, or whether Falcon has AS
> bugs that need to be fixed.
>
> - Gordon
>
>
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
RE: Falcon SDKSWCTests
Posted by Gordon Smith <go...@adobe.com>.
Whoops, the frameworkSWC() compilation test doesn't pass. There are still four warnings:
D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\framework\src\mx\collections\ListCollectionView.as:1398
Warning: variable definition duplicates function parameter: events.
var events:Array = updatedItems[j].events;
^
D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\framework\src\mx\utils\SHA256.as:111
Warning: Initializer value 3144134277 for type 'int' must be between -2147483648 and 2147483647 inclusive. An initial value of -1150833019 will be used instead.
var h1:int = 0xbb67ae85;
^
D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\framework\src\mx\utils\SHA256.as:113
Warning: Initializer value 2773480762 for type 'int' must be between -2147483648 and 2147483647 inclusive. An initial value of -1521486534 will be used instead.
var h3:int = 0xa54ff53a;
^
D:\Apache\incubator\flex\sdk\branches\develop\frameworks\projects\framework\src\mx\utils\SHA256.as:115
Warning: Initializer value 2600822924 for type 'int' must be between -2147483648 and 2147483647 inclusive. An initial value of -1694144372 will be used instead.
var h5:int = 0x9b05688c;
^
These are examples of Falcon being pickier (and more correct) than the old compiler.
Any volunteers to fix the source code so that this test passes?
- Gordon
-----Original Message-----
From: Gordon Smith [mailto:gosmith@adobe.com]
Sent: Friday, November 30, 2012 1:10 PM
To: flex-dev@incubator.apache.org
Subject: Falcon SDKSWCTests
@Cyril: Thanks for your help with introducing the compile-config.xml files so that we can more easily make Falcon JUnit tests that compile each SDK SWC.
Now that we have one such test - for compiling framework.swc - passing, would anybody like to work on investigating the status of other tests that compile rpc.swc, mx.swc, spark.swc, etc.? We need to figure out whether the SDK source code needs to change because Falcon is pickier than the old compiler, or whether Falcon has AS bugs that need to be fixed.
- Gordon
Re: Falcon SDKSWCTests
Posted by Michael Schmalle <ap...@teotigraphix.com>.
Quoting Chema Balsas <jb...@gmail.com>:
> Hi, I've checked the rest of functional tests and created jira issues to
> keep track of them so anyone can check where we stand.
>
> I have fixes for several of them, but want to run mustella tests before
> committing anything. In the meantime, there are several errors that may
> require Gordon's attention.
>
> In advancedgrids, we get a Warning: Metadata was not bound to a definition.
> This comes from something like:
>
> var a:Object = array[cellRow]
> [cellColumn];
I looked at one of these and I would say the code is wrong. Dynamic
member access needs to NOT have a newline. I know the one in the
datagrid was separated by a newline, this needs to be changed.
This is just another example where the Falcon grammar is a lot
stricter, which is GOOD.
Are there other metadata warnings that are all on one line?
> Is it possible that something has changed in the lexical analysis? Although
> just a warning, it looks like this could potentially break lots of code...
>
> Some of the projects (mobiletheme, spark and sparkskins) throw lots
> of "Error:
> Generated byte code contains an operand stack underflow." messages.
>
> In mx, Falcon can't work around embed directives in an mx:Object
> /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/frameworks/projects/mx/src/mx/controls/RichTextEditor.mxml:1053
> Error: Type * cannot be embedded
> <mx:Object
> icon="@Embed('assets/icon_align_left.png')" action="left"/>
>
> In spark, Falcon throws a java error
>
> Error: Internal error in ABC generator subsystem, when generating code for:
> /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/frameworks/projects/spark/src/spark/utils/TextFlowUtil.as:
> java.lang.NullPointerException
> at
> org.apache.flex.compiler.internal.as.codegen.ClassDirectiveProcessor.finishClassDefinition(ClassDirectiveProcessor.java:536)
> at
> org.apache.flex.compiler.internal.as.codegen.GlobalDirectiveProcessor.declareClass(GlobalDirectiveProcessor.java:423)
> at
> org.apache.flex.compiler.internal.as.codegen.DirectiveProcessor.processNode(DirectiveProcessor.java:206)
>
>
> Should we log some of this issues to keep track of them as well?
I would say log anything that is stopping SWCs from being created.
Mike
>
> Cheers,
> Chema
>
> 2012/12/15 Chema Balsas <jb...@gmail.com>
>
>> As a workaround, try adding "-locale=" to the compiler options for the
>>> tests that compile the SWCs, with a TODO that it should not be necessary.
>>
>>
>> That did fix the issue, at least temporarily. I'll add the TODO and a JIRA
>> issue to track this, and go on fixing the rest of errors.
>>
>> Cheers,
>> Chema
>>
>> 2012/12/15 Gordon Smith <go...@adobe.com>
>>
>>> While driving home I realized what's probably causing the resource bundle
>>> problems. SDK SWCs like mx.swc get compiled for "no locale" (-locale=)
>>> because they're not supposed to have any resource bundles inside. The
>>> resource bundles go into other resource bundle SWCs like en_US/mx_rb.swc,
>>> which gets compiled for, say, the en_US locale.
>>>
>>> So the problem may be that Falcon is defaulting to the en_US locale
>>> rather than to no locale. As a workaround, try adding "-locale=" to the
>>> compiler options for the tests that compile the SWCs, with a TODO that it
>>> should not be necessary.
>>>
>>> - Gordon
>>>
>>>
>>> -----Original Message-----
>>> From: Chema Balsas [mailto:jbalsas@gmail.com]
>>> Sent: Friday, December 14, 2012 5:27 PM
>>> To: flex-dev@incubator.apache.org
>>> Subject: Re: Falcon SDKSWCTests
>>>
>>> >
>>> > I'd like to fix these since they shouldn't be hard to fix.
>>>
>>>
>>> Fix them we will, then ;)
>>>
>>> Somehow <compc> is finding either the source code for the bundles on the
>>> > source path, or the compiled code for the bundles on the library path.
>>>
>>>
>>> This may have something to do with "addApplicationParentToSourcePath()"
>>> inside ResourceBundlePath in <compc>... I assume Falcon isn't doing this,
>>> but is it going to? It's easy to modify the compile-config files to get
>>> these, and it does show the dependencies more explicitly. What do
>>> you think?
>>>
>>> Cheers,
>>> Chema
>>>
>>> 2012/12/15 Gordon Smith <go...@adobe.com>
>>>
>>> > I'm not sure what's going on with the resource bundle issue, but I
>>> > don't think it's an example of Falcon being pickier. Somehow <compc>
>>> > is finding either the source code for the bundles on the source path,
>>> > or the compiled code for the bundles on the library path.
>>> >
>>> > > I see several "duplicated variables" warnings ahead. Do we want to
>>> > > fix
>>> > them or ignore them?
>>> >
>>> > I'd like to fix these since they shouldn't be hard to fix. (The
>>> > problem with fixing the previous problem with Version.as is that Alex
>>> > would kill us if we removed all the includes of Version.as.)
>>> >
>>> > - Gordon
>>> >
>>> >
>>> > -----Original Message-----
>>> > From: Chema Balsas [mailto:jbalsas@gmail.com]
>>> > Sent: Friday, December 14, 2012 5:05 PM
>>> > To: flex-dev@incubator.apache.org
>>> > Subject: Re: Falcon SDKSWCTests
>>> >
>>> > Also, I've already fixed some warnings, but I'd like to ask before
>>> > going and fix some more. We've already set to ignore
>>> > DuplicateQNameInSourcePathProblem. Should we stick to ignore warnings,
>>> > or try and fix them to end up with a cleaner/safer sdk code?
>>> >
>>> > For instance, I see several "duplicated variables" warnings ahead. Do
>>> > we want to fix them or ignore them?
>>> >
>>> > Cheers,
>>> > Chema
>>> >
>>> > 2012/12/15 Chema Balsas <jb...@gmail.com>
>>> >
>>> > > That's usually a configuration problem. Does the -source-path
>>> > > include
>>> > >> bundles/{locale}, and is -locale set to en_US ?
>>> > >
>>> > >
>>> > > You're right, that is the case. I was setting the locale, but the
>>> > > bundles folder is not in the source-path. How's that compc doesn't
>>> > > complain? Is this another place where Falcon is pickier?
>>> > >
>>> > > Take the mx project. Other than its bundles, it uses some from
>>> > > framework, so we need to add both folders to the source-path in
>>> > > compile-config.xml where none was used before. Is this the expected
>>> > > behavior or am I missing something?
>>> > >
>>> > > Cheers,
>>> > > Chema
>>> > >
>>> > > 2012/12/14 Gordon Smith <go...@adobe.com>
>>> > >
>>> > >> That's usually a configuration problem. Does the -source-path
>>> > >> include bundles/{locale}, and is -locale set to en_US ?
>>> > >>
>>> > >> - Gordon
>>> > >>
>>> > >> -----Original Message-----
>>> > >> From: Chema Balsas [mailto:jbalsas@gmail.com]
>>> > >> Sent: Friday, December 14, 2012 1:23 PM
>>> > >> To: flex-dev@incubator.apache.org
>>> > >> Subject: Re: Falcon SDKSWCTests
>>> > >>
>>> > >> Right now there's one recurring error when trying to compile almost
>>> > >> every missing swc.
>>> > >>
>>> > >> Error: Unable to resolve resource bundle 'core'
>>> > >> >
>>> > >> > [ResourceBundle("core")]
>>> > >> >
>>> > >>
>>> > >> This happens for several bundles. I've been trying to figure out
>>> > >> the reason, but this is still beyond my reach. It looks like Falcon
>>> > >> never does resolve these dependencies (but I'm not really sure what
>>> > >> I'm looking at here...). Gordon, do you think this is a
>>> > >> configuration problem and have any idea on how this could be
>>> > >> addressed? Or is maybe something missing in Falcon?
>>> > >>
>>> > >> Also, currently we're only checking the compile targets. Should we
>>> > >> also check the bundle ones?
>>> > >>
>>> > >> Cheers,
>>> > >> Chema
>>> > >>
>>> > >>
>>> > >> 2012/12/11 Chema Balsas <jb...@gmail.com>
>>> > >>
>>> > >> > Nice! That fixed other 5 tests for free and made other 2 easy to
>>> fix.
>>> > >> >
>>> > >> > I've committed the changes to the sdk and sdkswctests. We now
>>> > >> > have
>>> > >> > 18 out of 29 tests passing. I'll try to start looking over the
>>> > >> > hard ones over the week.
>>> > >> >
>>> > >> > Cheers,
>>> > >> > Chema
>>> > >> >
>>> > >> >
>>> > >> > 2012/12/10 Gordon Smith <go...@adobe.com>
>>> > >> >
>>> > >> >> > I've just commited some changes into rpc, authoringsupport,
>>> > >> >> > framework
>>> > >> >> and mobilecomponents so that they compile properly in falcon.
>>> > >> >> I've enabled those tests and now we have 11 out of 29 working.
>>> > >> >>
>>> > >> >> Nice progress!
>>> > >> >>
>>> > >> >> > Warning: mx.core.Version is defined by multiple files:
>>> > >> >>
>>> > >> >> This is an example where Falcon is pickier but since it's just a
>>> > >> >> warning I don't think we should try to fix it. Let's change the
>>> > >> >> tests to ignore this warning. You should be able to do this by
>>> > >> >> changing the SWC tests to run with the additional command-line
>>> > >> >> argument
>>> > >> -ignore-problems=... .
>>> > >> >>
>>> > >> >> - Gordon
>>> > >> >>
>>> > >> >>
>>> > >> >> -----Original Message-----
>>> > >> >> From: Chema Balsas [mailto:jbalsas@gmail.com]
>>> > >> >> Sent: Monday, December 10, 2012 2:20 PM
>>> > >> >> To: flex-dev@incubator.apache.org
>>> > >> >> Subject: Re: Falcon SDKSWCTests
>>> > >> >>
>>> > >> >> Hi,
>>> > >> >>
>>> > >> >> I've just commited some changes into rpc, authoringsupport,
>>> > >> >> framework and mobilecomponents so that they compile properly in
>>> > >> >> falcon. I've enabled those tests and now we have 11 out of 29
>>> > working.
>>> > >> >>
>>> > >> >> @Gordon One recurrent issue for other projects is
>>> > >> >>
>>> > >> >> Warning: mx.core.Version is defined by multiple files:
>>> > >> >> > /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/
>>> > >> >> > fr ame wor ks/projects/automation_agent/src/mx/core/Version.as
>>> > >> >>
>>> > >> >>
>>> > >> >> Is this something Falcon will take care of, or do we need to
>>> > >> >> figure out anoter way around like in the config files for example?
>>> > >> >>
>>> > >> >> Cheers,
>>> > >> >> Chema
>>> > >> >>
>>> > >> >> 2012/12/7 Chema Balsas <jb...@gmail.com>
>>> > >> >>
>>> > >> >> > Following with this, I've checked and in CompcTask, an
>>> > >> >> > include-config
>>> > >> >> > (ifSpec) is added with createElem instead of with
>>> > >> >> > createElemAllowAppend. Is there a reason for this? I've
>>> > >> >> > checked and changing it and adding 'append="true"' in the ant
>>> > >> >> > task to the include-file tag does fix this I don't know if
>>> > >> >> > there's something else
>>> > >> >> to take into account though.
>>> > >> >> >
>>> > >> >> > We won't be using it for now, but do you think we should try
>>> > >> >> > to fix this, or at least document it somewhere?
>>> > >> >> >
>>> > >> >> >
>>> > >> >> > 2012/12/7 Chema Balsas <jb...@gmail.com>
>>> > >> >> >
>>> > >> >> >> Yes, I already have it and it's working. I've accessed my
>>> > >> >> >> account through ssh to verify it and I've also checked, and I
>>> > >> >> >> have access to the apache commiters repository, but not ours.
>>> > >> >> >>
>>> > >> >> >>
>>> > >> >> >> 2012/12/7 Alex Harui <ah...@adobe.com>
>>> > >> >> >>
>>> > >> >> >>>
>>> > >> >> >>>
>>> > >> >> >>>
>>> > >> >> >>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
>>> > >> >> >>>
>>> > >> >> >>> > Oh, that explains it then... and how unfortunate
>>> > >> >> >>> >
>>> > >> >> >>> > From Gordon's comment, I assumed we were going to stop
>>> > >> >> >>> > including the version.properties file (at least for now).
>>> > >> >> >>> > That was exactly what I was about to commit, but it seems
>>> > >> >> >>> > I still don't have access to the svn repository.
>>> > >> >> >>> >
>>> > >> >> >>> Did you get an email asking about what you want your apache
>>> > >> >> >>> id to
>>> > >> be?
>>> > >> >> >>>
>>> > >> >> >>> --
>>> > >> >> >>> Alex Harui
>>> > >> >> >>> Flex SDK Team
>>> > >> >> >>> Adobe Systems, Inc.
>>> > >> >> >>> http://blogs.adobe.com/aharui
>>> > >> >> >>>
>>> > >> >> >>>
>>> > >> >> >>
>>> > >> >> >
>>> > >> >>
>>> > >> >
>>> > >> >
>>> > >>
>>> > >
>>> > >
>>> >
>>>
>>
>>
>
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
Hi, I've checked the rest of functional tests and created jira issues to
keep track of them so anyone can check where we stand.
I have fixes for several of them, but want to run mustella tests before
committing anything. In the meantime, there are several errors that may
require Gordon's attention.
In advancedgrids, we get a Warning: Metadata was not bound to a definition.
This comes from something like:
var a:Object = array[cellRow]
[cellColumn];
Is it possible that something has changed in the lexical analysis? Although
just a warning, it looks like this could potentially break lots of code...
Some of the projects (mobiletheme, spark and sparkskins) throw lots of "Error:
Generated byte code contains an operand stack underflow." messages.
In mx, Falcon can't work around embed directives in an mx:Object
/Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/frameworks/projects/mx/src/mx/controls/RichTextEditor.mxml:1053
Error: Type * cannot be embedded
<mx:Object
icon="@Embed('assets/icon_align_left.png')" action="left"/>
In spark, Falcon throws a java error
Error: Internal error in ABC generator subsystem, when generating code for:
/Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/frameworks/projects/spark/src/spark/utils/TextFlowUtil.as:
java.lang.NullPointerException
at
org.apache.flex.compiler.internal.as.codegen.ClassDirectiveProcessor.finishClassDefinition(ClassDirectiveProcessor.java:536)
at
org.apache.flex.compiler.internal.as.codegen.GlobalDirectiveProcessor.declareClass(GlobalDirectiveProcessor.java:423)
at
org.apache.flex.compiler.internal.as.codegen.DirectiveProcessor.processNode(DirectiveProcessor.java:206)
Should we log some of this issues to keep track of them as well?
Cheers,
Chema
2012/12/15 Chema Balsas <jb...@gmail.com>
> As a workaround, try adding "-locale=" to the compiler options for the
>> tests that compile the SWCs, with a TODO that it should not be necessary.
>
>
> That did fix the issue, at least temporarily. I'll add the TODO and a JIRA
> issue to track this, and go on fixing the rest of errors.
>
> Cheers,
> Chema
>
> 2012/12/15 Gordon Smith <go...@adobe.com>
>
>> While driving home I realized what's probably causing the resource bundle
>> problems. SDK SWCs like mx.swc get compiled for "no locale" (-locale=)
>> because they're not supposed to have any resource bundles inside. The
>> resource bundles go into other resource bundle SWCs like en_US/mx_rb.swc,
>> which gets compiled for, say, the en_US locale.
>>
>> So the problem may be that Falcon is defaulting to the en_US locale
>> rather than to no locale. As a workaround, try adding "-locale=" to the
>> compiler options for the tests that compile the SWCs, with a TODO that it
>> should not be necessary.
>>
>> - Gordon
>>
>>
>> -----Original Message-----
>> From: Chema Balsas [mailto:jbalsas@gmail.com]
>> Sent: Friday, December 14, 2012 5:27 PM
>> To: flex-dev@incubator.apache.org
>> Subject: Re: Falcon SDKSWCTests
>>
>> >
>> > I'd like to fix these since they shouldn't be hard to fix.
>>
>>
>> Fix them we will, then ;)
>>
>> Somehow <compc> is finding either the source code for the bundles on the
>> > source path, or the compiled code for the bundles on the library path.
>>
>>
>> This may have something to do with "addApplicationParentToSourcePath()"
>> inside ResourceBundlePath in <compc>... I assume Falcon isn't doing this,
>> but is it going to? It's easy to modify the compile-config files to get
>> these, and it does show the dependencies more explicitly. What do you think?
>>
>> Cheers,
>> Chema
>>
>> 2012/12/15 Gordon Smith <go...@adobe.com>
>>
>> > I'm not sure what's going on with the resource bundle issue, but I
>> > don't think it's an example of Falcon being pickier. Somehow <compc>
>> > is finding either the source code for the bundles on the source path,
>> > or the compiled code for the bundles on the library path.
>> >
>> > > I see several "duplicated variables" warnings ahead. Do we want to
>> > > fix
>> > them or ignore them?
>> >
>> > I'd like to fix these since they shouldn't be hard to fix. (The
>> > problem with fixing the previous problem with Version.as is that Alex
>> > would kill us if we removed all the includes of Version.as.)
>> >
>> > - Gordon
>> >
>> >
>> > -----Original Message-----
>> > From: Chema Balsas [mailto:jbalsas@gmail.com]
>> > Sent: Friday, December 14, 2012 5:05 PM
>> > To: flex-dev@incubator.apache.org
>> > Subject: Re: Falcon SDKSWCTests
>> >
>> > Also, I've already fixed some warnings, but I'd like to ask before
>> > going and fix some more. We've already set to ignore
>> > DuplicateQNameInSourcePathProblem. Should we stick to ignore warnings,
>> > or try and fix them to end up with a cleaner/safer sdk code?
>> >
>> > For instance, I see several "duplicated variables" warnings ahead. Do
>> > we want to fix them or ignore them?
>> >
>> > Cheers,
>> > Chema
>> >
>> > 2012/12/15 Chema Balsas <jb...@gmail.com>
>> >
>> > > That's usually a configuration problem. Does the -source-path
>> > > include
>> > >> bundles/{locale}, and is -locale set to en_US ?
>> > >
>> > >
>> > > You're right, that is the case. I was setting the locale, but the
>> > > bundles folder is not in the source-path. How's that compc doesn't
>> > > complain? Is this another place where Falcon is pickier?
>> > >
>> > > Take the mx project. Other than its bundles, it uses some from
>> > > framework, so we need to add both folders to the source-path in
>> > > compile-config.xml where none was used before. Is this the expected
>> > > behavior or am I missing something?
>> > >
>> > > Cheers,
>> > > Chema
>> > >
>> > > 2012/12/14 Gordon Smith <go...@adobe.com>
>> > >
>> > >> That's usually a configuration problem. Does the -source-path
>> > >> include bundles/{locale}, and is -locale set to en_US ?
>> > >>
>> > >> - Gordon
>> > >>
>> > >> -----Original Message-----
>> > >> From: Chema Balsas [mailto:jbalsas@gmail.com]
>> > >> Sent: Friday, December 14, 2012 1:23 PM
>> > >> To: flex-dev@incubator.apache.org
>> > >> Subject: Re: Falcon SDKSWCTests
>> > >>
>> > >> Right now there's one recurring error when trying to compile almost
>> > >> every missing swc.
>> > >>
>> > >> Error: Unable to resolve resource bundle 'core'
>> > >> >
>> > >> > [ResourceBundle("core")]
>> > >> >
>> > >>
>> > >> This happens for several bundles. I've been trying to figure out
>> > >> the reason, but this is still beyond my reach. It looks like Falcon
>> > >> never does resolve these dependencies (but I'm not really sure what
>> > >> I'm looking at here...). Gordon, do you think this is a
>> > >> configuration problem and have any idea on how this could be
>> > >> addressed? Or is maybe something missing in Falcon?
>> > >>
>> > >> Also, currently we're only checking the compile targets. Should we
>> > >> also check the bundle ones?
>> > >>
>> > >> Cheers,
>> > >> Chema
>> > >>
>> > >>
>> > >> 2012/12/11 Chema Balsas <jb...@gmail.com>
>> > >>
>> > >> > Nice! That fixed other 5 tests for free and made other 2 easy to
>> fix.
>> > >> >
>> > >> > I've committed the changes to the sdk and sdkswctests. We now
>> > >> > have
>> > >> > 18 out of 29 tests passing. I'll try to start looking over the
>> > >> > hard ones over the week.
>> > >> >
>> > >> > Cheers,
>> > >> > Chema
>> > >> >
>> > >> >
>> > >> > 2012/12/10 Gordon Smith <go...@adobe.com>
>> > >> >
>> > >> >> > I've just commited some changes into rpc, authoringsupport,
>> > >> >> > framework
>> > >> >> and mobilecomponents so that they compile properly in falcon.
>> > >> >> I've enabled those tests and now we have 11 out of 29 working.
>> > >> >>
>> > >> >> Nice progress!
>> > >> >>
>> > >> >> > Warning: mx.core.Version is defined by multiple files:
>> > >> >>
>> > >> >> This is an example where Falcon is pickier but since it's just a
>> > >> >> warning I don't think we should try to fix it. Let's change the
>> > >> >> tests to ignore this warning. You should be able to do this by
>> > >> >> changing the SWC tests to run with the additional command-line
>> > >> >> argument
>> > >> -ignore-problems=... .
>> > >> >>
>> > >> >> - Gordon
>> > >> >>
>> > >> >>
>> > >> >> -----Original Message-----
>> > >> >> From: Chema Balsas [mailto:jbalsas@gmail.com]
>> > >> >> Sent: Monday, December 10, 2012 2:20 PM
>> > >> >> To: flex-dev@incubator.apache.org
>> > >> >> Subject: Re: Falcon SDKSWCTests
>> > >> >>
>> > >> >> Hi,
>> > >> >>
>> > >> >> I've just commited some changes into rpc, authoringsupport,
>> > >> >> framework and mobilecomponents so that they compile properly in
>> > >> >> falcon. I've enabled those tests and now we have 11 out of 29
>> > working.
>> > >> >>
>> > >> >> @Gordon One recurrent issue for other projects is
>> > >> >>
>> > >> >> Warning: mx.core.Version is defined by multiple files:
>> > >> >> > /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/
>> > >> >> > fr ame wor ks/projects/automation_agent/src/mx/core/Version.as
>> > >> >>
>> > >> >>
>> > >> >> Is this something Falcon will take care of, or do we need to
>> > >> >> figure out anoter way around like in the config files for example?
>> > >> >>
>> > >> >> Cheers,
>> > >> >> Chema
>> > >> >>
>> > >> >> 2012/12/7 Chema Balsas <jb...@gmail.com>
>> > >> >>
>> > >> >> > Following with this, I've checked and in CompcTask, an
>> > >> >> > include-config
>> > >> >> > (ifSpec) is added with createElem instead of with
>> > >> >> > createElemAllowAppend. Is there a reason for this? I've
>> > >> >> > checked and changing it and adding 'append="true"' in the ant
>> > >> >> > task to the include-file tag does fix this I don't know if
>> > >> >> > there's something else
>> > >> >> to take into account though.
>> > >> >> >
>> > >> >> > We won't be using it for now, but do you think we should try
>> > >> >> > to fix this, or at least document it somewhere?
>> > >> >> >
>> > >> >> >
>> > >> >> > 2012/12/7 Chema Balsas <jb...@gmail.com>
>> > >> >> >
>> > >> >> >> Yes, I already have it and it's working. I've accessed my
>> > >> >> >> account through ssh to verify it and I've also checked, and I
>> > >> >> >> have access to the apache commiters repository, but not ours.
>> > >> >> >>
>> > >> >> >>
>> > >> >> >> 2012/12/7 Alex Harui <ah...@adobe.com>
>> > >> >> >>
>> > >> >> >>>
>> > >> >> >>>
>> > >> >> >>>
>> > >> >> >>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
>> > >> >> >>>
>> > >> >> >>> > Oh, that explains it then... and how unfortunate
>> > >> >> >>> >
>> > >> >> >>> > From Gordon's comment, I assumed we were going to stop
>> > >> >> >>> > including the version.properties file (at least for now).
>> > >> >> >>> > That was exactly what I was about to commit, but it seems
>> > >> >> >>> > I still don't have access to the svn repository.
>> > >> >> >>> >
>> > >> >> >>> Did you get an email asking about what you want your apache
>> > >> >> >>> id to
>> > >> be?
>> > >> >> >>>
>> > >> >> >>> --
>> > >> >> >>> Alex Harui
>> > >> >> >>> Flex SDK Team
>> > >> >> >>> Adobe Systems, Inc.
>> > >> >> >>> http://blogs.adobe.com/aharui
>> > >> >> >>>
>> > >> >> >>>
>> > >> >> >>
>> > >> >> >
>> > >> >>
>> > >> >
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>
>
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
>
> As a workaround, try adding "-locale=" to the compiler options for the
> tests that compile the SWCs, with a TODO that it should not be necessary.
That did fix the issue, at least temporarily. I'll add the TODO and a JIRA
issue to track this, and go on fixing the rest of errors.
Cheers,
Chema
2012/12/15 Gordon Smith <go...@adobe.com>
> While driving home I realized what's probably causing the resource bundle
> problems. SDK SWCs like mx.swc get compiled for "no locale" (-locale=)
> because they're not supposed to have any resource bundles inside. The
> resource bundles go into other resource bundle SWCs like en_US/mx_rb.swc,
> which gets compiled for, say, the en_US locale.
>
> So the problem may be that Falcon is defaulting to the en_US locale rather
> than to no locale. As a workaround, try adding "-locale=" to the compiler
> options for the tests that compile the SWCs, with a TODO that it should not
> be necessary.
>
> - Gordon
>
>
> -----Original Message-----
> From: Chema Balsas [mailto:jbalsas@gmail.com]
> Sent: Friday, December 14, 2012 5:27 PM
> To: flex-dev@incubator.apache.org
> Subject: Re: Falcon SDKSWCTests
>
> >
> > I'd like to fix these since they shouldn't be hard to fix.
>
>
> Fix them we will, then ;)
>
> Somehow <compc> is finding either the source code for the bundles on the
> > source path, or the compiled code for the bundles on the library path.
>
>
> This may have something to do with "addApplicationParentToSourcePath()"
> inside ResourceBundlePath in <compc>... I assume Falcon isn't doing this,
> but is it going to? It's easy to modify the compile-config files to get
> these, and it does show the dependencies more explicitly. What do you think?
>
> Cheers,
> Chema
>
> 2012/12/15 Gordon Smith <go...@adobe.com>
>
> > I'm not sure what's going on with the resource bundle issue, but I
> > don't think it's an example of Falcon being pickier. Somehow <compc>
> > is finding either the source code for the bundles on the source path,
> > or the compiled code for the bundles on the library path.
> >
> > > I see several "duplicated variables" warnings ahead. Do we want to
> > > fix
> > them or ignore them?
> >
> > I'd like to fix these since they shouldn't be hard to fix. (The
> > problem with fixing the previous problem with Version.as is that Alex
> > would kill us if we removed all the includes of Version.as.)
> >
> > - Gordon
> >
> >
> > -----Original Message-----
> > From: Chema Balsas [mailto:jbalsas@gmail.com]
> > Sent: Friday, December 14, 2012 5:05 PM
> > To: flex-dev@incubator.apache.org
> > Subject: Re: Falcon SDKSWCTests
> >
> > Also, I've already fixed some warnings, but I'd like to ask before
> > going and fix some more. We've already set to ignore
> > DuplicateQNameInSourcePathProblem. Should we stick to ignore warnings,
> > or try and fix them to end up with a cleaner/safer sdk code?
> >
> > For instance, I see several "duplicated variables" warnings ahead. Do
> > we want to fix them or ignore them?
> >
> > Cheers,
> > Chema
> >
> > 2012/12/15 Chema Balsas <jb...@gmail.com>
> >
> > > That's usually a configuration problem. Does the -source-path
> > > include
> > >> bundles/{locale}, and is -locale set to en_US ?
> > >
> > >
> > > You're right, that is the case. I was setting the locale, but the
> > > bundles folder is not in the source-path. How's that compc doesn't
> > > complain? Is this another place where Falcon is pickier?
> > >
> > > Take the mx project. Other than its bundles, it uses some from
> > > framework, so we need to add both folders to the source-path in
> > > compile-config.xml where none was used before. Is this the expected
> > > behavior or am I missing something?
> > >
> > > Cheers,
> > > Chema
> > >
> > > 2012/12/14 Gordon Smith <go...@adobe.com>
> > >
> > >> That's usually a configuration problem. Does the -source-path
> > >> include bundles/{locale}, and is -locale set to en_US ?
> > >>
> > >> - Gordon
> > >>
> > >> -----Original Message-----
> > >> From: Chema Balsas [mailto:jbalsas@gmail.com]
> > >> Sent: Friday, December 14, 2012 1:23 PM
> > >> To: flex-dev@incubator.apache.org
> > >> Subject: Re: Falcon SDKSWCTests
> > >>
> > >> Right now there's one recurring error when trying to compile almost
> > >> every missing swc.
> > >>
> > >> Error: Unable to resolve resource bundle 'core'
> > >> >
> > >> > [ResourceBundle("core")]
> > >> >
> > >>
> > >> This happens for several bundles. I've been trying to figure out
> > >> the reason, but this is still beyond my reach. It looks like Falcon
> > >> never does resolve these dependencies (but I'm not really sure what
> > >> I'm looking at here...). Gordon, do you think this is a
> > >> configuration problem and have any idea on how this could be
> > >> addressed? Or is maybe something missing in Falcon?
> > >>
> > >> Also, currently we're only checking the compile targets. Should we
> > >> also check the bundle ones?
> > >>
> > >> Cheers,
> > >> Chema
> > >>
> > >>
> > >> 2012/12/11 Chema Balsas <jb...@gmail.com>
> > >>
> > >> > Nice! That fixed other 5 tests for free and made other 2 easy to
> fix.
> > >> >
> > >> > I've committed the changes to the sdk and sdkswctests. We now
> > >> > have
> > >> > 18 out of 29 tests passing. I'll try to start looking over the
> > >> > hard ones over the week.
> > >> >
> > >> > Cheers,
> > >> > Chema
> > >> >
> > >> >
> > >> > 2012/12/10 Gordon Smith <go...@adobe.com>
> > >> >
> > >> >> > I've just commited some changes into rpc, authoringsupport,
> > >> >> > framework
> > >> >> and mobilecomponents so that they compile properly in falcon.
> > >> >> I've enabled those tests and now we have 11 out of 29 working.
> > >> >>
> > >> >> Nice progress!
> > >> >>
> > >> >> > Warning: mx.core.Version is defined by multiple files:
> > >> >>
> > >> >> This is an example where Falcon is pickier but since it's just a
> > >> >> warning I don't think we should try to fix it. Let's change the
> > >> >> tests to ignore this warning. You should be able to do this by
> > >> >> changing the SWC tests to run with the additional command-line
> > >> >> argument
> > >> -ignore-problems=... .
> > >> >>
> > >> >> - Gordon
> > >> >>
> > >> >>
> > >> >> -----Original Message-----
> > >> >> From: Chema Balsas [mailto:jbalsas@gmail.com]
> > >> >> Sent: Monday, December 10, 2012 2:20 PM
> > >> >> To: flex-dev@incubator.apache.org
> > >> >> Subject: Re: Falcon SDKSWCTests
> > >> >>
> > >> >> Hi,
> > >> >>
> > >> >> I've just commited some changes into rpc, authoringsupport,
> > >> >> framework and mobilecomponents so that they compile properly in
> > >> >> falcon. I've enabled those tests and now we have 11 out of 29
> > working.
> > >> >>
> > >> >> @Gordon One recurrent issue for other projects is
> > >> >>
> > >> >> Warning: mx.core.Version is defined by multiple files:
> > >> >> > /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/
> > >> >> > fr ame wor ks/projects/automation_agent/src/mx/core/Version.as
> > >> >>
> > >> >>
> > >> >> Is this something Falcon will take care of, or do we need to
> > >> >> figure out anoter way around like in the config files for example?
> > >> >>
> > >> >> Cheers,
> > >> >> Chema
> > >> >>
> > >> >> 2012/12/7 Chema Balsas <jb...@gmail.com>
> > >> >>
> > >> >> > Following with this, I've checked and in CompcTask, an
> > >> >> > include-config
> > >> >> > (ifSpec) is added with createElem instead of with
> > >> >> > createElemAllowAppend. Is there a reason for this? I've
> > >> >> > checked and changing it and adding 'append="true"' in the ant
> > >> >> > task to the include-file tag does fix this I don't know if
> > >> >> > there's something else
> > >> >> to take into account though.
> > >> >> >
> > >> >> > We won't be using it for now, but do you think we should try
> > >> >> > to fix this, or at least document it somewhere?
> > >> >> >
> > >> >> >
> > >> >> > 2012/12/7 Chema Balsas <jb...@gmail.com>
> > >> >> >
> > >> >> >> Yes, I already have it and it's working. I've accessed my
> > >> >> >> account through ssh to verify it and I've also checked, and I
> > >> >> >> have access to the apache commiters repository, but not ours.
> > >> >> >>
> > >> >> >>
> > >> >> >> 2012/12/7 Alex Harui <ah...@adobe.com>
> > >> >> >>
> > >> >> >>>
> > >> >> >>>
> > >> >> >>>
> > >> >> >>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
> > >> >> >>>
> > >> >> >>> > Oh, that explains it then... and how unfortunate
> > >> >> >>> >
> > >> >> >>> > From Gordon's comment, I assumed we were going to stop
> > >> >> >>> > including the version.properties file (at least for now).
> > >> >> >>> > That was exactly what I was about to commit, but it seems
> > >> >> >>> > I still don't have access to the svn repository.
> > >> >> >>> >
> > >> >> >>> Did you get an email asking about what you want your apache
> > >> >> >>> id to
> > >> be?
> > >> >> >>>
> > >> >> >>> --
> > >> >> >>> Alex Harui
> > >> >> >>> Flex SDK Team
> > >> >> >>> Adobe Systems, Inc.
> > >> >> >>> http://blogs.adobe.com/aharui
> > >> >> >>>
> > >> >> >>>
> > >> >> >>
> > >> >> >
> > >> >>
> > >> >
> > >> >
> > >>
> > >
> > >
> >
>
RE: Falcon SDKSWCTests
Posted by Gordon Smith <go...@adobe.com>.
While driving home I realized what's probably causing the resource bundle problems. SDK SWCs like mx.swc get compiled for "no locale" (-locale=) because they're not supposed to have any resource bundles inside. The resource bundles go into other resource bundle SWCs like en_US/mx_rb.swc, which gets compiled for, say, the en_US locale.
So the problem may be that Falcon is defaulting to the en_US locale rather than to no locale. As a workaround, try adding "-locale=" to the compiler options for the tests that compile the SWCs, with a TODO that it should not be necessary.
- Gordon
-----Original Message-----
From: Chema Balsas [mailto:jbalsas@gmail.com]
Sent: Friday, December 14, 2012 5:27 PM
To: flex-dev@incubator.apache.org
Subject: Re: Falcon SDKSWCTests
>
> I'd like to fix these since they shouldn't be hard to fix.
Fix them we will, then ;)
Somehow <compc> is finding either the source code for the bundles on the
> source path, or the compiled code for the bundles on the library path.
This may have something to do with "addApplicationParentToSourcePath()"
inside ResourceBundlePath in <compc>... I assume Falcon isn't doing this, but is it going to? It's easy to modify the compile-config files to get these, and it does show the dependencies more explicitly. What do you think?
Cheers,
Chema
2012/12/15 Gordon Smith <go...@adobe.com>
> I'm not sure what's going on with the resource bundle issue, but I
> don't think it's an example of Falcon being pickier. Somehow <compc>
> is finding either the source code for the bundles on the source path,
> or the compiled code for the bundles on the library path.
>
> > I see several "duplicated variables" warnings ahead. Do we want to
> > fix
> them or ignore them?
>
> I'd like to fix these since they shouldn't be hard to fix. (The
> problem with fixing the previous problem with Version.as is that Alex
> would kill us if we removed all the includes of Version.as.)
>
> - Gordon
>
>
> -----Original Message-----
> From: Chema Balsas [mailto:jbalsas@gmail.com]
> Sent: Friday, December 14, 2012 5:05 PM
> To: flex-dev@incubator.apache.org
> Subject: Re: Falcon SDKSWCTests
>
> Also, I've already fixed some warnings, but I'd like to ask before
> going and fix some more. We've already set to ignore
> DuplicateQNameInSourcePathProblem. Should we stick to ignore warnings,
> or try and fix them to end up with a cleaner/safer sdk code?
>
> For instance, I see several "duplicated variables" warnings ahead. Do
> we want to fix them or ignore them?
>
> Cheers,
> Chema
>
> 2012/12/15 Chema Balsas <jb...@gmail.com>
>
> > That's usually a configuration problem. Does the -source-path
> > include
> >> bundles/{locale}, and is -locale set to en_US ?
> >
> >
> > You're right, that is the case. I was setting the locale, but the
> > bundles folder is not in the source-path. How's that compc doesn't
> > complain? Is this another place where Falcon is pickier?
> >
> > Take the mx project. Other than its bundles, it uses some from
> > framework, so we need to add both folders to the source-path in
> > compile-config.xml where none was used before. Is this the expected
> > behavior or am I missing something?
> >
> > Cheers,
> > Chema
> >
> > 2012/12/14 Gordon Smith <go...@adobe.com>
> >
> >> That's usually a configuration problem. Does the -source-path
> >> include bundles/{locale}, and is -locale set to en_US ?
> >>
> >> - Gordon
> >>
> >> -----Original Message-----
> >> From: Chema Balsas [mailto:jbalsas@gmail.com]
> >> Sent: Friday, December 14, 2012 1:23 PM
> >> To: flex-dev@incubator.apache.org
> >> Subject: Re: Falcon SDKSWCTests
> >>
> >> Right now there's one recurring error when trying to compile almost
> >> every missing swc.
> >>
> >> Error: Unable to resolve resource bundle 'core'
> >> >
> >> > [ResourceBundle("core")]
> >> >
> >>
> >> This happens for several bundles. I've been trying to figure out
> >> the reason, but this is still beyond my reach. It looks like Falcon
> >> never does resolve these dependencies (but I'm not really sure what
> >> I'm looking at here...). Gordon, do you think this is a
> >> configuration problem and have any idea on how this could be
> >> addressed? Or is maybe something missing in Falcon?
> >>
> >> Also, currently we're only checking the compile targets. Should we
> >> also check the bundle ones?
> >>
> >> Cheers,
> >> Chema
> >>
> >>
> >> 2012/12/11 Chema Balsas <jb...@gmail.com>
> >>
> >> > Nice! That fixed other 5 tests for free and made other 2 easy to fix.
> >> >
> >> > I've committed the changes to the sdk and sdkswctests. We now
> >> > have
> >> > 18 out of 29 tests passing. I'll try to start looking over the
> >> > hard ones over the week.
> >> >
> >> > Cheers,
> >> > Chema
> >> >
> >> >
> >> > 2012/12/10 Gordon Smith <go...@adobe.com>
> >> >
> >> >> > I've just commited some changes into rpc, authoringsupport,
> >> >> > framework
> >> >> and mobilecomponents so that they compile properly in falcon.
> >> >> I've enabled those tests and now we have 11 out of 29 working.
> >> >>
> >> >> Nice progress!
> >> >>
> >> >> > Warning: mx.core.Version is defined by multiple files:
> >> >>
> >> >> This is an example where Falcon is pickier but since it's just a
> >> >> warning I don't think we should try to fix it. Let's change the
> >> >> tests to ignore this warning. You should be able to do this by
> >> >> changing the SWC tests to run with the additional command-line
> >> >> argument
> >> -ignore-problems=... .
> >> >>
> >> >> - Gordon
> >> >>
> >> >>
> >> >> -----Original Message-----
> >> >> From: Chema Balsas [mailto:jbalsas@gmail.com]
> >> >> Sent: Monday, December 10, 2012 2:20 PM
> >> >> To: flex-dev@incubator.apache.org
> >> >> Subject: Re: Falcon SDKSWCTests
> >> >>
> >> >> Hi,
> >> >>
> >> >> I've just commited some changes into rpc, authoringsupport,
> >> >> framework and mobilecomponents so that they compile properly in
> >> >> falcon. I've enabled those tests and now we have 11 out of 29
> working.
> >> >>
> >> >> @Gordon One recurrent issue for other projects is
> >> >>
> >> >> Warning: mx.core.Version is defined by multiple files:
> >> >> > /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/
> >> >> > fr ame wor ks/projects/automation_agent/src/mx/core/Version.as
> >> >>
> >> >>
> >> >> Is this something Falcon will take care of, or do we need to
> >> >> figure out anoter way around like in the config files for example?
> >> >>
> >> >> Cheers,
> >> >> Chema
> >> >>
> >> >> 2012/12/7 Chema Balsas <jb...@gmail.com>
> >> >>
> >> >> > Following with this, I've checked and in CompcTask, an
> >> >> > include-config
> >> >> > (ifSpec) is added with createElem instead of with
> >> >> > createElemAllowAppend. Is there a reason for this? I've
> >> >> > checked and changing it and adding 'append="true"' in the ant
> >> >> > task to the include-file tag does fix this I don't know if
> >> >> > there's something else
> >> >> to take into account though.
> >> >> >
> >> >> > We won't be using it for now, but do you think we should try
> >> >> > to fix this, or at least document it somewhere?
> >> >> >
> >> >> >
> >> >> > 2012/12/7 Chema Balsas <jb...@gmail.com>
> >> >> >
> >> >> >> Yes, I already have it and it's working. I've accessed my
> >> >> >> account through ssh to verify it and I've also checked, and I
> >> >> >> have access to the apache commiters repository, but not ours.
> >> >> >>
> >> >> >>
> >> >> >> 2012/12/7 Alex Harui <ah...@adobe.com>
> >> >> >>
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
> >> >> >>>
> >> >> >>> > Oh, that explains it then... and how unfortunate
> >> >> >>> >
> >> >> >>> > From Gordon's comment, I assumed we were going to stop
> >> >> >>> > including the version.properties file (at least for now).
> >> >> >>> > That was exactly what I was about to commit, but it seems
> >> >> >>> > I still don't have access to the svn repository.
> >> >> >>> >
> >> >> >>> Did you get an email asking about what you want your apache
> >> >> >>> id to
> >> be?
> >> >> >>>
> >> >> >>> --
> >> >> >>> Alex Harui
> >> >> >>> Flex SDK Team
> >> >> >>> Adobe Systems, Inc.
> >> >> >>> http://blogs.adobe.com/aharui
> >> >> >>>
> >> >> >>>
> >> >> >>
> >> >> >
> >> >>
> >> >
> >> >
> >>
> >
> >
>
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
>
> I'd like to fix these since they shouldn't be hard to fix.
Fix them we will, then ;)
Somehow <compc> is finding either the source code for the bundles on the
> source path, or the compiled code for the bundles on the library path.
This may have something to do with "addApplicationParentToSourcePath()"
inside ResourceBundlePath in <compc>... I assume Falcon isn't doing this,
but is it going to? It's easy to modify the compile-config files to get
these, and it does show the dependencies more explicitly. What do you think?
Cheers,
Chema
2012/12/15 Gordon Smith <go...@adobe.com>
> I'm not sure what's going on with the resource bundle issue, but I don't
> think it's an example of Falcon being pickier. Somehow <compc> is finding
> either the source code for the bundles on the source path, or the compiled
> code for the bundles on the library path.
>
> > I see several "duplicated variables" warnings ahead. Do we want to fix
> them or ignore them?
>
> I'd like to fix these since they shouldn't be hard to fix. (The problem
> with fixing the previous problem with Version.as is that Alex would kill us
> if we removed all the includes of Version.as.)
>
> - Gordon
>
>
> -----Original Message-----
> From: Chema Balsas [mailto:jbalsas@gmail.com]
> Sent: Friday, December 14, 2012 5:05 PM
> To: flex-dev@incubator.apache.org
> Subject: Re: Falcon SDKSWCTests
>
> Also, I've already fixed some warnings, but I'd like to ask before going
> and fix some more. We've already set to ignore
> DuplicateQNameInSourcePathProblem. Should we stick to ignore warnings, or
> try and fix them to end up with a cleaner/safer sdk code?
>
> For instance, I see several "duplicated variables" warnings ahead. Do we
> want to fix them or ignore them?
>
> Cheers,
> Chema
>
> 2012/12/15 Chema Balsas <jb...@gmail.com>
>
> > That's usually a configuration problem. Does the -source-path include
> >> bundles/{locale}, and is -locale set to en_US ?
> >
> >
> > You're right, that is the case. I was setting the locale, but the
> > bundles folder is not in the source-path. How's that compc doesn't
> > complain? Is this another place where Falcon is pickier?
> >
> > Take the mx project. Other than its bundles, it uses some from
> > framework, so we need to add both folders to the source-path in
> > compile-config.xml where none was used before. Is this the expected
> > behavior or am I missing something?
> >
> > Cheers,
> > Chema
> >
> > 2012/12/14 Gordon Smith <go...@adobe.com>
> >
> >> That's usually a configuration problem. Does the -source-path include
> >> bundles/{locale}, and is -locale set to en_US ?
> >>
> >> - Gordon
> >>
> >> -----Original Message-----
> >> From: Chema Balsas [mailto:jbalsas@gmail.com]
> >> Sent: Friday, December 14, 2012 1:23 PM
> >> To: flex-dev@incubator.apache.org
> >> Subject: Re: Falcon SDKSWCTests
> >>
> >> Right now there's one recurring error when trying to compile almost
> >> every missing swc.
> >>
> >> Error: Unable to resolve resource bundle 'core'
> >> >
> >> > [ResourceBundle("core")]
> >> >
> >>
> >> This happens for several bundles. I've been trying to figure out the
> >> reason, but this is still beyond my reach. It looks like Falcon never
> >> does resolve these dependencies (but I'm not really sure what I'm
> >> looking at here...). Gordon, do you think this is a configuration
> >> problem and have any idea on how this could be addressed? Or is maybe
> >> something missing in Falcon?
> >>
> >> Also, currently we're only checking the compile targets. Should we
> >> also check the bundle ones?
> >>
> >> Cheers,
> >> Chema
> >>
> >>
> >> 2012/12/11 Chema Balsas <jb...@gmail.com>
> >>
> >> > Nice! That fixed other 5 tests for free and made other 2 easy to fix.
> >> >
> >> > I've committed the changes to the sdk and sdkswctests. We now have
> >> > 18 out of 29 tests passing. I'll try to start looking over the hard
> >> > ones over the week.
> >> >
> >> > Cheers,
> >> > Chema
> >> >
> >> >
> >> > 2012/12/10 Gordon Smith <go...@adobe.com>
> >> >
> >> >> > I've just commited some changes into rpc, authoringsupport,
> >> >> > framework
> >> >> and mobilecomponents so that they compile properly in falcon. I've
> >> >> enabled those tests and now we have 11 out of 29 working.
> >> >>
> >> >> Nice progress!
> >> >>
> >> >> > Warning: mx.core.Version is defined by multiple files:
> >> >>
> >> >> This is an example where Falcon is pickier but since it's just a
> >> >> warning I don't think we should try to fix it. Let's change the
> >> >> tests to ignore this warning. You should be able to do this by
> >> >> changing the SWC tests to run with the additional command-line
> >> >> argument
> >> -ignore-problems=... .
> >> >>
> >> >> - Gordon
> >> >>
> >> >>
> >> >> -----Original Message-----
> >> >> From: Chema Balsas [mailto:jbalsas@gmail.com]
> >> >> Sent: Monday, December 10, 2012 2:20 PM
> >> >> To: flex-dev@incubator.apache.org
> >> >> Subject: Re: Falcon SDKSWCTests
> >> >>
> >> >> Hi,
> >> >>
> >> >> I've just commited some changes into rpc, authoringsupport,
> >> >> framework and mobilecomponents so that they compile properly in
> >> >> falcon. I've enabled those tests and now we have 11 out of 29
> working.
> >> >>
> >> >> @Gordon One recurrent issue for other projects is
> >> >>
> >> >> Warning: mx.core.Version is defined by multiple files:
> >> >> > /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/fr
> >> >> > ame wor ks/projects/automation_agent/src/mx/core/Version.as
> >> >>
> >> >>
> >> >> Is this something Falcon will take care of, or do we need to
> >> >> figure out anoter way around like in the config files for example?
> >> >>
> >> >> Cheers,
> >> >> Chema
> >> >>
> >> >> 2012/12/7 Chema Balsas <jb...@gmail.com>
> >> >>
> >> >> > Following with this, I've checked and in CompcTask, an
> >> >> > include-config
> >> >> > (ifSpec) is added with createElem instead of with
> >> >> > createElemAllowAppend. Is there a reason for this? I've checked
> >> >> > and changing it and adding 'append="true"' in the ant task to
> >> >> > the include-file tag does fix this I don't know if there's
> >> >> > something else
> >> >> to take into account though.
> >> >> >
> >> >> > We won't be using it for now, but do you think we should try to
> >> >> > fix this, or at least document it somewhere?
> >> >> >
> >> >> >
> >> >> > 2012/12/7 Chema Balsas <jb...@gmail.com>
> >> >> >
> >> >> >> Yes, I already have it and it's working. I've accessed my
> >> >> >> account through ssh to verify it and I've also checked, and I
> >> >> >> have access to the apache commiters repository, but not ours.
> >> >> >>
> >> >> >>
> >> >> >> 2012/12/7 Alex Harui <ah...@adobe.com>
> >> >> >>
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
> >> >> >>>
> >> >> >>> > Oh, that explains it then... and how unfortunate
> >> >> >>> >
> >> >> >>> > From Gordon's comment, I assumed we were going to stop
> >> >> >>> > including the version.properties file (at least for now).
> >> >> >>> > That was exactly what I was about to commit, but it seems I
> >> >> >>> > still don't have access to the svn repository.
> >> >> >>> >
> >> >> >>> Did you get an email asking about what you want your apache id
> >> >> >>> to
> >> be?
> >> >> >>>
> >> >> >>> --
> >> >> >>> Alex Harui
> >> >> >>> Flex SDK Team
> >> >> >>> Adobe Systems, Inc.
> >> >> >>> http://blogs.adobe.com/aharui
> >> >> >>>
> >> >> >>>
> >> >> >>
> >> >> >
> >> >>
> >> >
> >> >
> >>
> >
> >
>
RE: Falcon SDKSWCTests
Posted by Gordon Smith <go...@adobe.com>.
I'm not sure what's going on with the resource bundle issue, but I don't think it's an example of Falcon being pickier. Somehow <compc> is finding either the source code for the bundles on the source path, or the compiled code for the bundles on the library path.
> I see several "duplicated variables" warnings ahead. Do we want to fix them or ignore them?
I'd like to fix these since they shouldn't be hard to fix. (The problem with fixing the previous problem with Version.as is that Alex would kill us if we removed all the includes of Version.as.)
- Gordon
-----Original Message-----
From: Chema Balsas [mailto:jbalsas@gmail.com]
Sent: Friday, December 14, 2012 5:05 PM
To: flex-dev@incubator.apache.org
Subject: Re: Falcon SDKSWCTests
Also, I've already fixed some warnings, but I'd like to ask before going and fix some more. We've already set to ignore DuplicateQNameInSourcePathProblem. Should we stick to ignore warnings, or try and fix them to end up with a cleaner/safer sdk code?
For instance, I see several "duplicated variables" warnings ahead. Do we want to fix them or ignore them?
Cheers,
Chema
2012/12/15 Chema Balsas <jb...@gmail.com>
> That's usually a configuration problem. Does the -source-path include
>> bundles/{locale}, and is -locale set to en_US ?
>
>
> You're right, that is the case. I was setting the locale, but the
> bundles folder is not in the source-path. How's that compc doesn't
> complain? Is this another place where Falcon is pickier?
>
> Take the mx project. Other than its bundles, it uses some from
> framework, so we need to add both folders to the source-path in
> compile-config.xml where none was used before. Is this the expected
> behavior or am I missing something?
>
> Cheers,
> Chema
>
> 2012/12/14 Gordon Smith <go...@adobe.com>
>
>> That's usually a configuration problem. Does the -source-path include
>> bundles/{locale}, and is -locale set to en_US ?
>>
>> - Gordon
>>
>> -----Original Message-----
>> From: Chema Balsas [mailto:jbalsas@gmail.com]
>> Sent: Friday, December 14, 2012 1:23 PM
>> To: flex-dev@incubator.apache.org
>> Subject: Re: Falcon SDKSWCTests
>>
>> Right now there's one recurring error when trying to compile almost
>> every missing swc.
>>
>> Error: Unable to resolve resource bundle 'core'
>> >
>> > [ResourceBundle("core")]
>> >
>>
>> This happens for several bundles. I've been trying to figure out the
>> reason, but this is still beyond my reach. It looks like Falcon never
>> does resolve these dependencies (but I'm not really sure what I'm
>> looking at here...). Gordon, do you think this is a configuration
>> problem and have any idea on how this could be addressed? Or is maybe
>> something missing in Falcon?
>>
>> Also, currently we're only checking the compile targets. Should we
>> also check the bundle ones?
>>
>> Cheers,
>> Chema
>>
>>
>> 2012/12/11 Chema Balsas <jb...@gmail.com>
>>
>> > Nice! That fixed other 5 tests for free and made other 2 easy to fix.
>> >
>> > I've committed the changes to the sdk and sdkswctests. We now have
>> > 18 out of 29 tests passing. I'll try to start looking over the hard
>> > ones over the week.
>> >
>> > Cheers,
>> > Chema
>> >
>> >
>> > 2012/12/10 Gordon Smith <go...@adobe.com>
>> >
>> >> > I've just commited some changes into rpc, authoringsupport,
>> >> > framework
>> >> and mobilecomponents so that they compile properly in falcon. I've
>> >> enabled those tests and now we have 11 out of 29 working.
>> >>
>> >> Nice progress!
>> >>
>> >> > Warning: mx.core.Version is defined by multiple files:
>> >>
>> >> This is an example where Falcon is pickier but since it's just a
>> >> warning I don't think we should try to fix it. Let's change the
>> >> tests to ignore this warning. You should be able to do this by
>> >> changing the SWC tests to run with the additional command-line
>> >> argument
>> -ignore-problems=... .
>> >>
>> >> - Gordon
>> >>
>> >>
>> >> -----Original Message-----
>> >> From: Chema Balsas [mailto:jbalsas@gmail.com]
>> >> Sent: Monday, December 10, 2012 2:20 PM
>> >> To: flex-dev@incubator.apache.org
>> >> Subject: Re: Falcon SDKSWCTests
>> >>
>> >> Hi,
>> >>
>> >> I've just commited some changes into rpc, authoringsupport,
>> >> framework and mobilecomponents so that they compile properly in
>> >> falcon. I've enabled those tests and now we have 11 out of 29 working.
>> >>
>> >> @Gordon One recurrent issue for other projects is
>> >>
>> >> Warning: mx.core.Version is defined by multiple files:
>> >> > /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/fr
>> >> > ame wor ks/projects/automation_agent/src/mx/core/Version.as
>> >>
>> >>
>> >> Is this something Falcon will take care of, or do we need to
>> >> figure out anoter way around like in the config files for example?
>> >>
>> >> Cheers,
>> >> Chema
>> >>
>> >> 2012/12/7 Chema Balsas <jb...@gmail.com>
>> >>
>> >> > Following with this, I've checked and in CompcTask, an
>> >> > include-config
>> >> > (ifSpec) is added with createElem instead of with
>> >> > createElemAllowAppend. Is there a reason for this? I've checked
>> >> > and changing it and adding 'append="true"' in the ant task to
>> >> > the include-file tag does fix this I don't know if there's
>> >> > something else
>> >> to take into account though.
>> >> >
>> >> > We won't be using it for now, but do you think we should try to
>> >> > fix this, or at least document it somewhere?
>> >> >
>> >> >
>> >> > 2012/12/7 Chema Balsas <jb...@gmail.com>
>> >> >
>> >> >> Yes, I already have it and it's working. I've accessed my
>> >> >> account through ssh to verify it and I've also checked, and I
>> >> >> have access to the apache commiters repository, but not ours.
>> >> >>
>> >> >>
>> >> >> 2012/12/7 Alex Harui <ah...@adobe.com>
>> >> >>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
>> >> >>>
>> >> >>> > Oh, that explains it then... and how unfortunate
>> >> >>> >
>> >> >>> > From Gordon's comment, I assumed we were going to stop
>> >> >>> > including the version.properties file (at least for now).
>> >> >>> > That was exactly what I was about to commit, but it seems I
>> >> >>> > still don't have access to the svn repository.
>> >> >>> >
>> >> >>> Did you get an email asking about what you want your apache id
>> >> >>> to
>> be?
>> >> >>>
>> >> >>> --
>> >> >>> Alex Harui
>> >> >>> Flex SDK Team
>> >> >>> Adobe Systems, Inc.
>> >> >>> http://blogs.adobe.com/aharui
>> >> >>>
>> >> >>>
>> >> >>
>> >> >
>> >>
>> >
>> >
>>
>
>
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
Also, I've already fixed some warnings, but I'd like to ask before going
and fix some more. We've already set to
ignore DuplicateQNameInSourcePathProblem. Should we stick to ignore
warnings, or try and fix them to end up with a cleaner/safer sdk code?
For instance, I see several "duplicated variables" warnings ahead. Do we
want to fix them or ignore them?
Cheers,
Chema
2012/12/15 Chema Balsas <jb...@gmail.com>
> That's usually a configuration problem. Does the -source-path include
>> bundles/{locale}, and is -locale set to en_US ?
>
>
> You're right, that is the case. I was setting the locale, but the bundles
> folder is not in the source-path. How's that compc doesn't complain? Is
> this another place where Falcon is pickier?
>
> Take the mx project. Other than its bundles, it uses some from framework,
> so we need to add both folders to the source-path in compile-config.xml
> where none was used before. Is this the expected behavior or am I missing
> something?
>
> Cheers,
> Chema
>
> 2012/12/14 Gordon Smith <go...@adobe.com>
>
>> That's usually a configuration problem. Does the -source-path include
>> bundles/{locale}, and is -locale set to en_US ?
>>
>> - Gordon
>>
>> -----Original Message-----
>> From: Chema Balsas [mailto:jbalsas@gmail.com]
>> Sent: Friday, December 14, 2012 1:23 PM
>> To: flex-dev@incubator.apache.org
>> Subject: Re: Falcon SDKSWCTests
>>
>> Right now there's one recurring error when trying to compile almost every
>> missing swc.
>>
>> Error: Unable to resolve resource bundle 'core'
>> >
>> > [ResourceBundle("core")]
>> >
>>
>> This happens for several bundles. I've been trying to figure out the
>> reason, but this is still beyond my reach. It looks like Falcon never does
>> resolve these dependencies (but I'm not really sure what I'm looking at
>> here...). Gordon, do you think this is a configuration problem and have any
>> idea on how this could be addressed? Or is maybe something missing in
>> Falcon?
>>
>> Also, currently we're only checking the compile targets. Should we also
>> check the bundle ones?
>>
>> Cheers,
>> Chema
>>
>>
>> 2012/12/11 Chema Balsas <jb...@gmail.com>
>>
>> > Nice! That fixed other 5 tests for free and made other 2 easy to fix.
>> >
>> > I've committed the changes to the sdk and sdkswctests. We now have 18
>> > out of 29 tests passing. I'll try to start looking over the hard ones
>> > over the week.
>> >
>> > Cheers,
>> > Chema
>> >
>> >
>> > 2012/12/10 Gordon Smith <go...@adobe.com>
>> >
>> >> > I've just commited some changes into rpc, authoringsupport,
>> >> > framework
>> >> and mobilecomponents so that they compile properly in falcon. I've
>> >> enabled those tests and now we have 11 out of 29 working.
>> >>
>> >> Nice progress!
>> >>
>> >> > Warning: mx.core.Version is defined by multiple files:
>> >>
>> >> This is an example where Falcon is pickier but since it's just a
>> >> warning I don't think we should try to fix it. Let's change the tests
>> >> to ignore this warning. You should be able to do this by changing the
>> >> SWC tests to run with the additional command-line argument
>> -ignore-problems=... .
>> >>
>> >> - Gordon
>> >>
>> >>
>> >> -----Original Message-----
>> >> From: Chema Balsas [mailto:jbalsas@gmail.com]
>> >> Sent: Monday, December 10, 2012 2:20 PM
>> >> To: flex-dev@incubator.apache.org
>> >> Subject: Re: Falcon SDKSWCTests
>> >>
>> >> Hi,
>> >>
>> >> I've just commited some changes into rpc, authoringsupport, framework
>> >> and mobilecomponents so that they compile properly in falcon. I've
>> >> enabled those tests and now we have 11 out of 29 working.
>> >>
>> >> @Gordon One recurrent issue for other projects is
>> >>
>> >> Warning: mx.core.Version is defined by multiple files:
>> >> > /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/frame
>> >> > wor ks/projects/automation_agent/src/mx/core/Version.as
>> >>
>> >>
>> >> Is this something Falcon will take care of, or do we need to figure
>> >> out anoter way around like in the config files for example?
>> >>
>> >> Cheers,
>> >> Chema
>> >>
>> >> 2012/12/7 Chema Balsas <jb...@gmail.com>
>> >>
>> >> > Following with this, I've checked and in CompcTask, an
>> >> > include-config
>> >> > (ifSpec) is added with createElem instead of with
>> >> > createElemAllowAppend. Is there a reason for this? I've checked and
>> >> > changing it and adding 'append="true"' in the ant task to the
>> >> > include-file tag does fix this I don't know if there's something
>> >> > else
>> >> to take into account though.
>> >> >
>> >> > We won't be using it for now, but do you think we should try to fix
>> >> > this, or at least document it somewhere?
>> >> >
>> >> >
>> >> > 2012/12/7 Chema Balsas <jb...@gmail.com>
>> >> >
>> >> >> Yes, I already have it and it's working. I've accessed my account
>> >> >> through ssh to verify it and I've also checked, and I have access
>> >> >> to the apache commiters repository, but not ours.
>> >> >>
>> >> >>
>> >> >> 2012/12/7 Alex Harui <ah...@adobe.com>
>> >> >>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
>> >> >>>
>> >> >>> > Oh, that explains it then... and how unfortunate
>> >> >>> >
>> >> >>> > From Gordon's comment, I assumed we were going to stop
>> >> >>> > including the version.properties file (at least for now). That
>> >> >>> > was exactly what I was about to commit, but it seems I still
>> >> >>> > don't have access to the svn repository.
>> >> >>> >
>> >> >>> Did you get an email asking about what you want your apache id to
>> be?
>> >> >>>
>> >> >>> --
>> >> >>> Alex Harui
>> >> >>> Flex SDK Team
>> >> >>> Adobe Systems, Inc.
>> >> >>> http://blogs.adobe.com/aharui
>> >> >>>
>> >> >>>
>> >> >>
>> >> >
>> >>
>> >
>> >
>>
>
>
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
>
> That's usually a configuration problem. Does the -source-path include
> bundles/{locale}, and is -locale set to en_US ?
You're right, that is the case. I was setting the locale, but the bundles
folder is not in the source-path. How's that compc doesn't complain? Is
this another place where Falcon is pickier?
Take the mx project. Other than its bundles, it uses some from framework,
so we need to add both folders to the source-path in compile-config.xml
where none was used before. Is this the expected behavior or am I missing
something?
Cheers,
Chema
2012/12/14 Gordon Smith <go...@adobe.com>
> That's usually a configuration problem. Does the -source-path include
> bundles/{locale}, and is -locale set to en_US ?
>
> - Gordon
>
> -----Original Message-----
> From: Chema Balsas [mailto:jbalsas@gmail.com]
> Sent: Friday, December 14, 2012 1:23 PM
> To: flex-dev@incubator.apache.org
> Subject: Re: Falcon SDKSWCTests
>
> Right now there's one recurring error when trying to compile almost every
> missing swc.
>
> Error: Unable to resolve resource bundle 'core'
> >
> > [ResourceBundle("core")]
> >
>
> This happens for several bundles. I've been trying to figure out the
> reason, but this is still beyond my reach. It looks like Falcon never does
> resolve these dependencies (but I'm not really sure what I'm looking at
> here...). Gordon, do you think this is a configuration problem and have any
> idea on how this could be addressed? Or is maybe something missing in
> Falcon?
>
> Also, currently we're only checking the compile targets. Should we also
> check the bundle ones?
>
> Cheers,
> Chema
>
>
> 2012/12/11 Chema Balsas <jb...@gmail.com>
>
> > Nice! That fixed other 5 tests for free and made other 2 easy to fix.
> >
> > I've committed the changes to the sdk and sdkswctests. We now have 18
> > out of 29 tests passing. I'll try to start looking over the hard ones
> > over the week.
> >
> > Cheers,
> > Chema
> >
> >
> > 2012/12/10 Gordon Smith <go...@adobe.com>
> >
> >> > I've just commited some changes into rpc, authoringsupport,
> >> > framework
> >> and mobilecomponents so that they compile properly in falcon. I've
> >> enabled those tests and now we have 11 out of 29 working.
> >>
> >> Nice progress!
> >>
> >> > Warning: mx.core.Version is defined by multiple files:
> >>
> >> This is an example where Falcon is pickier but since it's just a
> >> warning I don't think we should try to fix it. Let's change the tests
> >> to ignore this warning. You should be able to do this by changing the
> >> SWC tests to run with the additional command-line argument
> -ignore-problems=... .
> >>
> >> - Gordon
> >>
> >>
> >> -----Original Message-----
> >> From: Chema Balsas [mailto:jbalsas@gmail.com]
> >> Sent: Monday, December 10, 2012 2:20 PM
> >> To: flex-dev@incubator.apache.org
> >> Subject: Re: Falcon SDKSWCTests
> >>
> >> Hi,
> >>
> >> I've just commited some changes into rpc, authoringsupport, framework
> >> and mobilecomponents so that they compile properly in falcon. I've
> >> enabled those tests and now we have 11 out of 29 working.
> >>
> >> @Gordon One recurrent issue for other projects is
> >>
> >> Warning: mx.core.Version is defined by multiple files:
> >> > /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/frame
> >> > wor ks/projects/automation_agent/src/mx/core/Version.as
> >>
> >>
> >> Is this something Falcon will take care of, or do we need to figure
> >> out anoter way around like in the config files for example?
> >>
> >> Cheers,
> >> Chema
> >>
> >> 2012/12/7 Chema Balsas <jb...@gmail.com>
> >>
> >> > Following with this, I've checked and in CompcTask, an
> >> > include-config
> >> > (ifSpec) is added with createElem instead of with
> >> > createElemAllowAppend. Is there a reason for this? I've checked and
> >> > changing it and adding 'append="true"' in the ant task to the
> >> > include-file tag does fix this I don't know if there's something
> >> > else
> >> to take into account though.
> >> >
> >> > We won't be using it for now, but do you think we should try to fix
> >> > this, or at least document it somewhere?
> >> >
> >> >
> >> > 2012/12/7 Chema Balsas <jb...@gmail.com>
> >> >
> >> >> Yes, I already have it and it's working. I've accessed my account
> >> >> through ssh to verify it and I've also checked, and I have access
> >> >> to the apache commiters repository, but not ours.
> >> >>
> >> >>
> >> >> 2012/12/7 Alex Harui <ah...@adobe.com>
> >> >>
> >> >>>
> >> >>>
> >> >>>
> >> >>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
> >> >>>
> >> >>> > Oh, that explains it then... and how unfortunate
> >> >>> >
> >> >>> > From Gordon's comment, I assumed we were going to stop
> >> >>> > including the version.properties file (at least for now). That
> >> >>> > was exactly what I was about to commit, but it seems I still
> >> >>> > don't have access to the svn repository.
> >> >>> >
> >> >>> Did you get an email asking about what you want your apache id to
> be?
> >> >>>
> >> >>> --
> >> >>> Alex Harui
> >> >>> Flex SDK Team
> >> >>> Adobe Systems, Inc.
> >> >>> http://blogs.adobe.com/aharui
> >> >>>
> >> >>>
> >> >>
> >> >
> >>
> >
> >
>
RE: Falcon SDKSWCTests
Posted by Gordon Smith <go...@adobe.com>.
That's usually a configuration problem. Does the -source-path include bundles/{locale}, and is -locale set to en_US ?
- Gordon
-----Original Message-----
From: Chema Balsas [mailto:jbalsas@gmail.com]
Sent: Friday, December 14, 2012 1:23 PM
To: flex-dev@incubator.apache.org
Subject: Re: Falcon SDKSWCTests
Right now there's one recurring error when trying to compile almost every missing swc.
Error: Unable to resolve resource bundle 'core'
>
> [ResourceBundle("core")]
>
This happens for several bundles. I've been trying to figure out the reason, but this is still beyond my reach. It looks like Falcon never does resolve these dependencies (but I'm not really sure what I'm looking at here...). Gordon, do you think this is a configuration problem and have any idea on how this could be addressed? Or is maybe something missing in Falcon?
Also, currently we're only checking the compile targets. Should we also check the bundle ones?
Cheers,
Chema
2012/12/11 Chema Balsas <jb...@gmail.com>
> Nice! That fixed other 5 tests for free and made other 2 easy to fix.
>
> I've committed the changes to the sdk and sdkswctests. We now have 18
> out of 29 tests passing. I'll try to start looking over the hard ones
> over the week.
>
> Cheers,
> Chema
>
>
> 2012/12/10 Gordon Smith <go...@adobe.com>
>
>> > I've just commited some changes into rpc, authoringsupport,
>> > framework
>> and mobilecomponents so that they compile properly in falcon. I've
>> enabled those tests and now we have 11 out of 29 working.
>>
>> Nice progress!
>>
>> > Warning: mx.core.Version is defined by multiple files:
>>
>> This is an example where Falcon is pickier but since it's just a
>> warning I don't think we should try to fix it. Let's change the tests
>> to ignore this warning. You should be able to do this by changing the
>> SWC tests to run with the additional command-line argument -ignore-problems=... .
>>
>> - Gordon
>>
>>
>> -----Original Message-----
>> From: Chema Balsas [mailto:jbalsas@gmail.com]
>> Sent: Monday, December 10, 2012 2:20 PM
>> To: flex-dev@incubator.apache.org
>> Subject: Re: Falcon SDKSWCTests
>>
>> Hi,
>>
>> I've just commited some changes into rpc, authoringsupport, framework
>> and mobilecomponents so that they compile properly in falcon. I've
>> enabled those tests and now we have 11 out of 29 working.
>>
>> @Gordon One recurrent issue for other projects is
>>
>> Warning: mx.core.Version is defined by multiple files:
>> > /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/frame
>> > wor ks/projects/automation_agent/src/mx/core/Version.as
>>
>>
>> Is this something Falcon will take care of, or do we need to figure
>> out anoter way around like in the config files for example?
>>
>> Cheers,
>> Chema
>>
>> 2012/12/7 Chema Balsas <jb...@gmail.com>
>>
>> > Following with this, I've checked and in CompcTask, an
>> > include-config
>> > (ifSpec) is added with createElem instead of with
>> > createElemAllowAppend. Is there a reason for this? I've checked and
>> > changing it and adding 'append="true"' in the ant task to the
>> > include-file tag does fix this I don't know if there's something
>> > else
>> to take into account though.
>> >
>> > We won't be using it for now, but do you think we should try to fix
>> > this, or at least document it somewhere?
>> >
>> >
>> > 2012/12/7 Chema Balsas <jb...@gmail.com>
>> >
>> >> Yes, I already have it and it's working. I've accessed my account
>> >> through ssh to verify it and I've also checked, and I have access
>> >> to the apache commiters repository, but not ours.
>> >>
>> >>
>> >> 2012/12/7 Alex Harui <ah...@adobe.com>
>> >>
>> >>>
>> >>>
>> >>>
>> >>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
>> >>>
>> >>> > Oh, that explains it then... and how unfortunate
>> >>> >
>> >>> > From Gordon's comment, I assumed we were going to stop
>> >>> > including the version.properties file (at least for now). That
>> >>> > was exactly what I was about to commit, but it seems I still
>> >>> > don't have access to the svn repository.
>> >>> >
>> >>> Did you get an email asking about what you want your apache id to be?
>> >>>
>> >>> --
>> >>> Alex Harui
>> >>> Flex SDK Team
>> >>> Adobe Systems, Inc.
>> >>> http://blogs.adobe.com/aharui
>> >>>
>> >>>
>> >>
>> >
>>
>
>
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
Right now there's one recurring error when trying to compile almost every
missing swc.
Error: Unable to resolve resource bundle 'core'
>
> [ResourceBundle("core")]
>
This happens for several bundles. I've been trying to figure out the
reason, but this is still beyond my reach. It looks like Falcon never does
resolve these dependencies (but I'm not really sure what I'm looking at
here...). Gordon, do you think this is a configuration problem and have any
idea on how this could be addressed? Or is maybe something missing in
Falcon?
Also, currently we're only checking the compile targets. Should we also
check the bundle ones?
Cheers,
Chema
2012/12/11 Chema Balsas <jb...@gmail.com>
> Nice! That fixed other 5 tests for free and made other 2 easy to fix.
>
> I've committed the changes to the sdk and sdkswctests. We now have 18 out
> of 29 tests passing. I'll try to start looking over the hard ones over the
> week.
>
> Cheers,
> Chema
>
>
> 2012/12/10 Gordon Smith <go...@adobe.com>
>
>> > I've just commited some changes into rpc, authoringsupport, framework
>> and mobilecomponents so that they compile properly in falcon. I've enabled
>> those tests and now we have 11 out of 29 working.
>>
>> Nice progress!
>>
>> > Warning: mx.core.Version is defined by multiple files:
>>
>> This is an example where Falcon is pickier but since it's just a warning
>> I don't think we should try to fix it. Let's change the tests to ignore
>> this warning. You should be able to do this by changing the SWC tests to
>> run with the additional command-line argument -ignore-problems=... .
>>
>> - Gordon
>>
>>
>> -----Original Message-----
>> From: Chema Balsas [mailto:jbalsas@gmail.com]
>> Sent: Monday, December 10, 2012 2:20 PM
>> To: flex-dev@incubator.apache.org
>> Subject: Re: Falcon SDKSWCTests
>>
>> Hi,
>>
>> I've just commited some changes into rpc, authoringsupport, framework and
>> mobilecomponents so that they compile properly in falcon. I've enabled
>> those tests and now we have 11 out of 29 working.
>>
>> @Gordon One recurrent issue for other projects is
>>
>> Warning: mx.core.Version is defined by multiple files:
>> > /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/framewor
>> > ks/projects/automation_agent/src/mx/core/Version.as
>>
>>
>> Is this something Falcon will take care of, or do we need to figure out
>> anoter way around like in the config files for example?
>>
>> Cheers,
>> Chema
>>
>> 2012/12/7 Chema Balsas <jb...@gmail.com>
>>
>> > Following with this, I've checked and in CompcTask, an include-config
>> > (ifSpec) is added with createElem instead of with
>> > createElemAllowAppend. Is there a reason for this? I've checked and
>> > changing it and adding 'append="true"' in the ant task to the
>> > include-file tag does fix this I don't know if there's something else
>> to take into account though.
>> >
>> > We won't be using it for now, but do you think we should try to fix
>> > this, or at least document it somewhere?
>> >
>> >
>> > 2012/12/7 Chema Balsas <jb...@gmail.com>
>> >
>> >> Yes, I already have it and it's working. I've accessed my account
>> >> through ssh to verify it and I've also checked, and I have access to
>> >> the apache commiters repository, but not ours.
>> >>
>> >>
>> >> 2012/12/7 Alex Harui <ah...@adobe.com>
>> >>
>> >>>
>> >>>
>> >>>
>> >>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
>> >>>
>> >>> > Oh, that explains it then... and how unfortunate
>> >>> >
>> >>> > From Gordon's comment, I assumed we were going to stop including
>> >>> > the version.properties file (at least for now). That was exactly
>> >>> > what I was about to commit, but it seems I still don't have access
>> >>> > to the svn repository.
>> >>> >
>> >>> Did you get an email asking about what you want your apache id to be?
>> >>>
>> >>> --
>> >>> Alex Harui
>> >>> Flex SDK Team
>> >>> Adobe Systems, Inc.
>> >>> http://blogs.adobe.com/aharui
>> >>>
>> >>>
>> >>
>> >
>>
>
>
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
Nice! That fixed other 5 tests for free and made other 2 easy to fix.
I've committed the changes to the sdk and sdkswctests. We now have 18 out
of 29 tests passing. I'll try to start looking over the hard ones over the
week.
Cheers,
Chema
2012/12/10 Gordon Smith <go...@adobe.com>
> > I've just commited some changes into rpc, authoringsupport, framework
> and mobilecomponents so that they compile properly in falcon. I've enabled
> those tests and now we have 11 out of 29 working.
>
> Nice progress!
>
> > Warning: mx.core.Version is defined by multiple files:
>
> This is an example where Falcon is pickier but since it's just a warning I
> don't think we should try to fix it. Let's change the tests to ignore this
> warning. You should be able to do this by changing the SWC tests to run
> with the additional command-line argument -ignore-problems=... .
>
> - Gordon
>
>
> -----Original Message-----
> From: Chema Balsas [mailto:jbalsas@gmail.com]
> Sent: Monday, December 10, 2012 2:20 PM
> To: flex-dev@incubator.apache.org
> Subject: Re: Falcon SDKSWCTests
>
> Hi,
>
> I've just commited some changes into rpc, authoringsupport, framework and
> mobilecomponents so that they compile properly in falcon. I've enabled
> those tests and now we have 11 out of 29 working.
>
> @Gordon One recurrent issue for other projects is
>
> Warning: mx.core.Version is defined by multiple files:
> > /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/framewor
> > ks/projects/automation_agent/src/mx/core/Version.as
>
>
> Is this something Falcon will take care of, or do we need to figure out
> anoter way around like in the config files for example?
>
> Cheers,
> Chema
>
> 2012/12/7 Chema Balsas <jb...@gmail.com>
>
> > Following with this, I've checked and in CompcTask, an include-config
> > (ifSpec) is added with createElem instead of with
> > createElemAllowAppend. Is there a reason for this? I've checked and
> > changing it and adding 'append="true"' in the ant task to the
> > include-file tag does fix this I don't know if there's something else to
> take into account though.
> >
> > We won't be using it for now, but do you think we should try to fix
> > this, or at least document it somewhere?
> >
> >
> > 2012/12/7 Chema Balsas <jb...@gmail.com>
> >
> >> Yes, I already have it and it's working. I've accessed my account
> >> through ssh to verify it and I've also checked, and I have access to
> >> the apache commiters repository, but not ours.
> >>
> >>
> >> 2012/12/7 Alex Harui <ah...@adobe.com>
> >>
> >>>
> >>>
> >>>
> >>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
> >>>
> >>> > Oh, that explains it then... and how unfortunate
> >>> >
> >>> > From Gordon's comment, I assumed we were going to stop including
> >>> > the version.properties file (at least for now). That was exactly
> >>> > what I was about to commit, but it seems I still don't have access
> >>> > to the svn repository.
> >>> >
> >>> Did you get an email asking about what you want your apache id to be?
> >>>
> >>> --
> >>> Alex Harui
> >>> Flex SDK Team
> >>> Adobe Systems, Inc.
> >>> http://blogs.adobe.com/aharui
> >>>
> >>>
> >>
> >
>
RE: Falcon SDKSWCTests
Posted by Gordon Smith <go...@adobe.com>.
> I've just commited some changes into rpc, authoringsupport, framework and mobilecomponents so that they compile properly in falcon. I've enabled those tests and now we have 11 out of 29 working.
Nice progress!
> Warning: mx.core.Version is defined by multiple files:
This is an example where Falcon is pickier but since it's just a warning I don't think we should try to fix it. Let's change the tests to ignore this warning. You should be able to do this by changing the SWC tests to run with the additional command-line argument -ignore-problems=... .
- Gordon
-----Original Message-----
From: Chema Balsas [mailto:jbalsas@gmail.com]
Sent: Monday, December 10, 2012 2:20 PM
To: flex-dev@incubator.apache.org
Subject: Re: Falcon SDKSWCTests
Hi,
I've just commited some changes into rpc, authoringsupport, framework and mobilecomponents so that they compile properly in falcon. I've enabled those tests and now we have 11 out of 29 working.
@Gordon One recurrent issue for other projects is
Warning: mx.core.Version is defined by multiple files:
> /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/framewor
> ks/projects/automation_agent/src/mx/core/Version.as
Is this something Falcon will take care of, or do we need to figure out anoter way around like in the config files for example?
Cheers,
Chema
2012/12/7 Chema Balsas <jb...@gmail.com>
> Following with this, I've checked and in CompcTask, an include-config
> (ifSpec) is added with createElem instead of with
> createElemAllowAppend. Is there a reason for this? I've checked and
> changing it and adding 'append="true"' in the ant task to the
> include-file tag does fix this I don't know if there's something else to take into account though.
>
> We won't be using it for now, but do you think we should try to fix
> this, or at least document it somewhere?
>
>
> 2012/12/7 Chema Balsas <jb...@gmail.com>
>
>> Yes, I already have it and it's working. I've accessed my account
>> through ssh to verify it and I've also checked, and I have access to
>> the apache commiters repository, but not ours.
>>
>>
>> 2012/12/7 Alex Harui <ah...@adobe.com>
>>
>>>
>>>
>>>
>>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
>>>
>>> > Oh, that explains it then... and how unfortunate
>>> >
>>> > From Gordon's comment, I assumed we were going to stop including
>>> > the version.properties file (at least for now). That was exactly
>>> > what I was about to commit, but it seems I still don't have access
>>> > to the svn repository.
>>> >
>>> Did you get an email asking about what you want your apache id to be?
>>>
>>> --
>>> Alex Harui
>>> Flex SDK Team
>>> Adobe Systems, Inc.
>>> http://blogs.adobe.com/aharui
>>>
>>>
>>
>
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
Hi,
I've just commited some changes into rpc, authoringsupport, framework and
mobilecomponents so that they compile properly in falcon. I've enabled
those tests and now we have 11 out of 29 working.
@Gordon One recurrent issue for other projects is
Warning: mx.core.Version is defined by multiple files:
> /Users/jbalsas/Documents/dev/apache/flex/sdk/branches/develop/frameworks/projects/automation_agent/src/mx/core/Version.as
Is this something Falcon will take care of, or do we need to figure out
anoter way around like in the config files for example?
Cheers,
Chema
2012/12/7 Chema Balsas <jb...@gmail.com>
> Following with this, I've checked and in CompcTask, an include-config
> (ifSpec) is added with createElem instead of with createElemAllowAppend. Is
> there a reason for this? I've checked and changing it and adding
> 'append="true"' in the ant task to the include-file tag does fix this I
> don't know if there's something else to take into account though.
>
> We won't be using it for now, but do you think we should try to fix this,
> or at least document it somewhere?
>
>
> 2012/12/7 Chema Balsas <jb...@gmail.com>
>
>> Yes, I already have it and it's working. I've accessed my account through
>> ssh to verify it and I've also checked, and I have access to the apache
>> commiters repository, but not ours.
>>
>>
>> 2012/12/7 Alex Harui <ah...@adobe.com>
>>
>>>
>>>
>>>
>>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
>>>
>>> > Oh, that explains it then... and how unfortunate
>>> >
>>> > From Gordon's comment, I assumed we were going to stop including the
>>> > version.properties file (at least for now). That was exactly what I was
>>> > about to commit, but it seems I still don't have access to the svn
>>> > repository.
>>> >
>>> Did you get an email asking about what you want your apache id to be?
>>>
>>> --
>>> Alex Harui
>>> Flex SDK Team
>>> Adobe Systems, Inc.
>>> http://blogs.adobe.com/aharui
>>>
>>>
>>
>
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
Following with this, I've checked and in CompcTask, an include-config
(ifSpec) is added with createElem instead of with createElemAllowAppend. Is
there a reason for this? I've checked and changing it and adding
'append="true"' in the ant task to the include-file tag does fix this I
don't know if there's something else to take into account though.
We won't be using it for now, but do you think we should try to fix this,
or at least document it somewhere?
2012/12/7 Chema Balsas <jb...@gmail.com>
> Yes, I already have it and it's working. I've accessed my account through
> ssh to verify it and I've also checked, and I have access to the apache
> commiters repository, but not ours.
>
>
> 2012/12/7 Alex Harui <ah...@adobe.com>
>
>>
>>
>>
>> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
>>
>> > Oh, that explains it then... and how unfortunate
>> >
>> > From Gordon's comment, I assumed we were going to stop including the
>> > version.properties file (at least for now). That was exactly what I was
>> > about to commit, but it seems I still don't have access to the svn
>> > repository.
>> >
>> Did you get an email asking about what you want your apache id to be?
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
>
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
Yes, I already have it and it's working. I've accessed my account through
ssh to verify it and I've also checked, and I have access to the apache
commiters repository, but not ours.
2012/12/7 Alex Harui <ah...@adobe.com>
>
>
>
> On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
>
> > Oh, that explains it then... and how unfortunate
> >
> > From Gordon's comment, I assumed we were going to stop including the
> > version.properties file (at least for now). That was exactly what I was
> > about to commit, but it seems I still don't have access to the svn
> > repository.
> >
> Did you get an email asking about what you want your apache id to be?
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: Falcon SDKSWCTests
Posted by Alex Harui <ah...@adobe.com>.
On 12/7/12 9:22 AM, "Chema Balsas" <jb...@gmail.com> wrote:
> Oh, that explains it then... and how unfortunate
>
> From Gordon's comment, I assumed we were going to stop including the
> version.properties file (at least for now). That was exactly what I was
> about to commit, but it seems I still don't have access to the svn
> repository.
>
Did you get an email asking about what you want your apache id to be?
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
Oh, that explains it then... and how unfortunate
>From Gordon's comment, I assumed we were going to stop including the
version.properties file (at least for now). That was exactly what I was
about to commit, but it seems I still don't have access to the svn
repository.
I'm not that much into the code yet, but maybe the way the ant task invokes
compc makes those commands take precedence as shown in
http://livedocs.adobe.com/flex/3/html/help.html?content=compilers_12.html#153670.
Maybe adding 'append="true"' in the config file could prevent this from
happening?
In any case, it would be worth looking into checkintests to see what is
missing there.
2012/12/7 Alex Harui <ah...@adobe.com>
>
>
> On 12/7/12 8:07 AM, "Chema Balsas" <jb...@gmail.com> wrote:
>
> > In the meantime, I noticed that spark.swc weights around 80kb more if
> > version.properties is not included which strikes me as quite odd... this
> > doesn't happen for rpc or spark_dmv. Is there a reason for this?
> Something
> > we should look into?
> Unfortunately, I have the answer, having just spent several hours last
> night
> and this morning trying to figure out why a simple HelloWorld was no longer
> working.
>
> Both the build.xml and the compile-config.xml were specifying include-file
> (the build.xml was specifying version.properties, and compile-config was
> specifying defaults.css and more) and it appears that when you do that, the
> build.xml wins and the include-file in compile-config gets ignored. This
> caused spark.swc to not have its defaults.css in it causing my Helloworld
> app to die.
>
> Interestingly, checkintests somehow passed, which it shouldn't have, so I
> am
> going to investigate that now.
>
> I'm not going to check in my fix. Please figure out what you want to do
> about version.properties and then make sure all of the include-files are
> specified in only one of build.xml or compile-config.xml
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: Falcon SDKSWCTests
Posted by Alex Harui <ah...@adobe.com>.
On 12/7/12 8:07 AM, "Chema Balsas" <jb...@gmail.com> wrote:
> In the meantime, I noticed that spark.swc weights around 80kb more if
> version.properties is not included which strikes me as quite odd... this
> doesn't happen for rpc or spark_dmv. Is there a reason for this? Something
> we should look into?
Unfortunately, I have the answer, having just spent several hours last night
and this morning trying to figure out why a simple HelloWorld was no longer
working.
Both the build.xml and the compile-config.xml were specifying include-file
(the build.xml was specifying version.properties, and compile-config was
specifying defaults.css and more) and it appears that when you do that, the
build.xml wins and the include-file in compile-config gets ignored. This
caused spark.swc to not have its defaults.css in it causing my Helloworld
app to die.
Interestingly, checkintests somehow passed, which it shouldn't have, so I am
going to investigate that now.
I'm not going to check in my fix. Please figure out what you want to do
about version.properties and then make sure all of the include-files are
specified in only one of build.xml or compile-config.xml
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
Ok, I removed them from the compile targets. I seem to be having some issue
with my svn access, so I'll commit the changes when that's solved.
In the meantime, I noticed that spark.swc weights around 80kb more if
version.properties is not included which strikes me as quite odd... this
doesn't happen for rpc or spark_dmv. Is there a reason for this? Something
we should look into?
2012/12/5 Gordon Smith <go...@adobe.com>
> If Apache doesn't care about that we should just drop it. It seems strange
> to have it in some SWCs and not others.
>
> - Gordon
>
> -----Original Message-----
> From: Gordon Smith [mailto:gosmith@adobe.com]
> Sent: Tuesday, December 04, 2012 6:21 PM
> To: flex-dev@incubator.apache.org
> Subject: RE: Falcon SDKSWCTests
>
> I think Adobe's build machines had some scripts that set build.number to
> the Perforce revision number that it was building.
>
> - Gordon
>
> -----Original Message-----
> From: Chema Balsas [mailto:jbalsas@gmail.com]
> Sent: Tuesday, December 04, 2012 6:08 PM
> To: flex-dev@incubator.apache.org
> Subject: Re: Falcon SDKSWCTests
>
> Ok, I've submitted a patch for that (
> https://issues.apache.org/jira/browse/FLEX-33286). I've checked and those
> were the only projects including that file.
>
> I've also checked, and the content of version.properties always seems to
> be "build=0". I've even compiled without including the file and everything
> seems to be working. Could we just remove those references completely or
> there may be some other side effects?
>
> Chema
>
> 2012/12/5 Gordon Smith <go...@adobe.com>
>
> > In that case, let's move -include-file option for version.properties
> > back out of compile-config.xml and into the <compc> task.
> >
> > - Gordon
> >
> > -----Original Message-----
> > From: Chema Balsas [mailto:jbalsas@gmail.com]
> > Sent: Tuesday, December 04, 2012 5:22 PM
> > To: flex-dev@incubator.apache.org
> > Subject: Re: Falcon SDKSWCTests
> >
> > Hi Cyril,
> >
> > The version.properties file is created and removed inside the compile
> > target for those projects.
> >
> > It is generated at the beginning of the target by:
> > <echo file="${FLEX_HOME}/frameworks/version.properties"
> > append="false">build=${build.number}</echo>
> >
> > And then removed at the end by:
> > <delete file="${FLEX_HOME}/frameworks/version.properties"/>
> >
> > which is why you shouldn't find it ;)
> >
> > 2012/12/5 Cyrill Zadra <cy...@gmail.com>
> >
> > > Hey Chema
> > >
> > > In the follwing compile-config.xml is the version.properties included.
> > >
> > > rpc
> > > spark
> > > spark_dmv
> > >
> > > <include-file>
> > > <name>version.properties</name>
> > > <path>../../version.properties</path>
> > > </include-file>
> > >
> > > In my builded flex sdk it does not exists. Is that part really used
> > > or can it be removed? Or does anyone know how this
> > > version.properties is generated?
> > >
> > > Cyrill
> > >
> > >
> > >
> > >
> > > On Mon, Dec 3, 2012 at 8:16 AM, Chema Balsas <jb...@gmail.com>
> wrote:
> > > > @Cyril Thanks for noticing!
> > > >
> > > > @Gordon You're welcome! I'm really happy to see all this movement
> > > > around Falcon/FalconJS lately :)
> > > >
> > > >
> > > > 2012/12/1 Gordon Smith <go...@adobe.com>
> > > >
> > > >> Oops! Thank you @Chema!
> > > >>
> > > >> Sent from my iPad
> > > >>
> > > >> On Nov 30, 2012, at 7:09 PM, "Cyrill Zadra"
> > > >> <cy...@gmail.com>
> > > >> wrote:
> > > >>
> > > >> > Hi Gordon
> > > >> >
> > > >> >> @Cyril: Thanks for your help with introducing the
> > > >> >> compile-config.xml
> > > >> files so that we can more easily make Falcon JUnit tests that
> > > >> compile
> > > each
> > > >> SDK SWC.
> > > >> >
> > > >> > That wasn't me .. I think that work was done by Chema Balsas
> > > >> > (see
> > > [1]).
> > > >> >
> > > >> > [1] https://issues.apache.org/jira/browse/FLEX-33226
> > > >> >
> > > >> > On Fri, Nov 30, 2012 at 1:09 PM, Gordon Smith
> > > >> > <go...@adobe.com>
> > > wrote:
> > > >> >> @Cyril: Thanks for your help with introducing the
> > > >> >> compile-config.xml
> > > >> files so that we can more easily make Falcon JUnit tests that
> > > >> compile
> > > each
> > > >> SDK SWC.
> > > >> >>
> > > >> >> Now that we have one such test - for compiling framework.swc -
> > > passing,
> > > >> would anybody like to work on investigating the status of other
> > > >> tests
> > > that
> > > >> compile rpc.swc, mx.swc, spark.swc, etc.? We need to figure out
> > > >> whether
> > > the
> > > >> SDK source code needs to change because Falcon is pickier than
> > > >> the old compiler, or whether Falcon has AS bugs that need to be
> fixed.
> > > >> >>
> > > >> >> - Gordon
> > > >> >>
> > > >>
> > >
> >
>
RE: Falcon SDKSWCTests
Posted by Gordon Smith <go...@adobe.com>.
If Apache doesn't care about that we should just drop it. It seems strange to have it in some SWCs and not others.
- Gordon
-----Original Message-----
From: Gordon Smith [mailto:gosmith@adobe.com]
Sent: Tuesday, December 04, 2012 6:21 PM
To: flex-dev@incubator.apache.org
Subject: RE: Falcon SDKSWCTests
I think Adobe's build machines had some scripts that set build.number to the Perforce revision number that it was building.
- Gordon
-----Original Message-----
From: Chema Balsas [mailto:jbalsas@gmail.com]
Sent: Tuesday, December 04, 2012 6:08 PM
To: flex-dev@incubator.apache.org
Subject: Re: Falcon SDKSWCTests
Ok, I've submitted a patch for that (
https://issues.apache.org/jira/browse/FLEX-33286). I've checked and those were the only projects including that file.
I've also checked, and the content of version.properties always seems to be "build=0". I've even compiled without including the file and everything seems to be working. Could we just remove those references completely or there may be some other side effects?
Chema
2012/12/5 Gordon Smith <go...@adobe.com>
> In that case, let's move -include-file option for version.properties
> back out of compile-config.xml and into the <compc> task.
>
> - Gordon
>
> -----Original Message-----
> From: Chema Balsas [mailto:jbalsas@gmail.com]
> Sent: Tuesday, December 04, 2012 5:22 PM
> To: flex-dev@incubator.apache.org
> Subject: Re: Falcon SDKSWCTests
>
> Hi Cyril,
>
> The version.properties file is created and removed inside the compile
> target for those projects.
>
> It is generated at the beginning of the target by:
> <echo file="${FLEX_HOME}/frameworks/version.properties"
> append="false">build=${build.number}</echo>
>
> And then removed at the end by:
> <delete file="${FLEX_HOME}/frameworks/version.properties"/>
>
> which is why you shouldn't find it ;)
>
> 2012/12/5 Cyrill Zadra <cy...@gmail.com>
>
> > Hey Chema
> >
> > In the follwing compile-config.xml is the version.properties included.
> >
> > rpc
> > spark
> > spark_dmv
> >
> > <include-file>
> > <name>version.properties</name>
> > <path>../../version.properties</path>
> > </include-file>
> >
> > In my builded flex sdk it does not exists. Is that part really used
> > or can it be removed? Or does anyone know how this
> > version.properties is generated?
> >
> > Cyrill
> >
> >
> >
> >
> > On Mon, Dec 3, 2012 at 8:16 AM, Chema Balsas <jb...@gmail.com> wrote:
> > > @Cyril Thanks for noticing!
> > >
> > > @Gordon You're welcome! I'm really happy to see all this movement
> > > around Falcon/FalconJS lately :)
> > >
> > >
> > > 2012/12/1 Gordon Smith <go...@adobe.com>
> > >
> > >> Oops! Thank you @Chema!
> > >>
> > >> Sent from my iPad
> > >>
> > >> On Nov 30, 2012, at 7:09 PM, "Cyrill Zadra"
> > >> <cy...@gmail.com>
> > >> wrote:
> > >>
> > >> > Hi Gordon
> > >> >
> > >> >> @Cyril: Thanks for your help with introducing the
> > >> >> compile-config.xml
> > >> files so that we can more easily make Falcon JUnit tests that
> > >> compile
> > each
> > >> SDK SWC.
> > >> >
> > >> > That wasn't me .. I think that work was done by Chema Balsas
> > >> > (see
> > [1]).
> > >> >
> > >> > [1] https://issues.apache.org/jira/browse/FLEX-33226
> > >> >
> > >> > On Fri, Nov 30, 2012 at 1:09 PM, Gordon Smith
> > >> > <go...@adobe.com>
> > wrote:
> > >> >> @Cyril: Thanks for your help with introducing the
> > >> >> compile-config.xml
> > >> files so that we can more easily make Falcon JUnit tests that
> > >> compile
> > each
> > >> SDK SWC.
> > >> >>
> > >> >> Now that we have one such test - for compiling framework.swc -
> > passing,
> > >> would anybody like to work on investigating the status of other
> > >> tests
> > that
> > >> compile rpc.swc, mx.swc, spark.swc, etc.? We need to figure out
> > >> whether
> > the
> > >> SDK source code needs to change because Falcon is pickier than
> > >> the old compiler, or whether Falcon has AS bugs that need to be fixed.
> > >> >>
> > >> >> - Gordon
> > >> >>
> > >>
> >
>
RE: Falcon SDKSWCTests
Posted by Gordon Smith <go...@adobe.com>.
I think Adobe's build machines had some scripts that set build.number to the Perforce revision number that it was building.
- Gordon
-----Original Message-----
From: Chema Balsas [mailto:jbalsas@gmail.com]
Sent: Tuesday, December 04, 2012 6:08 PM
To: flex-dev@incubator.apache.org
Subject: Re: Falcon SDKSWCTests
Ok, I've submitted a patch for that (
https://issues.apache.org/jira/browse/FLEX-33286). I've checked and those were the only projects including that file.
I've also checked, and the content of version.properties always seems to be "build=0". I've even compiled without including the file and everything seems to be working. Could we just remove those references completely or there may be some other side effects?
Chema
2012/12/5 Gordon Smith <go...@adobe.com>
> In that case, let's move -include-file option for version.properties
> back out of compile-config.xml and into the <compc> task.
>
> - Gordon
>
> -----Original Message-----
> From: Chema Balsas [mailto:jbalsas@gmail.com]
> Sent: Tuesday, December 04, 2012 5:22 PM
> To: flex-dev@incubator.apache.org
> Subject: Re: Falcon SDKSWCTests
>
> Hi Cyril,
>
> The version.properties file is created and removed inside the compile
> target for those projects.
>
> It is generated at the beginning of the target by:
> <echo file="${FLEX_HOME}/frameworks/version.properties"
> append="false">build=${build.number}</echo>
>
> And then removed at the end by:
> <delete file="${FLEX_HOME}/frameworks/version.properties"/>
>
> which is why you shouldn't find it ;)
>
> 2012/12/5 Cyrill Zadra <cy...@gmail.com>
>
> > Hey Chema
> >
> > In the follwing compile-config.xml is the version.properties included.
> >
> > rpc
> > spark
> > spark_dmv
> >
> > <include-file>
> > <name>version.properties</name>
> > <path>../../version.properties</path>
> > </include-file>
> >
> > In my builded flex sdk it does not exists. Is that part really used
> > or can it be removed? Or does anyone know how this
> > version.properties is generated?
> >
> > Cyrill
> >
> >
> >
> >
> > On Mon, Dec 3, 2012 at 8:16 AM, Chema Balsas <jb...@gmail.com> wrote:
> > > @Cyril Thanks for noticing!
> > >
> > > @Gordon You're welcome! I'm really happy to see all this movement
> > > around Falcon/FalconJS lately :)
> > >
> > >
> > > 2012/12/1 Gordon Smith <go...@adobe.com>
> > >
> > >> Oops! Thank you @Chema!
> > >>
> > >> Sent from my iPad
> > >>
> > >> On Nov 30, 2012, at 7:09 PM, "Cyrill Zadra"
> > >> <cy...@gmail.com>
> > >> wrote:
> > >>
> > >> > Hi Gordon
> > >> >
> > >> >> @Cyril: Thanks for your help with introducing the
> > >> >> compile-config.xml
> > >> files so that we can more easily make Falcon JUnit tests that
> > >> compile
> > each
> > >> SDK SWC.
> > >> >
> > >> > That wasn't me .. I think that work was done by Chema Balsas
> > >> > (see
> > [1]).
> > >> >
> > >> > [1] https://issues.apache.org/jira/browse/FLEX-33226
> > >> >
> > >> > On Fri, Nov 30, 2012 at 1:09 PM, Gordon Smith
> > >> > <go...@adobe.com>
> > wrote:
> > >> >> @Cyril: Thanks for your help with introducing the
> > >> >> compile-config.xml
> > >> files so that we can more easily make Falcon JUnit tests that
> > >> compile
> > each
> > >> SDK SWC.
> > >> >>
> > >> >> Now that we have one such test - for compiling framework.swc -
> > passing,
> > >> would anybody like to work on investigating the status of other
> > >> tests
> > that
> > >> compile rpc.swc, mx.swc, spark.swc, etc.? We need to figure out
> > >> whether
> > the
> > >> SDK source code needs to change because Falcon is pickier than
> > >> the old compiler, or whether Falcon has AS bugs that need to be fixed.
> > >> >>
> > >> >> - Gordon
> > >> >>
> > >>
> >
>
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
Ok, I've submitted a patch for that (
https://issues.apache.org/jira/browse/FLEX-33286). I've checked and those
were the only projects including that file.
I've also checked, and the content of version.properties always seems to be
"build=0". I've even compiled without including the file and everything
seems to be working. Could we just remove those references completely or
there may be some other side effects?
Chema
2012/12/5 Gordon Smith <go...@adobe.com>
> In that case, let's move -include-file option for version.properties back
> out of compile-config.xml and into the <compc> task.
>
> - Gordon
>
> -----Original Message-----
> From: Chema Balsas [mailto:jbalsas@gmail.com]
> Sent: Tuesday, December 04, 2012 5:22 PM
> To: flex-dev@incubator.apache.org
> Subject: Re: Falcon SDKSWCTests
>
> Hi Cyril,
>
> The version.properties file is created and removed inside the compile
> target for those projects.
>
> It is generated at the beginning of the target by:
> <echo file="${FLEX_HOME}/frameworks/version.properties"
> append="false">build=${build.number}</echo>
>
> And then removed at the end by:
> <delete file="${FLEX_HOME}/frameworks/version.properties"/>
>
> which is why you shouldn't find it ;)
>
> 2012/12/5 Cyrill Zadra <cy...@gmail.com>
>
> > Hey Chema
> >
> > In the follwing compile-config.xml is the version.properties included.
> >
> > rpc
> > spark
> > spark_dmv
> >
> > <include-file>
> > <name>version.properties</name>
> > <path>../../version.properties</path>
> > </include-file>
> >
> > In my builded flex sdk it does not exists. Is that part really used or
> > can it be removed? Or does anyone know how this version.properties is
> > generated?
> >
> > Cyrill
> >
> >
> >
> >
> > On Mon, Dec 3, 2012 at 8:16 AM, Chema Balsas <jb...@gmail.com> wrote:
> > > @Cyril Thanks for noticing!
> > >
> > > @Gordon You're welcome! I'm really happy to see all this movement
> > > around Falcon/FalconJS lately :)
> > >
> > >
> > > 2012/12/1 Gordon Smith <go...@adobe.com>
> > >
> > >> Oops! Thank you @Chema!
> > >>
> > >> Sent from my iPad
> > >>
> > >> On Nov 30, 2012, at 7:09 PM, "Cyrill Zadra"
> > >> <cy...@gmail.com>
> > >> wrote:
> > >>
> > >> > Hi Gordon
> > >> >
> > >> >> @Cyril: Thanks for your help with introducing the
> > >> >> compile-config.xml
> > >> files so that we can more easily make Falcon JUnit tests that
> > >> compile
> > each
> > >> SDK SWC.
> > >> >
> > >> > That wasn't me .. I think that work was done by Chema Balsas (see
> > [1]).
> > >> >
> > >> > [1] https://issues.apache.org/jira/browse/FLEX-33226
> > >> >
> > >> > On Fri, Nov 30, 2012 at 1:09 PM, Gordon Smith <go...@adobe.com>
> > wrote:
> > >> >> @Cyril: Thanks for your help with introducing the
> > >> >> compile-config.xml
> > >> files so that we can more easily make Falcon JUnit tests that
> > >> compile
> > each
> > >> SDK SWC.
> > >> >>
> > >> >> Now that we have one such test - for compiling framework.swc -
> > passing,
> > >> would anybody like to work on investigating the status of other
> > >> tests
> > that
> > >> compile rpc.swc, mx.swc, spark.swc, etc.? We need to figure out
> > >> whether
> > the
> > >> SDK source code needs to change because Falcon is pickier than the
> > >> old compiler, or whether Falcon has AS bugs that need to be fixed.
> > >> >>
> > >> >> - Gordon
> > >> >>
> > >>
> >
>
RE: Falcon SDKSWCTests
Posted by Gordon Smith <go...@adobe.com>.
In that case, let's move -include-file option for version.properties back out of compile-config.xml and into the <compc> task.
- Gordon
-----Original Message-----
From: Chema Balsas [mailto:jbalsas@gmail.com]
Sent: Tuesday, December 04, 2012 5:22 PM
To: flex-dev@incubator.apache.org
Subject: Re: Falcon SDKSWCTests
Hi Cyril,
The version.properties file is created and removed inside the compile target for those projects.
It is generated at the beginning of the target by:
<echo file="${FLEX_HOME}/frameworks/version.properties"
append="false">build=${build.number}</echo>
And then removed at the end by:
<delete file="${FLEX_HOME}/frameworks/version.properties"/>
which is why you shouldn't find it ;)
2012/12/5 Cyrill Zadra <cy...@gmail.com>
> Hey Chema
>
> In the follwing compile-config.xml is the version.properties included.
>
> rpc
> spark
> spark_dmv
>
> <include-file>
> <name>version.properties</name>
> <path>../../version.properties</path>
> </include-file>
>
> In my builded flex sdk it does not exists. Is that part really used or
> can it be removed? Or does anyone know how this version.properties is
> generated?
>
> Cyrill
>
>
>
>
> On Mon, Dec 3, 2012 at 8:16 AM, Chema Balsas <jb...@gmail.com> wrote:
> > @Cyril Thanks for noticing!
> >
> > @Gordon You're welcome! I'm really happy to see all this movement
> > around Falcon/FalconJS lately :)
> >
> >
> > 2012/12/1 Gordon Smith <go...@adobe.com>
> >
> >> Oops! Thank you @Chema!
> >>
> >> Sent from my iPad
> >>
> >> On Nov 30, 2012, at 7:09 PM, "Cyrill Zadra"
> >> <cy...@gmail.com>
> >> wrote:
> >>
> >> > Hi Gordon
> >> >
> >> >> @Cyril: Thanks for your help with introducing the
> >> >> compile-config.xml
> >> files so that we can more easily make Falcon JUnit tests that
> >> compile
> each
> >> SDK SWC.
> >> >
> >> > That wasn't me .. I think that work was done by Chema Balsas (see
> [1]).
> >> >
> >> > [1] https://issues.apache.org/jira/browse/FLEX-33226
> >> >
> >> > On Fri, Nov 30, 2012 at 1:09 PM, Gordon Smith <go...@adobe.com>
> wrote:
> >> >> @Cyril: Thanks for your help with introducing the
> >> >> compile-config.xml
> >> files so that we can more easily make Falcon JUnit tests that
> >> compile
> each
> >> SDK SWC.
> >> >>
> >> >> Now that we have one such test - for compiling framework.swc -
> passing,
> >> would anybody like to work on investigating the status of other
> >> tests
> that
> >> compile rpc.swc, mx.swc, spark.swc, etc.? We need to figure out
> >> whether
> the
> >> SDK source code needs to change because Falcon is pickier than the
> >> old compiler, or whether Falcon has AS bugs that need to be fixed.
> >> >>
> >> >> - Gordon
> >> >>
> >>
>
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
Hi Cyril,
The version.properties file is created and removed inside the compile
target for those projects.
It is generated at the beginning of the target by:
<echo file="${FLEX_HOME}/frameworks/version.properties"
append="false">build=${build.number}</echo>
And then removed at the end by:
<delete file="${FLEX_HOME}/frameworks/version.properties"/>
which is why you shouldn't find it ;)
2012/12/5 Cyrill Zadra <cy...@gmail.com>
> Hey Chema
>
> In the follwing compile-config.xml is the version.properties included.
>
> rpc
> spark
> spark_dmv
>
> <include-file>
> <name>version.properties</name>
> <path>../../version.properties</path>
> </include-file>
>
> In my builded flex sdk it does not exists. Is that part really used or
> can it be removed? Or does anyone know how this version.properties is
> generated?
>
> Cyrill
>
>
>
>
> On Mon, Dec 3, 2012 at 8:16 AM, Chema Balsas <jb...@gmail.com> wrote:
> > @Cyril Thanks for noticing!
> >
> > @Gordon You're welcome! I'm really happy to see all this movement around
> > Falcon/FalconJS lately :)
> >
> >
> > 2012/12/1 Gordon Smith <go...@adobe.com>
> >
> >> Oops! Thank you @Chema!
> >>
> >> Sent from my iPad
> >>
> >> On Nov 30, 2012, at 7:09 PM, "Cyrill Zadra" <cy...@gmail.com>
> >> wrote:
> >>
> >> > Hi Gordon
> >> >
> >> >> @Cyril: Thanks for your help with introducing the compile-config.xml
> >> files so that we can more easily make Falcon JUnit tests that compile
> each
> >> SDK SWC.
> >> >
> >> > That wasn't me .. I think that work was done by Chema Balsas (see
> [1]).
> >> >
> >> > [1] https://issues.apache.org/jira/browse/FLEX-33226
> >> >
> >> > On Fri, Nov 30, 2012 at 1:09 PM, Gordon Smith <go...@adobe.com>
> wrote:
> >> >> @Cyril: Thanks for your help with introducing the compile-config.xml
> >> files so that we can more easily make Falcon JUnit tests that compile
> each
> >> SDK SWC.
> >> >>
> >> >> Now that we have one such test - for compiling framework.swc -
> passing,
> >> would anybody like to work on investigating the status of other tests
> that
> >> compile rpc.swc, mx.swc, spark.swc, etc.? We need to figure out whether
> the
> >> SDK source code needs to change because Falcon is pickier than the old
> >> compiler, or whether Falcon has AS bugs that need to be fixed.
> >> >>
> >> >> - Gordon
> >> >>
> >>
>
Re: Falcon SDKSWCTests
Posted by Cyrill Zadra <cy...@gmail.com>.
Hey Chema
In the follwing compile-config.xml is the version.properties included.
rpc
spark
spark_dmv
<include-file>
<name>version.properties</name>
<path>../../version.properties</path>
</include-file>
In my builded flex sdk it does not exists. Is that part really used or
can it be removed? Or does anyone know how this version.properties is
generated?
Cyrill
On Mon, Dec 3, 2012 at 8:16 AM, Chema Balsas <jb...@gmail.com> wrote:
> @Cyril Thanks for noticing!
>
> @Gordon You're welcome! I'm really happy to see all this movement around
> Falcon/FalconJS lately :)
>
>
> 2012/12/1 Gordon Smith <go...@adobe.com>
>
>> Oops! Thank you @Chema!
>>
>> Sent from my iPad
>>
>> On Nov 30, 2012, at 7:09 PM, "Cyrill Zadra" <cy...@gmail.com>
>> wrote:
>>
>> > Hi Gordon
>> >
>> >> @Cyril: Thanks for your help with introducing the compile-config.xml
>> files so that we can more easily make Falcon JUnit tests that compile each
>> SDK SWC.
>> >
>> > That wasn't me .. I think that work was done by Chema Balsas (see [1]).
>> >
>> > [1] https://issues.apache.org/jira/browse/FLEX-33226
>> >
>> > On Fri, Nov 30, 2012 at 1:09 PM, Gordon Smith <go...@adobe.com> wrote:
>> >> @Cyril: Thanks for your help with introducing the compile-config.xml
>> files so that we can more easily make Falcon JUnit tests that compile each
>> SDK SWC.
>> >>
>> >> Now that we have one such test - for compiling framework.swc - passing,
>> would anybody like to work on investigating the status of other tests that
>> compile rpc.swc, mx.swc, spark.swc, etc.? We need to figure out whether the
>> SDK source code needs to change because Falcon is pickier than the old
>> compiler, or whether Falcon has AS bugs that need to be fixed.
>> >>
>> >> - Gordon
>> >>
>>
Re: Falcon SDKSWCTests
Posted by Chema Balsas <jb...@gmail.com>.
@Cyril Thanks for noticing!
@Gordon You're welcome! I'm really happy to see all this movement around
Falcon/FalconJS lately :)
2012/12/1 Gordon Smith <go...@adobe.com>
> Oops! Thank you @Chema!
>
> Sent from my iPad
>
> On Nov 30, 2012, at 7:09 PM, "Cyrill Zadra" <cy...@gmail.com>
> wrote:
>
> > Hi Gordon
> >
> >> @Cyril: Thanks for your help with introducing the compile-config.xml
> files so that we can more easily make Falcon JUnit tests that compile each
> SDK SWC.
> >
> > That wasn't me .. I think that work was done by Chema Balsas (see [1]).
> >
> > [1] https://issues.apache.org/jira/browse/FLEX-33226
> >
> > On Fri, Nov 30, 2012 at 1:09 PM, Gordon Smith <go...@adobe.com> wrote:
> >> @Cyril: Thanks for your help with introducing the compile-config.xml
> files so that we can more easily make Falcon JUnit tests that compile each
> SDK SWC.
> >>
> >> Now that we have one such test - for compiling framework.swc - passing,
> would anybody like to work on investigating the status of other tests that
> compile rpc.swc, mx.swc, spark.swc, etc.? We need to figure out whether the
> SDK source code needs to change because Falcon is pickier than the old
> compiler, or whether Falcon has AS bugs that need to be fixed.
> >>
> >> - Gordon
> >>
>
Re: Falcon SDKSWCTests
Posted by Gordon Smith <go...@adobe.com>.
Oops! Thank you @Chema!
Sent from my iPad
On Nov 30, 2012, at 7:09 PM, "Cyrill Zadra" <cy...@gmail.com> wrote:
> Hi Gordon
>
>> @Cyril: Thanks for your help with introducing the compile-config.xml files so that we can more easily make Falcon JUnit tests that compile each SDK SWC.
>
> That wasn't me .. I think that work was done by Chema Balsas (see [1]).
>
> [1] https://issues.apache.org/jira/browse/FLEX-33226
>
> On Fri, Nov 30, 2012 at 1:09 PM, Gordon Smith <go...@adobe.com> wrote:
>> @Cyril: Thanks for your help with introducing the compile-config.xml files so that we can more easily make Falcon JUnit tests that compile each SDK SWC.
>>
>> Now that we have one such test - for compiling framework.swc - passing, would anybody like to work on investigating the status of other tests that compile rpc.swc, mx.swc, spark.swc, etc.? We need to figure out whether the SDK source code needs to change because Falcon is pickier than the old compiler, or whether Falcon has AS bugs that need to be fixed.
>>
>> - Gordon
>>
Re: Falcon SDKSWCTests
Posted by Cyrill Zadra <cy...@gmail.com>.
Hi Gordon
> @Cyril: Thanks for your help with introducing the compile-config.xml files so that we can more easily make Falcon JUnit tests that compile each SDK SWC.
That wasn't me .. I think that work was done by Chema Balsas (see [1]).
[1] https://issues.apache.org/jira/browse/FLEX-33226
On Fri, Nov 30, 2012 at 1:09 PM, Gordon Smith <go...@adobe.com> wrote:
> @Cyril: Thanks for your help with introducing the compile-config.xml files so that we can more easily make Falcon JUnit tests that compile each SDK SWC.
>
> Now that we have one such test - for compiling framework.swc - passing, would anybody like to work on investigating the status of other tests that compile rpc.swc, mx.swc, spark.swc, etc.? We need to figure out whether the SDK source code needs to change because Falcon is pickier than the old compiler, or whether Falcon has AS bugs that need to be fixed.
>
> - Gordon
>