[Java] sbt docker publish fails due to Arrow dependecies
- Lingua principale
- Java
- Stelle
- 94
- Fork
- 152
- Merge medio
- 3g 16h
- PR unite (30g)
- 11
Descrizione
Hello guys
I'm using Arrow in my Scala project and included Maven deps in sbt as required.
However, when I try to publish a Docker container with sbt 'docker:publish', I get the following error:
[error] 1 error was encountered during merge
[error] java.lang.RuntimeException: deduplicate: different file contents found in the following:
[error] /home/bku/.cache/coursier/v1/https/repo1.maven.org/maven2/org/apache/arrow/arrow-vector/0.14.1/arrow-vector-0.14.1.jar:git.properties
[error] /home/bku/.cache/coursier/v1/https/repo1.maven.org/maven2/org/apache/arrow/arrow-format/0.14.1/arrow-format-0.14.1.jar:git.properties
[error] /home/bku/.cache/coursier/v1/https/repo1.maven.org/maven2/org/apache/arrow/arrow-memory/0.14.1/arrow-memory-0.14.1.jar:git.properties
My project is [here](https://github.com/Clover-Group/tsp/tree/kafka).
You may check project dependency tree attached.
How do I fix that?
Thank you
**Reporter**: [Boris V.Kuznetsov](https://issues.apache.org/jira/browse/ARROW-6361)
#### Related issues:
- [[Java] Inclusion of a git.properties resource in Arrow JARs causes confusion in Spring Boot applications](https://github.com/apache/arrow/issues/32154) (relates to)
#### Original Issue Attachments:
- [tree.txt](https://issues.apache.org/jira/secure/attachment/12978611/tree.txt)
**Note**: *This issue was originally created as [ARROW-6361](https://issues.apache.org/jira/browse/ARROW-6361). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia riproducendo il fallimento di sbt's docker:publish e ispeziona l’albero delle dipendenze tree.txt allegato, concentrandoti sui JAR di Arrow elencati nell’errore. Il lavoro è completato quando la pubblicazione Docker termina senza l’errore di merge di git.properties duplicati; l’issue non identifica alcun file sorgente o test da modificare.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- docker, java, scala
- Ambito
- build-system
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 30/100