Ok ... if it's all about YOUR priorities I can wait

I know I had Falcon building with Maven quite some time ago, but dropped the 
ball on that cause I had the crazy Idea about migrating everything to Antlr4 at 
the same time. I did create a JBurg Maven plugin and it is now possible to also 
do the JBurg stuff. 

But as long as things are as they are and Environment variables keep others 
from working ... I won't touch the thing (unless to bring it to Maven)

At least I will not conrtribute a single line of code till then (and without 
Falcon being available as Maven artifacts, working on ASJS doesn't make any 
sense)

Chris

________________________________________
Von: Alex Harui <aha...@adobe.com>
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" <christofer.d...@c-ware.de> 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 directories in Falcon too? This way we could make sure
>all generated and compiled stuff is located underneath a "target"
>directory and a simple delete would make sure that any legacy content is
>removed.

I've been pondering what Falcon should look like and how much work it will
take to get there.  flex-asjs was relatively easy because it was
essentially all AS producing SWCs and cross-compiled JS files.  Falcon has
Eclipse configurations, Jburg, Jflex, etc.  Again, I am concerned about
arriving at the San Francisco event with no new features, just a bunch of
files moved around.  Actually execution of the plan might need to wait
until after SF, but I am ready to discuss what goes where now.

>
>And ... I am currently giving a 3-day Maven training for two insurance
>companies ... so my tutorials and slides are fresh and up-to-date. Think
>I'd be able to compress everything into a one day Maven bootcamp
>crash-course. If one of my Talks is selected for ApacheCon, then I'd be
>able to take the trip and I'd be glad to give a free Maven training, if
>there is any Interest in this. I would specially be delighted to give
>Alex and Om such a training so we could achieve a more common
>understanding for the topic, which would definitely benefit the project
>greatly cause we could actually start working in the same direction.

Thanks for the offer, but again, it is a question of priorities.  How many
days should I invest in learning build systems vs developing new features?
 My preference would be to help reorganize the folders but let you do the
maven implementation and try to learn as I need to instead of blocking a
whole day right now.

-Alex

Reply via email to