Various apicurio-registry-distro-connect-converter types are unresolvable by maven
See original GitHub issueFor these maven bits https://mvnrepository.com/artifact/io.apicurio/apicurio-registry-distro-connect-converter/1.3.2.Final
Various types are uploaded – jar / tar / zip. However, it seems that only the jar is actually resolvable by maven since the following does not resolve
<dependency>
<groupId>io.apicurio</groupId>
<artifactId>apicurio-registry-distro-connect-converter</artifactId>
<version>${version.apicurio.converter}</version>
<type>zip</type>
</dependency>
The only type which can be resolved is jar. Debezium does something similar with its connectors (we publish zip and tar archives into maven central) and the type identifier can be used to determine which version is resolved.
Issue Analytics
- State:
- Created 3 years ago
- Comments:18 (10 by maintainers)
Top Results From Across the Web
Add local external jar - should not point at files within the ...
Copy the entire folder for this jar file (I'll call this as installed folder) from your local Maven repository to your project's lib...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That works, thanks a lot guys!
I think I should be all right with just the latest version. I will test this and let you know, thanks!