> During a normal release ... where would you download the source package? From
> the jenkins workspace? If yes, I could setup such a job.
Correct. For the SDK there is a 'nightly' build during dev and a
'release' build on Jenkins during the RC period (after LAST CALL) that
contains both the sour
> Or better yet... why don't we make FlexUnit part of the SDK?
+1 - it feels like it would make projects more likely to have unit
tests, and it would hopefully make contributions to FlexUnit more
likely.
>> 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 le
> 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
We just want to see the source package before you start a vote on it.
Thanks
Alex
Sent from my LG G3, an AT&T 4G LTE smartphone
-- Original message--
From: Christofer Dutz
Date: Thu, Apr 2, 2015 12:46 AM
To: dev@flex.apache.org;
Subject:AW: [LAST CALL] FlexUnit 4.3
The staging
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.
Sent from my LG G3, an AT&T 4G LTE smartphone
-- Original message--
From: Frédéric THOMAS
Date: Thu, Apr 2, 2015 1:54 AM
Hi,
Except the site [1] was extremely slow at me this morning at 9 am GMT +0, I've
been able to run all my tests with this new FU version from IntelliJ.
Out of the IDE, my build system for this app is done with Rake (ruby) and use a
Runner app which once compile is launched by ADL, for this
