Any Maven experts wanna weigh in on what I might b...

# build-tools

[Shawn]

Any Maven experts wanna weigh in on what I might be doing wrong? I’m trying out a multi-module build for the project I’m working on, and I’m running into some dependency/classpath issues. Here’s what my project looks like:

Foo
├── FooCore
│   ├── dependency-reduced-pom.xml
│   ├── pom.xml
│   ├── src
│   └── target
├── FooData
│   ├── pom.xml
│   └── src
├── FooService
│   ├── pom.xml
│   ├── src
│   └── target
└── pom.xml

I’m using dropwizard, which seems to prefer shaded jars, so I’ve got maven-shade-plugin in my root pom’s <build> section. I’ve also got <build> sections in the child poms that declare `sourceDirectory`; it seems that maven doesn’t include any of my Kotlin classes if I don’t do that.

The project ostensibly builds fine, but when I run my jar and try to hit the service w/ a request, I get a bizarre java.lang.AbstractMethodError: Method org/eclipse/jetty/server/HttpChannelOverHttp.contentComplete()Z is abstract.

On the advice of another K slack member, I added the maven-enforcer-plugin, and surprisingly enough, it doesn’t complain about Jetty, but it does complain about “Dependency convergence” errors for the two dependencies I’ve declared in the root pom, kotlin-stdlib-jre8 and slf4j-api. Really not sure where to go from here