Replying to the last message, before the thread was hijacked ;-) I don't quite get what you mean with the validation-suites ... but I guess the definition of downstream is what I'm having a problem with: - ASJS is compiled using Falcon, let's call ASJS downstream from Falcon. - Falcon needs ASJS in order to run it's tests, so let's call Falcon downstream from ASJS. So if we think of this mathematically: (Falcon <= ASJS) && (ASJS <= Falcon) --> ASJS == Falcon
In order to run the release build correctly both projects must be in the same reactor build or the build will fail. But then too the tests in falcon.jx must be moved into a separate testsuite artifact. We could use GIT submodules, to mount ASJS inside Falcon and hereby create a valid build. As soon as FlexJS is completely migrated to Maven, I guess I could make the same happen for the old SDK. We could then use GIT submodules to mount that in Falcon and create different assemblies for "Just Compiler", "FlexJS" and "Flex". Or we remove the dependency on ASJS from Falcon and start releasing things separately and independently. Chris ________________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Sonntag, 27. März 2016 16:31 An: dev@flex.apache.org Betreff: Re: [DISCUSS] How about bringing Falcon and ASJS together? We've had this discussion before. Falcon was also intended to be the next-generation compiler for the regular Flex SDK, and FalconJX is being considered for other non-Apache frameworks like Feathers. Is it really true that no Maven projects have validation suites against downstream projects? Maybe the integration tests need to be in a different repo or something? -Alex On 3/27/16, 2:38 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Hi, > > >I don't know if we had this discussion recently, but I would like to >propose to bring together the two sub-projects Falcon and ASJS. The >reason for this is that they are naturally tightly connected, which >becomes obvious every time a release is coming and internally a lot of >tests depend on ASJS and ASJS needs Falcon to be built. This entanglement >makes it hard do releases Maven-style. Bringing both together should make >a lot of things easier. > > >If the problem is adjusting the build for the merged project, I could >disable the cross-cutting tests (as I already have) and do the same Maven >conversion for ASJS. As soon as that's done it should be easy to merge >both parts. > > >And I would propose to name the project "FlexJS". > > >What do you think? > > >Chris
