This is the release notes for XWiki Commons, XWiki Rendering, XWiki Platform and XWiki Enterprise. They share the same release notes as they are released together and have the same version.

<insert description of release here>

New and Noteworthy (since XWiki 5.4)

Full list of issues fixed and Dashboard for <version>.

Moved to Java 7 as minimum version

The minimum required Java version to run XWiki is now Java 7. It's not just the minimum officially supported version, XWiki won't work on Java 6.

Wiki Application

• In the Wiki Index, all the wikis that the user can not access are not displayed anymore.

New Chart Renderers

The stackedbar and stackedbar3D plot renderers were added in the Chart Macro:

Miscellaneous

• The document references are displayed as wiki >> Space >> Page path in the extension install log.

  

• The "membership type" options are more clear

  

• The date search facets have a new option 'Older than 30 days':

  

• Added built in support for Apple's open directory groups in LDAP authenticator
• Generate extension event in Wikistream XAR input module when the XAR contains extension informations
• Add new Locale based API to manipulate current Locale:

  {{code language="velocity}}
    $xcontext.locale
    $xcontext.interfaceLocale
  {{/code}}

See the full list of JIRA issues fixed in this release.

For Developers

Advanced Solr Search Suggest Sources

The Search Suggest feature retrieves live search results from various configurable sources. These sources specify the search engine to use and the search query. The search doesn't perform well, at least on Solr, if we use only the search query because each query is different (when the input text is different) so the cache is not used efficiently. Best is to rely on the filter cache but for this we need to be able to specify the filter query.

Starting with this release you are able to specify more advanced search parameters in the search query and they will be passed directly to the search engine. This currently works with Solr. As an example, the following statement from the 'query' property of a Search Suggest Source

could be written as

Note that:

• you would use the filter query which is the same for all search requests to this Search Suggest Source so it will be cached by Solr
• you would be able to specify the boost for each field you want to search in
• the query statement used is '__INPUT__' by default, if not specified.

In order to preserve backward compatibility with existing Solr Search Suggest Sources, we use the following convention:

 A line that doesn't start with 'xxx=' specifies the query statement; in other words, existing Solr Search Suggest Sources are specifying only the query statement.

For example:

means the query statement is 'foo __INPUT__* bar'. Which is equivalent to:

See the Solr common query parameters and the Extended DisMax query parser parameters documentation  for details on what parameters you can pass to the search engine.

Action API

This Action API module is the entry point for all UIs and in charge of calling the correct backend code to display what the user has asked for (it's the Controller in MVC terminology).

Note that right now most Actions are still implemented the old way in the oldcore module without Components and using Struts. The goal is to progressively rewrite them using this new Action API.

WebJars Integration

The WebJars integration solves the issue of packaging JavaScript frameworks by bundling them as JARs. This allows XWiki Extensions to depend on JavaScript frameworks an be installable by the Extension Manager Application.

Miscellaneous

• The XAR plugins's format mojo now handles properly the defaultLanguage element: if a document has translation we assume it means the document is not a technical document and thus we set the default language to be English. This allows the XWiki SOLR Search to return results when the English language is selected in language facet.
• The XAR plugin's verify mojo now also handles the defaultLanguage check accordingly.
• The XAR plugin's verify mojo now checks for missing license headers (if the formatLicense configuration property is set to true).
• The XAR plugin's format and verify mojos now support including/excluding files.
• We changed a bit the behaviour of Solr search with respect to the current language. We stopped using the (dynamically computed) 'locales' filter by default. We now rely only on the 'locale' facet, which has the current language preselected. See XWIKI-9977 for the full story.
• $services.wiki.getAll() makes a better use of its internal cache, so the performances are better.

Deprecated and Retired projects

• xwiki-platorm-wiki-manager has been removed from the platform. It is still available on the contrib repository and via the extensions Wiki Manager Plugin and Wiki Manager Application.

Upgrades

The following dependencies have been upgraded:

• Logback 1.1.0
• commons-codec 1.9
• JRuby 1.7.10
• cssparser 0.9.13
• doxia 1.5
• Groovy 2.2.1
• HttpClient 4.3.2
• JGroups 3.4.2
• XStream 1.4.6
• SLF4J 1.7.6
• Commons FileUpload 1.3.1
• Aether 0.9.0.M4
• GWT 2.6
• SmartGWT 4.0

Translations

The following translations have been updated: 

• Language
• Language

Tested Browsers & Databases

Known issues

• Bugs we know about

Backward Compatibility and Migration Notes

General Notes

When upgrading make sure you compare your xwiki.cfg, xwiki.properties and web.xml files with the newest version since some configuration parameters may have been modified or added. Note that you should add xwiki.store.migration=1 so that XWiki will attempt to automatically migrate your current database to the new schema. Make sure you backup your Database before doing anything.

Moved to Java 7 as minimum version

The minimum required Java version to run XWiki is now Java 7. It's not just the minimum officially supported version, XWiki won't work on Java 6.

API Breakages

The following APIs were modified since <project> <version - 1>: