IDE Integration

IDE Integrations

Maven

javafx.platform (Obsolete)

To be able to build properly the javafx.platform variable must be set to win mac linux

The prefered way to do this is to add the following into the maven settings.xml file

<properties>
    <javafx.platform>win</javafx.platform>
</properties>

Eclipse

Required configuration

To build successfully using m2e inside Eclipse you musn’t use any embedded jre or maven installation

  • you MUST register an external JDK/JRE installation and attach it to the corresponding JavaSE configuration Without this configuration, eclipse m2e isn’t able to provide java.home to Maven (time of writing: Version: 2024-12 (4.34.0))

  • you MUST register an external MAVEN installation and set it as default Without this configuration, eclipse m2e isn’t able to provide maven.home to Maven (time of writing: Version: 2024-12 (4.34.0))

To allow annotation processors (MapStruct) to be configured inside Eclipse:

  • ensure “Automatically configure JDT APT” is selected in Window > Preferences > Maven > Annotation Processing

Importing projects

Eclipse integration is rather good but m2e still lacks some features about JPMS for a perfect integration

Maven compiler arguments like patch-module are not synchronized with the eclipse project classpath.

In order to work properly spring.core was patched to allow aspect to properly function in a multi ModuleLayer architecture. Those patch aren’t correctly handled in Eclipse and prevent successfull compilation.

To run the application from inside Eclipse projects

  • “emc4j.boot.jpms.patches” and nested projects must be removed from the workspace.
  • “emc4j.core.jpms.patches” and nested projects must be removed from the workspace.

Provided launchers

Some Eclipse launchers are provided in “dev.utils\ide\eclipse\launchers”

IDEA

fill it if you’re using it

Netbeans

fill it if you’re using it

Updated: