I thought that was available under the parameter expression $
{plugin}, which returns the current plugin's PluginDescriptor
instance...from there, I thought there was an accessor method that
exposed the artifacts used to create that plugin's classpath...
Maybe I'm dreaming, or maybe it's changed...but it might be a place
to start looking.
-john
On Sep 5, 2007, at 6:34 PM, Christian Gruber wrote:
Hey,
I'm trying to use pluginArtifacts to include the current
plugin's jar as a classpath for an external call, as I have created
a crazy but necessary wrapper. When I go to find the plugin in
pluginArtifacts, I find that I cannot, and that pluginArtifacts is
not populated on MavenProject. Is there metadata I'm missing that
I have to set that causes maven to populate this on this.project?
you know, the equivalent of @resolveDependencies.
Christian.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
