Nov 16th, 2010, 10:26 AM
grails controllers/services/taglibs in a seperate jar file
Is it possible to package Grails controllers/services/taglibs in seperate jar and use it in Grails application. We want to abstract common functionality there and use it in specific Grails apps.
I know that this would normally be achieved using grails plugin, however as far as we know hotfix to plugin requires rebuilt of all affected web apps using that plugin, which is a big overhead in our case (many web apps).
Would it be possible to package some of the core Grails artefacts (controllers/services/taglibs) in a jar file and put it on the classpath of the application server so in case of a bug we rebuilt only that jar, deploy it and restart app server as opposed to rebuilding all the web apps and redeploying them.
Thanks for any advices,
Nov 19th, 2010, 04:00 AM
It's not possible to package artifacts in JARs at the moment and it's unlikely to be added as a feature.
Note that plugins as runtime modules (so you can deploy them independently) is something we will be looking at for Grails 2.0.
Actually, it's probably possible to do what you want, but you have to understand the metadata requirements for Grails.