Found the answer at:
http://stackoverflow.com/questions/3998596/renaming-resources-in-maven
"You can avoid the over head of Ant by using the Maven Assembly plugin
<http://maven.apache.org/plugins/maven-assembly-plugin/> and the file
assembly descriptor
<http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_file>.
"
It worked perfectly but for the verbosity of the assembly descriptor.
On 03/11/2011 09:25 AM, Farrukh Najmi wrote:
My maven project manages files for an open standard and uses the
maven-assembly-plugin to produce a zip for all artifacts for a
specific version of the standard.
The project files are stored in version control so naturally the spec
document files that are in the assembly zip do not have the
${pom.version} in the filename. Instead the ${pom.version} is in the
name of the assembly zip file as is nornal maven practice.
The problem is that the standards organization requires the spec
document files in teh assembly zip to also have the ${pom.version} in
the filename. This seems like a bad rule but one that we have to live
with for now.
Is there some way that the maven-assembly-plugin can be told to rename
certain artifacts in the assembly zip?
I know I can do rename this via maven-antrun-plugin but is there a
cleaner way?
--
Regards,
Farrukh Najmi
Web: http://www.wellfleetsoftware.com
