addSbtPluginorganization

addSbtPluginorganization is not a standard feature or recognized term in sbt. In official sbt documentation and common usage, there is no directive or key by that exact name. If you encountered this term, it is likely a mis-typing or a confusion with related concepts such as addSbtPlugin or the organization setting in sbt.

In sbt, adding plugins to a project is done in the project/plugins.sbt file using addSbtPlugin. The syntax is typically addSbtPlugin("group" % "artifact" % "version"). This declares the plugin’s coordinates (groupId, artifactId, and version) and lets sbt download the plugin from a resolver. Plugins are not configured by a separate “organization” directive; instead, their own coordinates determine their origin and identity.

The term organization in sbt refers to a project-level setting that identifies the publishing organization for the project’s artifacts. It is set in build.sbt with something like organization := "com.example". This value affects the coordinates of the published artifacts and is distinct from the coordinates used to add plugins via addSbtPlugin.

If you meant to influence which plugin to use by group or organization, specify the exact plugin coordinates in project/plugins.sbt. There is no standard API or setting named addSbtPluginorganization. For accuracy, verify the spelling and consult the sbt documentation or the plugin’s documentation for the correct group, artifact, and version to use.