You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 20, 2022. It is now read-only.
In case a snapshot artefact is simply pushed in the fashion of a release artefact to a maven repository it lacks some information about the available snapshots and filenames in the maven-metadata.xml.
Use release style URL as fallback for snapshot artifacts in case of information missing in maven-metadata.xml.
Normally we require information about classifieres and most recent snapshot version to construct the download url
Use release style URL as fallback for snapshot artifacts in case of information missing in maven-metadata.xml.
Normally we require information about classifieres and most recent snapshot version to construct the download url
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In case a snapshot artefact is simply pushed in the fashion of a release artefact to a maven repository it lacks some information about the available snapshots and filenames in the maven-metadata.xml.
An example for such a case
A proper snapshot maven-metadata.xml would look like this
Currently we require the latter to construct the appropriate download url for a certain classifier.
If this is not available, the apidoc server simply fails constructing the url.
This should be changed, that the fallback in such cases (lacking the required information for snapshots) is a standard release style URL.
The text was updated successfully, but these errors were encountered: