[
https://issues.apache.org/jira/browse/CLOUDSTACK-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459028#comment-13459028
]
Rohit Yadav commented on CLOUDSTACK-150:
----------------------------------------
Prefix can be more complicated than you think. compile/install goal will work
only on ${project.target}, which gets tricky once you want to configure how to
package scripts, post/pre install scripts and other files
(ui/html/css/pngs/scripts/isos etc.).
Right now, waf calls ant calls maven gets deps, builds with ant, calls rpmbuild
to build rpms. With a possible rpm plugin it would be much easier to say build
rpm for only one submodule (say api) and not all of them. Same goes with debs.
Each submodule gets clean separation of building, testing and packaging. Every
submodule gets it own control or spec, unlike now. The rules to generate will
be within attributes in poms, or they can be in some other location as files.
If there is some way to do that, without using any plugins, that would be great
and less/no work for me :) Let me know what you think.
> 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
