[MANTRUN-221] Fails to pass maven properties set in user properties only

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.8
• Fix Version/s: 3.0.0
• Assignee: Enrico Olivelli
• Reporter: Alex Szczuczko
• Created: 09/Nov/19 15:05
• Updated: 05/Apr/20 16:51
• Resolved: 13/Dec/19 15:28

Description

A user of mine reported a problem between jsonpath-maven-plugin:set-properties and maven-antrun-plugin:run. My analysis points to a bug in maven-antrun-plugin, introduced in version 1.8 by MANTRUN-178.

MANTRUN-178 incorrectly assumes in AntRunMojo#copyProperties() that all properties will be present in mavenProject.getProperties(), and so fails to copy properties set at runtime in session.getUserProperties().

I've attached a MWE, showing maven-help-plugin:evaluate seeing the property set by jsonpath-maven-plugin:set-properties, and maven-antrun-plugin:run failing to see the same property.

I intend to file a PR to fix this shortly.

Issue Links

• is caused by: MANTRUN-178 Ignore precedence of mvn command line over property defined in <properties> section
• links to: GitHub Pull Request #1