[YANGTOOLS-1144] Resolve yang-parser-api naming Created: 18/Oct/20  Updated: 09/Feb/22  Resolved: 09/Feb/22

Status: Resolved
Project: yangtools
Component/s: parser
Affects Version/s: None
Fix Version/s: 8.0.0

Type: Task Priority: High
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
 Summary
 Type
 Status
 Assignee
YANGTOOLS-1274 Add org.opendaylight.yang.parser.api.... Sub-task Resolved Robert Varga  
YANGTOOLS-1278 Remove org.opendaylight.yang.model.pa... Sub-task Resolved Robert Varga  
Epic Link: Integrate completely with JMPS

 Description   

We have yang-parser-api, which exposes the same module (automatic) and really has yang.model.parser.api inside. We should be renaming the artifact or the package to make room for it, but it is kinda sticky.

OTOH, we can jump into the business of having multiple API packages in one JPMS module – that would probably work, too.

 Comments   
Comment by Robert Varga [ 09/Feb/22 ]

Resolved in https://git.opendaylight.org/gerrit/c/yangtools/+/95913

Generated at Wed Feb 07 20:55:18 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.