[MGNLCDEP-2] Please rename to "dependency" module Created: 25/Nov/10 Updated: 01/Dec/10 Resolved: 26/Nov/10 |
|
| Status: | Closed |
| Project: | Content Dependencies |
| Component/s: | None |
| Affects Version/s: | 1.0 |
| Fix Version/s: | 1.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Boris Kraft | Assignee: | Federico Grilli |
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
Now that we have a description of what this module does, I suggest to rename it to "dependency management" or something similar. This is IMHO much clearer. |
| Comments |
| Comment by Federico Grilli [ 26/Nov/10 ] |
|
OK, is magnolia-module-dependencies fine? |
| Comment by Boris Kraft [ 26/Nov/10 ] |
|
I think the project name can be Magnolia Content Dependency Module; the jar name is fine as you suggest it. |