[MAGNOLIA-405] Content export / zipper / import Created: 24/May/05 Updated: 12/Dec/08 Resolved: 12/Dec/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Sameer Charles | Assignee: | Magnolia International |
| Resolution: | Outdated | 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)
|
| Date of First Response: |
| Description |
|
I commited i.m.c.core.export package which includes first version of magnolia specific content export this package contains
if you wanna test PackageExport – |
| Comments |
| Comment by Boris Kraft [ 15/Jun/05 ] |
|
needs some more testing & thinking |
| Comment by Philipp Bracher [ 17/May/06 ] |
|
Nothing todo for the 3.0 release |
| Comment by Magnolia International [ 07/Apr/08 ] |
|
as far as i can tell, this package is not used atm. We should have a look at it for 3.6 and do some cleanup, along with cleaning up DataTransporter and friends |
| Comment by Magnolia International [ 09/Jul/08 ] |
|
deprecated the following classes for now, since they are not used:
|
| Comment by Magnolia International [ 12/Dec/08 ] |
|
Package introduced for this feature was removed for |