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
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,
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
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
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
you’re doing.
Harbs
On Feb 18, 2016, at 3:4
I’m not an expert on resolving conflicts in Git, but my understanding is that
it’s possible to resolve code conflicts even in moved files.
As I understand things, it should be possible to:
1. Create a new “maven” branch.
2. Move files around in the new branch.
3. Make changes to the original file
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
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
12 matches
Mail list logo
