maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niels Gylling ...@it-practice.dk>
Subject Re: Obtaining a plugin's dependencies
Date Mon, 08 Jan 2007 19:08:10 GMT
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}"
>      * @required
>      * @readonly
>      */
>     private List pluginArtifacts;
> 
> 
> On 1/8/07, Niels Gylling <ng@it-practice.dk> wrote:
>> 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
>> dependencies from there  - or just hard code the additional dependencies
>> in the plugin?
>>
>> I need this because my plugin start a new java process with a classpath
>> that I do now wish to copy to all modules referring to this plugin.
>>
>> /Niels
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 

/Niels

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message