Replies: 7 comments 4 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I tried to manually increase plexus-xompiler-manager to 2.15.0, still same result :(
|
Beta Was this translation helpful? Give feedback.
-
Tried now with 3.37.0, still same result
|
Beta Was this translation helpful? Give feedback.
-
While working on the reproduction, I think I figured it out. Looks like with 2.14.2 the apt processing was working even if there are some missing transitive dependencies, that isn't working anymore with 2.15.0. Concrete case was that we have an exclusion on spring for spring-jcl because we use slf4j and have it replaced with jcl-over-slf4j. We had only added jcl-over-slf4j where we are actually running it and not in the common module, now we have to add it to the compilation of the common module and then I think it should be good. |
Beta Was this translation helpful? Give feedback.
-
Unfortunately that was just one case, now found another where I think it's an issue. In this case I have one module which compiles fine and has a compile dependency to something, another module now depends on the first module and now fails with a similar issue, but in that case because it depends on the first module, the dependency should be included. So I think somehow transitive dependencies are not correctly included for the APT processing. I'll try to create a reproduction for it. |
Beta Was this translation helpful? Give feedback.
-
I gave up on this, for now I'm dropping the APT processing, then everything works. |
Beta Was this translation helpful? Give feedback.
-
When trying to upgrade from 2.14.2 to 2.15.0, we now get compilation errors like
We're using eclipse compiler with org.eclipse.jdt version 3.35.0
and changing the version of plexus-compiler ferom 2.14.2 to 2.15.0 is the only change.
Is there any known reason for this?
Beta Was this translation helpful? Give feedback.
All reactions