-
Notifications
You must be signed in to change notification settings - Fork 168
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
java.lang.NoSuchMethodError: scalaz.Scalaz$.ToValidationV(Ljava/lang/Object;)Lscalaz/syntax/ValidationV; #221
Comments
I'm getting this error too. What was the setting you added to fix it? @jagatsingh Thanks! |
@jagatsingh any chance you could tell us what the settings were? |
Can you try with sbteclipse 4.0.0-RC1? |
@benmccann got this bug when used sbteclipse plugin 4.0.0-RC1 here is complete plugins.sbt
myapp/project/plugins.sbt |
sbteclipse 4.0.0 won't work with Play 2.3 unfortunately. You can try with Play 2.4-M3 |
Getting the same error with sbt-eclipse 4.0.0-RC1 and Play 2.4.0-M3 Actually the stacktrace is not quite the same:
|
Oh, I know what this is now. I was confused at first and thought it was something else. This will be fixed in Play 2.4-RC1, which should be released any day now. I'm going to close this issue since it's already been fixed in Play. |
I was referencing sbteclipse version 4.0.0 which was giving this exception, However I could able to fix this issue by updating my sbteclipse version from 4.0.0 to 3.0.0 in global plugin.sbt (available in <USER_HOME>.sbt\0.13\plugins) file. addSbtPlugin("com.typesafe.sbteclipse" % "sbteclipse-plugin" % "3.0.0") |
I get this error with version 2.5.0, 3.0.0 and 4.0.0 @benmccann is there another version I can try? |
I think this error was conflicting versions of scalaz? You must be pulling in another version somewhere else in your project |
is there a version of sbteclipse compatible with "org.scalaz" %% "scalaz-core" % "7.1.2"? |
@benmccann we are using I tried bumping my version of sbteclipse and then that wasn't compatible with sbt-play 2.3.9 I tried bumping my play to 2.4.0 and there was errors. I will try 3.0.0 later :( |
Just in case someone hits this one again, it might be triggered by other enabled plugins. In my case, the issue/conflict with version 3.0.0 is triggered by |
And there is a similar issue with version 4.0.0 and coursier 1.0.0-M14 (due to alexarchambault/coursier/pull/328). |
Hi,
You will get the below error if we dont keep plugins.sbt in correct place.
Documenting for helping others not to waste time.
Eclipse 4.4
Added the required plugin settings in
/.sbt/0.13/plugins/plugins.sbt
full log is below.
The text was updated successfully, but these errors were encountered: