[MNG-2626] System scope dependencies in parent POM cause validation warnings for most plugins and errors in assembly plugin

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Duplicate
• Affects Version/s: 2.0-alpha-1
• Component/s: Errors
• Assignee: Brett Porter
• Reporter: Brian Topping
• Created: 20/Oct/06 19:34
• Updated: 01/Jul/09 12:44
• Resolved: 01/Jul/09 12:44

Description

When system scope dependencies are in a parent POM and the systemPath for those variables contain a variable to be interpolated as a root path, maven throws off a lot of spurious warnings that the POM does not validate because system paths need to be absolute. An example of this in a parent POM (where ${jboss.home} is defined in ~/.m2/settings.xml):

		<dependency>
			<groupId>jboss</groupId>
			<artifactId>activation</artifactId>
			<version>4.0.4.GA</version>
			<scope>system</scope>
			<systemPath>${jboss.home}/server/default/lib/activation.jar</systemPath>
		</dependency>

In discussing this with John and Jason online, both apparently have generic implementations that can go in at some point, but this is something I would like to get into 2.0.5. The patch is ~25 lines of new code with one replaced.

It's marked as blocker because we use the assembly plugin, which fails the build on the validation problem where most other plugins just enumerate every system scope dependency. For now, I will distribute the patched version around the company though

thanks

Issue Links

• is depended upon by: CONTINUUM-997 Can't import project
• is duplicated by: MNG-2694 property in plugin dependency's systemPath is not resolved and causes "system-scoped dependency must specify an absolute path systemPath."
• is superceded by: MNG-4148 Apply profiles from settings.xml to POMs built from the repository
• relates to: MNG-4148 Apply profiles from settings.xml to POMs built from the repository