[
https://issues.apache.org/jira/browse/CLOUDSTACK-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547721#comment-13547721
]
Hugo Trippaers commented on CLOUDSTACK-150:
-------------------------------------------
Hey guys,
This is an old ticket, we have discussed this on the dev-list. For packaging we
feel that maven is not the right tool, while there are plugins that make rpms
directly out of maven poms, this is not the ideal solution. The trouble with
this solution is that there will be no clear separation between the compile,
build and package steps, this makes it hard for anybody not directly involved
with the codebase to make package. If we wish for distros and other package
providers to start providing packages, we need this clear separation. So at the
moment Wido, me and several other are working on packaging outside of maven,
using the native tools like spec files and install scripts.
With this i'm going to close this ticket with a "Won't fix notation". The
ticket for the "other style" rpms is CLOUDSTACK-729 Provide RPM spec file
without depending on waf and system packages
Cheers,
Hugo
> Configure Maven to build rpm packages
> -------------------------------------
>
> Key: CLOUDSTACK-150
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-150
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Hugo Trippaers
> Priority: Blocker
> Fix For: 4.1.0
>
>
> Configure rpm-maven-plugin (http://mojo.codehaus.org/rpm-maven-plugin) to
> build rpm packages, deprecate waf for building rpms.
> Release Planning:
> Dev list discussion: http://markmail.org/message/wwa74uqid3g2fuh6
> Functional Spec: unknown
> Feature Branch: unknown
> Docs task is CLOUDSTACK-1
> QA will occur based on testing the whole release.
--
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
