Open talios opened 6 years ago
Interesting - this worked fine on another one of my modules that included adt4j. I'll investigate further, it may be something on our end with how the projects laid out.
Looks like added a direct dependency on joda-convert resolved the issue ( we ban transitive deps as a rule ) but it seems what/how adt4j does it's thing, didn't like the missing dep.
Maybe update the error message to include something like "check your build dependencies/classpath before reporting."
Restructuring my build and when I add adt4j to the annotation class path I get the following error:
My project doesn't include joda-convert anywhere, I tried including it's jar also on the annotation classpath to no joy, and also adding it as a direct dependency of the maven-compiler-plugin but also no joy.