IntelliJ’s Run Button Isn’t Magic: What It Actually Does Behind the Scenes

Today I learned that IntelliJ’s Run button isn’t magic.

It’s simply automating the steps I had just spent an hour doing manually.

Before an application can run, IntelliJ takes care of things like:

✅ Finding the correct source root so package names resolve properly.

✅ Compiling source code into a separate output directory instead of mixing .class files with .java files.

✅ Building the correct classpath and using the fully qualified class name (like com.bankingplatform.domain.Main) so the JVM knows exactly which class to execute.

I managed to get all three wrong at least once — running from the wrong directory, using Main instead of its fully qualified name, and compiling classes alongside my source code.

The biggest lesson?

A .class file carries its package identity inside it. That identity doesn't change just because you move the file to another folder or rename it.

Once I understood this, IntelliJ’s Run button stopped feeling like magic.

It became clear that the IDE isn’t doing anything mysterious — it’s just automating the same steps developers can perform manually.

And that’s exactly why tools like Maven become so valuable. They’re not just convenience tools — they automate repetitive, error-prone tasks so developers can focus on building software instead of remembering command-line details.

Sometimes doing things the hard way once helps you appreciate the tools you use every day. 🚀