On 2/24/16, 12:08 AM, "Christofer Dutz" wrote:
>Hi Alex,
>
>that sounds as if you are using assertions in a way that contradictory to
>what they are intended to be used.
It isn't me. I did not write this code or review it. Before Flex moved
to Apache, I had made maybe a half-dozen changes to
reff: AW: AW: AW: AW: [FALCONJX]Compiling Falcon with externs problems
Hi Alex,
that sounds as if you are using assertions in a way that contradictory to what
they are intended to be used.
Assertions are meant to be hard checks to the contract of a method. Assumptions
the code needs to operate correctl
Hi Alex,
that sounds as if you are using assertions in a way that contradictory to what
they are intended to be used.
Assertions are meant to be hard checks to the contract of a method. Assumptions
the code needs to operate correctly.
Usually you could do the same with if-statements, but in con
As i have never ever seen eclipse automatically run unit tests in a Maven
project, I think I can confirm that.
Chris
Von meinem Samsung Galaxy Smartphone gesendet.
Ursprüngliche Nachricht
Von: Alex Harui
Datum: 24.02.2016 02:11 (GMT+01:00)
An: dev@flex.apache.org
Betreff:
Well the one is needed at compile & runtime, the rest are code that is only
needed at build time. You should never bundle build code with your product. In
the Maven world "yet another artifact" usually doesn't matter, cause the tool
takes care of managing this.
Chris
__
