On 08/01/07, Niels Gylling [EMAIL PROTECTED] wrote:
That did not work, ${plugin.artifacts} og ${plugin.artifactMap} did
resolved when the plugin was executed - I had to use the 'brute force'
method of resolving the plugin artifact dependencies manually.
Have you got
Thanks Mark, it works.
Now next step is figuring out how I missed it from the documentation...
/Niels
Mark Hobson wrote:
On 08/01/07, Niels Gylling [EMAIL PROTECTED] wrote:
That did not work, ${plugin.artifacts} og ${plugin.artifactMap} did
resolved when the plugin was executed - I had to use
On 09/01/07, Niels Gylling [EMAIL PROTECTED] wrote:
Thanks Mark, it works.
Now next step is figuring out how I missed it from the documentation...
Problems with finding answers in the Maven documentation? Surely not.. ;)
Mark
Java plugin question:
When writing a Java plugin, how do I obtain the currently executed
plugins's dependency list?
I tried project.getBuild().getPlugins() but the plugin models here seems
to be without dependencies.
Do I have to perform a lookup of the plugin as an artifact and get the
/**
* @parameter expression=${plugin.artifacts}
* @required
* @readonly
*/
private List pluginArtifacts;
On 1/8/07, Niels Gylling [EMAIL PROTECTED] wrote:
Java plugin question:
When writing a Java plugin, how do I obtain the currently
That did not work, ${plugin.artifacts} og ${plugin.artifactMap} did
resolved when the plugin was executed - I had to use the 'brute force'
method of resolving the plugin artifact dependencies manually.
Tom Huybrechts wrote:
/**
* @parameter expression=${plugin.artifacts}
*
