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

Configuration names are different between compile and runtime #68

Open
2m opened this issue Mar 4, 2019 · 2 comments
Open

Configuration names are different between compile and runtime #68

2m opened this issue Mar 4, 2019 · 2 comments

Comments

@2m
Copy link
Member

2m commented Mar 4, 2019

For example here:

lazy val ScalaUnidoc = config("scalaunidoc") extend Compile
lazy val TestScalaUnidoc = config("testscalaunidoc") extend Test

Both should use the same capitalization.

@eed3si9n
Copy link
Member

Because Ivy Configuration (Maven scope) names are lower cased by convention, I think this is ok. See for example https://github.com/sbt/librarymanagement/blob/v1.2.4/core/src/main/scala/sbt/librarymanagement/ConfigurationExtra.scala#L41

  lazy val Compile = Configuration.of("Compile", "compile")

@2m
Copy link
Member Author

2m commented Mar 18, 2019

Thanks for looking into this. I might have linked to the wrong part of the source code. I had in mind the following discrepancy: in Alpakka here is how we modify scaladoc classpath:

ScalaUnidoc / unidoc / fullClasspath := { ...

https://github.com/akka/alpakka/blob/b860c64512f425b420f455dc30f6bfafd756eb82/build.sbt#L71

But to inspect the value in the sbt console, one needs to use configuration name with lower u:

sbt:alpakka> inspect Scalaunidoc / unidoc / fullClasspath
[info] Task: scala.collection.Seq[sbt.internal.util.Attributed[java.io.File]]
...

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

2 participants