bazel-contrib / bazel-contrib/rules_jvm_external

Server returned HTTP response code: 400

Open
#238 8 comments 0 reactions 1 assignee View on GitHub

@steve-hb is already working on this.

Since Sep 17, 2019.

needs-clarification
Dominant language
Java
Stars
373
Forks
301
Avg merge
7d 17h
Merged PRs (30d)
3

Description

Hey,

today I tried to migrate a project to bazel using the "new" rules, but while building the project I got many errors related to one single dependency.

I tried to download the dependency manually, but then I found the reason for the failure:

https://maven.CENSORED.de/repository/CESNORED/com/lowagie/itext/2.1.7.js6/itext-2.1.7.js6.pom

-> js6 shouldn't be where it is. Tbh idk why it appended js6...

The dependency string is (defined in WORKSPACE -> maven_install -> artifacts):

"com.lowagie:itext:2.1.7"

This projects includes about 35 dependencies and this is the only dependency failing. I also migrated another project successfully in the past.
Changing the order of my dependencies changed nothing for me. The 6 is still the same. (so the number has nothing to do with the order)

Here is a working link to an official maven repo:

https://repo1.maven.org/maven2/com/lowagie/itext/2.1.7/itext-2.1.7.pom

RULES_JVM_EXTERNAL_TAG = "2.7"

RULES_JVM_EXTERNAL_SHA = "f04b1466a00a2845106801e0c5cec96841f49ea4e7d1df88dc8e4bf31523df74"

PS: Currently I don't know if this problem is only related to this repo or coursier directly.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.