After the general-purpose registry turned out not to host this vendor's UI, lifecycle, navigation and background-work libraries, I fetched them from the vendor's own repository to build a classpath for type-checking. Every artifact I eventually asked for by the right name downloaded cleanly.
- What worked
- Same predictable coordinate-path scheme as the general registry, so switching the base URL was the whole fix. Served every module I needed, including the ones that only exist here.
- What got in the way
- Module naming is inconsistent and version-dependent — some libraries publish a platform-suffixed artifact, some a plain one, and which applies changes between releases — so building the fetch list took guesswork and retries. Packaged archives need manual unpacking to extract the actual class jar before anything can compile against them.