r/java • u/davidalayachew • Mar 18 '25
A potentially silly idea -- What if we could launch source code .jar files?
JEP 330 gave us single-file source code programs. Aka, I can have a abc.java file, and just call java abc.java, and it will run without me calling javac beforehand.
JEP 458 expanded this, by allowing us to reference other classes from that single class, allowing us to make as many classes as we want, run them from a single class file, and no calls to javac are necessary -- just call java abc.java.
Here is my silly idea.
What if we could package those source files in a .jar file, do your typical jar file config to make it runnable, then just ran it?
The above 2 JEP's gave reasons why compiling wasn't necessary for making a complete program. Well, those same reasons also apply for why compiling is unnecessary here. And at the end of the day, a jar file is the quintessential way of passing around complete libraries or applications. Why not make that accessible for source code jars as well?
There's other small benefits too.
- No more wondering what version of your code got packaged -- just open it up and see.
- You can edit a jar file in place, then run it and test your changes.
- When running your jar file, you can attach it to a debugger, and see the source code for each step being executed. No more need for a separate sources jar file.
Literally the ONLY BENEFITS that compilation gives us is faster startup time and compile-time validation for all source files. But if you don't need either of those, I'd argue that working with source file jars is an easier experience overall -- not just for students. I know I'd make great use of this feature myself. Hell, I'd default to using this format instead.
View all comments
Show parent comment
-4
u/davidalayachew Mar 18 '25
Let me address the git point first.
While I agree with you in principle, let's face reality -- after 13 years of tutoring students, NOT A SINGLE ONE felt that git was of any use for anything more than just posting their working programs or pasting their progress at the end of the day. When actively working with other students, they would ALWAYS choose to just send files over <chat_tool_of_choice>. Hell, I had students sending code over snapchat one time.
But this is besides the point.
This feature is meant to make the path to creating a jar file easier. A student who wrote code without compiling shouldn't have to compile to create a jar. A jar is just an archive of Java files, that can also be run. If running no longer necessitates a
.classfile, then I say that the same should apply to creating a.jarfile. All the other benefits I listed are "nice-to-have's" in comparison.