bump-pom-scijava: after deploying to OSS Sonatype, invalidate cache

Our primary mirror is the ImageJ Maven repository. This also happens to be
the go-to place for the maven-helper when looking for the latest version.

Therefore, let's just use the RESTful API of the Nexus instance that is
the ImageJ Maven repository to invalidate the cache of maven-metadata.xml
just after releasing to OSS Sonatype.

That way, the maven-helper will trigger that file to be fetched from OSS
Sonatype, merge it with what we have in the local Releases repository
(that was formerly the official place where we deployed pom-scijava), and
everything is groovy.

Signed-off-by: Johannes Schindelin <[email protected]>

Author: dscho

bump-pom-scijava.sh

@@ -223,6 +223,11 @@ die "Failed to remove intermediate $pom.new"
 commit_and_push "Increase pom-scijava version to $new_version" \
 	-m "$message" $pom
 
-test -n "$skip_commit" ||
-mvn -DupdateReleaseInfo=true -Psonatype-oss-release \
-	deploy nexus-staging:release
+NEXUS_URL=http://maven.imagej.net/
+SONATYPE_PROXY=$NEXUS_URL/service/local/data_cache/repositories/sonatype/content
+test -n "$skip_commit" || {
+	mvn -DupdateReleaseInfo=true -Psonatype-oss-release \
+		deploy nexus-staging:release &&
+	curl --netrc -i -X DELETE \
+		$SONATYPE_PROXY/org/scijava/pom-scijava/maven-metadata.xml
+}