[NPANDAY-417] Take explicit dependency to plexus-utils in a newer version to override the built-in dependency to plexus-utils 1.1 in MVN < 3 (improves cmd-line handling)

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4-incubating
• Fix Version/s: 1.4-incubating
• Component/s: Maven Plugins
• Assignee: Lars Corneliussen
• Reporter: Lars Corneliussen
• Created: 21/Apr/11 07:15
• Updated: 21/Apr/11 07:38
• Resolved: 21/Apr/11 07:38

Description

From Maven 2.0.6 Maven automatically injected plexus-utils:1.1 as a direct dependency to any Maven plugin.

So even if there was a transitive dependency to a higher version (in our case the executable-component needs at least 1.4.5), that got overruled by the automagically injected 1.1.

Related issues from Maven:

• http://jira.codehaus.org/browse/MNG-3819
• http://jira.codehaus.org/browse/MNG-4276
• http://jira.codehaus.org/browse/MNG-2892

This lead to NPANDAY-416, where we had trouble with the quoting of commandline parameters.

The solution is to add a direct dependency to a newer plexus-utils-version (specified in plugins-parent) into all our plugins.

Issue Links

• supercedes: NPANDAY-416 MVN 2.2.1: Tests in projects whose paths contains spaces fails: Reason: maven-test-plugin resolves to plexus-utils:1.1