Second milestone of the XWiki Enterprise 3.1 version (Roadmap). This is mostly an "upgrade" release in which we've upgraded lots of third party libraries we use. In addition we're now requiring Java 6 at runtime.

New and Noteworthy (since XWiki Enterprise 3.1M1)

Upgrades

• XWiki now requires Java 6!
• Upgrade JGroups to latest version 2.12.1
• Upgrade to Groovy 1.8
• Upgrade to commons-net-3.0
• Move from Commons Logging/Log4J to SLF4J/Logback
• Upgrade to hibernate-validator 4.1.0.Final

For developers

• XCOMMONS-10: Add support for injecting Logger with @Inject. Now you can have the XWiki Commons logging implementation inserted into your module using dependency injection.

Miscellaneous

• XWIKI-6583: Completion of Office document export from milestone 1 by fixing the embedding of images.
• XWIKI-116: Added the ability to dictate what mode documents should be edited in by default on a document by document basis.
• XWIKI-6574: Created a repository for automatically downloading XWiki Extensions using the Extension Manager.
• XWIKI-6599: Support for suggestion sources to provide custom icon/images for individual result entry
• XWIKI-6635: Add support for non-interactive wizard steps
• Lots of bug fixes and improvements, see a full list of issues closed in the 3.1M2 frame

Translations

• No changes were added to translations.

Known issues

• Bugs we know about

Test Report

You can check the manual test report to learn about what was tested and the results on various browsers.

Backward Compatibility and Migration Notes

Java 1.6

XWiki Enterprise 3.1 Milestone 2 and all subsequent versions will be compiled with Java6, Java5 is no longer supported.

Deprecated XClass database tables removed

In XWIKI-6624 a set of database tables and their supporting infrastructure were removed. These tables held XWiki Class information but since XWiki 1.0, the table method of storage has been deprecated and non-default. If upgrading from a pre-1.0 version of XWiki, it is important to make sure you are using the XML XWiki class storage and not the database tables first.

WYSIWYG Editor Configuration

In order to implement XWIKI-6618 we changed the format of the menu bar configuration. If you exclude the XWiki.WysiwygEditorConfig page when you upgrade your wiki pages (which you should do in order to preserve your WYSIWYG editor configuration) then you have to:

1. edit the XWiki.WysiwygEditorConfig page with the object editor
2. remove deprecated properties (you have to do this because we changed the type of the Menu Bar property to accommodate the new format)
3. change the value of the Menu Bar property to use the following JSON format:
   [{
    "feature" : "link",
    "subMenu" : ["linkEdit", "linkRemove", "linkWikiPage", "linkAttachment", "|", "linkWebPage", "linkEmail"]
   },
   {
    "feature" : "image",
    "subMenu" : ["imageInsertAttached", "imageInsertURL", "imageEdit", "imageRemove"]
   },
   {
    "feature" : "table",
    "subMenu" : ["inserttable", "insertcolbefore", "insertcolafter", "deletecol", "|", "insertrowbefore", "insertrowafter", "deleterow", "|", "deletetable"]
   },
   {
    "feature" : "macro",
    "subMenu" : ["macroInsert", "macroEdit", "|", "macroRefresh", "|", "macroCollapse", "macroExpand"]
   },
   {
    "feature" : "import",
    "subMenu" : ["importOffice"]
   }]

If importing XWiki.WysiwygEditorConfig or XWiki.WysiwygEditorConfigTemplate fails then you have to follow this steps in order to update the WYSIWYG editor configuration:

1. Revert the XWiki.WysiwygEditorConfigClass page to its previous version, i.e. the version before the import
2. Delete the XWiki.WysiwygEditorConfig and XWiki.WysiwygEditorConfigTemplate pages from your wiki
3. Import only the XWiki.WysiwygEditorConfigClass page from the upgrade XAR
4. Import the XWiki.WysiwygEditorConfig and XWiki.WysiwygEditorConfigTemplate pages from the upgrade XAR

General Notes

You may also want to import the default wiki XAR in order to benefit from the improvements listed above.

API Breakages

No APIs were modified since XWiki Enterprise 3.0.