Well I did some great progress in the train today. I managed to setup a script that moves stuff around into a Maven structure and wrote a pom.xml that does all of the generation steps (JFlex, Antlr2, Antlr3, JBurg) in Maven.
If all goes well, all you should need to do, would be to run the migration script and run "mvn install". But I need to do a little refactoring as jburg currently needs some classes of the same project compiled in order to run. Need to move them in a separate jar. Let's see how far I come 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 <aha...@adobe.com> 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:33 AM, "Harbs" <harbs.li...@gmail.com> 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 you’re doing. Agreed. If this is what you need to do to make progress, it sound reasonable to me. I will say, though, that Git handled renames much better than I expected when doing the refactor for flex-asjs. So if you think it is better to just take a branch and work there, that is also fine with me. I don't have major changes planned for flex-falcon at this time. Are you planning to change the set of dependencies or just make sure they are all sourced from Maven Central? When it does become time to try to apply the script to the develop branch for real, I would do it in a branch anyway. There will be conflicts where we both changed a file, but I think I will know enough to resolve them quickly. -Alex
