BUG-1070: log exceptions

When we fail to construct a schema context, we do not log any sensible
cause at all, leaving not nearly enough evidence to pin down the
problem. Step one is to start reporting thrown exceptions.

Change-Id: Ie8ccc8f77eb18dfc385d13b81b5c5094866df177
Signed-off-by: Robert Varga <rovarga@cisco.com>

diff --git a/yang/yang-parser-impl/src/main/java/org/opendaylight/yangtools/yang/parser/impl/util/URLSchemaContextResolver.java b/yang/yang-parser-impl/src/main/java/org/opendaylight/yangtools/yang/parser/impl/util/URLSchemaContextResolver.java
index fe32493b120efbe97cd3df5a3b7f426a8c6c4e51..41066939c79ac1fed046a8702a64316d01a589dd 100644 (file)
--- a/yang/yang-parser-impl/src/main/java/org/opendaylight/yangtools/yang/parser/impl/util/URLSchemaContextResolver.java
+++ b/yang/yang-parser-impl/src/main/java/org/opendaylight/yangtools/yang/parser/impl/util/URLSchemaContextResolver.java
@@ -145,7 +145,7 @@ public class URLSchemaContextResolver implements AdvancedSchemaSourceProvider<In
             }
             currentSourceContext = context;
         } catch (Exception e) {
-            LOG.error("Could not create schema context for {} ",context.getValidSources());
+            LOG.error("Could not create schema context for {} ", context.getValidSources(), e);
         }
         return Optional.absent();
     }