Null values injected when mixing Grails and Spring-batch

Mild annoyance that I haven't found the root cause for, but I'm finding that not all mistakes I make in wiring up a job (like missing tag closings or pointing to a bean that doesn't exist) showing up as errors when running tests. Instead it just injects null values and leaves me scratching my head. I assume this is because I'm using grails and not just straight spring, but again I'm still looking for the root cause.

Grails switching to and from inline plugin usage

We had developed some local plugins that would be installed in our main app when it was deployed. However, during development it was very convient to have them inline. Unfortunately, trying to switch back to inline usage we kept seeing a message indicating that it wanted to upgrade the plugin. Saying yes would cause it to delete the local folder and download the deployed version.

We were using a settings.groovy file in our ~/.grails that indicated the location for inline usage with "grails.plugin.location.pluginname". However, since we deployed the plugin with a name like 'plugin-name' it seems the two didn't match up. By using "grails.plugin.location.'plugin-name'" instead it worked like a champ.

Hrm...wonder if some validation could be added to help out with that - though I guess most people would just be consistent with the names...*sigh*