[
https://issues.apache.org/jira/browse/MNG-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825111#comment-17825111
]
Shannon Carey commented on MNG-2766:
------------------------------------
Ok... I guess I don't know enough about Mojos to figure it out. I don't see any
javadoc on the
{{requiresDependencyResolution}} and {{requiresDependencyCollection}}
properties of {{{}@Mojo{}}}.
As I was working on a contribution to the maven-exec-plugin, I noticed it is
still using deprecated methods like {{{}getTestArtifacts(){}}},
{{{}getRuntimeArtifacts(){}}}, etc. within
[https://github.com/mojohaus/exec-maven-plugin/blob/master/src/main/java/org/codehaus/mojo/exec/AbstractExecMojo.java#L133]
but I'm just not sure what that should look like instead. Especially since it
has to collect the artifacts at runtime based on its configuration, as opposed
to the Mojo annotation which is compiled into the plugin itself. I suppose I'll
have to leave it up to the maintainers to figure that out.
> Refactor DefaultLifecycleExecutor
> ---------------------------------
>
> Key: MNG-2766
> URL: https://issues.apache.org/jira/browse/MNG-2766
> Project: Maven
> Issue Type: Task
> Components: Plugins and Lifecycle
> Affects Versions: 3.0-alpha-1
> Reporter: Jason van Zyl
> Assignee: Jason van Zyl
> Priority: Major
> Fix For: 3.0-alpha-3
>
>
> Another large beast that needs to be broken up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
