This repository contains the community formulas that can be executed through Ritchie CLI once imported. This tool is an open source product that allows you to create, store and share any kind of automations, executing them through command lines, to run operations or start workflows ⚙️ 🖥 💡
[FEATURE] The Java/Kotlin Formula template should come configured with the Maven Wrapper Plugin script so that the user isn't greeted with an error if 'mvn' is not configured on PATH #369
As best practice, Maven and Gradle projects always have a wrapper script that automatically downloads/invokes Maven/Gradle, so that the user doesn't need to perform any preliminary setup of the build tool (also because the project might depend on a specific version of the tool that is different from the one configured/used otherwise by the user). We should make the standard Java/Kotlin Formula template adopt such approach.
Right now, if an user creates a Java/Kotlin Formula and uses the local runner, he's greeted with an error message if 'mvn' is not configured on PATH. By following Maven/Gradle projects' best practices in using a wrapper script, we can be much more user friendly. In the meantime, the documentation should reflect the fact the user is expected to have Maven installed and configured on PATH if the user expects to use the local runner.
What would you like to be added:
As best practice, Maven and Gradle projects always have a wrapper script that automatically downloads/invokes Maven/Gradle, so that the user doesn't need to perform any preliminary setup of the build tool (also because the project might depend on a specific version of the tool that is different from the one configured/used otherwise by the user). We should make the standard Java/Kotlin Formula template adopt such approach.
https://maven.apache.org/plugins/maven-wrapper-plugin/
Why is this needed:
Right now, if an user creates a Java/Kotlin Formula and uses the local runner, he's greeted with an error message if 'mvn' is not configured on PATH. By following Maven/Gradle projects' best practices in using a wrapper script, we can be much more user friendly. In the meantime, the documentation should reflect the fact the user is expected to have Maven installed and configured on PATH if the user expects to use the local runner.