[
http://jira.codehaus.org/browse/MRPM-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242112#action_242112
]
Brett Okken commented on MRPM-90:
---------------------------------
I do not really see a way to accomplish that change passively. As you indicated
the current behavior is working as designed and documented.
Would it be possible to set a property in the parent pom (i.e.
%{rpm.script.preinstall}) and refer to that in the children?
> Support for script and scriptFile
> ---------------------------------
>
> Key: MRPM-90
> URL: http://jira.codehaus.org/browse/MRPM-90
> Project: Mojo RPM Plugin
> Issue Type: Improvement
> Reporter: Jörg Hohwiller
> Assignee: Brett Okken
>
> I have a multi-module-build that creates a hole bunch of RPMs.
> Your rpm-maven-plugin does a good job here - thanks.
> However I have one wish to avoid redundancies in my build:
> I would like to have Scriptles with a <script> that is generic for all
> packages and also a <scriptFile> that if present extends the generic <script>
> with custom logic.
> However <scriptFile> is ignored in this scenario.
> This seems to work as designed:
> http://mojo.codehaus.org/rpm-maven-plugin/adv-params.html#Scripts
> "If both parameters are specified for a script, the external file will be
> ignored."
> Anyways I hope you understand my usecase. It would be nice to make use of
> mavens POM inheritance with the ability to extend with individual custom
> needs in specific modules.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
