-
Notifications
You must be signed in to change notification settings - Fork 32
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
Add caching for all SBT tasks #75
Conversation
* not having caching meant every time we run compile, the output files are deleted and freshly written. in a project with multiple modules and big swagger files, this leads to significant unnecessary overhead. * also added logging so that we see when things are compiled and made various other cleanups in the plugin.
@andreaTP @fralken What do you think? Please note that I created this PR (originally) based on the tag from 0.0.11, because that is the version we are using while master is already quite different. In fact, since
After that, I'd be happy to forward-port the changes, but I think the refactoring on |
Hi @rethab, thanks for your PR. If you need this on top of version For sure I would like to better isolate code generation from the plugin itself, now it is tightly coupled with Play code generation. This is my roadmap towards As for issue #74, I guess this should be fixed by the latest commits on |
@fralken sounds like a plan! Your code generation things are already on master though, aren't they? If so, are you going to drop them again or how shall we do this? |
We can create a branch from commit tagged |
Nice. Could you please do that? |
Ok, I just published version |
See PR #76 |
not having caching meant every time we run compile, the output files
are deleted and freshly written. in a project with multiple modules
and big swagger files, this leads to significant unnecessary overhead.
also added logging so that we see when things are compiled and made
various other cleanups in the plugin.