New and Noteworthy (since XWiki Enterprise 4.1 version)

JIRA Macro

A new JIRA Macro is now part of the Platform but is not bundled by default (you'll need to install it with the Extension Manager). We previously had a Contributed JIRA Macro but we decided that the JIRA macro was a good candidate to have in the Platform and thus supported by the XWiki Development Team. Compared to the older Contributed JIRA Macro, the new Macro has the following advantages:

• No Programming Rights required
• Supports issue ordering
• Supports ability to register new Styles, new Data Sources and new Field Displayers
• Displays closed issues as Striked-out
• Written in Java with automated tests

Miscellaneous

• Document attachments so far have been displayed in the order in which they are returned by the database, which most of the time happened to be the upload date. Starting with this version attachments are displayed ordered by their filename, which makes it easier to find an attachment, but support for selecting a different order (date, size, author...) will be added soon.
• It's now possible to use Velocity scripts in the Copyright field in the Administration.
• The XWiki Installer now fully works on Windows 7. The XWiki Data is now put in the %APPDATA%\XWiki Enterprise <version>\data directory, while the binaries are installed in Program Files.
• It is no longer allowed to use scripts in comments.  This reduces the security risk from users that only have comment rights.
• Macro parameters may now contain macro syntax.  Example: {{box title="{{info}}Hello!{{/info}}" }}Lorem ipsum ...{{/box}}
• Improve OOB support for JBoss AS7:
  • Removed Struts Taglibs completely since we don't use them and some were defined but not made available, causing errors in deployments on JBoss AS7 ()
  • Fixed Logging conflict between JBoss AS and XWiki ()

For Developers

• The transformation context have a "restricted" flag to indicate that macros and other transformations should not perform modifications to the database, expensive computations or other potentially harmful operations.  Developers of macros and other rendering extensions should pay attention to this flag.
• The messageSender macro now accepts 3 parameters that allow you to customize it by overriding the default displayed visibility levels for a message (that a user can choose from), the default selected visibility level and the default value (in case of user or group visibility). More details on .

Upgrades

The following dependencies have been upgraded:

• Selenium 2.22
• Reflections 0.9.8

Test Report

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

Tested Browsers

Here's the list of browsers tested with this version (i.e. browsers that we've tested as working - Check the list of supported browsers):

Tested Databases

Known issues

• Bugs we know about

Upgrade Notes

Version-specific Upgrade Notes

• The xwiki.work.dir and xwiki.temp.dir properties in the xwiki.cfg configuration file are no longer taken into account. The XWiki work dir (now called XWiki Data Directory or XWiki Permanent Directory) is now configured either by setting the xwiki.data.dir System property or by setting the xwiki.properties's environment.permanentDirectory property. The temporary directory is not configurable within XWiki but can be configured through your Servlet Container (since XWiki uses the Servlet container's temporary directory). See also Configuring directories.

General Upgrade Notes

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

API Breakages

The following APIs were modified since version 4.1: