release-version.sh: remove obsolete GPG check

It looked for <releaseProfiles>sonatype-oss-release</releaseProfiles>
in the <properties>. But the default for SciJava projects is now
sonatype-oss-release, meaning if the releaseProfiles property is not
explicitly set, it will try to release to Sonatype. So the test was
not flagging projects configured to release to OSS Sonatype anyway.

It is true that .travis/signingkey.asc.enc should be present for
projects intended for release to OSS Sonatype, and if it is not, then
the project will almost certainly fail to be released as intended.
The release_version.sh script could check for this, but it does not
check for similar prerequisites such as encrypted environment variable
entries in the .travis.yml. So for now, let's not bother checking it.

Author: ctrueden

release-version.sh

@@ -20,12 +20,6 @@ valid_semver_bump () {
 	sh -$- "$VALID_SEMVER_BUMP" "$@" || die
 }
 
-verify_gpg_settings () {
-	test "$SKIP_GPG" -o -f .travis/signingkey.asc.enc ||
-		die 'GPG configuration not found. Please use travisify.sh to add it.
-See also: https://github.com/scijava/pom-scijava/wiki/GPG-Signing'
-}
-
 verify_git_settings () {
 	if [ ! "$SKIP_PUSH" ]
 	then
@@ -113,10 +107,6 @@ valid_semver_bump "$pomVersion" "$VERSION"
 BASE_GAV="$(maven_helper gav-from-pom pom.xml)" ||
 die "Could not obtain GAV coordinates for base project"
 
-# If releasing to OSS Sonatype, enable some extra stuff
-mvn -Dexec.executable='echo' -Dexec.args='${releaseProfiles}' exec:exec -q | grep -q 'sonatype-oss-release' &&
-	verify_gpg_settings
-
 git update-index -q --refresh &&
 git diff-files --quiet --ignore-submodules &&
 git diff-index --cached --quiet --ignore-submodules HEAD -- ||