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
If the wrong group/artifact is provided then it is not possible to download the maven-metadata.xml.
If this happens the stored file contains something like this and the process does not fail:
<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
In a normal correct situation it contains both the desired groupId and artifactId.
If the wrong group/artifact is provided then it is not possible to download the
maven-metadata.xml
.If this happens the stored file contains something like this and the process does not fail:
In a normal correct situation it contains both the desired groupId and artifactId.
Proposal:
After retrieving the
maven-metadata.xml
the resulting file is checked if it contains bothif not then the rebuild fails.
The text was updated successfully, but these errors were encountered: