Published: Aug 19 2010 / 04:46
as if this is even an issue anymore. nobody would use this...
A solution to a non existing problem imho.
Yes it's bad to deliver your test binaries with the rest of your software. Not only does it increase the footprint of your library artifact but correct dependency management requires that it drag along all the test related dependencies as well (junit, jmock, etc).
The solution? Let's just build another tool to solve a problem that we created by eschewing convention.
That's just lame.
Is it really such a problem to put those tests in another source tree? Most build tools (maven, ant) make this easy to manage.
This post reminds me of a guy riding his bike the wrong way down the middle of a city street and shouting at all the cars going the other direction.
Why write the tests at all , that is a job of IDE and the compiler, Grow up kids.
Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.