Hmmm, but this way an old SDK won‘t be able to recieve updates to the unit-test framework. I think we shouldn't put everything in the sdk and give users the choice.
I think there were several packages available ... eventually we could do a normal build that works with most recent FDKs and one with "classifier" "legacy" package for older FDKs. During a normal release ... where would you download the source package? From the jenkins workspace? If yes, I could setup such a job. Chris -----Ursprüngliche Nachricht----- Von: Erik de Bruin [mailto:e...@ixsoftware.nl] Gesendet: Freitag, 3. April 2015 07:57 An: dev@flex.apache.org Cc: webdoubl...@hotmail.com Betreff: Re: AW: [LAST CALL] FlexUnit 4.3 > These kinds of verify errors indicate mixing different swc versions. All > swcs going into a swf must be on the same sdk version otherwise you risk > verify errors. Does that mean that we ideally should release different FlexUnit 'versions' to match each Apache Flex SDK version? At least for this release, to give each SDK it's own, 'native' FlexUnit? And going forward, should we release FlexUnit together with the SDK, and change it's versioning to indicate to which SDK it belongs: FlexUnit 4.15.0? EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
