You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing a Quarkus extension, it would be nice if the developer had a list of the existing BuildItems they can use.
For example, if I want to deploy a ServletContainerInitializer, I'd use a ServletContainerInitializerBuildItem. Finding the exact build item is a hard task and it would be nice to have a search mechanism to find this information
We have a page generated at https://quarkus.io/guides/all-builditems however it's a bit annoying to find what you need there. It would be nice if we had a list of potential builditems in an IDE tool window (bonus points if including those that are not available in the project)
The text was updated successfully, but these errors were encountered:
Another feature is that the @BuildSteps in an extension processor are considered unused methods in IJ, which is not true, but I am not sure if this should be in a separate issue
Another feature is that the @buildsteps in an extension processor are considered unused methods in IJ, which is not true, but I am not sure if this should be in a separate issue
Yes please create an issue for that. @fbricon did that for rest services.
When writing a Quarkus extension, it would be nice if the developer had a list of the existing BuildItems they can use.
For example, if I want to deploy a
ServletContainerInitializer
, I'd use aServletContainerInitializerBuildItem
. Finding the exact build item is a hard task and it would be nice to have a search mechanism to find this informationWe have a page generated at https://quarkus.io/guides/all-builditems however it's a bit annoying to find what you need there. It would be nice if we had a list of potential builditems in an IDE tool window (bonus points if including those that are not available in the project)
The text was updated successfully, but these errors were encountered: