Re-expose or offer alternative public API for things hidden in 1.0

sbt-structure uses parts of the sbt API that have been hidden in the sbt 1.0 line. This forced me to work around it by this shim that I import into otherwise compatible code to provide the definitions previously available under the sbt._ import. It would be helpful to have these things, or an appropriate replacement available under a public API.

Pasted for reference:

object apiAdapter {
  val Load = sbt.internal.Load
  type Load = sbt.internal.Load.type

  val SessionSettings = sbt.internal.SessionSettings
  type SessionSettings = sbt.internal.SessionSettings

  type GetClassifiersModule = sbt.internal.librarymanagement.GetClassifiersModule
  type LoadedBuildUnit = sbt.internal.LoadedBuildUnit
  type BuildStructure = sbt.internal.BuildStructure
  type BuildDependencies = sbt.internal.BuildDependencies
  type ScalaInstance = sbt.internal.inc.ScalaInstance
  type MavenRepository = sbt.librarymanagement.MavenRepository
}

[dwijnand]

Probably not. Lots of plugins rely on the internal APIs of structure/loading.

There’s also the issue that things are defined in “internal” but then expose as non-external in the sbt package object, which is the worst of both worlds because for sbt maintainers it looks like you can break it, but for users it looks like public API.

And I think there’s also stuff not exposed but should be to use features, like the parser/complete API.

[dwijnand]

@jastice I’m going to try to update sbt-project-graph this week, so I’ll be in the same situation, so I might be PRing a solution.