Repository offline

[rodrigocarvalhodev]

Repository http://nexus.hc.to/content/repositories/pub_releases is offline, please fix.

[Chasewhip8]

Can also confirm this is the case

[Haileykins]

Can also confirm, still. Cutting into development for me and I guarantee many other developers. Can we get some info? Maybe an ETA? Some semblance of a time frame

[Chasewhip8]

Just build it locally and it will be fine. Remove the repo and build local

[heartz66]

Meanwhile, use system scope directing to your Vault.jar

[Sataniel98]

Yeah, but even if I remove the Vault repo, Maven still tries to access it because there are other dependencies that use this repo. The repo doesn't seem to be 404-down but somehow erroneous. It loads forever until I get a 504 gateway time-out error. That sucks because Maven tries to access it over and over again for each dependency.

[Skyost]

Same for me. @MilkBowl why not self-hosting it using Github or using something like Jitpack ?

Anyway, for everyone interested just include the repository :

repositories {
    // Other repos
    maven { url 'https://jitpack.io' }
}

And the dependency :

dependencies {
    // Other dependencies
    compileOnly 'com.github.MilkBowl:VaultAPI:1.7'
}

[mdcfe]

You can also swap the Vault repo for the EssentialsX build server Maven repo, which also avoids having to change the artifact version to a commit hash:

Gradle

repositories {
    // ...
    maven { url 'https://ci.ender.zone/plugin/repository/everything/' }
}

dependencies {
    // ...
    compileOnly 'net.github.MilkBowl:VaultAPI:1.7'
}

Maven

<repositories>
    <!-- ... -->
    <repository>
        <id>essx-repo</id>
        <url>https://ci.ender.zone/plugin/repository/everything/</url>
    </repository>
</repositories>

<dependencies>
    <!-- ... -->
    <dependency>
        <groupId>net.milkbowl.vault</groupId>
        <artifactId>VaultAPI</artifactId>
        <version>1.7</version>
        <scope>provided</scope>
    </dependency>
</dependencies>

[PikaMug]

[mdcfe]

Still appears to be returning a 502 for me, but now it's instant instead of waiting for a long time.

[Sleaker]

@md678685 I've tagged it onto jitpack to attempt to alleviate the hosting issues:
https://jitpack.io/#MilkBowl/VaultAPI/1.7