Christian Posta bio photo

Christian Posta

Chief Architect, cloud application development @ Red Hat, author Microservices for Java Developers, open-source enthusiast, committer @ Apache, Cloud, Integration, Kubernetes, Docker, OpenShift, Fabric8, #blogger

Twitter Google+ LinkedIn Github Stackoverflow

When you set up a run configuration to run a Scala object's main function, you have the option to run it as an Application. If you manually set up the Scala Facet on the module in which your object is, and point to a local Scala distribution, everything runs as expected. But if you are trying to run the main() function from an object in a Maven project, and your scala-library and scala-compiler are marked as "provided", the scala library won't be included on the classpath when you try to run it in IDEA. I understand, per this issue ticket -- SCL-2465 that since a scala distribution is not included with IDEA, it won't put it onto the classpath by default, but there's got to be some way to notify the user that running an "Application" Run/Debug config is NOT like running a Java one. At the moment, it seems like it's supposed to happen seamlessly, but it doesn't. It chokes saying:

Caused by: java.lang.ClassNotFoundException: scala.ScalaObject
at Method)
at java.lang.ClassLoader.loadClass(
at sun.misc.Launcher$AppClassLoader.loadClass(
at java.lang.ClassLoader.loadClass(
... 18 more

To get around it, mark the library and compiler as "compile" scope in the maven pom.xml, but that sucks since it really isn't a compile dependency, it's a provided dependency (but apparently not when running in IDEA). Is there a way to specify a default Scala library to be included when running an Scala application when the scope is set to "provided"? i.e., is there a way for IDEA to "provide" it when running within its Run/Debug config mechanism?