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

"com.github.scala-incubator.io" % "scala-io-core_2.10" % "0.4.1" is not binary compatible with scala 2.10 #77

Open
arturaz opened this issue Jan 7, 2013 · 13 comments

Comments

@arturaz
Copy link

arturaz commented Jan 7, 2013

java.lang.NoSuchMethodError: scala.LowPriorityImplicits.charWrapper(C)Lscala/runtime/RichChar;
    at scalax.file.FileSystem.<init>(FileSystem.scala:49)
    at scalax.file.defaultfs.DefaultFileSystem.<init>(DefaultFileSystem.scala:20)
    at scalax.file.FileSystem$.<init>(FileSystem.scala:34)
    at scalax.file.FileSystem$.<clinit>(FileSystem.scala)
    at scalax.file.Path$.apply(Path.scala:84)
    at app.PostcodeSet$.fromDirectory(PostcodeSet.scala:31)

When running with scala 2.10.

@jesseeichar
Copy link
Owner

To the best of my knowledge I compiled with 2.10. But I will take another look. Did you clear your sbt cache or maven of old scala-io 0.4.1 binaries and ivy information. I found that I had to do that to make it work.

@arturaz
Copy link
Author

arturaz commented Jan 7, 2013

$ rm -rf project/target/ target/ ~/.ivy2/cache/com.github.scala-incubator.io.*
$ sbt
> clean
[success] Total time: 0 s, completed Jan 7, 2013 4:30:28 PM
> test-only app.PostcodeSetTest
...
[error] Could not run test app.PostcodeSetTest: java.lang.NoSuchMethodError: scala.LowPriorityImplicits.charWrapper(C)Lscala/runtime/RichChar;

Then I removed

 val ScalaIo = "0.4.1"
      "com.github.scala-incubator.io" % "scala-io-core_2.10" % V.ScalaIo,
      "com.github.scala-incubator.io" % "scala-io-file_2.10" % V.ScalaIo,

from my build and put freshly built scala-io-file_2.10.0-0.5.0-SNAPSHOT.jar & core into lib/ and everything went fine and dandy :)

@jesseeichar
Copy link
Owner

ok thanks for the update. I will look into this.

@arturaz
Copy link
Author

arturaz commented Jan 7, 2013

Thanks for the quick response :)

@jesseeichar
Copy link
Owner

I just did this:

 mv ~/.ivy2 ~/.ivy2_all
 curl -L http://jesseeichar.github.com/scala-io-doc/0.4.1/example_projects/example-sbt-project.zip >     tmp.zip && unzip tmp.zip && rm tmp.zip
 cd example-sbt-project
 sbt run

Could you see if this works for you because it works for me (and it uses scala 2.10.0). If it works for you...

If that works then we need to make the example more complex. If you have an idea how to change the example code or build.sbt to make it fail that would be a great help.

@arturaz
Copy link
Author

arturaz commented Jan 7, 2013

Will do when I get home :-)
On Jan 7, 2013 4:49 PM, "Jesse Eichar" [email protected] wrote:

I just did this:

mv ~/.ivy2 ~/.ivy2_all
curl -L http://jesseeichar.github.com/scala-io-doc/0.4.1/example_projects/example-sbt-project.zip > tmp.zip && unzip tmp.zip && rm tmp.zip
cd example-sbt-project
sbt run

Could you see if this works for you because it works for me (and it uses
scala 2.10.0). If it works for you...

If that works then we need to make the example more complex. If you have
an idea how to change the example code or build.sbt to make it fail that
would be a great help.


Reply to this email directly or view it on GitHubhttps://github.com//issues/77#issuecomment-11954066.

@arturaz
Copy link
Author

arturaz commented Jan 8, 2013

Didn't get the chance to do this at home. However I did this at work and yes, it does work. I'll try sniffing around to see what causes problems on my side.

@arturaz
Copy link
Author

arturaz commented Jan 8, 2013

Found it! The problem lies in typesafe repository.

I have "Typesafe" at "http://repo.typesafe.com/typesafe/releases/" in my resolvers list.

When I added it to your examples build.sbt, things broke with same error message. I guess a broken artifact lies around in typesafe repository.

@jesseeichar
Copy link
Owner

It is probably an old scala-arm binary in the typesafe repository.

Good job! :)

On Tue, Jan 8, 2013 at 11:08 AM, Artūras Šlajus [email protected]:

Found it! The problem lies in typesafe repository.

I have "Typesafe" at "http://repo.typesafe.com/typesafe/releases/" in my
resolvers list.

When I added it to your examples build.sbt, things broke with same error
message. I guess a broken artifact lies around in typesafe repository.


Reply to this email directly or view it on GitHubhttps://github.com//issues/77#issuecomment-11991306.

@arturaz
Copy link
Author

arturaz commented Jan 8, 2013

Can you remove it please ? ;)

@jesseeichar
Copy link
Owner

Sadly I don't have access to scala-arm binaries. I will talk to Josh
Suereth about it.

On Tue, Jan 8, 2013 at 11:10 AM, Artūras Šlajus [email protected]:

Can you remove it please ? ;)


Reply to this email directly or view it on GitHubhttps://github.com//issues/77#issuecomment-11991376.

@arturaz
Copy link
Author

arturaz commented Jan 8, 2013

Great. Thanks!

As a workaround people can use

        moduleConfigurations += ModuleConfiguration(
          "com.github.scala-incubator.io",
          DefaultMavenRepository
        )

for now.

@xuwei-k
Copy link

xuwei-k commented Jan 17, 2013

@jesseeichar please publish new version for Scala 2.10

playframework/playframework#676 (comment)

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