You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compared to version 3.37.0, version 3.37.1 and up contain an additional optional dependency on com.palantir.baseline:gradle-baseline. That artifact is not published to Maven Central. This was previously not a problem, but (I think) due to MCOMPILER-272, as of maven-compiler-plugin version 3.9.0, using this dependency causes a build failure when using Maven:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile (default-compile) on project refaster-compiler: Resolution of annotationProcessorPath dependencies failed: Missing:
[ERROR] ----------
[ERROR] 1) com.palantir.baseline:gradle-baseline:jar:4.156.0
It's not possible to simply tell Maven to exclude the dependency, because annotationProcessorPaths entries don't support <exclusions> (see MCOMPILER-395).
Given the name of this project I'm not sure you care about Maven compatibility at all, but I thought I'd share :). If nothing else it might be good to document this limitation.
NB: Of course maven-compiler-plugin should handle this better; I added a comment here.
The text was updated successfully, but these errors were encountered:
Compared to version 3.37.0, version 3.37.1 and up contain an additional optional dependency on
com.palantir.baseline:gradle-baseline
. That artifact is not published to Maven Central. This was previously not a problem, but (I think) due to MCOMPILER-272, as ofmaven-compiler-plugin
version 3.9.0, using this dependency causes a build failure when using Maven:It's not possible to simply tell Maven to exclude the dependency, because
annotationProcessorPaths
entries don't support<exclusions>
(see MCOMPILER-395).Given the name of this project I'm not sure you care about Maven compatibility at all, but I thought I'd share :). If nothing else it might be good to document this limitation.
NB: Of course
maven-compiler-plugin
should handle this better; I added a comment here.The text was updated successfully, but these errors were encountered: