m

mojo-executor-maven-plugin

A very simple example of how to use the Mojo Executor in a Maven plugin. This plugin allows you to specify the group ID, artifact ID, version, goal, and configuration of a plugin to execute. Why would you use this plugin instead of just executing the plugin directly? You wouldn't, probably! It's just for example and functional testing purposes.
maven simple functional purposes plugin version would allows probably directly just execute executor goal mojo artifact instead executing testing example wouldn group specify configuration this very
文件下载
文件名 操作
mojo-executor-maven-plugin-2.3.1.jar 下载
mojo-executor-maven-plugin-2.3.1.pom 下载
mojo-executor-maven-plugin-2.3.1-sources.jar 下载
Apache Maven 
<dependency>
  <groupId>org.twdata.maven</groupId>
  <artifactId>mojo-executor-maven-plugin</artifactId>
  <version>2.3.1</version>
  <type>maven-plugin</type>
</dependency>
Gradle Groovy 
implementation 'org.twdata.maven:mojo-executor-maven-plugin:2.3.1'
Gradle Kotlin 
implementation("org.twdata.maven:mojo-executor-maven-plugin:2.3.1")
Scala SBT 
libraryDependencies += "org.twdata.maven" % "mojo-executor-maven-plugin" % "2.3.1"
Groovy Grape 
@Grapes(
  @Grab(group='org.twdata.maven', module='mojo-executor-maven-plugin', version='2.3.1')
)
Apache Ivy 
<dependency org="org.twdata.maven" name="mojo-executor-maven-plugin" rev="2.3.1" />
Leiningen 
[org.twdata.maven/mojo-executor-maven-plugin "2.3.1"]
Apache Buildr 
'org.twdata.maven:mojo-executor-maven-plugin:jar:2.3.1'
本项目依赖 
<parent>
  <groupId>org.twdata.maven</groupId>
  <artifactId>mojo-executor-parent</artifactId>
  <version>2.3.1</version>
</parent>

compile

|-- org.apache.maven:maven-model

|-- org.apache.maven:maven-plugin-api

|-- org.codehaus.plexus:plexus-utils

|-- org.twdata.maven:mojo-executor

|-- commons-lang:commons-lang

|-- org.slf4j:slf4j-api

|-- org.apache.maven:maven-embedder

provided

|-- org.apache.maven:maven-core

|-- org.apache.maven.plugin-tools:maven-plugin-annotations