Open mihai1voicescu opened 6 years ago
Thank you for your report. It seems to work on our end, and we also use macOS.
For each dependency, Gradle tries a number of different urls/Maven repositories. All of the failed dependencies are in our snapshots repository. Therefore, of the multiple attempts to resolve a single dependency, the attempt that starts with the url https://artifacts.metaborg.org/content/repositories/snapshots/
should have succeeded. (Note the snapshot
part in the url.)
> Could not resolve org.metaborg:dynsem:2.6.0-SNAPSHOT.
> Unable to load Maven meta-data from https://artifacts.metaborg.org/content/repositories/snapshots/org/metaborg/dynsem/2.6.0-SNAPSHOT/maven-metadata.xml.
> Could not get resource 'https://artifacts.metaborg.org/content/repositories/snapshots/org/metaborg/dynsem/2.6.0-SNAPSHOT/maven-metadata.xml'.
> Could not GET 'https://artifacts.metaborg.org/content/repositories/snapshots/org/metaborg/dynsem/2.6.0-SNAPSHOT/maven-metadata.xml'.
> Connect to artifacts.metaborg.org:443 [artifacts.metaborg.org/131.180.125.32] failed: Bad file descriptor (connect failed)
For every of your failed dependencies, I opened the snapshot url in my browser, and they all correctly resolve to an xml Maven metadata file. For example the org.metaborg:dynsem:2.6.0-SNAPSHOT dependency.
Could you try again? Maybe there was an issue on our end that has now been resolved. Otherwise, it seems the issue is on your end.
Failed to install the plugin using both the command and the repository clone.
I'm running on macOS, maybe it's something related to that although the gradle build seems to fail to download the necessary dependencies.
At least 2 links do not work even in the browser ->
Here is the stack trace