released-version does not detect version if maven repository is not configured to look for snapshot

[stefanseifert]

We want to use build-helper:release-version to get the latest release of the artifact the plugin is defined in.
the artifact itself is currently using a SNAPSHOT version in the POM.

we use a minimal maven-settings.xml like this, defining only a single repository for lookup released version, but not snapshots:

<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <profiles>
    <profile>
      <id>default</id>
      <repositories>
        <repository>
          <id>central</id>
          <url>https://repo1.maven.org/maven2/</url>
          <layout>default</layout>
          <releases>
            <enabled>true</enabled>
            <updatePolicy>never</updatePolicy>
          </releases>
          <snapshots>
            <enabled>false</enabled>
          </snapshots>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <id>central</id>
          <url>https://repo1.maven.org/maven2/</url>
          <layout>default</layout>
          <releases>
            <enabled>true</enabled>
            <updatePolicy>never</updatePolicy>
          </releases>
          <snapshots>
            <enabled>false</enabled>
          </snapshots>
        </pluginRepository>
      </pluginRepositories>
    </profile>
  </profiles>
  <activeProfiles>
    <activeProfile>default</activeProfile>
  </activeProfiles>
</settings>

expected: detecting releases in this maven repo for the current module's artifact should work.

actual: it does not work, does not detect any released version (if there is also no released version in the local maven repo).

ArtifactMetadataSource.retrieveAvailableVersions does not find any released versions if the module it is executed on has a -SNAPSHOT version in the current POM.

---

workaround: if this part is removed from the repo definitions it's working - but then every snapshot request is also hitting the repo which is not intended:

<snapshots>
  <enabled>false</enabled>
</snapshots>