500 Internal Error in downloading verifiable-credentials-java:1.6.0

[jiyoonie9]

Hi! Thanks for creating this library. We are currently using it in our repository as a dependency.

We are currently getting a 500 Server Error when trying to download verifiable-credentials-java:1.6.0 via mvn install

We are also currently unable to render the repo website by browser - same 500 Server Error appears.

Because of this, we can't build our repo, which blocks our team.

Build error message, if you're interested:

Failed to execute goal on project kotlin-testsuite: Could not resolve dependencies for 
project website.tbd.developer.site:kotlin-testsuite:jar:0.1.0-SNAPSHOT: 
Failed to collect dependencies at xyz.block:tbdex:jar:0.10.0-beta -> 
xyz.block:tbdex-protocol:jar:0.10.0-beta -> 
xyz.block:web5:jar:0.0.11 -> 
xyz.block:web5-credentials:jar:0.0.11 -> 
com.danubetech:verifiable-credentials-java:jar:1.6.0: 
Failed to read artifact descriptor for com.danubetech:verifiable-credentials-java:jar:1.6.0: 

The following artifacts could not be resolved: 
com.danubetech:verifiable-credentials-java:pom:1.6.0 (absent): 
Could not transfer artifact com.danubetech:verifiable-credentials-java:pom:1.6.0 
from/to danubetech (https://repo.danubetech.com/repository/maven-public/): 
status code: 500, reason phrase: Server Error (500) -> [Help 1]

cc @peacekeeper @BernhardFuchs @azuzi

[praiaAndrewLeach]

This is also reproducing for 1.9.0 even when I explicitly remove the danube tech repo config for my build.gradle

Here's the build log from jitpack: https://jitpack.io/com/github/danubetech/verifiable-credentials-java/1.9.0/build.log

[ERROR] Failed to execute goal on project verifiable-credentials-java: Could not resolve dependencies for project com.danubetech:verifiable-credentials-java:jar:1.9.0: Failed to collect dependencies at info.weboftrust:ld-signatures-java:jar:1.9.0: Failed to read artifact descriptor for info.weboftrust:ld-signatures-java:jar:1.9.0: Could not transfer artifact info.weboftrust:ld-signatures-java:pom:1.9.0 from/to danubetech-maven-public (https://repo.danubetech.com/repository/maven-public/): Failed to transfer file https://repo.danubetech.com/repository/maven-public/info/weboftrust/ld-signatures-java/1.9.0/ld-signatures-java-1.9.0.pom with status code 500

[ALRubinger]

The repo looks back up as of now: https://repo.danubetech.com/repository/maven-public/com/danubetech/verifiable-credentials-java/1.6.0/verifiable-credentials-java-1.6.0.pom

[praiaAndrewLeach]

You think we can close this @jiyoontbd ?

[peacekeeper]

Hi all, thanks for reporting this, and sorry for the problems you experienced.

If it happens again, please feel free to create another issue like this one!

[ALRubinger]

Appreciate the fix, @peacekeeper!

[jiyoonie9]

@peacekeeper just FYI, this is giving us 404 today: https://repo.maven.apache.org/maven2/com/danubetech/verifiable-credentials-java/1.6.0/verifiable-credentials-java-1.6.0.pom

would you consider publishing to maven central?

[peacekeeper]

would you consider publishing to maven central?

I'm sorry but we don't have the workflows in place at the moment to publish to Maven central. Can you just use our repo (see README)?

E.g.: https://repo.danubetech.com/repository/maven-public/com/danubetech/verifiable-credentials-java/1.10.0/verifiable-credentials-java-1.10.0.pom

[peacekeeper]

Hello, we looked at this again, and it is not easy for us to publish to Maven Central due to requirements about proving ownership of the various libraries we maintain.

For example, in this librariy verifiable-credentials-java, we use the package name com.danubetech.*, which we control, but in another library ld-signatures-java, we use the package name info.weboftrust.*, which we don't control. So I think we would have to rename packages in order to be able to publish everything to Maven Central.