| Copying over some of the questions and discussions from Gitter channel: 1) Would this be done by using a process builder and calling the mvn dependency plugin? It looked like this is what was being done in the Custom War Packager
2) Since this would require the groupId, should the plugins.txt file and plugin CLIOption input format be changed so that it could accept the groupId as a parameter? Or if the user wants to download plugins from the maven repository, they would enter this in a yaml file or some other method? Feedback from Tim and Kristin: Yaml files would be similer, don't want to change plugins.txt format too much The way that the custom war packager is doing it is right; some of the "dependencies" might not be plugins but most will be. |
