[YANGTOOLS-641] yang-maven-plugin: allow flexible SchemaSource input Created: 30/Jul/16 Updated: 21/Sep/20 Resolved: 21/Sep/20 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | maven plugin |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | ||
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||||||
| Description |
|
Current yang-maven-plugin implementation requires input schemas to be present in YANG text format. But our model parsing infrastructure allows different inputs, for example YIN. Design and implement a way for the yang-maven-plugin to ingest alternative formats into the SchemaContext build pipeline. This should allow input formats to be provided at plugin use time, similar to how different code generation plugins are glued it. The output of processing should result in a YANG text file being generated and packaged in the output. The original input file should also be included. |
| Comments |
| Comment by Robert Varga [ 20/Feb/17 ] |
| Comment by Robert Varga [ 24/Feb/17 ] |
|
wrong link, should be https://git.opendaylight.org/gerrit/52045 |
| Comment by Robert Varga [ 27/Feb/17 ] |
|
Requires initial refactor in BUG-7568. |
| Comment by Robert Varga [ 21/Sep/20 ] |
|
We do not need this, as the alternative sources can be translated to YANG as an intermediate product. |