[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] How to chase @execute?
|
In that case, I'll stick with what I unearthed by spelunking:
Map<String, List<MojoExecution>> forkedExecutions =
mojoExecution.getForkedExecutions();
MojoExecution pmdGoalExecution = null;
for (List<MojoExecution> possiblePmdExecutionList :
forkedExecutions.values()) {
for (MojoExecution possiblePmdExecution : possiblePmdExecutionList) {
if ("org.apache.maven.plugins".equals(possiblePmdExecution.getGroupId())
&& "maven-pmd-plugin".equals(possiblePmdExecution.getArtifactId())
&& "pmd".equals(possiblePmdExecution.getGoal())) {
pmdGoalExecution = possiblePmdExecution;
break;
}
}
if (pmdGoalExecution != null) {
break;
}
}
On Sat, Nov 27, 2010 at 5:45 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
> I am not 100% sure but I think you need to parse the other mojo
> configuration. [1] explains what @execute does and you'd need to ask on
> maven-dev mailing list if you need more details.
>
>
> [1] http://maven.apache.org/developers/mojo-api-specification.html
>
> --
> Regards,
> Igor
>
> On 10-11-27 02:57 PM, Benson Margulies wrote:
>>
>> The check mojo in the pmd plugin uses the following to pull in the pmd
>> goal. They seem to share the configuration for the execution as a
>> result.
>>
>> @execute goal="pmd"
>>
>> If I want to examine the configuration of this as well, should I
>> expect to find an execution for this in the execution plan?
>> _______________________________________________
>> m2e-dev mailing list
>> m2e-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>
