I have a Maven project that it's only a POM working as a BOM listing a set of common dependencies, which is then imported by other projects.
For illustration purposes, this is the BOM in question:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>myorg</groupId>
    <artifactId>my-bom</artifactId>
    <version>1.2.3</version>
    <packaging>pom</packaging>
    <properties>
        <xyz.version>4.5.6</xyz.version>
        <abc.version>7.8.9</abc.version>
    </properties>
    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>foo.bar</groupId>
                <artifactId>xyz</artifactId>
                <version>${xyz.version}</version>
            </dependency>
            <dependency>
                <groupId>yolo</groupId>
                <artifactId>abc</artifactId>
                <version>${abc.version}</version>
            </dependency>
    </dependencies>
  </dependencyManagement>
</project>
For reasons specific to our organization and project, I would like to generate a properties file listing the properties (and their values) from this pom. Something like this:
abc.version=7.8.9
xyz.version=4.5.6
Generating the properties file can be done trivially as described in this answer here.
But it is not clear to me if I can attach this source with a 'properties' classifier and deploying it to our repo. At least not without adding a submodule of type jar or something.
Is there a way I can accomplish this, to attach an additional artifact (the generated 'properties' file) while keeping the BOM project as a single-module project?