-
Notifications
You must be signed in to change notification settings - Fork 102
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
Using thrifty-plugins with the thrifty gradle plugin #489
Comments
There's no official way to run plugins via the gradle plugin because the need has never arisen and I haven't previously thought about it. I like your JavaExec solution as a one-off, but will have to think about how to make this work "properly". |
Oh, I see. Your JavaExec task works because it's going through the "front door", as it were, via the |
Thank you very much for the prompt response and for your efforts to solve it! If you need my assistance I will be glad to help. |
With #490, your first effort at using the gradle plugin (extending the thrifty classpath) should work. As a bonus, you don't even have to specify the other thrifty libs - just your plugin. (the thrifty libs are already on the classpath). I'll open a new issue to track API design and testing; in the meantime will make a point release. |
Ok, thank you! I will check it as soon as possible. |
Version 3.1.0-RC02 contains this fix, and should be available on Maven Central and the Gradle Plugin Portal within the next 10-15 minutes. |
Works like a charm, thank you a lot! |
Glad to hear it - thanks for confirming! |
Finally coming back to this - soon you'll be able to declare a dependency using the new
|
This is not an issue but rather a question. Unfortunately I haven't find any other way to ask this question.
Is it possible to use thifty-plugins together with thrifty gralde plugin? How such a build.gradle[.kts] could look like?
I have tried to extend thriftyClasspath for the
generateThriftyFiles
task like this:but apparently it doesn't work.
However, it does work if I use a JavaExec approach like this:
The text was updated successfully, but these errors were encountered: