finalName is no longer working after plug-in version 3.3.5 or so

[kfowlks]

Hello All,

Recently we have encountered an issue where all of our multi-tenant deployments failed. We were using a single Mule API project for deploying to different tenants. We accomplished this by deploying each API with a suffix that was controlled via our build environment, which modified the xml attribute finalName (See Below). We are being forced to use a higher version of the mule deployment plugin 3.8.2 and setting this finalName no longer works. Can anyone tell us if this lose of functionality is a bug or a change in the direction of the mule deployment plug-in. Are there any workarounds that can be used to change the final artifact name?

Thank you,

• Kevin

<plugin>
				<groupId>org.mule.tools.maven</groupId>
				<artifactId>mule-maven-plugin</artifactId>
				<version>${mule.maven.plugin.version}</version>
				<extensions>true</extensions>
				<configuration>
					<classifier>mule-application</classifier>
					<armDeployment>
						<uri>https://anypoint.mulesoft.com</uri>
						<target>${target}</target>
						<targetType>${target.type}</targetType>
						<username>${username}</username>
						<password>${password}</password>
						<environment>${environment}</environment>
						<muleVersion>4.2.0</muleVersion>
						<properties>
							<sap.env>${sap.env}</sap.env>
						</properties>
						<applicationName>${application.name}</applicationName>
					</armDeployment>
					**<finalName>${project.artifactId}${sap.env}-${project.version}</finalName>**
				</configuration>
			</plugin>

Update - Example of finalName working is past versions

The below link shows the working behavior in past version the plug-in

https://help.mulesoft.com/s/article/Controlling-final-JAR-file-name-when-using-Maven-deployment-pipeline