@matt.aguirre Grails plugins have always been a double-edged sword. The ones that are maintained are the core plugins that the Grails team maintains, and those are pretty reliable. Anything else is community-driven. Meaning one person not unlike yourself thought there should be a plugin to make something easier or make integration with another technology smother. How long that person maintains that plugin, is vastly variable depending on how long they have Grails-related jobs, their interest in the plugin, how much time they have to do open source work, how demanding keeping up is, how long they stay a part of the community, etc. So the way I always looked at it was that the core plugins I could rely on or bug the Grails team about, and everything else was a good start that I might have to take and maintain or eventually migrate off of. If you're willing to, you can take up and maintain the plugin, if the original author is no longer interested in maintaining it, and or can't be gotten hold of, within a reasonable amount of time. At that point, if you want to pick it up I would get your changes ready to go, publish them, and then hit up

@puneetbehl

.

I think 90% of the plugins have been no longer necessary to maintain , they can be migrated to Spring Boot's AutoConfiguration , but plugins are still important , especially in the plugin based architecture can play its power , and the current plug-in API needs to be improved .