-
Notifications
You must be signed in to change notification settings - Fork 6
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
NoSuchMethodError #9
Comments
I haven't seen that error before. Is the repository you are trying to use this with public so I can try to reproduce? What version of Gradle are you using? Are you using any other plugins that interact with git?
|
The only thing I can think of that would cause that error is if the wrong version of I don't know exactly how Gradle plugins pull in dependencies, I assumed that they were hard-linked but maybe you have another plugin with an older version of |
If your source code isn't public, would you be able to share your |
there really isn't much to the build.gradle, and the source code will be public, but at the moment I'm just setting up |
buildscript {
repositories {
jcenter()
maven { url "https://plugins.gradle.org/m2/" }
}
dependencies {
// THIS LINE BELOW IS THE KEY
classpath "org.eclipse.jgit:org.eclipse.jgit:4.3.0.201604071810-r"
// THE LINE ABOVE IS THE KEY
classpath "gradle.plugin.com.zoltu.gradle.plugin:git-versioning:2.0.12"
}
} It appears that the By adding a reference to |
ok, question: What is this 'KEY' you're mentioning above? |
Sorry, I just meant that the line between the comments is what fixes the issue. "Key to solving the problem" |
Ah gotcha. I'm filing a bug against MinecraftForge/Srg2Source#11 |
To be clear, I'm not sure that is the issue, just a guess. All I know it's that the plugin is pulling in an old version of jgit. |
I'm closing this issue out. It appears that the linked MinecraftForge issue was resolved, so hopefully everything is now working for you! |
org.eclipse.jgit.api.DescribeCommand.setLong(Z)Lorg/eclipse/jgit/api/DescribeCommand
Not sure what's wrong here. full log
The text was updated successfully, but these errors were encountered: