Hi Anders,
Thanks for the quick reply I am not so much interested in the filename as
such, but the name encoded in the RPM, this is because the standards-nazis
at my present employer have come up with some bizarre naming scheme for
RPMs and I am trying to bolt the RPM build onto long existing maven
projects without having to go through the gymnastics of creating new
projects which copy down dependencies and bundle them into RPMs. I had
managed simply to add the major part of the configuration into my root
POM's pluginManagement section and just have a minimal reference in the
leaf projects. However the naming standards threw a spanner in the works.
I will look into creating a patch.

> The name of the artifact deployed to the repo is standardized by the
> repo layout. However, I agree that the file produced under target
> could use project.build.finalName (although is see little benefit of
> this as it is IMHO what is deployed to the repo that matters). If it's
> important, please file a ticket. A patch is always welcome! :-)
>
> /Anders
>
> On Wed, Apr 25, 2012 at 14:38, Sandy McPherson <alls...@xs4all.nl> wrote:
>> Hi,
>> This is a great plugin, only drawback would seem to be that the name of
>> the rpm is the project.artifactId and it is not configurable. This is a
>> great pity. I would have thought it more natural to use the
>> project.build.finalName as the default value of the RPM name, but still
>> have name configurable through the mojo configuration, or maybe I'm just
>> missing something here.
>> Thxs
>> Sandy
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to