vigneshsiva11 opened a new pull request, #15571: URL: https://github.com/apache/grails-core/pull/15571
## **Overview** This change is the step after the first part. It makes the Spring Boot configuration metadata generation better by improving the structure and consistency. ### Key Improvements * I put the annotation processor configuration in one place * Removed the setup from each module's build file * i still only enable it for "grails-databinding." * Made sure the metadata generation works as it should without adding risk This part is about making the code better and putting things together. I do not use the processor for things that I did before. --- ## **Problem** In this part I only enabled configuration metadata generation for "grails-databinding" because of some problems. * There were risks with incremental compilation * It was not stable when i used annotation processors for Groovy- modules But this also caused some issues. * i had to do the configuration many times * It was harder to maintain. i could easily make mistakes ### This Change Fixes * I do not have to do the configuration many times * I have control over annotation processing * It is easier to add this feature to things in the future --- ## **Technical Details** ### **Build Logic Changes** * i made a shared configuration for annotation processors * i put this logic in a place ### **Modules Updated** * `grails-databinding` * Now it uses the shared processor configuration * It works the same as before ### **Removed** * i removed the annotation processor setup from each module's build file ### **Key Characteristics** * i still have to enable annotation processing manually * It only works for "grails-databinding." * It does not change how things are compiled or what the output metadata looks like --- ## **Issues** * This is related to issue #15469 * It is the step, after #15566 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
