[
https://issues.apache.org/jira/browse/CLOUDSTACK-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459017#comment-13459017
]
David Nalley commented on CLOUDSTACK-150:
-----------------------------------------
So not arguing with the work you want to do here - but this seems circular to
me - maven calls rpmbuild which calls maven?
Why not a compile +install profile that allows you to define where you want
things to go (think of options like --prefix=path and --bindir=/path in a make
world).
And then just calling rpmbuild to call those profiles and assemble the package
- that would effectively get rid of waf - and mean that the work necessary to
get deb and rpm into shape is really upstream of the package itself (less work,
I think)
--David
> Configure Maven to build rpm packages
> -------------------------------------
>
> Key: CLOUDSTACK-150
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-150
> Project: CloudStack
> Issue Type: New Feature
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: 4.1.0
>
>
> Configure a Maven plugin to build rpm packages, deprecate waf for building
> rpms.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
