On Tue, Feb 16, 2016 at 4:17 AM, Harbs wrote:
> OK.
>
> It looks like my problem was due to some outdated files from previous
> compilations.
>
> I completely removed the flex-falcon folder and checked out a fresh copy
> of the repo, and my problems seem to have gone away.
>
I just ran into this
On 2/24/16, 12:08 AM, "Christofer Dutz" wrote:
>Hi Alex,
>
>that sounds as if you are using assertions in a way that contradictory to
>what they are intended to be used.
It isn't me. I did not write this code or review it. Before Flex moved
to Apache, I had made maybe a half-dozen changes to
reff: AW: AW: AW: AW: [FALCONJX]Compiling Falcon with externs problems
Hi Alex,
that sounds as if you are using assertions in a way that contradictory to what
they are intended to be used.
Assertions are meant to be hard checks to the contract of a method. Assumptions
the code needs to operate correctl
unctionNode_empty1:57 getValue() shouldn't
>be getting called on a non-expression MXMLFunctionNode
>
>Do you have an idea, why they are red?
>
>Chris
>
>
>
>
>Von: Alex Harui
>Gesendet: Dienstag, 23. Februar 2016 17:53
: Re: AW: AW: AW: [FALCONJX]Compiling Falcon with externs problems
On 2/23/16, 9:26 AM, "Christofer Dutz" wrote:
>Hi Alex,
>
>Well I think that's something completely different. I never knew you
>could setup Eclipse to run every test each time you save, but that so
On 2/23/16, 9:26 AM, "Christofer Dutz" wrote:
>Hi Alex,
>
>Well I think that's something completely different. I never knew you
>could setup Eclipse to run every test each time you save, but that sort
>of doesn't seem to make much sense to me. Isn't Eclipse already slow
>enough? ;-)
I guess I
ouldn't
>be getting called on a non-expression MXMLFunctionNode
>
>Do you have an idea, why they are red?
>
>Chris
>
>
>
>
>Von: Alex Harui
>Gesendet: Dienstag, 23. Februar 2016 17:53
>An: dev@flex.apache.org
>Betr
Von: Alex Harui
Gesendet: Dienstag, 23. Februar 2016 17:53
An: dev@flex.apache.org
Betreff: Re: AW: AW: [FALCONJX]Compiling Falcon with externs problems
On 2/23/16, 7:56 AM, "Christofer Dutz" wrote:
>Looking better and better each day :-
On 2/23/16, 7:56 AM, "Christofer Dutz" wrote:
>Looking better and better each day :-)
>
>With my adjusted base-class I get this:
>
>Tests run: 375, Failures: 8, Errors: 0, Skipped: 26
Good progress.
I have a question about the Eclipse projects. Will we have to get rid of
them and make Eclips
On 2/23/16, 5:24 AM, "Christofer Dutz" wrote:
>Ok ... so today I started having a look at the Unit tests. Turns out the
>reason for them failing is quite obvious :-)
>The test classes make heavy uses of those Environment Variables that I am
>so unhappy with to build the paths to the swc files o
Chris
Von: Christofer Dutz
Gesendet: Freitag, 19. Februar 2016 21:50
An: dev@flex.apache.org
Betreff: AW: AW: [FALCONJX]Compiling Falcon with externs problems
Ok ... so what do you think of this? ;-)
[INFO]
Dutz
Gesendet: Freitag, 19. Februar 2016 21:50
An: dev@flex.apache.org
Betreff: AW: AW: [FALCONJX]Compiling Falcon with externs problems
Ok ... so what do you think of this? ;-)
[INFO]
[INFO] BUILD SUCCESS
Gesendet: Montag, 22. Februar 2016 06:44
An: dev@flex.apache.org
Betreff: Re: AW: [FALCONJX]Compiling Falcon with externs problems
On 2/21/16, 11:38 AM, "Christofer Dutz" wrote:
>Ok,
>
>so I just created a new branch for falcon "feature/maven-migration" and
>I c
On 2/21/16, 11:38 AM, "Christofer Dutz" wrote:
>Ok,
>
>so I just created a new branch for falcon "feature/maven-migration" and I
>comitted my changes there.
>I can currently build compiler, compiler.jx and flex-compiler-oem using
>maven.
Sounds promising!
>
>And one thing ... what's the comp
__
Von: Christofer Dutz
Gesendet: Sonntag, 21. Februar 2016 12:41
An: dev@flex.apache.org
Betreff: AW: [FALCONJX]Compiling Falcon with externs problems
No
I the flex sdk today we don't release every jar separately. It consists of
several libs and all are released together. Currently f wit
alaxy Smartphone gesendet.
Ursprüngliche Nachricht
Von: Justin Mclean
Datum: 21.02.2016 10:16 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: [FALCONJX]Compiling Falcon with externs problems
Hi,
> I didn't say that we shouldn't bundle it, I just said that we s
Hi,
> I didn't say that we shouldn't bundle it, I just said that we shouldn't put
> it inside the compiler artifact. And just have it in a separate jar.
A separate jar would mean a different release right? So I guess your breaking
it up into multiple releases that depend on each other?
Thanks,
6 09:43 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: [FALCONJX]Compiling Falcon with externs problems
Hi,
> You should never bundle build code with your product. In the Maven world "yet
> another artifact" usually doesn't matter, cause the tool takes care of
> manag
Hi,
> You should never bundle build code with your product. In the Maven world "yet
> another artifact" usually doesn't matter, cause the tool takes care of
> managing this.
Possible there an excerption here for Apache policy? i.e. source releases need
to be able to be compiled so general need
naging this.
Chris
Von: Alex Harui
Gesendet: Samstag, 20. Februar 2016 17:45
An: dev@flex.apache.org
Betreff: Re: AW: AW: AW: [FALCONJX]Compiling Falcon with externs problems
On 2/20/16, 7:32 AM, "Christofer Dutz" wrote:
>Another thing I just noticed:
>We have eve
On 2/20/16, 7:32 AM, "Christofer Dutz" wrote:
>Another thing I just noticed:
>We have even more tools that are needed during the build:
>- AnnotateClass.java
>- ProblemEnumGenerator.java
>- ProblemLocalizer.java
>
>So I guess it would be good if I just moved those 3 together with the
>UnknownTr
2016 07:47
An: dev@flex.apache.org
Betreff: Re: AW: AW: [FALCONJX]Compiling Falcon with externs problems
On 2/19/16, 12:50 PM, "Christofer Dutz" wrote:
>Ok ... so what do you think of this? ;-)
>
>[INFO]
>
too many holes ... I might end up in one ;-)
Chris
____
Von: Alex Harui
Gesendet: Samstag, 20. Februar 2016 07:47
An: dev@flex.apache.org
Betreff: Re: AW: AW: [FALCONJX]Compiling Falcon wi
On 2/19/16, 12:50 PM, "Christofer Dutz" wrote:
>Ok ... so what do you think of this? ;-)
>
>[INFO]
>
>[INFO] BUILD SUCCESS
>[INFO]
>
>[INFO] Total ti
ustom one ...
think that's not really nice for useablity. But for now I'll focus on the maven
migration.
Chris
Von: Alex Harui
Gesendet: Freitag, 19. Februar 2016 07:00
An: dev@flex.apache.org
Betreff: Re: AW: [FALCONJX]Compiling Falcon with
e in the next few days. As soon as the compiler
>module is done, I'd continue with the others.
>
>Chris
>
>
>
>Von meinem Samsung Galaxy Smartphone gesendet.
>
>
> Ursprüngliche Nachricht ----
>Von: Alex Harui
>Datum: 18.02.2016 16:18 (GMT+01:
e, I'd continue with the others.
Chris
Von meinem Samsung Galaxy Smartphone gesendet.
Ursprüngliche Nachricht
Von: Alex Harui
Datum: 18.02.2016 16:18 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: [FALCONJX]Compiling Falcon with externs problems
On 2/18/16, 6:3
On 2/18/16, 6:33 AM, "Harbs" wrote:
>From my perspective, any solution to make this happen and allow progress
>to be made on Falcon is good.
>
>The migration script sounds like a good idea. It actually might have a
>side-benefit that folks like me can read the script to help understand
>what yo
fer Dutz
> Gesendet: Donnerstag, 18. Februar 2016 13:50
> An: dev@flex.apache.org
> Betreff: AW: AW: [FALCONJX]Compiling Falcon with externs problems
>
> As I said in the other Mail, I can't just change these thing as you guys are
> working on develop.
>
> That
working on a branch.
But I guess with this strategy it should work, what do you think?
Chris
Von: Christofer Dutz
Gesendet: Donnerstag, 18. Februar 2016 13:50
An: dev@flex.apache.org
Betreff: AW: AW: [FALCONJX]Compiling Falcon with externs problems
As I sa
obile phones while being at the Hotel breakfast sort of sucks)
>
> Chris
>
>
> Von: Alex Harui
> Gesendet: Donnerstag, 18. Februar 2016 08:57
> An: dev@flex.apache.org
> Betreff: Re: AW: [FALCONJX]Compiling Falcon with externs
writing
emails on mobile phones while being at the Hotel breakfast sort of sucks)
Chris
Von: Alex Harui
Gesendet: Donnerstag, 18. Februar 2016 08:57
An: dev@flex.apache.org
Betreff: Re: AW: [FALCONJX]Compiling Falcon with externs problems
On 2/17/16, 1
On 2/17/16, 11:14 PM, "Christofer Dutz" wrote:
>I'm currently not contributing, choose it's impossible to setup. And I'm
>just fed up with the build and could even work through the quirks. I just
>don't want to anymore.
>
> As justin said, I have a paid job where I have to deal with that sort o
ven training ;-)
Chris
Von meinem Samsung Galaxy Smartphone gesendet.
Ursprüngliche Nachricht
Von: Harbs
Datum: 17.02.2016 19:21 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: [FALCONJX]Compiling Falcon with externs problems
Except, people are only going to contribute once it
On 2/16/16, 11:04 PM, "Christofer Dutz" wrote:
>Ok ... if it's all about YOUR priorities I can wait
Well, if you are expecting me to do the work, then yes, it is about my
priorities. But my priorities are based on what I think the community
wants based on what I read on this mailing list and
Gesendet: Mittwoch, 17. Februar 2016 07:25
> An: dev@flex.apache.org
> Betreff: Re: AW: [FALCONJX]Compiling Falcon with externs problems
>
> On 2/16/16, 3:01 PM, "Christofer Dutz" wrote:
>
> >Hi,
> >
> >these are exactly the type of problems I was so sick of :-( Pr
working on ASJS doesn't make any
sense)
Chris
Von: Alex Harui
Gesendet: Mittwoch, 17. Februar 2016 07:25
An: dev@flex.apache.org
Betreff: Re: AW: [FALCONJX]Compiling Falcon with externs problems
On 2/16/16, 3:01 PM, "Christofer Dutz"
Except, people are only going to contribute once it has enough features to
really interest them.
Right now, all it really needs is some better “getting started with
contributing” documentation for people wanting to help. I could write that (now
that I worked out my issues). I’d rather have Alex
Hi,
> How many days should I invest in learning build systems vs developing new
> features?
Hypothetical question. If a day of your (paid) work means that more people can
contribite to the project isn’t that a good outcome for the project? Community
over code and all that.
Thanks,
Justin
Glad you got it to work. Somehow, I messed up my Git commands and the
env.properties change for flex-falcon got stashed instead of committed. I
just pushed It now, so you shouldn't need unittest.properties any more.
An env.properties file will override unittest.properties.
-Alex
On 2/16/16, 4:3
On 2/16/16, 3:01 PM, "Christofer Dutz" wrote:
>Hi,
>
>these are exactly the type of problems I was so sick of :-( Probably I
>was cursed by them more often, cause I didn't update my project that
>often. How about we do the same update of the directory structure as with
>some of the ASJS directo
eve a more common understanding for the topic, which would definitely
benefit the project greatly cause we could actually start working in the same
direction.
Chris
Von: Harbs
Gesendet: Dienstag, 16. Februar 2016 13:17
An: dev@flex.apache.org
Betreff:
Yay!
I got asjs to compile and XML compiles as well. The build failed because of
errors, but at least the errors make sense.
I can now get back to work. Phew!
Thanks Alex for bearing with me… ;-)
FWIW, I put together some instructions in a Google Doc with things that tripped
me up. I’ll put i
OK.
It looks like my problem was due to some outdated files from previous
compilations.
I completely removed the flex-falcon folder and checked out a fresh copy of the
repo, and my problems seem to have gone away.
I just got a successful build of falcon! :-)
Trying to compile asjs now…
On Fe
Renaming this because this has nothing to do with XML.
I’ve been trying various things related to the externs and nothing I’m doing
seems to be right.
1. Running it with all my existing externs files causes an error that Window
and Console are undefined.
2. Removing the js externs files causes
45 matches
Mail list logo
