[MGNLWORKFLOW-20] Create dependency-management section in magnolia-module-workflow-parent Created: 27/Dec/12 Updated: 15/Jan/13 Resolved: 15/Jan/13 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Daniel Lipp | Assignee: | Federico Grilli |
| Resolution: | Outdated | 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 |
|
As workflow has a module structure - magnolia-module-workflow-parent and two child pom's - it should follow the pattern to define the used versions only once in a dependency management section of the parent. e.g. magnolia-core version or junit version should go there. |
| Comments |
| Comment by Federico Grilli [ 15/Jan/13 ] |
|
This has beed superseded by |