[MGNLEE-150] bundling : since update of maven-assembly-plugin, dependencies of bundles are added to the bundle Created: 08/Jun/09 Updated: 23/Jun/14 Resolved: 08/Jun/09 |
|
| Status: | Closed |
| Project: | Magnolia DX Core |
| Component/s: | build / bundling |
| Affects Version/s: | None |
| Fix Version/s: | 4.1, 4.0.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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
|
||||||||
| Description |
|
As a result, we end up with extracted jars. This only happened with magnolia-tools so far (magnolia-tools.jar was extracted in the add-ons folder) because we only had this case one where an add-on was depending on another info.magnolia artifact which was not in scope:provided. (our assembly was including everything of the info.magnolia group) This showed up more prominently with newsletter, since it is one of those "custom" bundles that bundles several modules in a tgz. See |