Document changes to ietf-routing@2014-05-24.yang

The special-next-hop grouping
was renamed to

special-next-hop-grouping

due to ODL's Binding Specification bug.

Change grouping name back requires
switching to Binding Specificiation v2 (HONEYCOMB-420).

Change-Id: I2390176c06a7f64ae0261d62c8bc4f3d2ae193ca
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>

diff --git a/routing/routing-api/src/main/yang/hc2vpp-ietf-routing@2014-05-24.yang b/routing/routing-api/src/main/yang/hc2vpp-ietf-routing@2014-05-24.yang
index 118225c..63d163b 100644 (file)
--- a/routing/routing-api/src/main/yang/hc2vpp-ietf-routing@2014-05-24.yang
+++ b/routing/routing-api/src/main/yang/hc2vpp-ietf-routing@2014-05-24.yang
@@ -259,7 +259,12 @@ module hc2vpp-ietf-routing {
     }
   }
 
-  // WARNING - renamed due to yang sources generation problem(having same name for grouping and it's leaf ends up in error against Java Language Specification)
+  // TODO(HC2VPP-273): renamed due to https://jira.opendaylight.org/browse/MDSAL-1
+  // (having same name for grouping and it's leaf ends up in Java compilation error)
+  //
+  // Change grouping name back after switching to Binding Specificiation v2 (HONEYCOMB-420).
+  //
+  // grouping special-next-hop {
   grouping special-next-hop-grouping {
     description
       "This grouping provides the leaf for specifying special