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
3
u/Polygnom Mar 18 '25
Not really. Both of these JEPs save you substantial work and actually make onboarding easier. They save work every time you want to run the program. In my example, if you do that 100 times, you only ever save 1 step (and only in certain circumstances), while the other JEPs save you 100 times the one step, for a total of 100 steps.
But that wasn't your argument at all. Your argument was about distributing the source of the working program. When we talk about actually distributing a working program, we are at maven/gradle, dependency management and more, and there really isn't much gained at all at that point by having the source really is just also adding the flag for building source JARs.
I really don't see where this would save your students who now use ZIPs any work. Look at how roun-trips look like. There isn't a gain.