Re: Decoupling from Compilation was: sometimes too much help is not helping - r725533

2008-12-17 Thread Oleg Gusakov
Herve, Hervé BOUTEMY wrote: Le mercredi 17 décembre 2008, Benjamin Bentmann a écrit : Oleg Gusakov wrote: Unit tests were using those jars to compile test code. Just a technical question: Is it actually required/desirable to really compile code during the tests? Over in the Ma

Re: Decoupling from Compilation was: sometimes too much help is not helping - r725533

2008-12-17 Thread Hervé BOUTEMY
Le mercredi 17 décembre 2008, Benjamin Bentmann a écrit : > Oleg Gusakov wrote: > > Unit tests were using those jars to compile test code. > > Just a technical question: Is it actually required/desirable to really > compile code during the tests? > > Over in the Maven core ITs, running the Compiler

Re: Decoupling from Compilation

2008-12-17 Thread Benjamin Bentmann
Oleg Gusakov wrote: Test performance: 100s of millis added by the compiler do not add too much of a delay; the compilation unit is a 2-liner. Yep, it's surely of minor concern for the Mercury tests themselves. But just imagine a penalty of about 1 sec and scale this by 250 and you get an ide

Re: Decoupling from Compilation

2008-12-17 Thread Oleg Gusakov
Benjamin Bentmann wrote: Oleg Gusakov wrote: Unit tests were using those jars to compile test code. Just a technical question: Is it actually required/desirable to really compile code during the tests? Over in the Maven core ITs, running the Compiler (or Surefire) Plugin was the classical

Re: Decoupling from Compilation was: sometimes too much help is not helping - r725533

2008-12-17 Thread Benjamin Bentmann
Oleg Gusakov wrote: Unit tests were using those jars to compile test code. Just a technical question: Is it actually required/desirable to really compile code during the tests? Over in the Maven core ITs, running the Compiler (or Surefire) Plugin was the classical approach to test dependen