[MAGNOLIA-5357] ComponentsTestUtil setMagnoliaConfigurationProperties in Static Initializers Created: 03/Oct/13 Updated: 17/Mar/21 Resolved: 17/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Milan Divilek | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
info.magnolia.test.ComponentsTestUtil use Static Initializers for setMagnoliaConfigurationProperties into SystemProperty. So they are set when the class is initialized, but the problem is there is no clean way how to set them if they were clean. Only how they can be set again is call ComponentsTestUtil.clear() method. What is really ugly to setMagnoliaConfigurationProperties on clear... This cause problem when maven do the test during build. |