Valdis, look at currikiorg where this is done: - a web project with additional and replacement resources and additional dependencies, including own plugins, all maven built - a wiki project where src/main/webapp/resources are the xml that make up the xar and where src/main/webapp/pages are the source files of the pages that are pushed afterwards as page wiki (using "upload-to-wiki"). All but the last step seems to be the widespread way of working. Paul On 9 mai 2013, at 20:18, Valdis Vītoliņš wrote:

I'm working on a project, which potentially could be useful for more than one customer. Therefore I'm thinking how to manage automated updates for Xwiki content (xar file for partial export) and ../webapps/xwiki (additional jar files and differences/replacements for existing files) folder.

On the one hand it should provide easy steps for Linux/web admins, which are not very familiar with Xwiki for upgrading their, on the other hand, it shouldn't be too hard to manage for me also.

I assume, it could be some (xwiki?) github project though I wonder, what structure should I have there.

To not reinvent the wheel, can you describe what tools/approaches you see as the best?

E.g. how you manage content for: https://github.com/xwiki/xwiki-enterprise/tree/master/xwiki-enterprise-ui/sr...

Thanks! Valdis

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs