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

Version 3.0.0 - SCM adapter #358

Open
cyberveseli opened this issue Jul 7, 2022 · 1 comment
Open

Version 3.0.0 - SCM adapter #358

cyberveseli opened this issue Jul 7, 2022 · 1 comment

Comments

@cyberveseli
Copy link

cyberveseli commented Jul 7, 2022

Hello,

I am new in Gradle and i have very basic build file:

plugins {
    // Apply the java-library plugin for API and implementation separation.
    id 'java-library'
    id 'net.researchgate.release' version '3.0.0'
}

repositories {
    // Use Maven Central for resolving dependencies.
    mavenCentral()
}

dependencies {
    // Use JUnit Jupiter for testing.
    testImplementation 'org.junit.jupiter:junit-jupiter:5.8.1'

    // This dependency is exported to consumers, that is to say found on their compile classpath.
    api 'org.apache.commons:commons-math3:3.6.1'

    // This dependency is used internally, and not exposed to consumers on their own compile classpath.
    implementation 'com.google.guava:guava:30.1.1-jre'
}

tasks.named('test') {
    // Use JUnit Platform for unit tests.
    useJUnitPlatform()
}

Once i ran gradle release i am getting this error:

> Task :kafka-commons-release:kafka-commons:initScmAdapter FAILED

> Task :kafka-commons:release FAILED
Release process failed, reverting back any changes made by Release Plugin.
Release process failed, reverting back any changes made by Release Plugin.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':kafka-commons-release:kafka-commons:initScmAdapter'.
> Cannot invoke method init() on null object

Any idea what i am doing wrong?
Thanks a lot!

@uberbinge
Copy link

uberbinge commented Aug 30, 2022

Facing same issue with version 3.0.1. Is this fix related to it? cc @Hillkorn

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

2 participants