Understanding How Scala Code Gets Compiled with Java

Explore the seamless integration of Scala and Java in your development projects, and learn how Scala code gets compiled and utilized within Java environments.
---

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: how come scala code gets compiled with Java?

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How Does Scala Code Get Compiled with Java?

When you start learning Scala and working with Java, especially in Java IDEs like Eclipse, it’s common to get puzzled by how these two languages interact. One of the prevalent questions that arise is: How can Scala code be used and compiled within Java projects? In this guide, we will break down the underlying mechanics, making the relationship between Scala and Java clear and simple to understand.

The Basics: Scala and Java Relationship

Scala is a powerful language that combines functional and object-oriented programming paradigms. One of its most significant features is its compatibility with Java. Here's a brief overview of how they work together:

Language Compatibility: Scala runs on the Java Virtual Machine (JVM), making it interoperable with Java code. Thus, Scala code can call Java classes and vice versa.

Compilation Process: Scala code gets compiled into Java Bytecode. This is primarily done using the Scala compiler, scalac.

Common Misconceptions

In your journey, you might have the impression that Scala’s presence in Java projects requires direct use of the Scala compiler (scalac). Let’s clarify this step by step:

Compilation to Bytecode: When you declare dependencies in your project (like Spark, for example), those dependencies are typically pre-compiled by the maintainers. For instance, the JavaConverters class you mentioned has been compiled to Java class files by the Scala compiler.

Class Files Distribution: The maintainers of libraries, such as Janino, generate and distribute these compiled class files to repositories like Maven Central.

Your Project Configuration

The necessary Scala libraries (like spark-core_2.12, spark-sql_2.12, and others) are already pre-compiled and available in the form of JAR files.

The JAR files include the compiled classes that you can easily import in your Java code, such as the JavaConverters class.

What Happens Under the Hood

The processing works like this:

Java Compilation: The Java compiler (javac) translates your Java files into Java bytecode, utilizing the already compiled Scala classes found in the JARs.

Execution: Finally, through the Java Virtual Machine (JVM), everything runs smoothly, and your mixed Scala and Java code can interoperate seamlessly.

Conclusion

In summary, you don’t need to directly reference the Scala compiler for your Java projects when using compiled Scala libraries. Instead, trust that the community and library maintainers have done the hard work for you by compiling Scala class files, which are then distributed and made available through dependency management systems like Maven.

This "unknown magic" of Scala and Java working together is deeply rooted in the ecosystem of the JVM, enabling developers to leverage the strengths of both languages without any cumbersome setup. Happy coding!