Architecture #2251
closed
Packaging: use a variable to define which maven settings files to use
Added by Jonathan CLARKE about 13 years ago.
Updated about 10 years ago.
Description
To simplify changing the settings file used during a Maven build in packaging (RPM specific), we should store the settings filename in a spec file variable.
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:fa7bfb8bde1802feeb96caccdea7e84fa6b9b7cf.
%{maven_settings} variable is used instead of %{SOURCE2} or %{SOURCE3} but these variables are still defined in the Header section of rudder-inventory-endpoint.spec and rudder-webapp.spec
Nicolas PERRON wrote:
%{maven_settings} variable is used instead of %{SOURCE2} or %{SOURCE3} but these variables are still defined in the Header section of rudder-inventory-endpoint.spec and rudder-webapp.spec
Ah yes, well spotted. I've removed them, does it now look OK to you?
Yes, it seems good to me now !
- Status changed from Pending technical review to Released
- Project changed from Rudder to 34
- Category deleted (
11)
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF
Updated by Jonathan CLARKE 
Updated by Nicolas PERRON 
Updated by