ability to override a plugin's artefacts

have to be post 1.0 i'm afraid

one more similar use case. sometimes, user may want to disable/remove particular controller/services of a plugin, e.g.a demo controller

reference
http://www.nabble.com/Grails-plugin-and-demo-tt21494978.html#a21494978

Well for your issue, you could get around it by simply defining another Spring bean that matches the name of the service provided by the plugin. So if you have a FooService provided by Plugin A you simply defined

fooService(MyAlternativeImplementation)

in resources.groovy. For your case Mingfai. I have implemented the ability for a plugin author to exclude particular resources from a plugin when installed into an app like:

class FooGrailsPlugin {
	def pluginExcludes = ['grails-app/controllers/DemoController.groovy']
}

However I will leave this issue open as it would be nice to add overriding simply by defining a class of the same name as in a plugin, but I'm not sure we'll get this into 1.1

Moving non-critical issues that aren't going to make it into 1.1 to 1.2

I had this same problem while using Searchable plugin. I wanted to override the default SearchableController, but at least in my case the version in my project never got compiled. I think that groovyc doesn't overwrite existing classes and that was the problem. I made a quick fix to the _GrailsCompile.groovy . The "project classes" get compiled in a separate directory and they are moved to the actual classes directory after compiling . This solution makes it possible to override classes from plugins. (My env is Linux + Java 1.6.0_14ea) I'll attach the patch too.

Changes to _GrailsCompile.groovy that make it possible to override classes (like Controllers) coming from plugins in the grails application.

I'm not sure if this is the right solution, really we should be modifying the GrailsCompiler class to exclude plugin resources that are duplicates of application resources in the compile process. Applying this patch feels a bit hacky.

I agree that it's a quick fix that solved my problem. It's a simple solution.

btw. for controllers there isn't any problems in development mode in the original version (application's controller gets used instead of plugin's controller with the same name). The problem hit me after deploying the app as a war file.

Would the correct solution be to modify the compilePlugins target in _GrailsCompile.groovy to exclude any source file found in the application project? (is it getting too complex?)

The original solution didn't work in my env. I just wonder why groovyc doesn't overwrite the class files automaticly since application classes get compiled after plugin classes. Maybe it's normal javac/groovyc behaviour. btw. the original solution has a small problem because it might leave unused inner class files in the target directory.

Hi,

I'd like to override the doWithSpring(), doWithDynamicMethods() etc. methods of a plugin. Judging by the discussion above it seems that I could achieve this by defining a class with the same name as the plugin descriptor and placing it in the conf directory, is that right?

However, it seems like I'll need to wait until version 1.2-M2 before this will work, correct?

Thanks,
Don

I would appreciate this feature too. Hope it's going to be made into 1.2.
Thanks

There is no scope / time to resolve these remaining lower priority issues for 1.2 so moving to 1.3

for 1.2 final only issues considered blocking will now be fixed

Fixed: http://github.com/grails/grails-core/commit/595d80abe7efede56e22de64d30a5c1fc9110638

I used a classloading solution for development instead of relying on copying. Also formalized the separation of a plugin classes directory from the main classes directory.

I am running 1.3.1. I tried to override a plugin class located in the 'src/groovy' directory but it didn't work. The original plugin class still got loaded. My question is: can we overwrite the classes in the src folder?