Ok ... so the hint with the no longer excluded stuff was good ... wonder why I didn't see those changes ... oh well ... builds are back to "blue", so Alex feel free to do stuff.
But it keeps on getting more and more difficult to keep the branches in sync ... would be happy to do the move soon. But I would like to do one rearrangement. Any objections to move the falcon and falcon-jx modules under a "compiler" directory? I would like to have 3 directories in the end "utils", "compiler" and "externs". Each reflecting on major part of the build. If it was possible I would like to link in the asjs repo inside a "framework" directory. The old build sort of had the structure of the final SDK, I would replicate this using Mavens assembly mechanism. Then finished sdks would end up in the target directory of the assembly module. The final structure would be like this: /utils /utils/compiler-build-tools /utils/compiler-jburg-types /utils/flexjs-maven-plugin (Will move code from here to a dedicated flex-maven-plugin repo as soon as it's there) /compiler /compiler/compiler /compiler/compiler-jx /compiler/flex-compiler-oem /compiler/debugger /externs /externs/cordova /externs/createjs /externs/GCL /externs/google_maps /externs/jasmine /externs/jquery /externs/js /externs/node (framework is linked in using Git https://git-scm.com/book/en/v2/Git-Tools-Submodules) /framework /framework/Binding /framework/Charts /framework/Collections /framework/Core /framework/CreateJS /framework/... What do you think? Chris ________________________________________ Von: Christofer Dutz <christofer.d...@c-ware.de> Gesendet: Freitag, 22. April 2016 10:11 An: dev@flex.apache.org Betreff: AW: AW: AW: [FlexJS] Status on Maven migration I'm currently just pulling the jar from the latest SDK release ... anything wrong with that? Haven't worked on the debugger yet as I was going to migrate the non-essential parts after finishing the essential parts. Chris ________________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Donnerstag, 21. April 2016 23:00 An: dev@flex.apache.org Betreff: Re: AW: AW: [FlexJS] Status on Maven migration OK, got through compiler.jx and its tests. I started looking at flex-oem-compiler and noticed it is pulling in the Apache Flex SDK swfutils.jar instead of building a smaller subset that frees FlexJS from dependencies on the Flex SDK. Since the files we need are rarely changed, I am tempted to just check them into a project. Also, they are shared by the debugger project which does not seem to have a pom.xml. I think it would be ok to call this subset swfutils_min. The trick is that the classes in this swfutils subset apparently shared with FlashBuilder, so I think they have to retain their package names. Thoughts? -Alex On 4/21/16, 8:28 AM, "Alex Harui" <aha...@adobe.com> wrote: >Whee! The compiler tests are now working. > >I'm trying to figure out my next task. I'm afraid to sync up and push my >changes since Chris is saying things are broken. And I'm not clear how >desperate Harbs is for a fix for the Jquery thing. IMO, getting the Maven >branches merged into develop is the top priority. > >My current thinking is for me to plow ahead on the rest of the Ant build >without syncing up, then when I get through that I'll sync up and see if >the Ant build has the same problems Chris is seeing. Chris can you work >with an older revision of flex-falcon for now to make progress on >flex-asjs? > >-Alex > >On 4/21/16, 7:50 AM, "Alex Harui" <aha...@adobe.com> wrote: > >> >> >>On 4/21/16, 1:38 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >> >>>Ok ... so today I'm feeling like I'm wasting my time again :-( >>> >>>I merged the changes from develop up to my feature/maven-migration-test >>>... unfortunately I had do manually merge quite some stuff, but that's >>>ok. Now my build no longer worked. The Externs no longer compiled. So I >>>switched to my Ant version, updated and did a "clean-all" and "all" >>>build >>>... this too didn't work, even if I got different errors. So as a >>>measure >>>of last resort, I did that "wipe-all" and then an "all" build. Now at >>>least the Ant build worked again. Unfortunately I couldn't see what has >>>changed :-( >> >>What was the error you got? >> >>> >>>Could you guys please post to this list if you change any downloads or >>>change things in the build? It's one thing to port something, but it's a >>>completely different thing to find problems that now occur in a >>>previously ported part :-( >>> >>>I think it would eventually be a good idea to do the maven switch pretty >>>soon cause I'm loosing more and more of my time in keeping things in >>>sync >>>... time I would prefer to be investing on pushing the migration of ASJS >>>forward. >> >>I'm still work on the Ant build in maven-migration-test. I got through >>compiler-build-tools and compiler-jburg-types and most of compiler, but >>am >>currently on compiler/src/test. Then on to compiler.jx, and the externs >>and other things. Hope to be done with it maybe Monday. >> >>-Alex >> >
