[MAGNOLIA-1025] configuration: improve properties finding, enable resource filtering, use system properties Created: 05/Sep/06 Updated: 23/Jan/13 Resolved: 06/Sep/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | build |
| Affects Version/s: | 3.0 RC2 |
| Fix Version/s: | 3.0 RC3 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| 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)
|
| Date of First Response: |
| Description |
|
some small things would make the current configuration mechanism a little bit easier to handle:
Doing this we can avoid doublicated files by having multiple configurations in one jar. It is obsolete to change the config files (for bindName or similar) if you run multiple magnolias in on container. |
| Comments |
| Comment by Philipp Bracher [ 06/Sep/06 ] |
|
commited |