Same problem as Malte:
My plugin has a dependency on jquery, but my grails app using the plugin can't resolve jquery when using the "grails.plugin.location.X" mechanism unless it's an absolute path. I would never have figured this out if it were not for Malte's comment above. The docs on specifying plugin locations (12.2) use a relative path in the example... which is what i used and works... only if your plugin itself does not have further dependencies (e.g. jquery).
Grails plugin: A
Grails application using plugin: B
Both A and B projects reside under same directory: /Users/admin/Documents/workspace
Plugin class for A (AGrailsPlugin.groovy):
def dependsOn = ['jquery':'1.4 > *']
BuildConfig.groovy for B:
grails.plugin.location.A = "../A"
Results in the following error on run-app for B:
Running script /Users/admin/Applications/springsource/grails-1.3.6/scripts/RunApp.groovy
Environment set to development
[groovyc] Compiling 1 source file to /Users/admin/Documents/workspace/B/target/classes
- Plugin: A
! jquery (Required: 1.4 > *, Found: Not Installed) [INVALID]
When i change the BuildConfig parameter to use an absolute path, it works.
Revised BuildConfig.groovy for B:
grails.plugin.location.A = "/Users/admin/Documents/workspace/A"
Not sure why a difference in absolute/relative path for an apps plugin resolution would affect dependency resolution for that plugins' dependency resolution (jquery).