[MDSAL-221] Map model module for binding2 Created: 17/Jan/17 Updated: 16/Mar/19 Resolved: 16/Mar/19 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | Binding V2 codegen |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jakub Toth | Assignee: | Martin Ciglan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 7566 | ||||||||
| Comments |
| Comment by Martin Ciglan [ 17/Jan/17 ] |
|
MDSAL-model module elements are bound to yang-binding & binding-parent modules and we need to be independent in this matter from Binding Spec v2 point of view. That allows us to install Binding spec v2 features as necessary and also, get rid of Binding v1 eventually in future. |
| Comment by Jakub Toth [ 23/Jan/17 ] |
|
https://git.opendaylight.org/gerrit/#/c/50557/8 |
| Comment by Martin Ciglan [ 31/Jan/17 ] |
|
this needs to be designed and implemented in respect of having more than one binding in project (v1, v2, maybe scala in future), putting task back to confirmed. |
| Comment by Martin Ciglan [ 20/Apr/17 ] |
|
relates to new milestone and follows code generator implementation, |