[MGNLWORKFLOW-97] Create a bundle for workflow modules Created: 24/Jul/13 Updated: 25/Mar/14 Resolved: 06/Feb/14 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | None |
| Affects Version/s: | 5.0 |
| Fix Version/s: | 5.3 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Espen Jervidalo |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Description |
|
I removed the currently unused/unneeded bundle of the workflow module. This caused dependency resolution issues with the ee-bundle that I will describe below. Should this bundle ever be needed again, please be aware of the following. There is a bug in Maven 2.2.1; it is apparently solved in Maven 3.1, but I haven't found a bug report yet, so it could also be fixed in 3.0.x. Maven bug description
SymptomsIn the case of workflow and ee-bundle, the impacted dependency was antlr. magnolia-module-jbpm was excluding it by means of an <exclusion> on its dependency on jbpm-flow-builder. This exclusion was apparently added to reduce the size of said bundle. I'm assuming the intention was to avoid redundancy with artifacts that were already in EE bundle. (indeed, the 4-5-migration module, upon which many modules depend, uses antlr). What to do
Alternatively
Further weirdnessMost uses of antlr i've seen actually declare a dependency on org.antlr:antlr:3.x. For some weird reason, this ends up transitively depending on antlr:antlr:2.7.7. This shouldn't have consequences at runtime, since both use a different package structure. I'm not sure what the intention of this was; perhaps the author intended for users to exclude antlr themselves ? And for some reason I can't explain either, the bug above only seemed to impact (i.e exclude) antlr:antlr, not org.antlr:antlr |