Sort out yang.model.repo.{api,spi,util} placement

Description

During the course of transitioning to JPMS modules the repo.api package placement came up. Resolve it somehow – either by creating a new component, or renaming it.

This needs to be examined with yang-parser-api in mind.

Activity

Show:

Robert Varga February 11, 2021 at 9:21 AM

These classes are really a different take on yang-parser-api, where the management of models follows transformations and keeps all sorts of caches. The interfaces could be hosted in yang-parser-api, but that might cause confusion. These need to be split into yang-repo-{api,spi) hosting repo.api, repo.spi. Current contents of repo.util should go to repo.spi.

Finally the yang-parser-rfc7950 bits need to be examined and cleaned up as well.