Explicit marking of maven junit targets as test only cause issues in downstream targets #10

gkdn · 2025-03-01T02:27:19Z

bazel_worker_java defines junit maven.artifacts via explicitly marking them as testonly.

However there are projects out there that define a dependency to junit via their pom but they are not test only targets. As a result, depending on bazel-worker-java breaks the build in such cases.

For example:
https://github.com/javacc/javacc/blob/d1e39b60908fb6c6cd5b7c278cca63324a46eee8/pom.xml#L165

I think it would be more appropriate to mark test-only targets via repo aliases instead of directly on maven.install.

On the other side, these targets should have been probably also marked as devonly.

This helper provides additional features like GC and worker multiplexing - though they are not yet enabled in this CL. CL is temporarily forking the files until bazel_worker_java could be added as a dep for repo: bazelbuild/bazel-worker-api#10 PiperOrigin-RevId: 733024990

gkdn changed the title ~~Explicit marking of maven junit targets cause issues in downstream targets~~ Explicit marking of maven junit targets as test only cause issues in downstream targets Mar 1, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Explicit marking of maven junit targets as test only cause issues in downstream targets #10

Explicit marking of maven junit targets as test only cause issues in downstream targets #10

gkdn commented Mar 1, 2025

Explicit marking of maven junit targets as test only cause issues in downstream targets #10

Explicit marking of maven junit targets as test only cause issues in downstream targets #10

Comments

gkdn commented Mar 1, 2025