doc updates

Author: plaird

docs/README.md

@@ -8,4 +8,4 @@ Most user and developer docs for BEF are rooted here.
 - [Known Issues](issues.md)
 
 For developers that want to contribute to BEF:
-- [BEF Dev Guide][dev/README.md] (if you would like to build/modify the BEF)
+- [BEF Dev Guide](dev/README.md) (if you would like to build/modify the BEF)

docs/using_the_feature.md

@@ -8,6 +8,7 @@ All of them assume you have already [installed your toolchain](install.md).
 - [Import your Bazel workspace into the IDE](using_the_feature_import.md)
 - [Configure the project Settings](using_the_feature_settings.md)
 - [Building your project](using_the_feature_builds.md)
+- [Understanding the Java Classpath with the Bazel Eclipse Feature](using_the_feature_classpath.md)
 - [Running apps and tests](using_the_feature_launching.md)
 
 **Modifying the Bazel Eclipse Feature**

docs/using_the_feature_classpath.md

@@ -1,4 +1,4 @@
-## Understanding the Classpath with the Bazel Eclipse Feature
+## Understanding the Java Classpath with the Bazel Eclipse Feature
 
 BEF ultimately computes classpath information and maps it into the existing Java Developer Tools (JDT) plugins of Eclipse.
 This works well, but there are some caveats to this mapping.

tests/com.salesforce.bazel-java-sdk.tests/src/com/salesforce/bazel/sdk/command/BazelLauncherBuilderTest.java

@@ -32,7 +32,6 @@
 import java.util.Collections;
 import java.util.List;
 
-import org.junit.Ignore;
 import org.junit.Rule;
 import org.junit.Test;
 import org.junit.rules.TemporaryFolder;