Skip to content

The JavaGenerator plugin for Gradle has no cache configuration #7091

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
heruan opened this issue May 26, 2025 · 1 comment
Open

The JavaGenerator plugin for Gradle has no cache configuration #7091

heruan opened this issue May 26, 2025 · 1 comment

Comments

@heruan
Copy link

heruan commented May 26, 2025

Is your enhancement related to a problem? Please describe

When running the crd2Java task of the JavaGenerator plugin for Gradle, the plugin always generates sources even if the CRDs have not changed.

Describe the solution you'd like

This could be optimized by setting the CRDs as inputs of the task, and the generated sources as outputs of the task.

Describe alternatives you've considered

No response

Additional context

No response

@andreaTP
Copy link
Member

Hi @heruan , thanks for taking the time to file this issue!

That's correct, we are currently always re-generating everything, since the generation is idempotent this is "only" a matter of efficiency.

Seems like you already know what are the necessary changes(I expect something along those lines ), would you mind submitting a PR to fix this aspect?

As input we need to have the CRDs plus the plugin configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants