[MAGNOLIA-1084] workflow module depends on dms Created: 27/Sep/06 Updated: 23/Jan/13 Resolved: 17/Oct/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | workflow |
| Affects Version/s: | 3.0 RC2 |
| Fix Version/s: | 3.0 RC4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Fabrizio Giustina | Assignee: | Nicolas Modrzyk |
| 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 |
|
Although the workflow module doesn't define any explicit dependency on the dms one, the workflow bootstrap contains configuration for commands in the dms module (/modules/dms/trees/dms/commands) and magnolia doesn't work properly when workflow is installed and dms isn't. The following is the exception you get while starting magnolia (apart from removing this dependency we should also make sure that the module registration doesn't try to load dummy module definitions without a class defined): WARN info.magnolia.cms.beans.config.ModuleRegistration ModuleRegistration.java(readModuleDefinitions:201) 27.09.2006 11:18:19 no proper module definition file found for [dms]: will add an adhoc definition |
| Comments |
| Comment by Nicolas Modrzyk [ 17/Oct/06 ] |
|
tested. fixed in current trunk. |