See: http://forums.gradle.org/gradle/topics/custom_plugin_jar_meta_inf_gradle_plugins_properties_file_not_found_error
The JDK internally caches a table of contents of jar files that it loads, which causes problems when using the daemon because jar files can change during the life of the JVM. Because the daemon is long lived, this causes us problems. I think we could solve this particular problem by using our own strategy instead of classLoader.getResource() here: https://github.com/gradle/gradle/blob/master/subprojects/core/src/main/groovy/org/gradle/api/internal/plugins/DefaultPluginRegistry.java#L87 Anyway, there is a workaround of killing the daemon or not using it so this is no blocker. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
