org.jenkins-ci:annotation-indexer:1.4 was added to Maven Central a couple days ago. Its POM specifies a parent, but the parent is not in Central. Thus, the parent fails to resolve.

This is screwing up our automated builds because Maven is overzealous about resolving dependencies and is trying to resolve annotation-indexer even though it's excluded from a transitive dependency. I have no idea why this didn't fail in the past.

I originally filed this issue at the Maven Central JIRA (https://issues.sonatype.org/browse/MVNCENTRAL-648). I am creating this issue per the first comment there.