Project

General

Profile

Bug #12200

Bug #12199: Parent pom update needed for plugins

Dependencies update consequences

Added by François ARMAND about 2 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Category:
-
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

As the number of plugins increase, we want to normalize their structure and the quantity of information that is duplicated in each of them.

The main points are:

- use a "master" build.conf for rudder-branch and perhaps other properties common to all plugin on a given branch,
- perhaps use a master pom to centralize common behaviour (at least, the maximun number of them)
- perhaps find a simpler to check for license build. We would like to have that provided as a service to all plugin without any code on their side for the status checking (it's extremelly error prone and verbose right now)

Some change will need to be made in 4.1, other in 4.3 (because they will also need changes in Rudder plugin API). This ticket takes care of 4.1 branch.

#1

Updated by François ARMAND about 2 years ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
#2

Updated by François ARMAND about 2 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1868
#3

Updated by Rudder Quality Assistant about 2 years ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND
#4

Updated by François ARMAND about 2 years ago

  • Status changed from Pending technical review to Pending release
#5

Updated by Vincent MEMBRÉ about 2 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.3.0~rc1 which was released today.

#6

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version set to 4.3.0~rc1

Also available in: Atom PDF