在同一项目中使用多种JVM语言

Question

I'd like to use Kotlin & Scala together in projects, and maybe some other languages, but I've seen no good way of doing it. The only way I thought of was compiling one language and decompiling it into Java to work with the other. Are there any alternatives?

Answer 1

You can use Scala and Java simultaneously, since scalac understands and compiles Java files. The same probably holds for other languages. Problems might arise when using multiple alternative JVM languages, since, eg, the Kotlin compiler probably can't understand the Scala files and vice versa.

I think the best way would be to split the project into different modules, and use at most one alternative language per module.

What do I mean with module ?

With module , I mean a set of source files that gets translated into one (binary) artifact, ie a jar file. Under different circumstances I would simply call a "module" a project. Note that a module may depend on other modules on the binary level (eg has some jar files as dependencies).

Multi module support in IDEs

I think it should be possible with most major IDEs to work on different modules simultaneously, even if each module uses a different language. Terminology varies across IDEs.

Terminology

For Intellij IDEA, one of my modules is called "module". For Eclipse it would be called "project".

Answer 2

For the sake of completeness and not putting words into someone else's mouth, I wanted to weigh in.

I agree with the last sentence of ziggystar's answer . The right thing to do is to take a component-based approach and not try to combine multiple languages in one component or project.

From a technical perspective, each of the JVM languages has their own compiler. Some, such as Scala's, can compile both Scala and Java files. However, this may or may not be true for other compilers. In order to avoid strange build processes, a good approach would be to use a single language for every built module.

Since you're sticking to JVM languages, every languages can be compiled into a JAR, so you can easily distribute your executable binary as a single JAR file, with all of the components wrapped up inside it. This is the Fat JAR approach (see this question on Stack Overflow , this post on Java Code Geeks ).

From a human readability perspective, this should also make your software more easily understood. Not only have you decomposed it into logical building blocks (each component), but someone making modifications only needs to understand the language that the component they are working on is written in and the public interface of the components they need to interact with. There's no mental context switching between languages.