From 8a42fe4ae1d0bcc9bdceba58c9e34fa0f3d73f0f Mon Sep 17 00:00:00 2001
From: bjiang <bjiang@us.ibm.com>
Date: Fri, 6 May 2016 16:19:59 -0400
Subject: [PATCH] javadoc

---
 .../analyzer/RubyBundlerAnalyzer.java          | 18 ++++++++----------
 1 file changed, 8 insertions(+), 10 deletions(-)

diff --git a/dependency-check-core/src/main/java/org/owasp/dependencycheck/analyzer/RubyBundlerAnalyzer.java b/dependency-check-core/src/main/java/org/owasp/dependencycheck/analyzer/RubyBundlerAnalyzer.java
index 0725d8202..b74f05e90 100644
--- a/dependency-check-core/src/main/java/org/owasp/dependencycheck/analyzer/RubyBundlerAnalyzer.java
+++ b/dependency-check-core/src/main/java/org/owasp/dependencycheck/analyzer/RubyBundlerAnalyzer.java
@@ -23,22 +23,20 @@ import java.io.FilenameFilter;
 import org.owasp.dependencycheck.Engine;
 import org.owasp.dependencycheck.analyzer.exception.AnalysisException;
 import org.owasp.dependencycheck.dependency.Dependency;
-import org.owasp.dependencycheck.utils.Settings;
 
 /**
- * Used to leverage Ruby gems that are deployed or installed by Ruby bundler (http://bundler.io).
- * Ruby bundler creates new .gemspec files under a folder called "specifications" at deploy time, 
- * in addition to the original .gemspec files from source. The advantage of bundler generated 
- * .gemspec files is that they contain fully resolved attributes thus provides more accurate 
- * evidences, whereas the original .gemspec from source often contain variables for attributes
- * that can't be used for evidences.
- * 
- * This analyzer accepts the fully resolved .gemspec installed by the bundler for 
- * better evidence results. It also tries to resolve the dependency packagePath 
+ * This analyzer accepts the fully resolved .gemspec created by the Ruby bundler (http://bundler.io)
+ * for better evidence results. It also tries to resolve the dependency packagePath 
  * to where the gem is actually installed. Then during <code>AnalysisPhase.PRE_FINDING_ANALYSIS</code>
  * <code>DependencyBundlingAnalyzer</code> would merge two .gemspec dependencies together if 
  * <code>Dependency.getPackagePath()</code> are the same.
  * 
+ * Ruby bundler creates new .gemspec files under a folder called "specifications" at deploy time, 
+ * in addition to the original .gemspec files from source. The bundler generated 
+ * .gemspec files always contain fully resolved attributes thus provide more accurate 
+ * evidences, whereas the original .gemspec from source often contain variables for attributes
+ * that can't be used for evidences.
+ * 
  * Note this analyzer share the same <code>Settings.KEYS.ANALYZER_RUBY_GEMSPEC_ENABLED</code> as
  * <code>RubyGemspecAnalyzer</code>, so it will enabled/disabled with <code>RubyGemspecAnalyzer</code>.
  *