-
Notifications
You must be signed in to change notification settings - Fork 237
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
Prevent running unnecesarily #161
Comments
Hi Richard, thanks for using the tool. In Maven it is possible to configure typescript-generator either to run in each build or only on demand. |
I'd possibly suggest removing the lines referenced above, then any users who want the tool to run on every build can add |
This would be incompatible change. Lets wait for more feedback on this issue. |
I agree that running the tool on every build is overkill. It would be preferable to run |
Isn't the problem here just that the inputs and outputs are not declared, so gradle can't work out whether to skip it? Typically you would have the task run every time, but gradle will skip it if the inputs and outputs are not changed. |
@jechlin yes, automatically determining whether |
@r89m I just pushed commit which removed setting dependency on |
Perfect. It may be worth adding a note under the Gradle section of the readme outlining how to call the task, ie |
Hi Vojtěch,
Thanks for you tool - I've been finding it really useful.
One issue I've been having it that it runs a bit too often (on every build) due to the addition of the generateTypeScript tasks as a dependency on the classes tasks here:
https://github.com/vojtechhabarta/typescript-generator/blob/master/typescript-generator-gradle-plugin/src/main/java/cz/habarta/typescript/generator/gradle/TypeScriptGeneratorPlugin.java#L14-L16
Is there a reason for this, or would it be possible to configure it to not always run?
At the moment I'm doing
classes.dependsOn.remove(generateTypeScript)
which works but feels like a work around. I'd love it if I could configure it to only run when I callgenerateTypeScript
Thanks,
Richard
The text was updated successfully, but these errors were encountered: