From version < 2.1 >
edited by Vincent Massol
on 2019/12/05
To version < 4.1 >
edited by Thomas Mortagne
on 2020/01/20
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.VincentMassol
1 +XWiki.ThomasMortagne
Content
... ... @@ -21,6 +21,7 @@
21 21  The following runtime dependencies have been upgraded (they have a different release cycle than [[XWiki Commons>>http://commons.xwiki.org]], [[XWiki Rendering>>http://rendering.xwiki.org]] and [[XWiki Platform>>http://platform.xwiki.org]]):
22 22  
23 23  * [[CSS4J 2.0.0>>https://jira.xwiki.org/browse/XWIKI-16905]]
24 +* [[Jodconverter 4.2.3>>https://jira.xwiki.org/browse/XWIKI-16973]]
24 24  
25 25  = Translations =
26 26  
... ... @@ -61,10 +61,24 @@
61 61  ** ##hibernate.cfg.xml##
62 62  * Add ##xwiki.store.migration=1## in ##xwiki.cfg## so that XWiki will attempt to automatically migrate your current database to any new schema. Make sure you backup your Database before doing anything.
63 63  
64 -== Issues specific to XWiki <version> ==
65 +== Issues specific to XWiki 12.0RC1 ==
65 65  
66 -<issues specific to the project>
67 +=== Velocity 2.2 upgrade ===
67 67  
69 +After more than 9 years Velocity is getting an update. While this bring some nice new things it also comes with unavoidable behavior changes that might be a breackage for your scripts or break some extensions:
70 +
71 +* The Velocity Java API changed quite a lot, if you use advanced features directly in Java there is a big chance that you need to update your code. You can find more details on https://velocity.apache.org/engine/2.2/upgrading.html
72 +* Most names of Velocity configuration properties have changed ; old names are still functional but will emit a deprecation warning in the log. See the [[Configuration Changes in Velocity 2.1>>https://velocity.apache.org/engine/2.2/configuration-property-changes-in-2.1.html]] page.
73 +* We tried to reduce as much as possible the breaking changes in the language using some retro compatibility flags provided by Velocity and some hacks on XWiki side but there is still things for which you might want to be carefull:
74 +** Deprecations: A lot of APIs are now deprecated, they should work fine but will produce a warning in the log (unless you disabled that using the new property ##logging.deprecated.enabled## in ##xwiki.properties##)
75 +*** $listtool was already deprecatedd since Velocity 1.6 which added support for allows all List methods to be called on arrays
76 +*** $sorttool replaced by $collectiontool
77 +*** $velocityCount and $velocityHasNext where already deprecated in Velocity 1.7 without producing any deprecation warning, they now do
78 +** Breackages:
79 +*** No more macro semi-local context: in Velocity 1.7 variable set inside a macro and set both in the global context and in a special local context. In Velocity 2.x this local context does not exist anymore. In pratice in means that if in your macro you #set a variable and execute another Velocity template which set the same variable your macro will be affected while it used to be "protected" by the previous explicit #set
80 +** Known bugs:
81 +*** Macro parameters names mess with expression passed to the macro: see https://issues.apache.org/jira/browse/VELOCITY-904?focusedCommentId=17019513&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17019513. Should be fixed in 12.0 final.
82 +
68 68  == API Breakages ==
69 69  
70 70  The following APIs were modified since <project> <version - 1>:

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

New and Noteworthy (since XWiki )

Full list of issues fixed and Dashboard for .

For Users

No changes!

Miscellaneous

  • Rendered Changes Using Image Data: A change in the source URL, or reference, of an image displayed on a wiki page, where the image itself is not modified, doesn't appear in the rendered diff anymore when comparing the revisions of that page.

For Admins

Name Strategies for XWiki Pages


A new Name Strategy Module has been introduced to allow administrators to have more control on the wiki page names.
The name strategies allow to validate and transform page names before they are created to comply with a defined policy.
The transformation of page name is performed before page creations through XWiki UI, while page name validation is performed at the API level.

Two strategies have been implemented as a start for this new feature:
  - the Character Replacement Strategy: allows to define forbidden characters in page names, and replacement characters for each. If no replacement characters are defined, the forbidden characters are simply removed from page names.
  - the Slug Name Strategy: allows to normalize page names to remove any special characters and accents.

By default, the Character Replacement Strategy is used with "/" (slash) and "\" (backslash) as forbidden characters, without defined characters. Only the page name transformation is enabled, page name validation is still experimental and should be used with caution. 

This new feature can be setup in the Administration in Editing > Name Strategies.

Miscellaneous

  • Disable deprecation warnings: A new property property logging.deprecated.enabled xwiki.properties allow controlling if warning related to use of deprecated APIs should be logged or not. See Logging Module for more details.

  • XAR export improvement: A new version of the XAR format has been introduced to improve the way attachment history is exported:

    • it's streamable (exporting an attachment history used to require a lot of memory)
    • version with identical content are de-duplicated (for example the history contain the current version so with the old format it's stored in both the current version and the history)

    This new format is used by default to store deleted documents but not yet in the XAR export administration, should be enabled in 12.0 final.

  • Solr Debian package: A new xwiki-solr-core Debian package is now provided, which automatically registers an xwiki core in a standalone Solr instance (provided it uses the standard setup).

  • Select the Wiki Home Page with the new Page Picker: The wiki descriptor administration section is now using the new page picker for the home page field.

For Developers

Velocity upgrade to 2.2


After 9 years Velocity finally got a update. You can see a detailed changelog on https://velocity.apache.org/engine/2.2/changes.html but here are the important new things from XWiki script authors:

  • Allow expressions inside []: $foo[$bar + 1]
  • New strategy for reference boolean evaluation:
    • return false for a null object
    • return its value for a Boolean object, or the result of the getAsBoolean() method if it exists.
    • if directive.if.emptycheck is false (true by default), stop here and return true.
    • check for emptiness:
      • return whether an array is empty.
      • return whether isEmpty() is false (covers String and all Collection classes).
      • return whether length() is zero (covers CharSequence classes other than String).
      • returns whether size() is zero.
      • return whether a Number strictly equals zero.
    • check for emptiness after explicit conversion methods:
      • return whether the result of getAsString() is empty (and false for a null result) if it exists.
      • return whether the result of getAsNumber() strictly equals zero (and false for a null result) if it exists.
  • Support $array.empty, as for $list.empty
  • Fix parsing of $obj._method()
  • Have #foreach honnor the Closeable interface on the iterator
  • Fix regression: #setleft-paren no longer valid grammar
  • Fix parser for '$map{key}' text rendering
  • #foreach should work over any Iterable class
  • Method arguments can now be expressions
  • Fixed quotes escaping so that doubling single quotes only works when enclosing quotes are single quotes (and same behaviour for double quotes)
  • Add ability to specify default values for macro parameters, e.g.; #macro(foo bar=1)
  • Add ability to place line comments next to macro parameter definitions
  • Block directives no longer require parenthesis so #@foo #end is now allowed. Also, brackets now work with Block Macros so #{@foo}bar#end works
  • Default block for empty loops: #foreach($i in []) loop block #else empty #end
  • Rendering of arrays should display their content, as for lists
  • New generic $collectiontool which replaces and enhances the former SortTool
  • New generic $logtool

Moved Modules

Upgrades

The following runtime dependencies have been upgraded (they have a different release cycle than XWiki Commons, XWiki Rendering and XWiki Platform):

Translations

The following translations have been updated: 

  • Language
  • Language

Known issues

Backward Compatibility and Migration Notes

General Notes

  • When upgrading make sure you compare and merge the following XWiki configuration files since some parameters may have been modified, removed or added:
    • xwiki.cfg
    • xwiki.properties
    • web.xml
    • hibernate.cfg.xml
  • Add xwiki.store.migration=1 in xwiki.cfg so that XWiki will attempt to automatically migrate your current database to any new schema. Make sure you backup your Database before doing anything.

Issues specific to XWiki

Issues specific to XWiki 12.0RC1

Velocity 2.2 upgrade

After more than 9 years Velocity is getting an update. While this bring some nice new things it also comes with unavoidable behavior changes that might be a breackage for your scripts or break some extensions:

  • The Velocity Java API changed quite a lot, if you use advanced features directly in Java there is a big chance that you need to update your code. You can find more details on https://velocity.apache.org/engine/2.2/upgrading.html
  • Most names of Velocity configuration properties have changed ; old names are still functional but will emit a deprecation warning in the log. See the Configuration Changes in Velocity 2.1 page.
  • We tried to reduce as much as possible the breaking changes in the language using some retro compatibility flags provided by Velocity and some hacks on XWiki side but there is still things for which you might want to be carefull:
    • Deprecations: A lot of APIs are now deprecated, they should work fine but will produce a warning in the log (unless you disabled that using the new property logging.deprecated.enabled in xwiki.properties)
      • $listtool was already deprecatedd since Velocity 1.6 which added support for allows all List methods to be called on arrays
      • $sorttool replaced by $collectiontool
      • $velocityCount and $velocityHasNext where already deprecated in Velocity 1.7 without producing any deprecation warning, they now do
    • Breackages:
      • No more macro semi-local context: in Velocity 1.7 variable set inside a macro and set both in the global context and in a special local context. In Velocity 2.x this local context does not exist anymore. In pratice in means that if in your macro you #set a variable and execute another Velocity template which set the same variable your macro will be affected while it used to be "protected" by the previous explicit #set
    • Known bugs:

API Breakages

The following APIs were modified since :

Credits

The following people have contributed code and translations to this release (sorted alphabetically):

Get Connected