---
schema_version: "1"
id: e55d527277352dc00b9d4bdbfb1ed351ae7ef0e75d895e30f69a343fb05f76e4
title: Mule Maven Plugin 4.10.2 Release Notes (Deprecated)
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/mule-maven-plugin/mule-maven-plugin-4.10.2-release-notes.md
canonical_url: https://docs.mulesoft.com/release-notes/mule-maven-plugin/mule-maven-plugin-4.10.2-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 3d285da922c4addd7a35a33c77da2dfbfb16cdfe0a917bee05acc1668a5fa7b6
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
---

# Mule Maven Plugin 4.10.2 Release Notes (Deprecated)

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

Use the Mule Maven plugin to integrate the packaging and deployment of your Mule applications with
your Maven lifecycle.

Mule Maven Plugin 4.10.2 implements all security updates and bug fixes from 4.10.1.

## October 7, 2026

## What’s New

- Mule Maven plugin now supports building and deploying applications that target Mule runtime engine
  4.13.0. To build and deploy these applications, upgrade to Mule Maven plugin 4.10.2 or later. For
  more information, see
  [Mule Runtime Engine 4.13.0 Release Notes](https://docs.mulesoft.com/release-notes/mule-runtime/mule-4.13.0-release-notes).

## Hardware and Software Requirements

- Microsoft Windows 10

- Apple macOS X 10.15.0+

- Linux (tested on Ubuntu 22)

- Java 8, 11, 17, and 21

- Maven 3.9.0 to 3.9.15

> [!NOTE] Mule Maven plugin supports Java 8, 11, 17, and 21. The `minMuleVersion` specified in your
> Mule application must be compatible with the Java version used to run the plugin.

## Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule runtime engine</p></td><td><p>4.3 or later</p></td></tr><tr><td><p>Anypoint Studio</p></td><td><p>7.x</p></td></tr></tbody></table>

## Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>Application properties configured in Runtime Manager are no longer cleared when you redeploy an application to on-premises servers by using <code>armDeployment</code>. The plugin now sends properties only when they’re defined in the plugin configuration.</p></td><td><p>W-24207441</p></td></tr><tr><td><p>The Mule Maven plugin now determines which Java versions are supported based on the <code>minMuleVersion</code> value declared in the <code>mule-artifact.json</code> file. The plugin uses this information to validate the <code>javaSpecificationVersions</code> value at build time.</p></td><td><p>W-24192837</p></td></tr><tr><td><p>The build now fails if <code>javaSpecificationVersions</code> in the <code>mule-artifact.json</code> file contains a Java version that the Mule version set in <code>minMuleVersion</code> doesn’t support. The plugin checks the Mule runtime engine support matrix, or a bundled copy for offline builds. To skip this validation, set <code>-DskipJavaVersionValidation=true</code>.</p></td><td><p>W-24192843</p></td></tr></tbody></table>

## See Also

- [Salesforce Help](https://help.salesforce.com)

- [MuleSoft Services](https://www.mulesoft.com/support-and-services)

- [Known Issues](https://help.salesforce.com/s/issues)

- [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept)