[MNG-4277] Remove core artifacts from ${plugin.artifacts}

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-3
• Fix Version/s: 3.0-alpha-3
• Component/s: Plugins and Lifecycle
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 02/Aug/09 14:28
• Updated: 02/Aug/09 14:40
• Resolved: 02/Aug/09 14:40

Description

PluginDescriptor.getArtifacts(), exposed to plugins via the expression ${plugin.artifacts}, previously also contained a reference to the uber JAR as a substitution for the core artifacts. The code for this needs to make ugly assumptions on the resource URLs returned by the class loader framework to derive a file path from this. And just resolving the core artifacts from the repos is also suboptimal as it causes CPU/network overhead (the plugin manager doesn't need these files).

So unless somebody can present a good use case to have the core artifacts resolved, we will safe us this complexity and limit the plugin.artifacts to the non-core artifacts. This is sufficient for Surefire and many other plugins that use this info merely to easily grab a few specific JARs to fork another tool.

Issue Links

• relates to: MNG-3428 ${plugin.artifacts} doesn't contain maven core artifacts