unit testing issues in eclipse-y environment

So I'm working yet another gig where Eclipse is the dominant platform (though I am getting some Idea uptake)... New gig, but same old problem: Eclipse doesn't distinguish between test and main resources and therefore "exports" test dependencies across compilation boundaries.

The best solution would be to get people to respect project boundaries at test time, but Eclipse encourages the opposite behavior and so that's an uphill battle. Eventually we'll get to maven, but this problem needs to be quietly solved first.

In the past, I've created a standalone project with test resources in the main branch, but then that ends up depending upon everything else which in turn depend on it, and *bang* the problem is worse...

Please sign in to leave a comment.