Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't apply plugin using Gradle 4.8, 4.9 (or 4.10) #77

Open
george-moberly opened this issue Sep 5, 2018 · 2 comments
Open

can't apply plugin using Gradle 4.8, 4.9 (or 4.10) #77

george-moberly opened this issue Sep 5, 2018 · 2 comments

Comments

@george-moberly
Copy link

george-moberly commented Sep 5, 2018

Gradle 4.7 works, starting with 4.8, 4.9 and 4.10:

here is what I see, I am using 2.0.6 of the plugin:

$ ./gradlew clean
Download https://jcenter.bintray.com/com/github/robfletcher/compass-gradle-plugin/2.0.6/compass-gradle-plugin-2.0.6.pom
Download https://jcenter.bintray.com/com/github/robfletcher/compass-gradle-plugin/2.0.6/compass-gradle-plugin-2.0.6.jar

FAILURE: Build failed with an exception.

  • Where:
    Build file '...repos/ratpack/ratpack-manual/ratpack-manual.gradle' line: 41

  • What went wrong:
    A problem occurred evaluating project ':ratpack-manual'.

Failed to apply plugin [id 'com.github.robfletcher.compass']
Could not create task of type 'CompassFork'.

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

BUILD FAILED in 3s

@george-moberly george-moberly changed the title can't apply plugin using Gradle 4.10 can't apply plugin using Gradle 4.9 (or 4.10) Sep 5, 2018
@george-moberly george-moberly changed the title can't apply plugin using Gradle 4.9 (or 4.10) can't apply plugin using Gradle 4.8, 4.9 (or 4.10) Sep 5, 2018
@blindpirate
Copy link

blindpirate commented Sep 7, 2018

Seems like this is due to an internal API usage of com.github.johnrengelman.processes. The good news is this issue has already been fixed by https://github.com/johnrengelman/gradle-processes/blob/929467012b6c5ed54ecbce4803944096c2858ee6/src/main/java/com/github/jengelman/gradle/plugins/processes/internal/DefaultJavaForkAction.java#L17

Is there any possibility to release a new compass plugin to support this update, i.e. com.github.johnrengelman.processes 0.5.0?

gidsg added a commit to openregister/openregister-java that referenced this issue Nov 22, 2018
fork compass-gradle-plugin to publish version which supports Gradle 4.10 (see robfletcher/gradle-compass#77)
@jmini
Copy link

jmini commented Jun 13, 2019

One way to force usage of 0.5.0 is:

buildscript {
  repositories {
    jcenter()
    maven { url "http://dl.bintray.com/robfletcher/gradle-plugins" }
    maven { url "https://plugins.gradle.org/m2" }
  }
  dependencies {
    classpath("com.github.robfletcher:compass-gradle-plugin:2.0.6") {
        exclude group: 'com.github.jengelman.gradle.plugins', module: 'gradle-processes'
    }
    classpath "com.github.johnrengelman.processes:com.github.johnrengelman.processes.gradle.plugin:0.5.0"
  }
}

(be aware the maven coordinates changed)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants