Actions
Architecture #2251
closed
Packaging: use a variable to define which maven settings files to use
Pull Request:
Effort required:
Name check:
Fix check:
Regression:
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.
Updated by Jonathan CLARKE almost 13 years ago
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:fa7bfb8bde1802feeb96caccdea7e84fa6b9b7cf.
Updated by Nicolas PERRON almost 13 years ago
%{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
Updated by Jonathan CLARKE almost 13 years ago
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?
Updated by Jonathan CLARKE almost 13 years ago
- Status changed from Pending technical review to Released
Updated by Nicolas PERRON almost 12 years ago
- Project changed from Rudder to 34
- Category deleted (
11)
Updated by Benoît PECCATTE over 9 years ago
- Project changed from 34 to Rudder
- Category set to Packaging
Actions