Our workaround for this one jar was to just explicitly list those dependencies in the target in the repo.