|
||||||||
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)
Without totally changing the behavior and implementation of this plugin this seams impossible. Take the trivial example (see example1.pom
) which installs the main artifact and a dependency in /opt/foo/lib.
To build a SRPM for this we must include the source for the main artifact, which is possible. This would require Maven to compile it this could be solved by bundling it or depending on an RPM which includes it, but we also need to execute this in the correct context, i.g. with the correct settings.xml and correct Maven repositories accessible. This is something out of control of the rpm-plugin. The same goes for dependencies.
If you want to distribute your source code. Just build a archive from your SCM or use the maven-assembly-plugin to zip etc. and include proper build instructions.