[xwiki-devs] checkin - checkout
Hello fellow developers, The usage of a bunch of command-line tools for checking-out the (XML of) xwiki pages and checking them in would be really useful. The xar approach is not really practical: there's no merge, it's problematic when it gets big, and it still doesn't have a command-line to integrate within a build-flow. I am convinced it would be easy, for example, to use the XEclipse code to make checkout, update, and checkin ant-tasks or command-line tools. Did anyone try? thanks in advance paul
Hi Paul! You could easily make such a tool by using the available XML-RPC API. Just use these the jars in the org.xwiki.eclipse.xmlrpc package from XEclipse ( http://svn.xwiki.org/svnroot/xwiki/xeclipse/trunk/plugins/org.xwiki.eclipse.... ). For an example of using the XML-RPC API, you could look at the RemoteXWikiDataStorage.java file at http://svn.xwiki.org/svnroot/xwiki/xeclipse/trunk/plugins/org.xwiki.eclipse.... Of course, you do have the http://platform.xwiki.org/xwiki/bin/view/Features/XMLRPC link which you should check out, but I think that if you are already a bit familiar with XEclipse, you might find that the Java file I specified offers more specific examples of handling content. Let us know how it turns out. :) Paul Libbrecht wrote:
Hello fellow developers,
The usage of a bunch of command-line tools for checking-out the (XML of) xwiki pages and checking them in would be really useful.
The xar approach is not really practical: there's no merge, it's problematic when it gets big, and it still doesn't have a command-line to integrate within a build-flow.
I am convinced it would be easy, for example, to use the XEclipse code to make checkout, update, and checkin ant-tasks or command-line tools.
Did anyone try?
thanks in advance
paul ------------------------------------------------------------------------
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
On Nov 11, 2008, at 9:44 AM, Eduard Moraru wrote:
Hi Paul!
You could easily make such a tool by using the available XML-RPC API.
That would be easy except for the object/class editor I think. -Vincent
Just use these the jars in the org.xwiki.eclipse.xmlrpc package from XEclipse ( http://svn.xwiki.org/svnroot/xwiki/xeclipse/trunk/plugins/org.xwiki.eclipse.... ).
For an example of using the XML-RPC API, you could look at the RemoteXWikiDataStorage.java file at http://svn.xwiki.org/svnroot/xwiki/xeclipse/trunk/plugins/org.xwiki.eclipse....
Of course, you do have the http://platform.xwiki.org/xwiki/bin/view/Features/XMLRPC link which you should check out, but I think that if you are already a bit familiar with XEclipse, you might find that the Java file I specified offers more specific examples of handling content.
Let us know how it turns out. :)
Paul Libbrecht wrote:
Hello fellow developers,
The usage of a bunch of command-line tools for checking-out the (XML of) xwiki pages and checking them in would be really useful.
The xar approach is not really practical: there's no merge, it's problematic when it gets big, and it still doesn't have a command- line to integrate within a build-flow.
I am convinced it would be easy, for example, to use the XEclipse code to make checkout, update, and checkin ant-tasks or command-line tools.
Did anyone try?
thanks in advance
paul
I know it sounds easy therefore I wish someone has done it. My scenario would be: - first a checkout, creates a bunch of xml files of the selected files and spaces - for some of the xml files, "extract text and save aside with proper extension" - edit happily with IDE tools - update because others have worked, that merges (that's probably the hardest) - edit happily with IDE tools - commit to xwiki (for these spaces and files), the ant tool would first make an xml file with the revised source thanks for the pointers at least. paul Le 11-nov.-08 à 09:46, Vincent Massol a écrit :
On Nov 11, 2008, at 9:44 AM, Eduard Moraru wrote:
Hi Paul!
You could easily make such a tool by using the available XML-RPC API.
That would be easy except for the object/class editor I think.
-Vincent
Just use these the jars in the org.xwiki.eclipse.xmlrpc package from XEclipse ( http://svn.xwiki.org/svnroot/xwiki/xeclipse/trunk/plugins/org.xwiki.eclipse.... ).
For an example of using the XML-RPC API, you could look at the RemoteXWikiDataStorage.java file at http://svn.xwiki.org/svnroot/xwiki/xeclipse/trunk/plugins/org.xwiki.eclipse....
Of course, you do have the http://platform.xwiki.org/xwiki/bin/view/Features/XMLRPC link which you should check out, but I think that if you are already a bit familiar with XEclipse, you might find that the Java file I specified offers more specific examples of handling content.
Let us know how it turns out. :)
Paul Libbrecht wrote:
Hello fellow developers,
The usage of a bunch of command-line tools for checking-out the (XML of) xwiki pages and checking them in would be really useful.
The xar approach is not really practical: there's no merge, it's problematic when it gets big, and it still doesn't have a command- line to integrate within a build-flow.
I am convinced it would be easy, for example, to use the XEclipse code to make checkout, update, and checkin ant-tasks or command-line tools.
Did anyone try?
thanks in advance
paul
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
On Nov 11, 2008, at 9:55 AM, Paul Libbrecht wrote:
I know it sounds easy therefore I wish someone has done it.
My scenario would be:
- first a checkout, creates a bunch of xml files of the selected files and spaces - for some of the xml files, "extract text and save aside with proper extension"
- edit happily with IDE tools
- update because others have worked, that merges (that's probably the hardest)
- edit happily with IDE tools
- commit to xwiki (for these spaces and files), the ant tool would first make an xml file with the revised source
thanks for the pointers at least.
If you search the mailing list archives you'll see this has been discussed quite a bit in the past too. I also wanted to do that at the time by adding the ability to checkout/commit directly from a XWiki installation (AFAIR). Thanks -Vincent
Le 11-nov.-08 à 09:46, Vincent Massol a écrit :
On Nov 11, 2008, at 9:44 AM, Eduard Moraru wrote:
Hi Paul!
You could easily make such a tool by using the available XML-RPC API.
That would be easy except for the object/class editor I think.
-Vincent
Just use these the jars in the org.xwiki.eclipse.xmlrpc package from XEclipse ( http://svn.xwiki.org/svnroot/xwiki/xeclipse/trunk/plugins/org.xwiki.eclipse.... ).
For an example of using the XML-RPC API, you could look at the RemoteXWikiDataStorage.java file at http://svn.xwiki.org/svnroot/xwiki/xeclipse/trunk/plugins/org.xwiki.eclipse....
Of course, you do have the http://platform.xwiki.org/xwiki/bin/view/Features/XMLRPC link which you should check out, but I think that if you are already a bit familiar with XEclipse, you might find that the Java file I specified offers more specific examples of handling content.
Let us know how it turns out. :)
Paul Libbrecht wrote:
Hello fellow developers,
The usage of a bunch of command-line tools for checking-out the (XML of) xwiki pages and checking them in would be really useful.
The xar approach is not really practical: there's no merge, it's problematic when it gets big, and it still doesn't have a command- line to integrate within a build-flow.
I am convinced it would be easy, for example, to use the XEclipse code to make checkout, update, and checkin ant-tasks or command-line tools.
Did anyone try?
thanks in advance
paul
Hi Paul, If you mean transforming from XML to plain text and vice-versa yes that's currently a pain when you want to update a page. We can't transform a page content in plain text easily since we have objects/ classes into page definitions and there's no wiki syntax for these (I had this idea of defining such a syntax using macros for example but that's another story...) The current way to do this is to use a live installation and export the page as a XAR. It's not a bad choice I think since it allows you to visualize your change through the rendering and ensure it's correct. We could do the same with XEclipse since it now has the ability to edit objects (and classes?). Now I agree it would be nice to also have the ability for XEclipse to read XML definitions from the file system. However it would still need to send it to the serve for rendering it somehow (that's till we have an XE packaged in XEclipse). Any ideas? Did I understand what you mean Paul? Thanks -Vincent On Nov 11, 2008, at 7:08 AM, Paul Libbrecht wrote:
Hello fellow developers,
The usage of a bunch of command-line tools for checking-out the (XML of) xwiki pages and checking them in would be really useful.
The xar approach is not really practical: there's no merge, it's problematic when it gets big, and it still doesn't have a command- line to integrate within a build-flow.
I am convinced it would be easy, for example, to use the XEclipse code to make checkout, update, and checkin ant-tasks or command-line tools.
Did anyone try?
thanks in advance
participants (3)
-
Eduard Moraru -
Paul Libbrecht -
Vincent Massol