From b495cf7d9b7347c3b8849c553a6f64eb507e8f3a Mon Sep 17 00:00:00 2001 From: Manik Magar Date: Wed, 30 Nov 2022 10:15:17 -0500 Subject: [PATCH] docs: update distribution note in readme --- README.md | 29 ++++++++++++++++++++++++++++- 1 file changed, 28 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 73bc2919..6f5e2f73 100644 --- a/README.md +++ b/README.md @@ -15,6 +15,33 @@ The tool supports two type of authentication methods - 1. Basic Anypoint Platform Credentials 2. Anypoint [Connected App Credentials](https://help.mulesoft.com/s/article/How-to-deploy-an-application-to-CloudHub-using-Connected-App-functionality) +# Distribution + +Starting v1.2.0, The Maven Plugin and Core library is published to [Maven Central](https://repo1.maven.org/maven2/com/avioconsulting/mule/). To **use released versions** from maven central, you do not need any credential or pluginRepository declaration. Just add mule-deploy-maven-plugin configuration to your project and you are good to go. + + +## Snapshots +Starting v1.2.0, SNAPSHOTs are build from `master` branch and are published to [Sonatype Snapshot Repository](https://oss.sonatype.org/content/repositories/snapshots/com/avioconsulting/mule/). + +To use snapshot versions, you would need to add following in your pom.xml - + +```xml + + + + oss.sonatype.org-snapshot + https://oss.sonatype.org/content/repositories/snapshots + + false + + + true + + + +``` + + # Maven plugin NOTE: The Maven plugin has 2 goals (deploy and validate). Regardless of whether you use it to actually perform the deployment, it's highly recommended you use the validate goal to ensure your DSL file is correct during the build pipeline. @@ -42,7 +69,7 @@ If you have no strong preference, then stick with the "with POM" approach which com.avioconsulting.mule mule-deploy-maven-plugin - 1.0.0 + ${mule-deploy-maven-plugin.version} do_validation