![]() Your test classpath will be incorrect if you rely on the Bazel implicit classpath (described in #43). ![]() □ Note that this release is affected by #293. You will need to choose the Bazel JUnit Launcher.Īs with all releases starting with 1.4.0, this new release is supported on Windows in addition to Linux and macOS. The first time you run tests in the Eclipse workspace, you will be asked to choose the launcher in the UI.Please delete any JUnit launchers you have in your workspace that were created before this release.Tests were slow to launch because the test classpath was computed multiple times.Īs a result of the redesign, you will notice these differences:.Only the Bazel JUnit Target option worked. Running tests with the standard JUnit Test option previously resulted in a Class Not Found exception. ![]() The latter option has been removed with this release. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |