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
It appears that in reactor projects where downstream modules depend on the build output of a module in which protobuf-maven-plugin generates code, with Maven 3.8.x the build products are no longer available on the classpath for the downstream modules—they fail to compile with "cannot find symbol" errors for the protobuf products.
I find that the protobuf products are built as expected in target/generated-sources and target/classes of the upstream module, it appears that the problem is only in classpath propagation through the reactor build state.
Describe the bug
It appears that in reactor projects where downstream modules depend on the build output of a module in which protobuf-maven-plugin generates code, with Maven 3.8.x the build products are no longer available on the classpath for the downstream modules—they fail to compile with "cannot find symbol" errors for the protobuf products.
I find that the protobuf products are built as expected in
target/generated-sources
andtarget/classes
of the upstream module, it appears that the problem is only in classpath propagation through the reactor build state.Reverting to Maven 3.6.3 works around the issue.
Environment
Standalone or IDE
Standalone
Plugin configuration
To Reproduce
I will try to come back to this issue to add a minimal and publicly-available reproduction project.
Steps to reproduce the behavior:
mvn --also-make compile
Log output
Compilation errors with "cannot find symbol" for the proto products. Again, can update with actual build logs from a public repro.
Expected behavior
Module B builds successfully, as it does when using Maven 3.6.
The text was updated successfully, but these errors were encountered: