Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repository offline #69

Closed
rodrigocarvalhodev opened this issue Feb 16, 2019 · 10 comments
Closed

Repository offline #69

rodrigocarvalhodev opened this issue Feb 16, 2019 · 10 comments

Comments

@rodrigocarvalhodev
Copy link

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

@Chasewhip8
Copy link

Can also confirm this is the case

@Haileykins
Copy link

Haileykins commented Feb 17, 2019

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
Copy link

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

@heartz66
Copy link

Meanwhile, use system scope directing to your Vault.jar

@Sataniel98
Copy link

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
Copy link

Skyost commented Feb 18, 2019

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'
}

Poslovitch added a commit to BentoBoxWorld/BentoBox that referenced this issue Feb 18, 2019
@mdcfe
Copy link

mdcfe commented Feb 18, 2019

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
Copy link
Contributor

PikaMug commented Feb 25, 2019

batman-bat-signal-light_141264

@mdcfe
Copy link

mdcfe commented Mar 1, 2019

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

@Sleaker
Copy link
Member

Sleaker commented Mar 1, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants