macro-compat | small library which allows you to compile macros | Plugin library

From the gradle java-plugin doc,

The api configuration should be used to declare dependencies which are exported by the library API, whereas the implementation configuration should be used to declare dependencies which are internal to the component. Dependencies appearing in the api configurations will be transitively exposed to consumers of the library, and as such will appear on the compile classpath of consumers. Dependencies found in the implementation configuration will, on the other hand, not be exposed to consumers, and therefore not leak into the consumers' compile classpath

Let's say of you want to expose eu.timepit:singleton-ops_${vs.scalaBinaryV}:0.5.0 to all of the common library then you need to add this as api dependency in common module build.gradle.kts.

So I managed to fix the problem with the maven-shade-plugin. I added following piece of code to my pom.xml file:

Try replace logback with log4j (remove logback dependency), at least it helped in our similar case.

First make sure it works when running sbt it:test or if you use sub-modules sbt module/it:test

If it doesn't sbt has this great resource: https://www.scala-sbt.org/1.x/docs/Testing.html#Integration+Tests

As a template for a working setup, a build.sbt:

To Provide a complete answer to those who might stumble upon this question later:

stsatlantis' suggestion indeed solves one of the problems (thanks for your comment!), while the other one can be solved by slightly modifying the accountStatusEncoder. An alternative solution is to use case classes in your ADT, however, if you already have case objects it is probably because they better fit your needs/domain.

The changes I ended up going with:

It turned out the issue was that in a subproject, one of our teammates imported org.scalatest in the maven pom.xml and didn't set the scope to test... Aside from the crazy dependency conflicts this created, it was somehow overriding my version of scalatest. By setting the scope of scalatest to "test" in the subproject, this issue was fixed. i.e. Adding test fixed things; see the example below.

Standard ZIP file can be used for that (which JAR is with MANIFEST.MF file as the first file in ZIP).

The following layout have to be used - which is same as Maven repositor layout. The reasin is Karaf uses Aether to resolve bundles, which is the engine of newer versions of maven. (As I remember later than 3.3):

/repository - which is standard maven layout. So the bunldes have to be stored as groupId parts as directory / version / artifactId-version.jar.

In the repository you have to store the feature repository xml file too, to be able to resolve features. Have to store same as it is on local maven repository.

Examample of kar structure (its a fragment):