[MGNLNEWSLETTER-2] Bundling Created: 03/Jun/09  Updated: 16/Sep/15  Resolved: 16/Jun/09

Status: Closed
Project: Newsletter (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0 RC2

Type: Task 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

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

We need a proper bundle for the newsletter modules. Currently, only the -campaign-monitor produces a bundle, and it includes tons of (most probably and hopefully) unnecessary dependencies (probably related to axis usage at build time)



 Comments   
Comment by Magnolia International [ 04/Jun/09 ]

We now have a bundle providing the necessary jar files to integrate the Magnolia Standard Templating Kit with Campaign Monitor. (using the HTTP-GET-based API only)

Comment by Magnolia International [ 05/Jun/09 ]

reopening - although the issue is more likely to get fixed in the ee bundle itself: when adding this bundle in the add-ons folder of the ee-bundle, we get the correct jars and text files, but somehow the jars are ALSO extracted in there. (i.e you have:

add-ons/
|-- LICENSE.txt
|-- META-INF
|   |-- MANIFEST.MF
|-- info
|   `-- magnolia
|       *... classes..
|-- mgnl-bootstrap
| ...
|-- magnolia-* add-ons folders
...
Comment by Magnolia International [ 16/Jun/09 ]

bundle of newsletter itself is fine. bundling of newsletter-bundle in ee-bundle is fixed by MGNLEE-150.

Comment by Michael Mühlebach [ 16/Sep/15 ]

This ticket was closed because former resolved tickets are deemed to be closed now. If this assumption is untrue in this particular case please feel free to reopen the ticket again.

Generated at Mon Feb 12 10:21:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.