[MDSAL-281] Binding v2 generator exception: Type parameter MUST be specified and cannot be NULL Created: 31/Jul/17 Updated: 09/Mar/18 Resolved: 14/Aug/17 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | Binding V2 codegen |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Andrej Záň | Assignee: | Jie Han |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 8911 |
| Description |
|
When generating sources for this model: module test { yang-version 1; revision "2017-02-24" { description "Initial revision of test model."; } container testContainer { } notification testLeafrefNotification { } } then this exception is thrown: [ERROR] yang-to-sources: Unable to generate sources with org.opendaylight.mdsal.binding.javav2.maven.api.gen.plugin.CodeGeneratorImpl generator If notification is changed to container, then code generation pass, but generated code is not compilable what is already mentioned in |
| Comments |
| Comment by Jie Han [ 03/Aug/17 ] |
|
Fixed by this patch: |
| Comment by Jie Han [ 14/Aug/17 ] |
| Comment by A H [ 14/Aug/17 ] |
|
A patch was submitted to revert the changes and fix this bug in Carbon SR2: https://git.opendaylight.org/gerrit/#/c/61602 To better assess the impact of this bug and fix, could someone from your team please help us identify the following: |
| Comment by A H [ 14/Aug/17 ] |
|
Reopening bug because related patches in Carbon SR2 have not been merged yet: |
| Comment by Robert Varga [ 14/Aug/17 ] |
|
Regression: No. Severity: The issue prevents Binding v2 from being adopted by our end users, Workaround: None. Testing: The patch includes a unit test for the specific failure and has not introduced any detectable regression. Impact: The fix for this issue has no effect on downstream projects within the Simultaneous Release. The presence of this issue blocks adoption of a Carbon feature by our end users. Given the timeline (our next Carbon deliverable is SR3 on 11/9), I believe it is crucial we deliver the fix in SR2. |