olliefreeman opened a new issue, #14597: URL: https://github.com/apache/grails-core/issues/14597
Don't know if this belongs in this repo or grails-core. Thanks for reporting an issue for GORM, please review the task list below before submitting the issue. > WARNING: Your issue report will be closed if the issue report is incomplete and does not include an example. Make sure the below tasks not completed! > NOTE: If you are unsure about something and the issue is more of a question a better place to ask questions is on Stack Overflow (http://stackoverflow.com/tags/grails) or Slack (http://slack-signup.grails.org). DO NOT use the issue tracker to ask questions. ### Task List - [x] Steps to reproduce provided - [ ] Stacktrace (if present) provided - [x] Example that reproduces the problem uploaded to Github - [x] Full description of the issue provided (see below) ### Steps to Reproduce If you initialise/create any services as interfaces or abstract classes and use the `grails.gorm.services.Service` annotation, and then also wire in the grailsApplication to verify, none of the annotated classes are included inside the Service artefact type. Even if they are in the `grails-app/services` folder, and end in `Service`. I believe this is affecting wiring of spring bean dependencies. ### Expected Behaviour Services should be in the Service artefact list and all beans should be wired. ### Actual Behaviour They aren't ### Environment Information - **Operating System**: Mac OS X Sierra - **GORM Version:** 6.1.8 - **Grails Version (if using Grails):** 3.3.1 - **JDK Version:** 8u141 ### Example Application https://github.com/olliefreeman/grails-issues Run the `rest.api.app.NonDomainServiceSpec` integration test -- 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]
