Only warn about unmatched inputs in modules

We used to issue an error when the module service's run() method
was called with inputs that are not specified explicitly in the
corresponding ModuleInfo.

That is fragile: should the implementing classes be modified and remove
an input parameter, we should still do our best to continue.

Therefore, let's just warn instead and continue, making the unmatched
input available to the module and just skipping the conversion to
an explicit type (because the info does not specify it).

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Author: dscho

src/main/java/org/scijava/module/DefaultModuleService.java

@@ -343,17 +343,20 @@ private void assignInputs(final Module module,
 
 		for (final String name : inputMap.keySet()) {
 			final ModuleItem<?> input = module.getInfo().getInput(name);
+			final Object value = inputMap.get(name);
+			final Object converted;
 			if (input == null) {
-				log.error("No such input: " + name);
-				continue;
+				log.warn("Unmatched input: " + name);
+				converted = value;
 			}
-			final Object value = inputMap.get(name);
-			final Class<?> type = input.getType();
-			final Object converted = ConversionUtils.convert(value, type);
-			if (value != null && converted == null) {
-				log.error("For input " + name + ": incompatible object " +
-					value.getClass().getName() + " for type " + type.getName());
-				continue;
+			else {
+				final Class<?> type = input.getType();
+				converted = ConversionUtils.convert(value, type);
+				if (value != null && converted == null) {
+					log.error("For input " + name + ": incompatible object " +
+						value.getClass().getName() + " for type " + type.getName());
+					continue;
+				}
 			}
 			module.setInput(name, converted);
 			module.setResolved(name, true);