Eclipse -- Junit test definitions

Is there a way to set the classpath for all Junit tests runs at one
time? Currently it seems I must define the classpath for each test
case, even though all the test cases require the same classpath.

Also, is there a way to conveniently store launch definitions and
project build paths in the source code control system? It seems that
everytime we need a new library, all N developers have to go add that
library to the class path for their project. I'm used to storing all
this stuff in a Makefile that is checked in to the source code control
system, so that when one developer adds something, everyone else can
see it. But with Eclipse it seems that there are any number of actions
that must be repeated by every developer on the team.

.

Relevant Pages

  • Re: Eclipse -- Junit test definitions
    ... select the proper launch configuration ... even though all the test cases require the same classpath. ... project build paths in the source code control system? ... that must be repeated by every developer on the team. ...
    (comp.lang.java.softwaretools)
  • JAR in a JAR?
    ... library (developed by a different developer) uses a library within ... OtherDevExternalLibrary.jar (in my classpath) ... NullPointerException because things that are in here cannot be found ... for some reason. ...
    (comp.lang.java.programmer)
  • Re: JAR in a JAR?
    ... Jason Cavett wrote: ... library (developed by a different developer) uses a library within ... JAR file. ... OtherDevExternalLibrary.jar (in my classpath) ...
    (comp.lang.java.programmer)
  • Double Whammy - the Fuckup Fairy and the Pontificator
    ... Our development project uses a source code control system. ... The Fuckup Fairy is a developer who has only been on the project for 6 ... This touched off The Pontificator. ...
    (alt.sysadmin.recovery)
  • Re: Back to Square 1 -- User Control and GUID problems...
    ... all the developers in a given environment should have ... Make sure each developer has an identical hiearchy, ... Use a source code control system such as VSS or WinCVS. ...
    (microsoft.public.vb.general.discussion)