[
https://jira.codehaus.org/browse/MRPM-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296493#comment-296493
]
Anders Hammar commented on MRPM-107:
------------------------------------
Ran into something similar on a ubuntu box:
[INFO] Wrote:
/home/kama/workspace/rpm-maven-plugin/target/it/rpm-3/target/rpm/rpm-3/RPMS/somearch/rpm-3-1.0-1.somearch.rpm
[DEBUG] Adding RPM as primary artifact:
/home/kama/workspace/rpm-maven-plugin/target/it/rpm-3/target/rpm/rpm-3/RPMS/someArch/rpm-3-1.0-1.someArch.rpm
Notice that somearch != someArch.
> Get "The packaging for this project did not assign a file to the build
> artifact" on Mac
> ---------------------------------------------------------------------------------------
>
> Key: MRPM-107
> URL: https://jira.codehaus.org/browse/MRPM-107
> Project: Mojo RPM Plugin
> Issue Type: Bug
> Components: rpm
> Affects Versions: 2.1-alpha-1
> Environment: Mac OS 10.7.3, Mac Ports rpm
> Reporter: Anders Hammar
> Assignee: Brett Okken
>
> When doing "mvn clean install" on IT rpm-3 (for example) I get an error from
> Maven saying:
> The packaging for this project did not assign a file to the build artifact
> I think the problem is that the plugin thinks the naming of the rpm file is
> something different that it is on my Mac and Maven notices that the specified
> artifact file doesn't exist.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
