Hello,

since approximate two hours, my team and I are unable to download artifacts coming from your Maven repository (a 500 error is returned). After a little research, we found that this issue is caused by a low-disk space on the machine hosting the database attached with the Maven repository (as demonstrated on this page):

javax.servlet.ServletException: com.orientechnologies.orient.core.exception.OLowDiskSpaceException: Error occurred while executing a write operation to database 'component' due to limited free space on the disk (6 MB). The database is now working in read-only mode. Please close the database (or stop OrientDB), make room on your hard drive and then reopen the database. The minimal required space is 256 MB. Required space is now set to 256MB (you can change it by setting parameter storage.diskCache.diskFreeSpaceLimit) . DB name="component" 

Disclaimer: I know that this issue is not directly related to ProtocolLib but developers are affected significantly, and that's the only place I found to warn about it.

@dmulloy2 any update ?

Hello,

since approximate two hours, my team and I are unable to download artifacts coming from your Maven repository (a 500 error is returned). After a little research, we found that this issue is caused by a low-disk space on the machine hosting the database attached with the Maven repository (as demonstrated on this page):

javax.servlet.ServletException: com.orientechnologies.orient.core.exception.OLowDiskSpaceException: Error occurred while executing a write operation to database 'component' due to limited free space on the disk (6 MB). The database is now working in read-only mode. Please close the database (or stop OrientDB), make room on your hard drive and then reopen the database. The minimal required space is 256 MB. Required space is now set to 256MB (you can change it by setting parameter storage.diskCache.diskFreeSpaceLimit) . DB name="component" 

Disclaimer: I know that this issue is not directly related to ProtocolLib but developers are affected significantly, and that's the only place I found to warn about it.

I confirm: I'm unable to use ProtocolLib with maven or gradle

Same, was forced to remove the repository and ProtocolLib from my pom.xml!

Update: Sound like the Maven repository is offline now.

dmulloy2 let me know if you need a hosted maven repo but I assume it just needs some love.

Till things are resolved I've mirrored to mine. Use the following repo definition:

        <!-- Bundabrg's Repo -->
        <repository>
            <id>bundabrg-repo</id>
            <url>https://repo.worldguard.com.au/repository/maven-public</url>
            <releases>
                <enabled>true</enabled>
            </releases>
            <snapshots>
                <enabled>false</enabled>
            </snapshots>
        </repository>

@bundabrg Thanks. Hjälten vi behöver

@bundabrg no doesn't work :-/

I provide that as well and have modified protocollib-parent pom to remove the repos in there.

You may need to remove ~./m2/repositories/com/comphenix then perform a mvn -U clean install

@hornta

@bundabrg @hornta Just add a trailing slash to the repo url :) But you will still get errors as his repo might provide ProtocolLib, but no further dependencies like BukkitExecutors.

Hi, Can anyone host protocollib 4.5.0 (latest build)?

@wmelo92 @hornta
i uploaded it to a temporary repo
only 4.4.0, build425, i am sorry but i don't have 4.5.0
i will delete it when official repo online
repo url: https://dl.bintray.com/yun-shan/ProtocolLib-Temporary/

gradle example:

    maven {
        name 'ProtocolLib Repo'
        // url 'http://repo.dmulloy2.net/nexus/repository/public/'
        url 'https://dl.bintray.com/yun-shan/ProtocolLib-Temporary/'
    }

Hello, I'm hosting both 4.4.0 and 4.5.0 on repo.codemc.io

Nexus view: https://repo.codemc.io/#browse/browse:maven-public:com%2Fcomphenix%2Fprotocol%2FProtocolLib

You can also check the automatic build jobs for both branches at:
https://ci.codemc.io/job/ThirdParty/job/ProtocolLib/
https://ci.codemc.io/job/ThirdParty/job/ProtocolLib-Legacy/

Maven:

<repository>
    <id>codemc-repo</id>
    <url>https://repo.codemc.io/repository/maven-public/</url>
</repository>

Gradle:

maven {
    name 'CodeMc repo'
    url 'https://repo.codemc.io/repository/maven-public/'
}

Should be coming back up now.

Sorry for the delay, was on vacation

Thanks for keeping this excellent plugin going.

out of interest sake @sgdc3 how do you handle ProtocolLib-Parent pom adding the (then) broken repo back into the mix thus invalidating the ability to host a mirror? I'm thinking of adding 3rd party compiles but get caught by this often.

@bundabrg 😎

I did the same with BukkitExecutors

@pixar02 with the official repo? try with the "-B -U clean package" maven scope

Thanks that fixed it.

The executors are broken. My gradle project is unable to build the project because of this.