Error when executing "sbt +publishLocal in the Api-First-Hand directory"

[ebowman]

Error when executing "sbt +publishLocal in the Api-First-Hand directory"

[slavaschmidt]

@zyv you're right, but unfortunately I don't know how to build the SBT plugin which must be build for scala 2.10 without cross-building the whole project. If you have an idea, it would be cool.

[slavaschmidt]

Hi!

Could you please try with sbt publishLocal without "plus" sign?

[SellamiRami]

Thank you @slavaschmidt for your response.

It successfully works.

Could you please explain to me why it doesn't work with the "+" since in the ReadMe file it is written with it?

[zyv]

@SellamiRami

> help +
+ <command>
	Runs <command> for each Scala version specified for cross-building.

	For each string in `crossScalaVersions` in the current project, this command sets the
	`scalaVersion` of all projects to that version, reloads the build, and
	executes <command>.  When finished, it reloads the build with the original
	Scala version.

	See also `help ++`

My understanding is that Play framework is not compatible with Scala 2.10 since version 2.5, but because of the plus sign, sbt attempts to build for Scala 2.10 as well.

I guess this means that my commit in #45 is wrong then, and one should remove Scala 2.10 compatibility if it is no longer supported, instead of removing + from the publishLocal command.

@slavaschmidt ?

[slavaschmidt]

@zyv Yes, that's correct. We cannot build for scala 2.10 because it's not supported by play itself.
But I think you removed the + sign in the #45, so why is it wrong then?

[zyv]

Well, I thought that instead of restricting the build to the current version of Scala by removing the plus, one should simply remove cross-building from the build system, if it is so, that the project will only ever be compatible with the current version of Play, which itself will only ever be compatible with the current version of Scala.

However, I lack background in Scala to decide what's best. If you think that removing the plus sign is better, because cross-building will be used again in the future, then everything is alright :-)

[LappleApple]

Hi @zyv, just following up on @slavaschmidt's point/openness to ideas on this. If you'd like to share, it would be great! Otherwise, I'll close this thread...

[zyv]

@LappleApple sorry, no idea; lacking background in as far as Scala ecosystem is concerned, I still don't quite get it why some sbt plugin must be built for Scala 2.10 and not Scala 2.11, and besides see #47 :-/

[slavaschmidt]

Just to clarify a bit: sbt 0.13 does not support scala 2.11 or 2.12 (at least not officially). The plugin code must be scala 2.10 and must be compiled with scala 2.10

[gipeshka]

Would updating to sbt 0.13.13 solve the issue?
Directly on 2.12 page they say 0.13.13 should be ok
http://www.scala-lang.org/news/2.12.0

[slavaschmidt]

@gipeshka Well, it's complicated :) The SBT plugin supports different Scala versions as a build tool.
The tool itself is a different story. The SBT supports Scala 2.12 but it's source code does not.
Imagine Java 8 would not be compatible with Java 6 and maven sources would be Java 6. Then you can build whatever you want with maven but you must build maven itself with Java 6, right?