Actions
Architecture #14359
closed
Change Scala project structure so that parent-pom is a real parent project
Status:
Released
Priority:
N/A
Assignee:
Category:
Architecture - Code maintenance
Target version:
Fix check:
Regression:
Description
Now that all scala projects are on the same repos, we can move parent pom as a real maven top project, which will all to have only one "mvn package" to do - and more consistency between our project modules.
I propose to test that set-up in 5.1, and if things are going well, to backport it in all other version to simplify tooling.
Updated by François ARMAND almost 6 years ago
- Status changed from New to In progress
Updated by François ARMAND almost 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/2148
Updated by François ARMAND almost 6 years ago
- Related to Architecture #14147: Merge all scala code repository into rudder one and update directory hierarchy added
Updated by François ARMAND almost 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|5debd7c650abf64f15bd9180d7c70ec5c3b1269a.
Updated by Nicolas CHARLES almost 6 years ago
Applied in changeset rudder|232634bb282b5635598dafacf22683bc208308e0.
Updated by Vincent MEMBRÉ about 5 years ago
This bug has been fixed in Rudder 6.0.0~beta1 which was released today.
Updated by Vincent MEMBRÉ about 5 years ago
- Related to Architecture #14384: Update mvn direct call in rudder-webapp package makefile added
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
Actions