Hello,
for some of our projects we generate RPM packages during the package
phase. These RPM files are later on attached for installation and
deployment using a small plugin we wrote. The problem is, the name of
those RPM files intentionally does not follow the (Maven) convention of
${project.artifactId}-${project.version}.rpm, but uses prefixes and
suffixes that we require (some of them commonly found in the RPM world,
like .el5.x86_64(.rpm) or .noarch(.rpm)). However, during mvn install or
mvn deploy, the final name of the rpm package is changed back to
${project.artifactId}-${project.version}.rpm, which hides some important
details that we would like to keep.
To illustrate on example:
[...]
[INFO] [util:attach {execution: default}]
[INFO]
Attaching:/home/radek/workspace/project-2.3.0-1/target/rpm/RPMS/noarch/group-project-2.3.0.1-16287.noarch.rpm
[INFO] [install:install]
[INFO] Installing /home/radek/workspace/project-2.3.0-1/pom.xml to
/home/radek/.m2/repository/com/seamless/group/project/2.3.0-1/project-2.3.0-1.pom
[INFO] Installing
/home/radek/workspace/project-2.3.0-1/target/rpm/RPMS/noarch/group-project-2.3.0.1-16287.noarch.rpm
to
/home/radek/.m2/repository/com/seamless/group/project/2.3.0-1/project-2.3.0-1.rpm
[...]
As you can see, the file group-project-2.3.0.1-16287.noarch.rpm is
installed as project-2.3.0-1.rpm. Is there a way to prevent this, ie.
keep the original file name?
Note that we would like that only for RPM packages (not even pom files),
because we don't use them as dependencies in our mavenized projects. We
don't want to change file names of artifacts of other types to not break
the dependency resolution.
Thanks,
Radek
signature.asc
Description: This is a digitally signed message part
