[FORGE-90] Content Synchronization module for Magnolia CMS Created: 19/Mar/18 Updated: 15/May/18 Resolved: 09/Apr/18 |
|
| Status: | Resolved |
| Project: | Forge |
| Type: | Project registration | Priority: | Neutral |
| Reporter: | Mariusz Chruscielewski | Assignee: | Pete Ryland |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Project Name: | Content Synchronization |
| Project Short Name: | content-sync |
| Project Description: | Content Synchronization Module
The Content Synchronization Module is used to get content from a source instance into a target instance. For example, you can get content from a PRODuction environment sync'ed (i.e. pulled) into a TEST environment. Workspaces as well as nodes can both be synchronised in one go. Configuration is stored in JCR and done in node /modules/content-synchronisation/config/. How it works: Synchronization first removes configured workspaces/nodes on the target instance, then pulls content from source instance. After synchronization, all imported content is published. Synchronization works in a PULL manner, so it imports content to the instance where user starts it. It does NOT push anything. |
| Developers: |
, Marcel Evers, Stef te Winkel
|
| Project SCM: | External (please specify) |
| Project Jira key: | CONTSYNC |
| Project Maven groupID: | nl.info.magnolia |
| Project License: | GPLv3 |
| Description |
|
Repository is at https://bitbucket.info.nl/projects/TA/repos/content-synchronization |
| Comments |
| Comment by Pete Ryland [ 09/Apr/18 ] |
|
Can you please supply the maven id and repository address? |
| Comment by Mariusz Chruscielewski [ 09/Apr/18 ] |
|
Hi Pete. We have code in our corporate Bitbucket https://bitbucket.info.nl/projects/TA/repos/content-synchronization/browse We were thinking about making that open, but first we wanted to release module.
Artifact details: <dependency>
<groupId>nl.info.magnolia</groupId>
<artifactId>content-synchronization</artifactId>
<version>1.0.9</version>
</dependency>
For the license we chose GPLv3 (as suggested by magnolia)
/** * This file Copyright (c) Info.nl (http://www.info.nl) All rights reserved. * This file is licensed under the GNU General Public License. * <p> * This file is distributed in the hope that it will be * useful, but AS-IS and WITHOUT ANY WARRANTY; without even the * implied warranty of MERCHANTABILITY or FITNESS FOR A * PARTICULAR PURPOSE, TITLE, or NONINFRINGEMENT. * Redistribution, except as permitted by GPL is prohibited. * <p> * 1. For the GPL license (GPL), you can redistribute and/or * modify this file under the terms of the GNU General * Public License, Version 3, as published by the Free Software * Foundation. * <p> * Any modifications to this file must keep this entire header * intact. */
|
| Comment by Pete Ryland [ 09/Apr/18 ] |
|
Mariusz, thanks for registering a new project at the Magnolia Forge ! A Jira project is available for you at https://jira.magnolia-cms.com/projects/CONTSYNC. More details about the infrastructure are available for you at https://forge.magnolia-cms.com/. Please reopen this issue if you have any question or if you encounter any issue. |
| Comment by Marc Champion [ 14/May/18 ] |
|
Hi Mariusz, we had problems with our maven build because your parent pom team-amsterdam-parent-pom cannot be resolved:
Failed to collect dependencies at nl.info.magnolia:content-synchronization:jar:2.0.21: Failed to read artifact descriptor for nl.info.magnolia:content-synchronization:jar:2.0.21: Could not find artifact nl.info.maven.pom:team-amsterdam-parent-pom:pom:3.0.2
After removing the <parent> section from content-synchronization-2.0.21.pom and infonl-magnolia-utils-2.0.22.pom the maven build works as expected. Thank you, Marc |
| Comment by Mariusz Chruscielewski [ 14/May/18 ] |
|
Hi Marc, Thanks a lot for finding. I will look into this this week and release fix. Cheers Mariusz |
| Comment by Mariusz Chruscielewski [ 15/May/18 ] |
|
Hi Marc. It's fixed in version 1.0.18 and 2.0.22.
Regards Mariusz |
| Comment by Marc Champion [ 15/May/18 ] |
|
Hi Mariusz, Thanks for your quick response. 2.0.22 works perfectly for me. Best, Marc |