-
It is allowed to add <packaging>dolphinscheduler-plugin</packaging> to the pom file. If dolphinscheduler-plugin is added to the pom file, the DolphinScheduler service will load this model as a DolphinScheduler plugin.
-
Automatically check the model with dolphinscheduler-plugin added to the pom file, and will automatically generate META-INF/services/org.apache.dolphinscheduler.spi.DolphinScheduler file when compile.
-
Automatically check DolphinScheduler's maven dependency. Especially the dependencies used by plugins.
If we are running on the server deployment. Because the plug-ins are in the corresponding plug-in directory, and the plug-in jar package has the corresponding META-INF/services, there is no problem.
However, when we develop locally in IDE, we have no plug-ins dir and no plug-ins jar file . If we want to test and debug the plugin code, we need add the plugin module to the pom.xml of alert module ,But this violates the original intention of SPI. So we can`t add the plug-in module to the alert module as a dependency, So there will be a problem that the alert module cannot find the plug-in classes.
With this maven plug-in, by scanning the pom file of the project ,The pluginloader can find the module identified by dolphinscheduler-plugin, then can load this module`s class files and its dependent third-party jars from the target/classes dir of the plug-in module. This will debug locally
mvn clean package
And then you can found apache-dolphinscheduler-maven-plugin-incubating-${RELEASE.VERSION}-bin.tar.gz in the target dir.
-
Download the apache-dolphinscheduler-maven-plugin-incubating-${RELEASE.VERSION}-bin.tar.gz file from
the release candidates
(it will be provided in the vote email). -
Unzip the apache-dolphinscheduler-maven-plugin-incubating-${RELEASE.VERSION}-bin.tar.gz file
-
Go to apache-dolphinscheduler-maven-plugin-incubating-${RELEASE.VERSION}-bin/bin dir and run
chmod 755 install_to_localrepository.sh & sh install_to_localrepository.sh
. This will install apache-dolphinscheduler-maven-plugin to your local repository. -
add this plugin to your project`s pom.xml file like this:
<plugins> ... <plugin> <groupId>org.apache.dolphinscheduler</groupId> <artifactId>dolphinscheduler-maven-plugin</artifactId> <version>${RELEASE.VERSION}</version> <extensions>true</extensions> </plugin> ... </plugins>
-
run
mvn clean verify
test the plugin.