Skip to content
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

Allow controlling where code is generated #215

Open
dalewking opened this issue May 13, 2024 · 0 comments
Open

Allow controlling where code is generated #215

dalewking opened this issue May 13, 2024 · 0 comments

Comments

@dalewking
Copy link

The plugin is hardcoded to generate code to build/generated directory, but that is not what i want. I want it to go to a different directory and we actually commit the generated code in to git so we can see what has changed.

It is actually possible to change where it is generated by using something like:

        configureTask {
            outputDir.set("$projectDir/desiredDirectory")
        }

But the one thing that doesn't cover is the setting up of srcDir to the sourceSet. I can do that set up myself and end up with a srcDir pointing at non-existent directory, but it seems it would be easy enough to add a property to the spec block that is the output directory that just defaults to its current location but can be changed.

In addition, it is not possible to disable the automatic configuration of srcDir. It is required to have a string for sourceSet and if that sourceSet does not exist the build fails. So perhaps make the sourceSet property nullable and if null skip the srcDir configuration.

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

No branches or pull requests

1 participant