|
||||||||
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 |
- [mojo-dev] [jira] (MRPM-87) Create SRPM Christopher Tubbs (JIRA)
- [mojo-dev] [jira] (MRPM-87) Create SRPM Rickard von Essen (JIRA)
- [mojo-dev] [jira] (MRPM-87) Create SRPM Rickard von Essen (JIRA)
- [mojo-dev] [jira] (MRPM-87) Create SRPM Christopher Tubbs (JIRA)
- [mojo-dev] [jira] (MRPM-87) Create SRPM Knut Vidar Siem (JIRA)
- [mojo-dev] [jira] (MRPM-87) Create SRPM Knut Vidar Siem (JIRA)
- [mojo-dev] [jira] (MRPM-87) Create SRPM Knut Vidar Siem (JIRA)
- [mojo-dev] [jira] (MRPM-87) Create SRPM Christopher Tubbs (JIRA)
The point of an SRPM is to be able to package once and quickly rebuild an RPM on different architectures... not to simply distribute source. This is especially important if you're building arch-dependent RPMs (think JNI libs vs. just jars).
I'd be happy if there were an option to generate the SPEC file and drop in a tarball I create with the assembly plugin. But, I suppose I can do this with exec-maven-plugin. It just seems like there's some utility (and within scope) in making it more convenient with this plugin.