pappmiku opened a new issue, #14923:
URL: https://github.com/apache/grails-core/issues/14923

   ### Expected Behavior
   
   The `resources.groovy` file should be bundled by default regardless of what 
plugins are applied.
   
   ### Actual Behaviour
   
   Having the `org.apache.grails.gradle.grails-plugin` plugin applied in 
`build.gradle` causes the `resources.groovy` file to not be included in 
`build/resources/main/spring`.
   It looks to be a direct match for the file name; files with a profile suffix 
or named e.g. `resourcess.groovy` are included.
   
   Upon further inspection, it seems even the `views` folder (or more likely 
`*.gsp` files) is affected and completely excluded when using the plugin, 
though other files such as `application.groovy`, `runtime.groovy` and 
`logback-spring.xml` are bundled correctly.
   
   Without the plugin         |  With the plugin
   :-------------------------:|:-------------------------:
   <img width="411" height="882" alt="Image" 
src="https://github.com/user-attachments/assets/fe7241fc-ac8e-47a6-ba19-a00b49f1c3b3";
 />  |<img width="410" height="795" alt="Image" 
src="https://github.com/user-attachments/assets/760febf6-b52b-4280-bbf2-ac77784ecd37";
 />
   
   ### Steps To Reproduce
   
   1. bootstrap a new project using https://start.grails.org/ (both M5 and 
SNAPSHOT have this behaviour)
   2. run the `others/processResources` gradle task
   3. check the `build/resources/main/spring` folder for the `resources.groovy` 
file (it should be there)
   4. add `plugins.apply("org.apache.grails.gradle.grails-plugin")` to 
`build.gradle`
   5. run `others/processResources` again
   6. check the `build/resources/main/spring` folder for the `resources.groovy` 
file (it should NOT be there)
   
   ### Environment Information
   
   - OS: Manjaro Linux 6.15.6-arch1-1.1-g14
   - JDK: 17.0.15-tem
   
   ### Example Application
   
   _No response_
   
   ### Version
   
   7.0.0-SNAPSHOT


-- 
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]

Reply via email to