[
https://issues.apache.org/jira/browse/AVRO-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906736#comment-17906736
]
Martin Tzvetanov Grigorov commented on AVRO-4099:
-------------------------------------------------
You can workaround the issue by excluding the missing dependencies:
{code:java}
avro-exec on main [!?] is 📦 v0.0.1-SNAPSHOT via ☕ v17.0.13
❯ git diff
diff --git i/pom.xml w/pom.xml
index aadcbf7..58174f3 100644
--- i/pom.xml
+++ w/pom.xml
@@ -17,7 +17,7 @@
<properties>
<java.version>21</java.version>
- <avro.version>1.11.3</avro.version>
+ <avro.version>1.11.4</avro.version>
<m2.repository>${user.home}/.m2/repository</m2.repository>
</properties>
<dependencies>
@@ -70,6 +70,16 @@
<groupId>org.apache.avro</groupId>
<artifactId>avro-tools</artifactId>
<version>${avro.version}</version>
+ <exclusions>
+ <exclusion>
+ <groupId>org.apache.avro</groupId>
+ <artifactId>trevni-core</artifactId>
+ </exclusion>
+ <exclusion>
+ <groupId>org.apache.avro</groupId>
+ <artifactId>trevni-avro</artifactId>
+ </exclusion>
+ </exclusions>
</dependency>
</dependencies>
</plugin>
{code}
I didn't find how to exclude only the `classifier=tests` dependencies ...
If you need to use the non-tests Trevni (with avro-tools) then you can add them
explicitly to the dependencies.
> trevni-core-tests and trevni-avro-tests are missing from maven central in
> 1.11.4
> --------------------------------------------------------------------------------
>
> Key: AVRO-4099
> URL: https://issues.apache.org/jira/browse/AVRO-4099
> Project: Apache Avro
> Issue Type: Bug
> Components: trevni
> Affects Versions: 1.11.4
> Reporter: Giacomo Baso
> Priority: Major
>
> avro-tools declares a depedency on trevni-core:tests and trevni-avro:tests.
> Since those are missing from maven central (compare
> [v1.11.4|https://repo1.maven.org/maven2/org/apache/avro/trevni-core/1.11.4/]
> with
> [v.1.11.3|https://repo1.maven.org/maven2/org/apache/avro/trevni-core/1.11.3]
> - or any other), any uses of avro-tools 1.11.4 via maven (for example using
> maven exec plugin) fails.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
