Yes they do test against other stuff, but the released versions of them ... In all of your examples are run against released versions. If for example we would test against the last released version, this would be fine, but we are testing one unreleased version against another unreleased version and that's where the Hen-Eg-Problem comes from.
Chris ________________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Dienstag, 29. März 2016 16:57 An: dev@flex.apache.org Betreff: Re: AW: [DISCUSS] How about bringing Falcon and ASJS together? On 3/29/16, 6:18 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Replying to the last message, before the thread was hijacked ;-) > >I don't quite get what you mean with the validation-suites ... Perhaps the term "compatibility suite" would be better? I know that before Flash ships a release, there is a bunch of testing on existing SWFs. IMO, before Falcon ships, there should be testing against the AS code in the Flex and FlexJS SDK. And I know that before Windows ships, it tests against a bunch of existing apps. >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 IMO, the definition of downstream has only to do with the actual functional code and not the tests. Most, if not all frameworks are downstream of their compilers and tools. > >Or we remove the dependency on ASJS from Falcon and start releasing >things separately and independently. Again, I think it is just a test dependency. If the code that was in compiler or compiler.jx actually needs code flex-asjs to run, that would be a problem that definitely needs to be fixed. Because I see multiple customers for Falcon and FalconJX, I think they shouldn't be tied to what is in flex-asjs. So my question reworded is, don't any Maven projects run tests against downstream projects to make sure they didn't break them or to make sure those downstream users code bases still work with the latest changes? -Alex
