A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/JetBrains/sbt-idea-plugin/issues/72 below:

IJ configurations are generated incorrectly if project name and lazy val name are different · Issue #72 · JetBrains/sbt-idea-plugin · GitHub

If when defining a top level plugin project one uses different names for the lazy val binding the project instance and name setting key, and then using a runner project to generate IJ artifact definitions and run configurations, the generated run configuration will reference a non-existing artifact as it's build dependency.
This happens because when importing a project from SBT IJ uses lazy val's names to reference a module(project) and run configuration generator uses name key to reference an artifact.
Example build with this issue:

lazy val IntellijPluginInScala = project.in(file("."))
  .enablePlugins(SbtIdeaPlugin)
  .settings(
    name := "myExample", // mind the name - it should be the same as lazy val name(or vice versa)
    version := "1.0-SNAPSHOT",
    libraryDependencies += "org.scalatest" %% "scalatest" % "3.2.0",
    intellijPlugins += "org.intellij.scala::Nightly".toPlugin
  )

lazy val pluginRunner = createRunnerProject(IntellijPluginInScala)

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4