mule-maven-plugin | Maven plugins for Mule Runtime | Build Tool library

I have configured Azure DevOps Maven task to connect to an Artifacts feed to store the artifacts and dependencies, but I only see the Maven Central dependencies, none of the others are stored.

Here is the MuleSoft pom.xml:

I have recently hosted a mule application in Maven Central Repo. The app contains two java files and a dwl file. The dwl file uses those java files to do some operation. This is the primary app (app1) which I want to reference in another app (app2 )as a pom dependency.

The name of the primary is encryption-1.0.5-mule-application.jar.

The name of dwl script which it contains is encryption.dwl. The Java files are available in the jar file /company package.

Case 1: If I package this primary mule app (app1) as a jar and install the app into my local .m2 repo, and later include this as pom dependency and a shared library for mule-maven-plugin of another secondary mule app (app2). The app2 is able to recognize the dwl script and it works when deployed.

I am attempting to deploy to Mulesoft from a BitBucket Pipeline using Maven. The deployment target is an RTF instance that is configured for inbound traffic. I am using the following bitbucket-pipelines.yml:

While deploying my Mule project with Mule runtime 4.3.0 to cloudhub through maven, i am getting below exception:

Execution default-deploy of goal org.mule.tools.maven:mule-maven-plugin:3.3.5:deploy failed: MessageBodyReader not found for media type=application/json;charset=utf-8, type=class org.mule.tools.client.arm.model.AuthorizationResponse, genericType=class org.mule.tools.client.arm.model.AuthorizationResponse.

Any help will be appreciated. Thanks Vikas

This is for Mule 4, on 4.3 EE Runtime

POM File holds standard dependency, and thanks to Aled's answer also included it as a shared library:

I have a project on Mule Runtime 4.2.2 and I am working on AnypointStudio.

Now I am trying to exclude dev.properties file from src/main/resources folder when packaging. Because I am using prod.properties on a production. But for some reason nothing works. It keeps showing up in .jar file.

Here is what I did:

1) Created a new file in the project folder named "_muleExclude"

2) Added exclusion rule: dev.properties. Also tried **/src/main/resources/dev.properties

3) Packaged with mvn clean package

I am using mule-maven-plugin version 3.3.5. Found only this documentation about _muleExclude: https://docs.mulesoft.com/mule-runtime/4.3/package-a-mule-application#exclude-files-from-the-application-package

I'm trying to create a build using mule maven plugin, it has to execute MUnit test cases. I've used a configuration property and it has been configured as app-{mule.env}.yaml While running the app it works fine as I pass the argument mule.env=dev but causes failure while creating maven build using mule maven plugin below is POM structure

MUnit specific config: