Project

General

Profile

Actions

Architecture #2251

closed

Packaging: use a variable to define which maven settings files to use

Added by Jonathan CLARKE about 12 years ago. Updated about 9 years ago.

Status:
Released
Priority:
3
Category:
Packaging
Target version:
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.

Actions #1

Updated by Jonathan CLARKE about 12 years ago

  • Status changed from In progress to Pending technical review
  • % Done changed from 0 to 100

Applied in changeset commit:fa7bfb8bde1802feeb96caccdea7e84fa6b9b7cf.

Actions #2

Updated by Nicolas PERRON about 12 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

Actions #3

Updated by Jonathan CLARKE about 12 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?

Actions #4

Updated by Nicolas PERRON about 12 years ago

Yes, it seems good to me now !

Actions #5

Updated by Jonathan CLARKE about 12 years ago

  • Status changed from Pending technical review to Released
Actions #6

Updated by Nicolas PERRON about 11 years ago

  • Project changed from Rudder to 34
  • Category deleted (11)
Actions #7

Updated by Benoît PECCATTE about 9 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions

Also available in: Atom PDF