grails-plugin

In grails 2.x, we were allowed to add an in place plugin by adding following in BuildConfig.groovy grails.plugin.location."my-plugin" = "../my-plugin" My question is, can we add our local plugins similarly in-place in grails3.0 as well or there is some other way to do this in grails. Actual purpose is to test the plugin whether it's working properly or not before pushing it to bintray. Yes, there is. Grails 3 is based on Gradle so multi-project gradle builds solve your issue. Basically you add dependency as: compile project(':../my-custom-plugin') and has to modify settings.gradle to include

In spring security version 3.0.6, which fixed a CRLF logout exploit ( https://jira.springsource.org/browse/SEC-1790 ) they disabled the use of the 'spring-security-redirect' parameter. Default support for the redirect parameter in logout URLs has also been removed in 3.0.6. In 3.1 it already needs to be enabled explicitly. Is there a way to turn the redirect parameter back on, so that I can dynamically redirect in my Grails Spring Security Logout Controller? LogoutContoller.groovy def user = springSecurityService.currentUser if (params.redirect) { // this needs to log the user out and then

I need to call the Static Resources Plugin ( http://www.grails.org/Static+Resources+Plugin ) from my domain class. This works perfectly in a controller: def tstLink = resourceLinkTo(dir:"docs/${identifier}",file:originalFileName) but in a domain class I get Exception Message: No signature of method: static org.maflt.ibidem.Item.resourceLinkTo() is applicable for argument types: (java.util.LinkedHashMap) values: [[dir:docs/19e9ea9d-5fae-4a35-80a2-daedfbc7c2c2, file:2009-11-12_1552.png]] I assume this is a general problem. So how do you call a taglib as a function in a domain class? I

Is there an a way to initialise some data in a Plugin. I am modulizing my code and it would be nice to have something like the bootstrap in the Plugin but I cannot find it. Nor can I find references using the Google. BootStrap.groovy is excluded by default from a plugin zip, but you can create a MyPluginBootStrap.groovy (name doesn't matter, just can't be BootStrap) and that'll be packaged and run along with the application's BootStrap. 来源： https://stackoverflow.com/questions/2994379/is-there-an-equivalent-to-the-bootstrap-class-in-a-plugin

It appears the Grails 2.1 log4j plugin resets the log4j configuration during initialization of the grails application (see stack trace below). at org.apache.log4j.LogManager.resetConfiguration(LogManager.java:233) at org.apache.log4j.LogManager$resetConfiguration.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112) at org.codehaus.groovy.grails.plugins.log4j

I would like to use certain plugin in development environment, but would like to exclude this plugin from production and from generated war. What is the easiest way to accomplish this? Yes, using plugin scopes. From http://grails.org/1.1+Release+Notes : Plugins can now be scoped using either the environment or predefined build scopes: def environments = ['dev', 'test'] def scopes = [excludes:'war'] The plugins will only load in those environments and will not be packaged into the WAR file. This allows "development-only" plugins to not be packaged for production use. I don't believe that there

I get Error Failed to resolve dependencies error when I try to run, clean, or compile. My BuildConfig.groovy file is as follows: grails.servlet.version = "2.5" // Change depending on target container compliance (2.5 or 3.0) grails.project.class.dir = "target/classes" grails.project.test.class.dir = "target/test-classes" grails.project.test.reports.dir = "target/test-reports" grails.project.target.level = 1.6 grails.project.source.level = 1.6 //grails.project.war.file = "target/${appName}-${appVersion}.war" //Start company specific //set plugin directory (needed for having plugins in perforce)