Ok I think I know... Actually the message is printed in the console. You see something in the page only if you print in the global scope because this is what gets returned by script evaluation. Calling “println” in a class doesn’t return anything in the evaluation and thus you don’t see anything. That’s why the examples at http://extensions.xwiki.org/xwiki/bin/view/Extension/Groovy+Macro work. Thanks -Vincent On 18 Dec 2014 at 22:10:54, Bryn Jeffries (bryn.jeffries@sydney.edu.au(mailto:bryn.jeffries@sydney.edu.au)) wrote: Actually this is a good question! I don’t know… I’ve tried it in the groovy web console and it works so it’s something specific to the way XWiki uses Groovy. Could be because that we use the Scripting API (JSR 223) to access Groovy. It probably means that the output is not wired when inside the class scope but I’m not sure why… The method is invoked for since the following works fine: {{groovy}} class Callee {  String hello() {    return "hello, world"  } } c = new Callee() println c.hello() {{/groovy}} If someone has an idea… Thanks -Vincent

Ok I’ve discussed with Guillaume Laforge from Groovy fame and here are more details: * In our code we capture the output of the script and use it to display the rendered page so any println located directly in the script will work. * However for a println in a Class, Groovy call System.out.println(…) - which is why it goes in the xwiki logs - and we would need to capture that in a thread safe way to redirect it to the page rendering this is a bit more involved: ** Use System.set(PrintStream) with a custom PrintStream that would use for example a threadlocal variable to direct the content to our page being rendered ** Use Groovy’s runtime metaprogramming feature, for example: PrintStream.metaClass.println = { String s -> ...handle thread safety here.. }. ** Use Groovy’s compile-time metaprogramming feature and implement a Groovy AST Transformation to transform all println calls into something else. For example by adding a binding to the ScriptContext and using that binding instead of println. This requires using a CompilationCustomizer (we already do that in XWiki btw) which returns an ASTTransformationCustomizer to do the work. Thanks -Vincent On 19 Dec 2014 at 00:10:18, Bryn Jeffries (bryn.jeffries@sydney.edu.au(mailto:bryn.jeffries@sydney.edu.au)) wrote:

Last time I did a mediawiki import I used https://github.com/xwiki-contrib/sandbox/tree/master/xwiki-wikiimporter, worked reasonably well but yes there is no release of it (but it's easy to build it with Maven). Ideally someone need to spend some time converting and improving the mediawiki part it as an input module for the new XWiki Filter module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+Module). On Fri, Dec 19, 2014 at 5:08 PM, Ilsa Loving <iloving(a)jonahgroup.com> wrote: -- Thomas Mortagne