As an alternative to the IDEA integration, you can start most of the applications using the spring-boot-maven-plugin.

Exception: The Studio Client must be started via pnpm.

Using CoreMedia’s configuration facade makes it very simple to use remote services when developing a single app. Simply run the application via Spring Boot Maven plugin, like:

mvn spring-boot:run \
-Dspring-boot.run.jvmArguments="-Dinstallation.host=<FQDN> ..." \
-Dspring-boot.run.profiles=<profiles>

The Spring profiles are most likely to be dev,local,private (in that particular order) but can vary depending on the spring profiles defined for the application. If more than one app is started locally, simply add the required convenience host properties to the apps' private Spring profile or the environment variables.

Note

Maven’s mvnDebug command does not work with current Spring Boot versions. Instead, you can enable debugging by adding the debug configuration like -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=*:8000 to the JVM arguments.

Windows users might run into exceptions with the message "The filename or extension is too long" when starting the applications via the Spring Boot Maven plugin. This is a known issue, fixed in more recent Spring Boot 3.3.0 version. As a workaround, start the applications via your IDE which likely offers an option to shorten the command line.