IntelliJ Maven Proxy Settings: Importer vs. Runner
Compare importer and runner settings when IntelliJ can build through a proxy but cannot sync, or the reverse.
If Maven goals work in IntelliJ but sync fails, inspect the importer before replacing the proxy endpoint. These are separate consumers:
| Working or failing operation | Relevant process settings |
|---|---|
| IDE HTTP connection check | IntelliJ's own HTTP networking configuration |
| Project import or sync | Maven importer JDK and JVM options |
| Maven goal execution | Maven runner runtime and JVM options |
First compare the Maven distribution and selected user settings file, including explicit overrides used in the terminal. Make the active proxy in the effective settings consistent before adding properties in several VM fields.
Then locate any Java proxy property, custom truststore or other JVM option at the failing process. Runner options affect goals; importer options affect import. They are not aliases. Two selected JDKs can also trust different organization CAs while using the same endpoint, so a certificate error does not establish a password failure.
A sync-only error directs attention to the importer and its inputs. A goal-only error directs attention to the runner. A test or forked application can introduce another JVM with its own settings.
Keep the repair at that owner instead of pasting generic proxyHost properties everywhere or editing bundled Maven files. An identifiable settings file and targeted process options make the result reproducible after IDE updates.