gradlecm does not work with maven-publish

[tschulte]

The gradlecm plugin does not work smoothly with maven-publish(http://www.gradle.org/docs/current/userguide/publishing_maven.html).

If the uploadArchives configuration is replaced with

publishing {
    publications {
        plugin(MavenPublication) {
            from components.java
        }
    }
    repositories {
        maven {
            name 'snapshots'
            url "file://${rootDir}/../mvn-repo/snapshots"
        }
        maven {
            name 'releases'
            url "file://${rootDir}/../mvn-repo/releases"
        }
    }

}

and

apply plugin: 'maven'

replaced with

apply plugin: 'maven-publish'

I get the error

FAILURE: Build failed with an exception.

* Where:
Build file 'C:\projekte\gradle\GradleCMPlugin\build.gradle' line: 92

* What went wrong:
A problem occurred evaluating root project 'GradleCMPlugin'.
> Cannot configure the 'publishing' extension after it has been accessed.

[kercheval]

The publish maven and ivy plugins are still in incubation, but the publish task will not allow after task graph manipulation (in fact, these tasks are can only be configured once per invocation and are considered deferred.)

This will require an alternate technique for a hook or may require an explicit doFirst addition to the publish task.

An explicit task for upload which does an explicit publish execute and setting the upload task to this new one explicitly is a reasonable workaround for now.

ie.

buildreleaseinit {
uploadtask = myUploadTask
}

myUploadTask << {
tasks.publish.execute()
}

[kercheval]

Corrected in code as of commit 4401f42.

Corrected by altering the hook method to use a task execution listener installed after task graph completion. Some additional testing and readme additions to be made prior to formal release (binary updates).

[kercheval]

Version 1.17-20131127.150613 has been published

[tschulte]

It does still not work. The problem seems to be with the buildinfo plugin. If I manually apply all plugins gradlecm applies and leave out buildinfo, it works.

[kercheval]

I am currently duplicating and evaluating.

[kercheval]

This is order dependent. I will look into the order dependency, but this can be resolved short term by including gradlecm prior to inclusion of maven-publish.

[tschulte]

The problem with the reversed order is, that publishToMavenLocal does not work:

Following minimal example will work (tested with gradle 1.9) on first sight:

apply plugin: 'java'
apply plugin: 'gradlecm'
apply plugin: 'maven-publish'

group = 'test'

buildscript {
    repositories {
        mavenCentral()
        maven {
            name 'kercheval'
            url 'http://kercheval.org/mvn-repo/releases'
        }
    }
    dependencies {
        classpath 'org.kercheval:GradleCMPlugin:+'
    }
}

buildvcs {
    type = 'none'
}

publishing {
    publications {
        mavenJava(MavenPublication) {
            from components.java
        }
    }
}

but gradle publishToMaveLocal fails with

$ gradle clean publishToMavenLocal
:clean
:generatePomFileForMavenJavaPublication
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:jar
:publishMavenJavaPublicationToMavenLocal FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':publishMavenJavaPublicationToMavenLocal'.
> Failed to publish publication 'mavenJava' to repository 'MavenLocal'
   > Invalid publication 'mavenJava': artifact file does not exist: '/home/tobias/Projects/gradlecmtest/build/libs/gradlecmtest.jar'

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

I think the maven-publish plugin does not have the version at the time it is configured. It therefore tries to upload the version without any version.

I think the buildversion plugin must be applied before all other plugins are applied. Changing the above example to:

apply plugin: 'java'
apply plugin: 'gradlecm'
buildvcs {
    type = 'none'
}
tasks.buildversion.execute()
apply plugin: 'maven-publish'

group = 'test'

buildscript {
    repositories {
        mavenCentral()
        maven {
            name 'kercheval'
            url 'http://kercheval.org/mvn-repo/releases'
        }
    }
    dependencies {
        classpath 'org.kercheval:GradleCMPlugin:+'
    }
}

publishing {
    publications {
        mavenJava(MavenPublication) {
            from components.java
        }
    }
}

allows me to call publishToMavenLocal.

[kercheval]

The buildinfo issue should be cleared with commit 7eff1d5.

Please let me know if you see any further issues.

version should be applied very early in your script. Normally this should be done as the first block in your gradle file (many plugins can see problems when version specification is delayed).

I will look at your most recent example and create a new issue if I can duplicate.

[kercheval]

Validated and duplicated ordering issue with buildversion and maven local task. Version does seems to be stored very early on by the -publish plugins. Not very good behavior for these incubating plugins. Reopening thread again.

[tschulte]

Just tried https://github.com/townsfolk/gradle-release. The same problem, publish tries to use the previous version instead of the new one. I will ask at the gradle forum (http://forums.gradle.org/gradle) about the issues. I think all available release-plugins (I know of https://github.com/ari/gradle-release-plugin, https://github.com/stianh/gradle-release-plugin, townsfolk and yours) will have an interest in an answer.