This little bit of trickery works. Thanks.
It still doesn't feel right. It relies on the fact that it knows that
only one .rpm file will exists in the directory where it is built. If
that assumption were false, all such files would be successively renamed
to the desired name, with the result that only the last one would exist.
But the assumption in this case is a valid one.
Thanks for pointing it out.
Steve
On 04/09/2015 06:47 PM, Stephen Connolly wrote:
If you use the move ant task you can take the fileset of possible names
that the RPM could have and map them to the name you want to use in the
attach task...
(and since you will always be moving, you have the added bonus of knowing
that its a fresh file as the old ones will always have been moved away)
On 9 April 2015 at 21:47, Steve Cohen <[email protected]> wrote:
On 04/09/2015 03:04 PM, Stephen Connolly wrote:
On Thursday, April 9, 2015, Steve Cohen <[email protected]> wrote:
I think that both of these solutions (Karl's and Stephen's) fall short
because the redline:rpm ant task does some opaque magic to name the rpm.
Therefore it is impossible to specify other than by hardcoding the name
of
the archive you want to attach and the maven plugins (buildhelper and
antrun) aren't flexible enough to accept wildcards.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
