---
schema_version: "1"
id: cab1468bad79f1fb1e96acdcb3346a1e600b5e40c87d339d3678ac7db0ce8ddc
title: Patching the Embedded Mule Runtime Engine Version
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/munit/2.3/runtime-patching.md
canonical_url: https://docs.mulesoft.com/munit/2.3/runtime-patching
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 43b6cb4d001efc6bf9efa9b2f3e9dfb3e4206c9e9f37f7132b580ed3fb220bca
description: MuleSoft Documentation Site
release: "2.3"
latest: false
---
---
product: MUnit
version: 2.3
---

# Patching the Embedded Mule Runtime Engine Version

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Patching in MUnit is different from patching in Mule runtime engine. MUnit runs using an embedded
Mule container, which downloads all required dependencies to start Mule based on a given version. To
use a patched Mule version (for example, `4.3.0-20200727`), you must point MUnit to run specifically
against it. You can do this from either Maven or Anypoint Studio.

## Patch MUnit Using Maven

By default, MUnit runs against the Mule version corresponding to the `minMuleVersion` defined in the
`mule-artifact.json` file. You can override this version by using the `runtimeVersion` attribute of
the `munit-maven-plugin` artifact configuration:

```xml
<plugin>
    <groupId>com.mulesoft.munit.tools</groupId>
    <artifactId>munit-maven-plugin</artifactId>
    <version>${munit.version}</version>
    <executions>
        <execution>
            <id>test</id>
            <phase>test</phase>
            <goals>
                <goal>test</goal>
            </goals>
        </execution>
    </executions>
    <configuration>
      <runtimeVersion>4.3.0-20200727</runtimeVersion> (1)
    </configuration>
</plugin>
```

<table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>Be sure to replace the placeholder version in this example with your version, as provided by MuleSoft.</td></tr></tbody></table>

## Patch MUnit Using Studio

By default, MUnit runs in Anypoint Studio with the Mule runtime engine version of the project
server. You can override this version by specifying the patched Mule version in the MUnit run
configuration menu:

1.  In the top menu bar, select **Run** and **Run Configurations…**.

2.  Under **MUnit**, select your MUnit test file.

3.  In the **Mule Runtime Version** field under **Advanced Settings** type the Mule patched version
    you want to use.

    ![runtime patching studio](/mulesoft/current/en-us/munit/2.3/_images/runtime-patching-studio.png)

If you already set the `runtimeVersion` attribute in the POM file of your project, click **Load
configuration from POM file** to automatically load this version into the **Mule Runtime Version**
field.

## See Also

- [Mule Runtime Release Notes](https://docs.mulesoft.com/release-notes/mule-runtime/mule-esb)

- [MUnit Maven Plugin](https://docs.mulesoft.com/munit/2.3/munit-maven-plugin)