Merge pull request bndtools#6765 from chrisrueger/fix-wording

wording: Imports that lack version ranges

Author: chrisrueger

biz.aQute.bndlib/src/aQute/bnd/osgi/Analyzer.java

@@ -2129,8 +2129,8 @@ && complainAboutMissingVersionRange(packageRef, ee)) {
 
 		if (isPedantic() && noimports.size() != 0) {
 			warning(
-				"Imports that lack version ranges due to not being found in any bundle on the -buildpath: %s (These could stem from transitive dependencies of non-OSGi jars in your classpath (e.g. from -includeresource). "
-					+ "Adding this dependency to your -buildpath could help bnd adding version information.)",
+				"Imports that lack version ranges due to not being found in any bundle on the -buildpath: %s (These could stem from transitive dependencies of the jars on your buildpath (e.g. by wrapping non-OSGi jars via -includeresource or if Require-Bundle is involved)."
+					+ "Explicitly adding these dependencies to your -buildpath could help bnd find the correct version information.)",
 				noimports);
 		}
 	}

docs/_chapters/920-faq.md

@@ -50,7 +50,7 @@ A usually better way is to make the imports optional:
 
 Note the end at the Import-Package statement, that wildcard '*' is crucial for remaining imports, see [No Imports Show Up](?#noImports).
 
-## No Imports Show Up <a name="noImports"/>
+## No Imports Show Up
 The imports that show up in your Import-Package manifest header are controlled by the bnd file's Import-Package instruction. In bnd, the list is a set of patterns that are sequentially applied to your imports as calculated by bnd from the classes, resources, and headers in the JAR.
 
 The default Import-Package bnd instruction is:
@@ -69,6 +69,19 @@ Another reason is the exclude operator ('!') that will remove imports. If this i
 
 Last but not least, look at the `[USEDBY]` section of the JAR print out, make sure there are actually references.
 
+## Why do I have imports without version ranges?
+
+With `-pedantic:true` bnd creates a warning like
+
+> Imports that lack version ranges due to not being found in any bundle on the -buildpath: `com.example.foo.bar` ...
+
+These could stem from transitive dependencies of the jars on your buildpath.
+There are multiple reasons for that, for example they could stem from transitive dependencies:
+- of non-OSGi jars which are included via [-includeresource](/instructions/includeresource.html)
+- of OSGi bundles on your classpath, if the import version ranges for those bundles are not specified in the Bundle. E.g. if the bundle imports the dependency via `Require-Bundle` it won't have the import range, or if it uses `Import-Package` with no import range.
+
+
+
 ## Why No Automatic Bundle-Activator <a name="automaticActivator"/>
 Many people are surprised that bnd does not automatically calculate the Bundle-Activator. Basically, there are the following issues: