github-actions[bot] commented on issue #6625: URL: https://github.com/apache/dolphinscheduler/issues/6625#issuecomment-953544136
### Search before asking -[X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened branch: dev Development branch When use standalone server, the DolphinPluginManager looks for plugin dependencies from local maven repository. but the local maven repository is a fixed value in `DolphinPluginManagerConfig.java` who's value is `${user.home}/.m2/repository`. When using local stand-alone development, the plugin loader will load the plugin from the local Maven repository, but the value of the local repository is hard-coded in the code: `${user.home}/.m2/repository`. In my developement envirionment, I set the maven local repository path (localRepository) to `D:\\repository` in `${user.home}/.m2/settings.xml`. In my development environment, I set the address of the local repository (localRepository) in the Maven configuration file `${user.home}/.m2/settings.xml`  so that the plugin manager could not load plugin correctly Therefore, the plugin loader cannot load the plugin correctly ### What you expected to happen * we should load from settings.xml firstly 1. load from `${user.home}/.m2/settings.xml` 2. if `${user.home}/.m2/settings.xml` not exists, load from `${MAVEN_HOME}/conf/settings.xml` * if settings.xml not exists or the node `localRepository` not exists in settings.xml, use default value ### How to reproduce * set local repository into another path in ide * start standalone server ### Anything else _No response_ ### Are you willing to submit PR? -[X] Yes I am willing to submit a PR! ### Code of Conduct -[X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
