Adam,

On Sat, 2009-05-02 at 07:05 +1000, Adam Murdoch wrote:
> Can you run this build with -s and post the stack trace?

Certainly.  I should have done this in the first place.

> Russel Winder wrote:
> > I just tried Gradle again for the first time in over a week.  I pulled
> > Trunk and rebuilt and now a script that used to work gives me the error:
> >
> >         Cause: Configuration with name 'providedCompile' not found.
> >
> > Clearly there is a change that I have failed to note and account for in
> > my use of Gradle, but I haven't a clue as to what it might be.  Anyone
> > any ideas?  Thanks.


        Cause: Configuration with name 'providedCompile' not found.
        
        Exception is:
        org.gradle.api.GradleScriptException: Build file 
'/home/users/russel/Repositories/Bazaar/Masters/ADS/build.gradle' line: 48
        A problem occurred evaluating root project 'ADS'.
                at 
org.gradle.configuration.DefaultProjectEvaluator.evaluate(DefaultProjectEvaluator.java:66)
                at 
org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:642)
                at 
org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:62)
                at 
org.gradle.configuration.BuildConfigurer$_closure1.doCall(BuildConfigurer.groovy:41)
                at $Proxy0.execute(Unknown Source)
                at 
org.gradle.api.internal.project.AbstractProject.applyActions(AbstractProject.java:613)
                at 
org.gradle.api.internal.project.AbstractProject.allprojects(AbstractProject.java:608)
                at 
org.gradle.configuration.BuildConfigurer.process(BuildConfigurer.groovy:48)
                at org.gradle.Gradle.runInternal(Gradle.java:113)
                at org.gradle.Gradle.run(Gradle.java:93)
                at org.gradle.Main.execute(Main.java:229)
                at org.gradle.Main.main(Main.java:79)
                at org.gradle.BootstrapMain.main(BootstrapMain.java:53)
        Caused by: org.gradle.api.artifacts.UnknownConfigurationException: 
Configuration with name 'providedCompile' not found.
                at 
org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.createNotFoundException(DefaultConfigurationContainer.java:72)
                at 
org.gradle.api.internal.DefaultDomainObjectContainer.getByName(DefaultDomainObjectContainer.java:91)
                at 
org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.getByName(DefaultConfigurationContainer.java:32)
                at 
org.gradle.api.plugins.MavenPlugin.configureWarScopeMappings(MavenPlugin.java:106)
                at org.gradle.api.plugins.MavenPlugin.apply(MavenPlugin.java:56)
                at 
org.gradle.api.internal.project.PluginRegistry.apply(PluginRegistry.java:78)
                at 
org.gradle.api.internal.project.AbstractProject.usePluginInternal(AbstractProject.java:677)
                at 
org.gradle.api.internal.project.AbstractProject.usePlugin(AbstractProject.java:656)
                at 
org.gradle.api.internal.project.AbstractProject.usePlugin(AbstractProject.java:652)
                at 
org.gradle.api.internal.project.DefaultProject.invokeMethod(DefaultProject.groovy)
                at 
org.gradle.groovy.scripts.DefaultProjectScriptMetaData$_applyMetaData_closure1.doCall(DefaultProjectScriptMetaData.groovy:34)
                at build_gradle.run(build_gradle:48)
                at 
org.gradle.configuration.DefaultProjectEvaluator.evaluate(DefaultProjectEvaluator.java:61)
                ... 12 common frames omitted
        
        BUILD FAILED
        
        Total time: 3.694 secs

OK, this is clearly to do with the Maven plugin.  I removed the:

        usePlugin ( 'maven' )

and the little bit of code for the install task from my build.gradle and
everything worked so the all the Java plugin things work fine.  As soon
as I add:

        usePlugin ( 'maven' )

things go awry.  So the problem is fairly and squarely in there.
COnsequently, the problem must be due to something to do with:

        |> grep War `find . -name "*Maven*"`
        ./api/plugins/MavenPlugin.java:        if (isWarPluginApplied(project)) 
{
        ./api/plugins/MavenPlugin.java:            
configureWarScopeMappings(project.getRepositories(), 
project.getConfigurations());
        ./api/plugins/MavenPlugin.java:    private boolean 
isWarPluginApplied(Project project) {
        ./api/plugins/MavenPlugin.java:    private void 
configureWarScopeMappings(ResolverContainer resolverContainer, 
ConfigurationContainer configurations) {
        ./api/plugins/MavenPlugin.java:        
resolverContainer.getMavenScopeMappings().addMapping(PROVIDED_COMPILE_PRIORITY, 
configurations.getByName(WarPlugin.PROVIDED_COMPILE_CONFIGURATION_NAME),
        ./api/plugins/MavenPlugin.java:        
resolverContainer.getMavenScopeMappings().addMapping(PROVIDED_RUNTIME_PRIORITY, 
configurations.getByName(WarPlugin.PROVIDED_RUNTIME_CONFIGURATION_NAME),

I am not sure why the Maven plugin must depend on the War plugin, but
clearly it does, but for me this Just Breaks :-(

-- 
Russel.
============================================================
Dr Russel Winder                 Partner

Concertant LLP          t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,     f: +44 8700 516 084    voip:  
sip:[email protected]
London SW11 1EN, UK.    m: +44 7770 465 077    xmpp: [email protected]

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to