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.
You won't be able to build the project at the moment, cause I have to release the jburg-maven-plugin and a new version of JBurg, that doesn't use the system classloader. As soon as that's done you should all be able to build the project with Maven. I also started migrating the unit-tests (moving them from the separate projects in with the modules they are designed to test: compiler.teste --> compiler compiler.jx.teste --> compiler.jx Unfortunately not a single test is passing at the moment. I will probably have to do a little refactoring of the tests themselves as they use some assumptions, that don't fit well with maven (create temp fils in a directory called "temp" ... should probably be changed to "target/temp". I also re-wrote 3 of the source-generators that we were using. I think two of them needed the compiled classes which sort of produces a cycle and adds unneeded complexity. So I replaced them with versions that do the same thing, but use the source files as input. My next goal will be to make the unit-tests run. And one thing ... what's the compiler.js directory? Is this needed at the moment or is this an old experiment that's no longer maintained? Chris ________________________________________ Von: Christofer Dutz <christofer.d...@c-ware.de> 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 with falcon I can see 3 or 4 artifacts, all bundled to a distribution. We would just have a few nite jars in that package. Chris Von meinem Samsung Galaxy Smartphone gesendet. -------- Ursprüngliche Nachricht -------- Von: Justin Mclean <justinmcl...@me.com> 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 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, Justin
