|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
You still have invalid syntax. "mapping" is supposed to be a closure, but you are defining it sort of like a map (See http://grails.org/doc/latest/guide/single.html#ormdsl)
Please attach a complete zipped app containing this example that shows this working correctly. I have a hard time believing it would work correctly anywhere, let alone Jenkins. The jenkins grails plugin isn't going to alter the runtime GORM mapping behavior of grails. The only way it could do so is if you supplied an external config as part of the build step, which is a standard Grails convention anyways and again nothing specific to Jenkins.