Just be careful with versions since maven and rpm versions aren't 100 %
compatible.
On May 7, 2015 4:59 AM, "Dan Tran" <dant...@gmail.com> wrote:
> I am in another plugin, so best way is to have r-m-p to push to location
> to a maven property
>
> or have r-m-p to comply to maven convention by copy it
> ot ${project.build.directory}/${project.artifactId}-${project.version}.rpm
>
> -Dn
>
> On Wed, May 6, 2015 at 4:32 PM, Brett Okken <brett.okken...@gmail.com>
> wrote:
>
>> Can you get the primary or secondary artifact information, which would
>> include file location, from maven?
>> On May 4, 2015 5:55 PM, "Dan Tran (JIRA)" <j...@codehaus.org> wrote:
>>
>>> Dan Tran
>>> <https://jira.codehaus.org/secure/ViewProfile.jspa?name=dantran>
>>> *updated* an issue Mojo's RPM Maven Plugin
>>> <https://jira.codehaus.org/browse/MRPM> / [image: Bug]
>>> <https://jira.codehaus.org/browse/MRPM-185> MRPM-185
>>> <https://jira.codehaus.org/browse/MRPM-185> Predictable final RPM
>>> location <https://jira.codehaus.org/browse/MRPM-185> Change By: Dan
>>> Tran <https://jira.codehaus.org/secure/ViewProfile.jspa?name=dantran>
>>> I have a requirement to deploy RPM into another box during build.
>>>
>>> I plan to write a custom plugin to push the rpm out, however ,
>>> there is not a way to can programmatically determine the RPM
>>> location after it is built created . [image: Add Comment]
>>> <https://jira.codehaus.org/browse/MRPM-185#add-comment> Add Comment
>>> <https://jira.codehaus.org/browse/MRPM-185#add-comment>
>>> This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) [image:
>>> Atlassian logo]
>>> --------------------------------------------------------------------- To
>>> unsubscribe from this list, please visit:
>>> http://xircles.codehaus.org/manage_email
>>
>>
>
