search

vadbch / orika

Automatically exported from code.google.com/p/orika
0 stars 0 forks source link

COMPILER_STRATEGY system property not unset in tearDown of Issue25TestCase #175

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
The Issue25TestCase sets the compiler strategy to EclipseJdtCompiler in the 
setUp() but does not unset it in the tearDown(). As a result , subsequent tests 
that do rely on the default compiler strategy and that not explicit set it, may 
use the EclipseJdtCompiler instead of the JavaAssistCompiler, depending on how 
the tests are ran (within the same vm ) . This was the case for me when running 
the entire suite in IntelliJ and on the command-line with maven.

Thanks,
Geert.

Original issue reported on code.google.com by gdel...@trispark.com on 1 Oct 2014 at 2:48

GoogleCodeExporter commented 8 years ago 
Thanks !

Original comment by elaat...@gmail.com on 1 Oct 2014 at 3:30