[MDSAL-180] Java binding v1: naming conflict with java.lang types Created: 29/Jun/16 Updated: 09/Mar/18 Resolved: 22/Aug/16 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vratko Polak | Assignee: | Vratko Polak |
| 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: | 6126 |
| Description |
|
A simple yang model showcasing the conflict: https://git.opendaylight.org/gerrit/41037 Binding generator sometimes omits the prefix for basic Java types (such as java.lang.Long) which is wrong if the model generates class with the same base name (Long). |
| Comments |
| Comment by Vratko Polak [ 29/Jun/16 ] |
|
A fix for the symptom described: https://git.opendaylight.org/gerrit/41040 |
| Comment by Vratko Polak [ 22/Aug/16 ] |
|
Merged to master (Boron and Carbon): https://git.opendaylight.org/gerrit/41040 Waiting for review for Beryllium: https://git.opendaylight.org/gerrit/44468 Target Milestone changed, to signal this is fixed on post-Beryllium branches. |