Groowiki is a Wiki program and a document management system together. It is a wiki program that utilizes Subversion, Groovy, Velocity, and many more existing products. It lets you edit Wiki pages in a tree structure just like any other wiki, but it also gives you SVN access that makes it very easy to add files to the content. It stores everything in SVN. This way all information is versioned and (optionally) accessible offline, and you can upload your modifications in batches. This is especially useful if you work with large files and the Wiki pages mainly summarize the contents of the documents.
| Tags | Wiki Groovy SVN velocity |
|---|---|
| Licenses | GPL |
| Operating Systems | OS Independent |
| Implementation | Java 5 |
| Translations | English |
Recent releases


Release Notes: Lucene indexing and search, a document oriented graphical workflow, RADEOX support, a WYSIWYG editor, a skin facelift, and simplified installation.


Release Notes: This release is available as prepackaged ZIP file that new users can unzip into C:\groowiki and start without configuration under Windows. A null pointer exception when Groowiki was restarted and some users were still logged in has been fixed.


Release Notes: This release supports the Radeox format and is programmable in Java and Groovy. This release contains numerous bugfixes as well as a new API for extension plugins that make it possible to write plugins in Java and in Groovy. The wiki engine now contains the Radeox engine, so you can write the description of the files in the well-known WikiCreole standard formatting. Authentication can be configured to be based on SVN (just as before) as well as external authentication sources. From this release there are Community (free, GPL) as well as Professional, Enterprise, and ASP editions of the program available.


Release Notes: A bug that prevented installation to anywhere but the ROOT application of the servlet container was fixed. A new PDF version of the Users' Guide is also available with this release.
Tools to analyze and find common issues with eScript code based on best practices for coding.