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
Seems like it wont build anymore due to a few of the maven-metadata.xml files can't be downloaded due to missing from the github repos... any idea how to change it so these can be built? I'm trying to get it running on an arm64 and the builds are all amd64.
For example, the following repo seems to have deleted their 4.0.0-snapshot directories
Failed to execute goal on project snake-ui: Could not resolve dependencies for project uk.co.bithatch:snake-ui:jar:1.0-SNAPSHOT: Failed to collect dependencies at com.github.hypfvieh:dbus-java:jar:4.0.0-SNAPSHOT: Failed to read artifact descriptor for com.github.hypfvieh:dbus-java:jar:4.0.0-SNAPSHOT: Could not transfer artifact com.github.hypfvieh:dbus-java:pom:4.0.0-SNAPSHOT from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [javassh-opensource-snapshots (http://artifactory.javassh.com/opensource-snapshots, default, snapshots), javassh-opensource-releases (http://artifactory.javassh.com/opensource-releases, default, releases)]
[WARNING] Could not transfer metadata com.sshtools:two-slices:0.0.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/com/sshtools/two-slices/0.0.1-SNAPSHOT/maven-metadata.xml
[WARNING] com.sshtools:two-slices:0.0.1-SNAPSHOT/maven-metadata.xmlfailed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata com.sshtools:two-slices:0.0.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/com/sshtools/two-slices/0.0.1-SNAPSHOT/maven-metadata.xm
The text was updated successfully, but these errors were encountered:
Seems like it wont build anymore due to a few of the maven-metadata.xml files can't be downloaded due to missing from the github repos... any idea how to change it so these can be built? I'm trying to get it running on an arm64 and the builds are all amd64.
For example, the following repo seems to have deleted their 4.0.0-snapshot directories
https://github.com/hypfvieh/dbus-java
Failed to execute goal on project snake-ui: Could not resolve dependencies for project uk.co.bithatch:snake-ui:jar:1.0-SNAPSHOT: Failed to collect dependencies at com.github.hypfvieh:dbus-java:jar:4.0.0-SNAPSHOT: Failed to read artifact descriptor for com.github.hypfvieh:dbus-java:jar:4.0.0-SNAPSHOT: Could not transfer artifact com.github.hypfvieh:dbus-java:pom:4.0.0-SNAPSHOT from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [javassh-opensource-snapshots (http://artifactory.javassh.com/opensource-snapshots, default, snapshots), javassh-opensource-releases (http://artifactory.javassh.com/opensource-releases, default, releases)]
and
http://0.0.0.0/com/github/hypfvieh/dbus-java/4.0.0-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata com.sshtools:two-slices:0.0.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/com/sshtools/two-slices/0.0.1-SNAPSHOT/maven-metadata.xml
[WARNING] com.sshtools:two-slices:0.0.1-SNAPSHOT/maven-metadata.xmlfailed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata com.sshtools:two-slices:0.0.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/com/sshtools/two-slices/0.0.1-SNAPSHOT/maven-metadata.xm
The text was updated successfully, but these errors were encountered: