[2.1] NoSuchMethodError when running play new after clean framework build

[Ike]

I deleted my ivy cache, the repository, ran ./cleanEverything and then ./build -> publish-local on commit d85e1c045. When I try to create a new app I get this:

Getting play console_2.9.2 2.1-SNAPSHOT ...

:: retrieving :: org.scala-sbt#boot-app

confs: [default]

32 artifacts copied, 0 already retrieved (9545kB/1819ms)

       _            _

 _ __ | | __ _ _  _| |

| '_ \| |/ _' | || |_|

|  __/|_|\____|\__ (_)

|_|            |__/

play! 2.1-SNAPSHOT (using Scala 2.9.2), http://www.playframework.org

The new application will be created in /Users/ike/dev/workspace/play2-test

What is the application name? 

> play2-test

Which template do you want to use for this new application? 

  1             - Create a simple Scala application

  2             - Create a simple Java application

  3             - Create an empty project

  <g8 template> - Create an app based on the g8 template hosted on Github

> 1

java.lang.NoSuchMethodError: scalax.io.Input.string$default$1()Lscalax/io/Codec;

at play.console.Console$.replace(Console.scala:29)

at play.console.Console$.generateLocalTemplate(Console.scala:61)

at play.console.Console$.newCommand(Console.scala:133)

at play.console.Console$$anonfun$10$$anonfun$apply$5.apply(Console.scala:182)

at play.console.Console$$anonfun$10$$anonfun$apply$5.apply(Console.scala:182)

at play.console.Console$$anonfun$11.apply(Console.scala:185)

at play.console.Console$$anonfun$11.apply(Console.scala:184)

at scala.Option.map(Option.scala:133)

at play.console.Console$.main(Console.scala:184)

at play.console.Console.run(Console.scala:208)

at play.console.Console.run(Console.scala:205)

at xsbt.boot.Launch$.run(Launch.scala:55)

at xsbt.boot.Launch$$anonfun$explicit$1.apply(Launch.scala:45)

at xsbt.boot.Launch$.launch(Launch.scala:69)

at xsbt.boot.Launch$.apply(Launch.scala:16)

at xsbt.boot.Boot$.runImpl(Boot.scala:31)

at xsbt.boot.Boot$.main(Boot.scala:20)

at xsbt.boot.Boot.main(Boot.scala)

Error during sbt execution: java.lang.NoSuchMethodError: scalax.io.Input.string$default$1()Lscalax/io/Codec;

I'm on MacOS 10.7.5. I build the framework twice, once with Apple's JDK (1.6.0_35-b10-428-11M3811) and once with Oracle's latest (1.7.0_06-b24). Same thing.

Can anybody reproduce this?

[Steven Wong]

Yes, see my post here

https://groups.google.com/d/msg/play-framework/cVqBvywCs4k/GfupfApH6X0J

[Joel Söderström]

Same thing happens to me - cannot create a new project. I did not find a solution in the post above.

/Joel

[Diwa Laksh]

Same problem for me too. Even on fresh machines with no previous play installs 

[Pascal Voitot Dev]

Play master is under heavy work to migrate to Scala 2.10 so it's a bit unstable.
It should be back & stable soon (& even better ;) )

Pascal

--
You received this message because you are subscribed to the Google Groups "play-framework" group.

To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/lCs4Xs5j47EJ.

To post to this group, send email to play-fr...@googlegroups.com.
To unsubscribe from this group, send email to play-framewor...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/play-framework?hl=en.

[Ike]

Pascal, do you know how far back I need to go to get a working build? Does anybody know of a workable commit offhand?

[Pascal Voitot Dev]

To be sure to work with a clean snapshot, I would advise a snapshot before we began integrating Scala 2.10.
For ex this commit: https://github.com/playframework/Play20/commit/b7e4bec91f1eea865e3ee6b5be8b6836d6576b0c from last 16th September.

Pascal

To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/MAALuq3ZIFwJ.

[Ike]

Thanks Pascal. I see the development team continues to commit to this branch, so I'm guessing they're able to build and run apps on it. Is that because they turn on an 'experimental' flag to compile against an RC for Scala 2.10? Are there any instructions somewhere about how to turn this on if someone else wants to play with it?

[Ben McCann]

I'm getting this error on the latest version from Github where Scala 2.10 is now the default.  Is there a solution for this?  Are you all still having this problem?

Thanks,

Ben

[Diwa Laksh]

Yes. I have been facing this problem for a couple of weeks now in several clean machines.

I noticed that when sbt starts up for first time, it tried to download some 2.9.2 stuff and that could be a reason.

Current workaround i am using is to create a new project using the 2.0.4 version and then update the plugins.sbt to 2.1-SNAPSHOT and the build.properties to 0.12.1

[Ben McCann]

I just spent the past couple of hours rebuilding Play on various CLs to see where "play new" broke and posted about it on my other thread.

It's broken on this CL:

https://github.com/playframework/Play20/commit/ead15b9ca87b57e382e1bd387f2f4add4d9658e6

But works on the CL before it:

https://github.com/playframework/Play20/commit/f01a253c533fac3810fbb15d5386d8b2f431a9a8

Does that line up with what you're seeing?

Thanks,

Ben

[Ben McCann]

P.S. you can do "git reset --hard ead15b9ca87b57e382e1bd387f2f4add4d9658e6" and "git reset --hard f01a253c533fac3810fbb15d5386d8b2f431a9a8" to sync to that change and then do "./build publish-local" to test.

[peter hausel]

this should be fixed now ( https://github.com/playframework/Play20/commit/286b0f4eef56c26f35992995d354d2d16b6b18ad )

you'd need to delete your cache (<playhome>/framework/sbt/boot/scala-2.9.2/play or something like that) and rebuild play to get it working.

[Ike]

'play new' works again after the Peter's fix. I ran cleanEverything and then build -> publish-local.

Thanks guys.