mvncenter: org.twdata.maven:mojo-executor-maven-plugin:2.4.1-m2

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.

Files download

File	Operation
mojo-executor-maven-plugin-2.4.1-m2.jar	download
mojo-executor-maven-plugin-2.4.1-m2.pom	download
mojo-executor-maven-plugin-2.4.1-m2-sources.jar	download

Apache Maven

<dependency>
  <groupId>org.twdata.maven</groupId>
  <artifactId>mojo-executor-maven-plugin</artifactId>
  <version>2.4.1-m2</version>
  <type>maven-plugin</type>
</dependency>

Gradle Groovy

implementation 'org.twdata.maven:mojo-executor-maven-plugin:2.4.1-m2'

Gradle Kotlin

implementation("org.twdata.maven:mojo-executor-maven-plugin:2.4.1-m2")

Scala SBT

libraryDependencies += "org.twdata.maven" % "mojo-executor-maven-plugin" % "2.4.1-m2"

Groovy Grape

@Grapes(
  @Grab(group='org.twdata.maven', module='mojo-executor-maven-plugin', version='2.4.1-m2')
)

Apache Ivy

<dependency org="org.twdata.maven" name="mojo-executor-maven-plugin" rev="2.4.1-m2" />

Leiningen

[org.twdata.maven/mojo-executor-maven-plugin "2.4.1-m2"]

Apache Buildr

'org.twdata.maven:mojo-executor-maven-plugin:jar:2.4.1-m2'

Dependencies

<parent>
  <groupId>org.twdata.maven</groupId>
  <artifactId>mojo-executor-parent</artifactId>
  <version>2.4.1-m2</version>
</parent>

compile

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

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

|-- org.apache.commons:commons-lang3

provided

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

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

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

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

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

|-- org.eclipse.sisu:org.eclipse.sisu.plexus

|-- org.slf4j:slf4j-api