name setting isn't taken from cross project but from lazy val name

[fkz]

Consider the following build.sbt:

lazy val somename := (project in file("somefile")).settings(
  name := "super-cool-name",
  organization := "organization-name"
  // ...
).cross

lazy val somename_2_11 = somename("2.11.8")
lazy val somename_2_12 = somename("2.12.1")

Let's test some values in sbt:

> somename-2_11/name
[info] somename
> somename-2_11/organization
[info] organization-name

so the name is used from the name of the lazy val instead of the name setting in the project. For organization, libraryDependencies and others it works perfectly though.

Workaround is to add .setting(name := "super-cool-name") to all subprojects. But it would be great if this wouldn't be needed.

[pauldraper]

This happens because project is a macro equivalent to

lazy val somename = Project("somename", file("somefile"))

sbt-cross uniquifies somename id to somename-2_11. Since by default SBT uses the id as name, which would cause the undesirable somename-2_11 to appear in Ivy, etc., sbt-cross overrides name to be the original id somename.

---

Workaround 1

lazy val `some-cool-name` = (project in file("somefile")).settings(
  organization := "organization-name",
  // ...
)

Workaround 2

lazy val somename = Project("some-cool-name", file("somefile")).settings(
  organization := "organization-name",
  // ...
)

Workaround 3

Write name := "some-cool-name" in somefile/build.sbt.

Note: Workarounds 1 and 2 change ids (the things you use in the SBT console) to some-cool-name-2_11 and some-cool-name-2_12, which may or may not be acceptable.

---

I pushed a fix. See README.md for using latest master. Let me know if it works.