-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
enable gradle for extension development #3322
Comments
If nobody start to work on it, i will try. |
request makes sense but this would be post v1. I would actually prefer we had a native No need to strictly use either mvn or gradle for this step is my point ;) |
This would be largely beneficial for the expansion and adoption of Quarkus. We are incredibly interested in using Quarkus because it's a great framework and the extensions really open up possibilities for my team. However, our CI/CD architecture relies on Gradle (and many can argue that Gradle is superior) so being able to develop extensions with Gradle would be great! |
sorry I have no more time to work on quarkus. But you can try a contribution. create a task here: |
I think this one can be close as the |
The cli Would be the place to have the command yes. Not sure if all is in place to develop a quarkus extension with gradle - @aloubyansky ? |
It's definitely possible to develop extensions with gradle. As to the tooling support, the maven extension-descriptor goal is pretty advanced now. But we have to start with the equivalent gradle support at some point. So, let's. |
I misunderstood the issue. I will start working on this next week then :) |
I didn't mean to add |
Yes, when I mention that the issue could be close as the cli is here I was thinking about the project generation part. But as you mentioned in your previous comment, the gradle plug-in don't do anything regarding the extension property file. That could be handled some how in the plug-in. |
+1 I've updated issue title to reflect this. Have create extension cli command support gradle but for that have the remaining things done we still only have in maven ext plugin |
Would love to be able to add a real Quarkus extension in JobRunr. JobRunr uses Gradle as build tool and I prefer not to mix this with maven. |
@rdehuyss do you mean you want to develop a Quarkus extension for the JobRunr? I can help you set it up in Gradle. |
@aloubyansky , that would be great! Is there perhaps an example somewhere I missed? |
Are you on Zulip? That'll be easier to communicate. |
I can help too if needed. |
Not yet, I'll join in about an hour. |
Ping @aloubyansky and @glefloch when you're there. |
which is the state of this? I saw in the devtool directory that there is a I'm trying to use the gradle
Note that there is no Do you know of any extension using Gradle? |
It's supposed to be https://quarkus.io/guides/writing-extensions#using-gradle |
Right there is a minimal quarkus extension gradle plugin. It has some limitation such as unit test support that need to be adresse before it can be fully used. and also, this project have a gradle based quarkus extension but without using the plugin: https://github.com/jobrunr/jobrunr/tree/master/framework-support/jobrunr-quarkus-extension Regarding your error, I will update at least the error message, thanks for reporting it. |
thank you for pointing me in the right direction! 😀 |
A followup of #2113 . A Maven mojo was added via #3191 (see also #3321 )
The text was updated successfully, but these errors were encountered: