JetBrains/intellij-scala

Scala plugin for IntelliJ IDEA

moglideveloper

@moglideveloper

that I am not able to figure out

and google results are not very helpful for "what is org.scala-tools.sxr"

@dhinojosa

Whether IntelliJ will accept it or not will be a concern

A confirmation on this, will be really helpful

Daniel Hinojosa

@dhinojosa

It may be the simplest answer is don't create a src/main/scala and src/test/java folder.

Your solution works, but it is rather "violent". If anyone tries to use src/main/scala they get an exception

[error] scala.reflect.internal.MissingRequirementError: object scala in compiler mirror not found.
[error] scala.reflect.internal.MissingRequirementError$.notFound(MissingRequirementError.scala:24)
[error] scala.reflect.internal.Mirrors$RootsBase.$anonfun$getModuleOrClass$6(Mirrors.scala:66)
[error] scala.reflect.internal.Mirrors$RootsBase.getPackage(Mirrors.scala:66)
[error] scala.reflect.internal.Definitions$DefinitionsClass.ScalaPackage$lzycompute(Definitions.scala:196)
[error] scala.reflect.internal.Definitions$DefinitionsClass.ScalaPackage(Definitions.scala:196)
[error] scala.reflect.internal.Definitions$DefinitionsClass.ScalaPackageClass$lzycompute(Definitions.scala:197) | => mogli-dev / Compile / compileIncremental 11s

moglideveloper

@moglideveloper

As suggested I removed src/main/scala and src/test/java directories. Still support for scala is not visible in test sources

Daniel Hinojosa

@dhinojosa

I think you need still name and version in build.sbt

I have scala in my tests just fine

moglideveloper

@moglideveloper

added (build file corrected, reuploaded screenshot)

Daniel Hinojosa

@dhinojosa

Did you reload?

Click the "refresh" button so changes take effect

moglideveloper

@moglideveloper

yes i did. but I think, I am missing something

uploaded my project here

uploaded project here https://github.com/moglideveloper/java-app-scala-test

request you to please verfiy my build file

Daniel Hinojosa

@dhinojosa

https://github.com/dhinojosa/mogli-dev

moglideveloper

@moglideveloper

it worked :)

Thanks you so much @dhinojosa for all the help and time

really appreciate

Daniel Hinojosa

@dhinojosa

Yes, excellent!

moglideveloper

@moglideveloper

I was missing scalaVersion := "2.13.5"

Daniel Hinojosa

@dhinojosa

AHHHH

Yes

moglideveloper

@moglideveloper

intention was not to ship scala library accidentally in our final build package. That's why we were trying to enable scala in our test scope only

what I understood so far that combination of

//this will enable scala in complete project
scalaVersion := "2.13.5"
//this will disable scala
autoScalaLibrary := false
//and this will enable scala again in test scope
libraryDependencies += "org.scala-lang" % "scala-library" % scalaVersion.value % "test"

Daniel Hinojosa

@dhinojosa

If you get creative you can create custom tasks that would ensure there is no src/main/scala or src/test/java before you compile

moglideveloper

@moglideveloper

my understanding was, even if scalaVersion is not defined, will be picked based on the sbt.version that is defined in build.properties

Daniel Hinojosa

@dhinojosa

I think maybe IntelliJ requires name, version, scalaVersion at the very least

moglideveloper

@moglideveloper

your solution really helped. but again, this is not clear why directly enabling scala library in test is not sufficient, when scala version is by default pulled from sbt version defined in build.properties

//this will enable scala in complete project
scalaVersion := "2.13.5"
//this will disable scala
autoScalaLibrary := false
//and this will enable scala again in test scope
libraryDependencies += "org.scala-lang" % "scala-library" % scalaVersion.value % "test"

Daniel Hinojosa

@dhinojosa

Probably just how the IntelliJ Scala Plugin recognizes a Scala Project.

Adding scala-libarary to the test scope only I would assume is very rare

moglideveloper

@moglideveloper

ok. Thanks again @dhinojosa

Ishan Shah

@nullptr7

Intellij attempts to download the scalafmt jars from the public internet and the firewall in our org doesn't allow that. We do have scalafmt within our internal maven repository though. Is there any way we can point the Scala plugin to use a local scalafmt jar, or tell it what maven repo to download it from? Thanks

Eric Peters

@er1c

Is there a way to pass in a sbt arg like "testPreRelease" configuration into the ScalaTest intellij run config?

2 replies

Eric Peters

@er1c

I also noticed that when running through sbt it runs each test suite one at a time, which also triggers code formatting checks we have and does recompiling each time (which seems odd) - e.g.

[IJ]{file:/Users/eric/dd/bigdata-master/web_api/}web_api/ testOnly feature_factory_interfaces.output.SmallFeatureDescriptorSetSerializerTest

how can I use the ScalaTest and just have it run the single testPreRelease

4 replies

bbhoss

@bbhoss

I'm just trying to open a project with the Scala plugin that uses sbt. No matter what I try I can't seem to get it to recognize that it's an actual sbt project. I "Opened as Project" to no avail. The scala plugin is installed and it's able to highlight code, but the sbt window doesn't appear. Any ideas?

bbhoss

@bbhoss

blowing away .idea seems to fix :frowning:

Dario Abdulrehman

@dabd

does anyone know how to add support for scalafix-organize-imports in IntelliJ?

Dermot Haughey

@hderms

Is there any plan to make Intellij work with SBT under wsl2? I know they got it working with maven and gradle

2 replies

wangzaixiang

@wangzaixiang

the plugin can't support debug breakpoints on top-level method.

2 replies

Loup

@loup-fox

I have issues with the auto import feature since I started working with Scala3 both on Metal with VSCode and with Intellij. Does someone know why?

Brian P. Holt

@bpholt

Is it possible to debug ScalaJS code running in NodeJS inside IntelliJ? I’m not sure how one would set up the run configuration for that.

Nicholas Molenaar

@nmolenaar_gitlab

@loup-fox same, eventually deleting the .bloop / .bsp / .idea folder and make sure to be on the stable branch of the scala plugin made it work again (changed also back to SBT project instead of BSP)

moglideveloper

@moglideveloper

There is a sample intellij plugin that depends on org.intellij.scala plugin also.
Now, this sample intellij plugin has a functionality to fetch json over http and then parse it.

For parsing json in scala, there are multiple libraries, and we decided to use spray json library.

Reason for choosing spray json :-

spray json library is present in library dependency graph of org.intellij.scala, and sample intellij plugin directly depends on org.intellij.scala plugin.

So to keep sample intellij plugin library size minimum, we thought of using json parser library that is used by org.intellij.scala plugin.

But, we are getting PluginClassLoader exception :-

java.lang.LinkageError: loader constraint violation: when resolving method 'spray.json.RootJsonFormat spray.json.DefaultJsonProtocol$.jsonFormat1(scala.Function1, spray.json.JsonFormat, scala.reflect.ClassTag)' the class loader com.intellij.ide.plugins.cl.PluginClassLoader @2a4b0539 of the current class, com/sample/plugin/FetchDomainObjectsFromWire, and the class loader com.intellij.ide.plugins.cl.PluginClassLoader @573b8e9c for the method's defining class, spray/json/DefaultJsonProtocol$, have different Class objects for the type scala/Function1 used in the signature (com.sample.plugin.FetchDomainObjectsFromWire is in unnamed module of loader com.intellij.ide.plugins.cl.PluginClassLoader @2a4b0539, parent loader 'bootstrap'; spray.json.DefaultJsonProtocol$ is in unnamed module of loader com.intellij.ide.plugins.cl.PluginClassLoader @573b8e9c, parent loader 'bootstrap')

Our understanding so far for this exception :-

As org.intellij.scala and sample intellij are loaded in different classloaders, so sample intellij plugin can't use any class loaded by PluginClassLoader of org.intellij.scala.
To use spray json classes in sample intellij plugin, spray json should be explicitly added to libraryDependencies in sample intellij plugin.

Adding spray json to libraryDependencies in sample intellij plugin will solve the class-loader issue,

but increase the packaged plugin binary size, as spray json library is also packaged in sample intellij plugin.

plugin.xml

    <id>com.logicovercode</id>
    <name>IjPlugin</name>
    <vendor email="moglideveloper@gmail.com" url="https://github.com/JetBrains/sbt-idea-plugin/discussions/107">Linkage Error</vendor>
    <version>2021.1.18</version>
    <depends>org.intellij.scala</depends>
    <idea-version since-build="211.5538" until-build="211.*"/>

build.sbt :

scalaVersion := "2.13.2"

intellijPlugins += "org.intellij.scala:2021.1.18".toPlugin
intellijDownloadSources := true
ThisBuild / bundleScalaLibrary  := false

plugins.sbt

addSbtPlugin("org.jetbrains" % "sbt-idea-plugin" % "3.12.2")

Final Note: if spray-json is not present in SamplePlugin/target/plugin/logicIj/lib, then plugin is giving LinkageError, when run from intellij-run configuration or by loading sample plugin izip in fresh intellij instance.

Kindly confirm, if our understanding is correct and please suggest recommended approach/ best practices for this scenario.

For reference purpose, this question can also be found here :
https://github.com/JetBrains/sbt-idea-plugin/discussions/107

Thanks.

1 reply

Where communities thrive

People

Repo info

Activity