[MGNLSTK-1104] Dependency mgmt is unnecessarily complicated Created: 27/Feb/13 Updated: 07/Mar/13 Resolved: 27/Feb/13 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | build |
| Affects Version/s: | None |
| Fix Version/s: | 2.5 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Daniel Lipp | Assignee: | Eric Hechinger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Description |
|
STK parent pom's dependency mgmt section defines version as usual. Unfortunately it doesn't define all version there. Hence we have a mix of how version are defined. e.g. dependency mgmt section defines versions for
As most of these non-managed dependencies are used in several modules, updating any version e.g. when preparing a release is unnecessarily "complex" |