Description csccsccsc 2008-07-10 14:28:31 EDT

When doing rightclick->RunAsJunit on a specific Junit class or method a launcher is created and run taking the classpath from the project settings.

However our runtime project setting need to differ to our compile time project settings.

We have a bridge pattern in place and use the project classpath setting to enforce that no developer accidentally includes references to a specific implementation and only goes through the project that is the abstraction layer.

Our normal application launcher and global JUnit launcher include the classpath for the implementation project.

However when Run->AsJunit auto-creates the launcher and auto-launches it uses our project settings only and so fails at runtime.

The normal technique is to run once expecting it to fail and then amend the launcher and run again.

Some project setting would be preferable where we could specify additional projects to include during JUnit run.