Failing to generate a standalone pom

Help/Discuss
1

I am following the example at http://gradle.org/docs/current/userguide/maven_plugin.html to generate a POM file.

When I do it in a standalone project, it works, but in my “real” project:

This works:

    task writeNewPom << {
        // println pom
        pom {
            println "Hello " + this
            println "Hello " + delegate
            println "Hello " + project 
            // project { } 
      }
}

But the moment I uncomment the project { }, I get:

Caused by: org.gradle.api.internal.MissingMethodException: Could not find method pom() for arguments [build_4vy411cu6b99sjp1dveviwcg0$_run_closure3_closure41_closure46@5e9de4cf] on task ':mycompany-myproject:writeNewPom'.
        at org.gradle.api.internal.AbstractDynamicObject.methodMissingException(AbstractDynamicObject.java:68)
        at org.gradle.api.internal.AbstractDynamicObject.invokeMethod(AbstractDynamicObject.java:56)
        at org.gradle.api.internal.CompositeDynamicObject.invokeMethod(CompositeDynamicObject.java:172)
        at org.gradle.api.DefaultTask_Decorated.invokeMethod(Unknown Source)
        at build_4vy411cu6b99sjp1dveviwcg0$_run_closure3_closure41.doCall(/home/shevek/java/compilerworks/build.gradle:127)
        at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:548)
        at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:529)
        at org.gradle.api.internal.tasks.TaskMutator$1.execute(TaskMutator.java:77)
        at org.gradle.api.internal.tasks.TaskMutator$1.execute(TaskMutator.java:73)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)
2

Possibly useful differences between my standalone test project and this real one:
Test project has only the root project. Real project has the above code in a subprojects {} block.
JDK is Azul Zulu 8.6.0.1

I don’t even know what else to write, I’m totally foxed by this. Surely { println } is a closure just as { project { } } is, so if one works, the other should. It’s complaining about pom(Closure) not project anyway.

3

This is likely due to the fact the Maven plugin hasn’t been applied when you are attempting to call pom(). I would add the following to the subprojects { } block.

apply plugin: 'maven'
4

I’m afraid not. If I don’t apply the maven plugin then pom{} doesn’t work.

If I DO apply the maven plugin, then pom{} works, but pom{project{}} does not. It’s weird.

5

To clarify, the maven plugin is DEFINITELY applied in a subprojects{} scope.

6

I was only able to replicate this issue if you define a named argument for the subprojects { } closure named project. If you are doing so either rename the argument or remove it.

subprojects { project ->
7

Ohhh… you’re right! That’s VERY odd. Thank you; please consider this issue solved.

8

@mark_vieira Removing the project -> has introduced a new issue: Now the pom has no dependencies in it.

It feels as if the pom is generated with respect to the root project, even though it’s in a subprojects{} scope. The group id is missing, and the project name in the generated pom is still my root project name.

A few printlns shows me that while ‘project’ has the subproject value, it seems that ‘this’ references the root project.

The code is now roughly:

subprojects {
  group = 'com.myproject'
  apply plugin: 'maven'
  task generatePom << { pom { }.writeTo("build/pom.xml"); }
}

but the generated pom.xml is bare, and does not contain the group.

Calling project.pom {...} didn’t help.

9

This is probably some weird issue with closure delegates. Try this:

subprojects { proj ->
    task generatePom << {
        proj.pom {
            // pom configuration
        }
    }
}
10

No luck yet. Of course I’ve constructed a minimal test case, and that passes, whereas my main project fails, and I’m playing spot-the-difference. all my printlns print equivalent things in both systems, though. :frowning: What else can I print to help me figure this out?

11 
    println "Compile project is " + project 
    task createPom << {
        println "Runtime project is " + project 
        pom {
            println "Project is " + project + " in " + delegate.dump() + " ; this=" + this

Confirmed: delegate.dump() refers to the subproject in my test case but the root project in my real code.

Using subprojects { subproject -> ..... subproject.pom { } } does not make the delegate be the subproject. :frowning:

12

Solved. My fault now. During one of my experiments, I moved the maven plugin to the root project. Your other fix solved the other thing. thank you.