The configuration of a "Invoke top-level Maven targets" build step in a Freestyle project, and the configuration of the Build section in a Maven project type are so completely different, that I don't even know where to begin.

Options are called differently, are in a different order, some are missing from the first, some are missing from the other. Imho, these should really be completely the same.

Missing on one side:

• Properties: this nice textarea is missing completely from the maven project type, instead we have to use -D... in a single-line textfield
• Use private Maven repository: the freestyle version is missing the "local to executor" option
• Run headless: only available in Maven project
• Maven Validation level: only available in Maven project
• Maven Version: the popup offers a "(default)" choice (whatever that is) in Freestyle, but not in Maven Project

Naming inconsistencies:

• JVM Options <-> MAVEN_OPTS: same thing, different names, also MAVEN_OPTS might sound to the unwary that you can put your properties here
• "Goals" <-> "Goals and options": also it's an expandable textbox in Freestyle, but not in Maven project

Different order/section:

• "Goals" and "Pom" fields are swapped
• "Use custom workspace": Freestyle: hidden in "Advanced project options", maven: in main Build section
• "Build Environment": Freestyle: above the Build section, Maven: below the Build section

There are some more options in Maven project, that only make sense there, so that's OK. But at least the rest should be identical.