buildscript.dependencies.classpath overwrites dependencies of second external plugin

I am using two external plugins.

buildscript {

repositories { … }

dependencies {

classpath group: ‘at.mikemitterer.gradle’, name: ‘TexenPlugin’, version: ‘1.4’

classpath group: ‘at.mikemitterer.gradle’, name: ‘jettytoolsplugin’, version: ‘1.1’

} }

The TexenPlugin (my own plugin) sets some dependencies in project.configurations:

Source:

void apply(Project project) {

configureDependencies(project);

}

private void configureDependencies(final Project project) {

project.configurations { velocityAntTask }

project.repositories { mavenCentral() }

project.dependencies {

velocityAntTask group: ‘org.apache.velocity’, name: ‘velocity’,

version: ‘1.7’

velocityAntTask group: ‘commons-lang’,

name: ‘commons-lang’,

version: ‘2.6’

velocityAntTask group: ‘commons-collections’, name: ‘commons-collections’,version: ‘3.2.1’

}

}

If the order of the classpath-settings is as shown above (TexenPlugin first) - everything works fine but if “jettytoolsplugin” is first:

dependencies {

classpath group: ‘at.mikemitterer.gradle’, name: ‘jettytoolsplugin’, version: ‘1.1’

classpath group: ‘at.mikemitterer.gradle’, name: ‘TexenPlugin’, version: ‘1.4’

}

the “texen”-Task (defined in TexenPlugin) fails because it can’t find it’s dependencies anymore.

It seems as the second classpath entry overwrites somehow the first one… Any hints?

Hard to say what’s going on. Probably best to ask the author of the plugins.