nt: Tuesday, November 20, 2012 1:02 PM
> To: flex-dev@incubator.apache.org
> Subject: Re: Falcon compiler(.tests) building
>
> Gordon uses a Windows machine and the tests have some backslashes in the
> paths so the fail on Mac.
>
> What is the proper way to deal with slashes on
I think we can simply use forward slashes..
- Gordon
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Tuesday, November 20, 2012 1:02 PM
To: flex-dev@incubator.apache.org
Subject: Re: Falcon compiler(.tests) building
Gordon uses a Windows machine and the tests have
@incubator.apache.org
Subject: Re: Falcon compiler(.tests) building
Well, at least I know I'm not crazy, since you see the same failures ;-)
I'll wait for Gordon and meanwhile do a bit of the new website.
EdB
On Tue, Nov 20, 2012 at 5:15 PM, Carol Frampton wrote:
> Erik,
>
>
Looks like Carol fixed. I get all tests passing now on Mac. Yay!
On 11/20/12 1:11 PM, "Michael Schmalle" wrote:
> Carol,
>
> I can fix these, how would you suggest? Just using + concatenation? or
> StringBuffer?
>
> Mike
>
> Quoting Carol Frampton :
>
>> File.separatorChar
>>
>>
>> On 1
Carol,
I can fix these, how would you suggest? Just using + concatenation? or
StringBuffer?
Mike
Quoting Carol Frampton :
File.separatorChar
On 11/20/12 4 :01PM, "Alex Harui" wrote:
Gordon uses a Windows machine and the tests have some backslashes in the
paths so the fail on Mac.
Wha
File.separatorChar
On 11/20/12 4 :01PM, "Alex Harui" wrote:
>Gordon uses a Windows machine and the tests have some backslashes in the
>paths so the fail on Mac.
>
>What is the proper way to deal with slashes on different platforms in
>Java?
>If you know, you can fix the code in
>compiler.tests/
I would guess that it is File.separator
Mike
Quoting Alex Harui :
Gordon uses a Windows machine and the tests have some backslashes in the
paths so the fail on Mac.
What is the proper way to deal with slashes on different platforms in Java?
If you know, you can fix the code in
compiler.tests/
Gordon uses a Windows machine and the tests have some backslashes in the
paths so the fail on Mac.
What is the proper way to deal with slashes on different platforms in Java?
If you know, you can fix the code in
compiler.tests/unit-tests/org/apache/flex/compiler/internal/tree/mxml/MXMLNo
deBaseTes
Well, at least I know I'm not crazy, since you see the same failures ;-)
I'll wait for Gordon and meanwhile do a bit of the new website.
EdB
On Tue, Nov 20, 2012 at 5:15 PM, Carol Frampton wrote:
> Erik,
>
> I sent just email to Gordon and got back an "out of office" until Monday
> email so yo
Erik,
I sent just email to Gordon and got back an "out of office" until Monday
email so you'll either have to wait or debug it.
Carol
On 11/20/12 7 :17AM, "Erik de Bruin" wrote:
>Just guessing now, but: the MXML is read from a file in the 'temp'
>dir, right? If I put a breakpoint somewhere, I
On 11/20/12 6 :54AM, "Erik de Bruin" wrote:
>Latest news:
>
>- I got myself a new working copy of the entire Flex SVN repo, so I
>don't need to mess with paths etc. anymore.
>- I did a build of the SDK in 'branches/develop' without problems.
>- I did a build of the Falcon compiler ('ant main' i
Just guessing now, but: the MXML is read from a file in the 'temp'
dir, right? If I put a breakpoint somewhere, I can see those files are
created and the contents that I can see seem to be correct. But what
about the contents that are not immediately visible? There was a lot
to do about line ending
I did exactly what you now tried; checkout the whole Apache project,
build framework and build compiler.
The only difference I see here is you are on OSX, but I think Carol is to.
I just ran my tests from the compiler.tests/build.xml and all passed.
Unfortunately, without sitting next to you
Latest news:
- I got myself a new working copy of the entire Flex SVN repo, so I
don't need to mess with paths etc. anymore.
- I did a build of the SDK in 'branches/develop' without problems.
- I did a build of the Falcon compiler ('ant main' in trunk) and got
the EXACT SAME results as before, i.e
Ok,
I did a super-clean and main on the SDK, was successful.
Did a wipe and main on the compiler and compiler.tests, no luck.
I've piped the results of the compiler main to a text file. If anyone
is interested, I'll create a JIRA ticket and attache that file to it.
EdB
On Mon, Nov 19, 2012 at
Thank you! I already figured out the first 3, but not the
'sdk.branch', good suggestion.
EdB
On Mon, Nov 19, 2012 at 4:53 PM, Carol Frampton wrote:
>
>
> On 11/18/12 12 :55PM, "Erik de Bruin" wrote:
>
>>Hi,
>>
>>I have followed the various instructions and was able to successfully
>>build the
I was just about to say something like this.
From his directory structure (unit tests output), it doesn't look
like he checked things out from the full flex svn.
I decided to check out the whole Apache Flex project which took hours
but now I have a whole mirror of the Apache Flex svn on my
Yeah,
I was going to amend what I said about the fileNode not being created,
when I stepped through it I realized your fileNode was created but
there was no children, thats why I pasted the tree structure.
As far as the problem... It has to be an obvious error but I can't
seem to understa
On 11/18/12 12 :55PM, "Erik de Bruin" wrote:
>Hi,
>
>I have followed the various instructions and was able to successfully
>build the Falcon compiler. Along the way I encountered several issues
>that are not yet documented (I'm on OS X 10.8):
>
>- I needed to edit the 'build.xml' file on line 5
Stepped through it, and this is what I found:
A file is created in 'temp', and it has a MXML structure in it
(Sprite->Declaration->[nodeTypeToTest]).
A valid 'fileNode' is created, BUT only the top level node seems to be parsed:
MXMLFileNode(MXMLFileID)
"/Users/erik/Documents/ApacheFlex/svn/apac
Erik,
My advice is get in Eclipse, right click on the MXMLArray test and
Debug as JUnit, have a break point in;
MXMLNodeBaseTests.java at line 129; Step through and then click on the
fileNode variable;
If the output window dosn't show;
MXMLFileNode(MXMLFileID)
"C:\Users\Graphix\project
Ok,
This error means the fileNode is not getting created which means there
is a problem with the compiler.
This explains all your errors.
Are you sure you build the compiler project correctly?
Mike
Quoting Erik de Bruin :
Same result in Terminal.
I do see a 'temp' folder.
In JUnit (whi
> I updated the build.xml file to create the temp folder, did you svn update?
>
> Mike
>
Yes.. I just wanted to make sure it's not the issue in Erik's case.
> So, my environment seems to be set up. Now: how can I help?
>
> Note: I'm a noob on the topic of compilers, but I can copy-paste like
> a Boss, so I'm sure you can use me ;-) Point me to the code and put me
> to work!
>
Hey .. welcome in the club. Same here no compiler expirience. What I
do is t
Same result in Terminal.
I do see a 'temp' folder.
In JUnit (which I'm not intimately familiar with) I do see the
following when I run the first test in MXMLArrayNodeTests.java:
java.lang.NullPointerException
at
org.apache.flex.compiler.internal.tree.mxml.MXMLArrayNodeTests.getMXMLArrayNode(MX
Cyrill,
I updated the build.xml file to create the temp folder, did you svn update?
Mike
Quoting Cyrill Zadra :
Ok.. mhh
How do you execute the junit tests?
With ant script or eclipse?
On Sun, Nov 18, 2012 at 10:54 AM, Erik de Bruin wrote:
Cyrill,
Yes, an empty 'temp' folder exists in t
Eclipse…
Now trying ant in Terminal...
EdB
On Sun, Nov 18, 2012 at 7:58 PM, Cyrill Zadra wrote:
> Ok.. mhh
>
> How do you execute the junit tests?
>
> With ant script or eclipse?
>
> On Sun, Nov 18, 2012 at 10:54 AM, Erik de Bruin wrote:
>> Cyrill,
>>
>> Yes, an empty 'temp' folder exists in
Ok.. mhh
How do you execute the junit tests?
With ant script or eclipse?
On Sun, Nov 18, 2012 at 10:54 AM, Erik de Bruin wrote:
> Cyrill,
>
> Yes, an empty 'temp' folder exists in the root of compile.tests.
>
> So, I reverted the compile.tests back to it's original state and run
> the 'download
Cyrill,
Yes, an empty 'temp' folder exists in the root of compile.tests.
So, I reverted the compile.tests back to it's original state and run
the 'download' target. That indeed also cleared up the missing library
issue. But didn't solve the Failed tests thing :-(
EdB
On Sun, Nov 18, 2012 at 7:4
Hi Erik
> [javac]
> /Users/erik/Documents/ApacheFlex/svn/apacheFlex-falcon/compiler/build.xml:415:
> warning: 'includeantruntime' was not set, defaulting to
> build.sysclasspath=last; set to false for repeatable builds
> Warning: /Users/erik/Documents/ApacheFlex/svn/apacheFlex-sdk/ant/lib does
I'm sure something is wrong in my setup, seeing as my version has the
errors. I'm trying to diagnose it as we 'speak'.
EdB
On Sun, Nov 18, 2012 at 7:32 PM, Michael Schmalle
wrote:
> Usually Eclipse doesn't refresh folders immediately( the results folder is
> created by junit build), press F5 o
Usually Eclipse doesn't refresh folders immediately( the results
folder is created by junit build), press F5 on the compiler.tests
project folder.
Hmm, you need the stack trace in the JUnit view in Eclipse to show you
where exactly the null pointer was.
But let me say this again, I have t
Ha, I just found the 'result' directory, must be 'hidden' in the
Eclipse project…
Here is another snippet:
java.lang.NullPointerException
at
org.apache.flex.compiler.internal.tree.mxml.MXMLArrayNodeTests.getMXMLArrayNode(Unknown
Source)
at
org.apache.flex.compiler.internal.tree.mxml.MXML
Yeah, that is not right, there is something failing in your setup.
Look at the stack traces of the errors.
Mike
Quoting Erik de Bruin :
When running 'compiler.tests', this is a snippet of a failed test:
[junit] Running
org.apache.flex.compiler.internal.tree.mxml.MXMLArrayNodeTests
When running 'compiler.tests', this is a snippet of a failed test:
[junit] Running
org.apache.flex.compiler.internal.tree.mxml.MXMLArrayNodeTests
[junit] Tests run: 7, Failures: 0, Errors: 6, Time elapsed: 0.26 sec
[junit] TEST
org.apache.flex.compiler.internal.tree.mxml.MXMLArrayNod
I do see some warnings on the 'compiler' build:
"[javac]
/Users/erik/Documents/ApacheFlex/svn/apacheFlex-falcon/compiler/build.xml:415:
warning: 'includeantruntime' was not set, defaulting to
build.sysclasspath=last; set to false for repeatable builds"
When I do a 'wipe' and build again, I see o
Hi Erik,
I don't remember that many problems but, I'm not on OSX either.
Running the compiler.tests you should only have 1 failed test being
frameworkSWC() functional test (with warnings no errors), all other
tests should pass as it stands.
- I did get the 'ANT_JAR' problem.
I would have
Hi,
I have followed the various instructions and was able to successfully
build the Falcon compiler. Along the way I encountered several issues
that are not yet documented (I'm on OS X 10.8):
- I needed to edit the 'build.xml' file on line 50, to point the
'sdk.branch' property to the correct loc
38 matches
Mail list logo
