jdaugherty commented on issue #14814: URL: https://github.com/apache/grails-core/issues/14814#issuecomment-2972278286
I created this branch: https://github.com/apache/grails-core/tree/url-mapping-testing Added a controller "DuplicateController" in grails-test-examples/app1/.../DuplicateController Added a controller "DuplicateController" in grails-test-examples/plugins/loadfirst/...DuplicateController Ran the gradle build: ./gradlew build changed to the libs directory: cd grails-test-examples/app1/build/libs ran the bootJar: java -jar grails-test-examples-app1-0.1.jar Visited: http://localhost:8080/duplicate which shows "app controller" so I can't immediately reproduce this. Can you please provide an application to reproduce it? In the past these bugs have been because of a bug in the gradle plugin where the groovy compiler script isn't picked up. Is it possible you're still using the older gradle plugins? Can you look in the plugin build directory, there should be a grailsGroovyCompilerConfig, is there? For example in the branch I created, it has this content for compile: withConfig(configuration) { inline(phase: 'CONVERSION') { source, context, classNode -> classNode.putNodeMetaData('projectVersion', '0.1-SNAPSHOT') classNode.putNodeMetaData('projectName', 'grails-test-examples-plugins-loadafter') classNode.putNodeMetaData('isPlugin', 'true') } } If this script is missing, the behavior described in this ticket would exist. -- 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]
