Request for supporting maven repository custom file extension

[yakirm-cr]

• What problem are you trying to solve?
  We have been using Nexus for several years and we find it extermely useful. 🙂
  Currently, when uploading to a hosted Maven repository *.gz files, which are NOT *.tar.gz (e.g. *.img.gz), with a classifier the artifact's metadata is defined incorrectly in Nexus.
  For example:

Filename	Expected metadata	Actual metadata
my-artifact-1.0.0-type1.img.gz	<dependency>   <groupId>org.company.example</groupId>   <artifactId>my-artifact</artifactId>   <version>1.0.0</version>   <classifier>type1</classifier>   <type>img.gz</type> </dependency>	<dependency>   <groupId>org.company.example</groupId>   <artifactId>my-artifact</artifactId>   <version>1.0.0</version>   <classifier>type1.img</classifier>   <type>gz</type> </dependency>
my-artifact-1.0.0-type2.img.gz	<dependency>   <groupId>org.company.example</groupId>   <artifactId>my-artifact</artifactId>   <version>1.0.0</version>   <classifier>type2</classifier>   <type>img.gz</type> </dependency>	<dependency>   <groupId>org.company.example</groupId>   <artifactId>my-artifact</artifactId>   <version>1.0.0</version>   <classifier>type2.img</classifier>   <type>gz</type> </dependency>

• Do you have a workaround you are using at present?
  Yes.
  We modify plugins/nexus-repository-maven/src/main/java/org/sonatype/nexus/repository/maven/internal/Maven2MavenPathParser.java to support the custom extension img.gz and rebuild the nexus-repository-maven plugin every time we upgrade Nexus to a newer version.

• What feature or behavior is this required for?
  To support a custom extension file for Maven artifacts which contain a dot (e.g. img.gz).

• How could we solve this issue?
  Add configuration to the Maven repository plugin and UI for hosted Maven repositories to allow defining custom extension files that override the default behavior when rebuilding the metadata of the Maven repository.

• Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?
  We are using Nexus 3.63.0 OSS (with the internal OrientDB) deployed via Docker on Ubuntu 22.04.

• Anything else?
  Nope. 🙂