Release Notes for XWiki 6.3-milestone-1 (XWiki.org)

This is the release notes for [[XWiki Commons>>http://commons.xwiki.org]], [[XWiki Rendering>>http://rendering.xwiki.org]], [[XWiki Platform>>http://platform.xwiki.org]] and [[XWiki Enterprise>>http://enterprise.xwiki.org]]. They share the same release notes as they are released together and have the same version.

6

7

8

9

= New and Noteworthy (since XWiki 6.2) =

10

11

[[Full list of issues fixed and Dashboard for 6.3>>http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=12693]].

12

13

== Extension Manager and Repository improvements ==

14

15

* ##<scm>## element from Maven ##pom.xml## is now supported and has been added to the standard in the API

16

* ##<issueManagement>## element from Maven ##pom.xml## is now supported and has been added to the standard in the API

17

* When importing an extension unknown but valid versions are not removed anymore

18

19

== User Directory customized globally ==

20

21

The administrator of the wiki can customize the default columns to be displayed by the user directory.

22

23

{{image reference="userDirectoryGloballyConfigurableInAdministration.png"/}}

24

25

For more information, see the [[documentation>>extensions:Extension.User Directory Application]]

== Flamingo ==

The Flamingo skin was introduced as experimental in XWiki 6.0 & 6.1 and has been deemed usable in XWiki 6.2. However we're still tuning details. It happens that we did not all agree on the location of the "Add" button (some wanted it inside the content, next to the "Edit" buttons and others wanted it back at the top - You can [[follow the discussion here>>http://markmail.org/message/jqbcj4p4ryc56sms]] if you're interested ;)). Thus we've decided for the moment to put it back at the top where it was in the Colibri skin in order to not force our users to learn a new location for the moment. This is still a discussion in progress and if you have inputs and preferences please do not hesitate to let us know on the [[XWiki Users Mailing List>>dev:Community.MailingLists]] or on the [[related Issue>>http://jira.xwiki.org/browse/XWIKI-11167]]. Thanks!

31

32

33

* The 'Add' button has been moved back to the top bar and the search bar to the right:(((

34

{{image reference="ReleaseNotesXWiki622@flamingo-add.png" width="60%"/}}

35

)))

36

* When you click on the 'add' button, the order of the choices have been inverted, to propose to create a page first, then a space, and finally a wiki:(((

37

{{image reference="ReleaseNotesXWiki622@flamingo-add-options.png"/}}

38

)))

39

* The Wiki/Space/Page buttons in the top bar have been changed and are no longer split into two parts. You do not need to click the arrow specifically any more to open the contextual menu:(((

40

41

)))

42

* To navigate to the current Wiki/Space/Page in the top bar, there is now a new "Go to..." item:(((

43

|=Wiki|=Space|=Page

44

|{{image reference="ReleaseNotesXWiki622@flamingo-goto-wiki.png"/}}|{{image reference="ReleaseNotesXWiki622@flamingo-goto-space.png"/}}|{{image reference="ReleaseNotesXWiki622@flamingo-goto-page.png"/}}

45

)))

46

* The languages selection is now located in the top bar. It is displayed only when the multilingual mode is enabled:(((

47

{{image reference="ReleaseNotesXWiki622@languages.png" width="60%"/}}

48

When there is no translation available:

49

{{image reference="ReleaseNotesXWiki622@languages-no-alternative.png"/}}

50

When there is some translations available:

51

{{image reference="ReleaseNotesXWiki622@languages-with-alternatives.png"/}}

52

)))

53

* The [[Livetable>>extensions:Extension.Livetable Macro]] is now responsive to the screen size, so you can use them with smartphones:(((

54

{{image reference="ReleaseNotesXWiki622@Livetable-Responsive.png"/}}

55

)))

56

* The "Add" button has now a default action to create a new page. You can still create other kind of contents (Wiki, Space) by using the arrow, just like we do with the different "edit" actions.(((

57

58

)))

59

* The Flamingo Theme Application now uses a new Color Picker.(((

60

61

)))

62

* To sum up, this is the new look:(((

)))

== Miscellaneous ==

* The default color themes (DefaultColorTheme and FlamingoDefaultTheme) have been renamed Azure and Charcoal.

69

* In the select field of the 'color theme' property, in the administration, the color themes are now ordered by name.

70

* In the administration, clicking the "Customize" button for customizing a Skin or a Color Theme now opens the page it leads to in edit mode.

71

* Improved L&F when a template fails to render:(((

72

73

)))

74

* We have created dedicated groups for Colibri and Flamingo Themes inside the Administration. Every themes can be used with both skins but they looks better when they are used with the corresponding theme.(((

75

76

)))

77

* The start/stop shell scripts provided with the Standalone Distribution have been improved to display usage information when an invalid parameter is passed or when the ##-h## or ##~-~-help## parameters are passed. Also note that the start script doesn't stop anymore a running XWiki instance if the ##-k## or ##~-~-kill## parameter is passed (this parameter has been removed).

78

* It's now possible to configure the maximum number of search results to be returned from a search operation using ##xwiki.authentication.ldap.maxresults## property in ##xwiki.cfg## file. See [[LDAP documentation>>platform:AdminGuide.Authentication||anchor="HGenericLDAPconfiguration"]].

79

* The "Empty is today" option on Date fields of classes created with Application Within Minutes is now working as expected. See [[XWIKI-10296>>http://jira.xwiki.org/browse/XWIKI-10296]]

80

* Office macro can now take a URL as input. See [[extensions:Extension.Office Macro]] for more details

81

82

See the [[full list of JIRA issues>>http://jira.xwiki.org/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+in+%28XCOMMONS%2C+XRENDERING%2C+XWIKI%2C+XE%29+and+status+%3D+Closed+and+resolution+%3D+Fixed+and+fixVersion+%3D+%22<version>%22&tempMax=1000]] fixed in this release.

= For Developers =

== Velocity macros to display users and groups ==

87

88

We extracted the code that displays in view mode a property of type 'List of Users' and 'List of Groups' from the corresponding custom displayers (found in ##displayer_users.vm## and ##displayer_groups.vm##) into two Velocity macros that can be used to display arbitrary users and groups, even when you don't have an object. Here's how you can use them:

= Users =

== Just one ==

#displayUser('XWiki.Admin')

96

97

== List of users ==

98

#displayUser(['Admin', 'XWiki.mflorea'])

99

100

== A reference of a user ==

101

#displayUser($xcontext.userReference)

102

103

== A list of references of users ==

104

#displayUser([$xcontext.userReference, $otherUserReference])

= Groups =

== Just one ==

#displayGroup('XWiki.XWikiAdminGroup')

109

110

== List of groups ==

111

#displayGroup(['XWikiAdminGroup','XWiki.HRGroup'])

112

113

== A reference of a group ==

114

#set($adminGroupRef = $services.model.resolveDocument('XWiki.XWikiAdminGroup'))

115

#set($allGroupRef = $services.model.resolveDocument('XWiki.XWikiAllGroup'))

116

#displayGroup($adminGroupRef)

117

118

== A list of references of groups ==

119

#displayGroup([$adminGroupRef, $allGroupRef])

== New Velocity Tools ==

126

127

* New URL Tool ##$urltool##: A [[new tool>>extensions:Extension.Velocity Module||anchor="HVelocityTools"]] has been added with one method to parse query string from the URL ##$urltool.parseQuery(String)##. The value returned by this is method is a ##Map<String, List<String>>## which maps parameter names to (possibly multiple) values, and can be passed e.g. directly into ##$escapetool.url(Map<String, ?>)## to convert it back to a string. This is useful e.g. in cases where one want to pass a complete query string around between requests, as it happend for the PDF export; the ##$urltool## allows for a sane deserialization of the value passed around.

128

* New Exception Tool ##$exceptiontool##: A [[new tool>>extensions:Extension.Velocity Module||anchor="HVelocityTools"]] to manipulate Java Exceptions (get root cause, convert into String, etc).

129

130

== Ability to catch Exceptions from Velocity ==

131

132

A new Velocity Directive has been added to catch Exceptions from Velocity. In addition a new ###displayUnexpectedException()## velocity macro has also been added to nicely display an exception to the user.

For example:

#try()

#set($outputSyntax = $xwiki.getAvailableRendererSyntax($request.outputSyntax, $request.outputSyntaxVersion))

139

#if ($outputSyntax)

140

## If the passed syntax is not an HTML-compatible syntax we need to HTML-escape it so that it can be

141

## displayed fine in HTML (since at the point this vm file is called we're already inside an HTML page with

142

## panels on the side, header, etc).

143

#set($syntaxType = $outputSyntax.type.toIdString())

144

#if (($syntaxType == "xhtml") || ($syntaxType == "html"))

145

#set ($renderedContent = $tdoc.getRenderedContent($outputSyntax))

146

#else

147

## Make sure to print correctly the result when it's not HTML

148

#set ($renderedContent = "<pre>$escapetool.html($tdoc.getRenderedContent($outputSyntax))</pre>")

149

#end

150

#else

151

#set ($renderedContent = $tdoc.getRenderedContent())

#end

#end

...

#if ("$!exception" != '')

157

#displayUnexpectedException($exception)

#else

$renderedContent

#end

</div>

...

This generates the following in case of error rendering the page:

== New #displayException macro ==

170

171

Displays an error message with a title that can be clicked and expands to display an exception.

172

173

Example from a wiki page:

#set ($message = $services.mailsender.createMessage())

$message.send()

#displayException("hello world", $services.mailsender.lastError)

== Component Disposal ==

187

188

The order used by the ComponentManager to dispose its components is computed based on declared dependencies. However there might be cases when you wish a Component's ##dispose()## method to be called before or after all other components. In this case you can use the ##DisposePriority## annotation. The default priority is 1000. A higher value will mean disposing before all other components not having this annotation. For example:

@Component

@Singleton

@DisposePriority(10000)

194

public class DefaultHibernateSessionFactory implements HibernateSessionFactory, Disposable

{

...

@Override

public void dispose() throws ComponentLifecycleException

199

{

200

... called after other components in order to shut down the database late...

}

...

}

See the [[Component Reference documentation>>extensions:Extension.Component Module]] for other details.

207

208

== New LiveTable Filtering Option ==

209

210

You can now specify how the filter value should be matched against the stored value. One use case when this is useful is when you have a live table for an XClass that has a Database List property and you want to use a text input filter instead of the default drop down list filter. Currently the user has to enter the full value in the text input in order to filter. Would be good if partial matching would work. This is possible starting with this version:

211

212

213

#set ($columnsProperties = {

214

'doc.name': {'type': 'text', 'size': 10, 'link': 'view'},

215

...

216

'myDatabaseList': {'type': 'text', 'size': 10, 'match': 'partial'},

...

})

Checkout the [[LiveTable Macro documentation>>extensions:Extension.Livetable Macro||anchor="HParameter24columnsProperties"]] for more details about the **match** option.

== Miscellaneous ==

* The wiki provisioning job has now the current user set in the context.

226

* 10 new icons have been mapped into [[Font Awesome Icon Theme>>extensions:Extension.Font Awesome Icon Theme]].

227

* It's now possible to overwrite the id of a Java bean property using an annotation. See [[extensions:Extension.Properties Module||anchor="HPopulateaJavaBean"]] for more.

228

* [[It's possible to get DEBUG information only for shutdown operations>>dev:Community.Debugging||anchor="HLoggingshutdownoperations"]] by editing ##logback.xml## and setting:(((

)))

* When importing an extension unknown but valid versions are not removed anymore

== Upgrades ==

The following dependencies have been upgraded:

238

239

* [[JGroups 3.5.1>>http://jira.xwiki.org/browse/XWIKI-10987]]

240

* [[Tika 1.6>>http://jira.xwiki.org/browse/XWIKI-10956]]

241

* [[reflections 0.9.9>>http://jira.xwiki.org/browse/XCOMMONS-654]]

242

* [[Groovy 2.3.7>>http://jira.xwiki.org/browse/XCOMMONS-655]]

243

* [[jQuery 1.11.1>>http://jira.xwiki.org/browse/XWIKI-11094]]

244

* [[Doxia 1.6>>http://jira.xwiki.org/browse/XRENDERING-364]]

245

* [[Joda-Time 2.5>>http://jira.xwiki.org/browse/XRENDERING-365]]

246

* [[commons-compress 1.9>>http://jira.xwiki.org/browse/XCOMMONS-665]]

= Translations =

The following translations have been updated:

= Tested Browsers & Databases =

255

256

{{include reference="TestReports.ManualTestReportXWiki63M1Summary"/}}

= Known issues =

* [[Bugs we know about>>http://jira.xwiki.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=category+%3D+%22Top+Level+Projects%22+AND+issuetype+%3D+Bug+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC]]

261

262

= 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.

== API Breakages ==

The following APIs were modified since XWiki 6.2:

Wiki source code of Release Notes for XWiki 6.3-milestone-1

Quick Links

Let us know

About

About

Support

Platform

User Guide

Admin Guide

Developer Guide

Projects

XWiki

Extensions

Other

Contribute

Status

Practices

Under the Hood

Get Involved

Get Connected

author	version	line-number	content
		1	{{box cssClass="floatinginfobox" title="Contents"}}
		2	{{toc/}}
		3	{{/box}}
		4
		5	This is the release notes for [[XWiki Commons>>http://commons.xwiki.org]], [[XWiki Rendering>>http://rendering.xwiki.org]], [[XWiki Platform>>http://platform.xwiki.org]] and [[XWiki Enterprise>>http://enterprise.xwiki.org]]. They share the same release notes as they are released together and have the same version.
		6
		7	<insert description of release here>
		8
		9	= New and Noteworthy (since XWiki 6.2) =
		10
		11	[[Full list of issues fixed and Dashboard for 6.3>>http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=12693]].
		12
		13	== Extension Manager and Repository improvements ==
		14
		15	* ##<scm>## element from Maven ##pom.xml## is now supported and has been added to the standard in the API
		16	* ##<issueManagement>## element from Maven ##pom.xml## is now supported and has been added to the standard in the API
		17	* When importing an extension unknown but valid versions are not removed anymore
		18
		19	== User Directory customized globally ==
		20
		21	The administrator of the wiki can customize the default columns to be displayed by the user directory.
		22
		23	{{image reference="userDirectoryGloballyConfigurableInAdministration.png"/}}
		24
		25	For more information, see the [[documentation>>extensions:Extension.User Directory Application]]
		26
		27	== Flamingo ==
		28
		29	{{info}}
		30	The Flamingo skin was introduced as experimental in XWiki 6.0 & 6.1 and has been deemed usable in XWiki 6.2. However we're still tuning details. It happens that we did not all agree on the location of the "Add" button (some wanted it inside the content, next to the "Edit" buttons and others wanted it back at the top - You can [[follow the discussion here>>http://markmail.org/message/jqbcj4p4ryc56sms]] if you're interested ;)). Thus we've decided for the moment to put it back at the top where it was in the Colibri skin in order to not force our users to learn a new location for the moment. This is still a discussion in progress and if you have inputs and preferences please do not hesitate to let us know on the [[XWiki Users Mailing List>>dev:Community.MailingLists]] or on the [[related Issue>>http://jira.xwiki.org/browse/XWIKI-11167]]. Thanks!
		31	{{/info}}
		32
		33	* The 'Add' button has been moved back to the top bar and the search bar to the right:(((
		34	{{image reference="ReleaseNotesXWiki622@flamingo-add.png" width="60%"/}}
		35	)))
		36	* When you click on the 'add' button, the order of the choices have been inverted, to propose to create a page first, then a space, and finally a wiki:(((
		37	{{image reference="ReleaseNotesXWiki622@flamingo-add-options.png"/}}
		38	)))
		39	* The Wiki/Space/Page buttons in the top bar have been changed and are no longer split into two parts. You do not need to click the arrow specifically any more to open the contextual menu:(((
		40	{{image reference="ReleaseNotesXWiki622@flamingo-menubar.png"/}}
		41	)))
		42	* To navigate to the current Wiki/Space/Page in the top bar, there is now a new "Go to..." item:(((
		43	\|=Wiki\|=Space\|=Page
		44	\|{{image reference="ReleaseNotesXWiki622@flamingo-goto-wiki.png"/}}\|{{image reference="ReleaseNotesXWiki622@flamingo-goto-space.png"/}}\|{{image reference="ReleaseNotesXWiki622@flamingo-goto-page.png"/}}
		45	)))
		46	* The languages selection is now located in the top bar. It is displayed only when the multilingual mode is enabled:(((
		47	{{image reference="ReleaseNotesXWiki622@languages.png" width="60%"/}}
		48	When there is no translation available:
		49	{{image reference="ReleaseNotesXWiki622@languages-no-alternative.png"/}}
		50	When there is some translations available:
		51	{{image reference="ReleaseNotesXWiki622@languages-with-alternatives.png"/}}
		52	)))
		53	* The [[Livetable>>extensions:Extension.Livetable Macro]] is now responsive to the screen size, so you can use them with smartphones:(((
		54	{{image reference="ReleaseNotesXWiki622@Livetable-Responsive.png"/}}
		55	)))
		56	* The "Add" button has now a default action to create a new page. You can still create other kind of contents (Wiki, Space) by using the arrow, just like we do with the different "edit" actions.(((
		57	{{image reference="flamingo-add.png"/}}
		58	)))
		59	* The Flamingo Theme Application now uses a new Color Picker.(((
		60	{{image reference="ReleaseNotesXWiki621@NewColorPicker.png"/}}
		61	)))
		62	* To sum up, this is the new look:(((
		63	{{image reference="ReleaseNotesXWiki622@flamingo.png"/}}
		64	)))
		65
		66	== Miscellaneous ==
		67
		68	* The default color themes (DefaultColorTheme and FlamingoDefaultTheme) have been renamed Azure and Charcoal.
		69	* In the select field of the 'color theme' property, in the administration, the color themes are now ordered by name.
		70	* In the administration, clicking the "Customize" button for customizing a Skin or a Color Theme now opens the page it leads to in edit mode.
		71	* Improved L&F when a template fails to render:(((
		72	{{image reference="templateerror.png" width="650px"/}}
		73	)))
		74	* We have created dedicated groups for Colibri and Flamingo Themes inside the Administration. Every themes can be used with both skins but they looks better when they are used with the corresponding theme.(((
		75	{{image reference="ColorThemeDisplayer.png"/}}
		76	)))
		77	* The start/stop shell scripts provided with the Standalone Distribution have been improved to display usage information when an invalid parameter is passed or when the ##-h## or ##~-~-help## parameters are passed. Also note that the start script doesn't stop anymore a running XWiki instance if the ##-k## or ##~-~-kill## parameter is passed (this parameter has been removed).
		78	* It's now possible to configure the maximum number of search results to be returned from a search operation using ##xwiki.authentication.ldap.maxresults## property in ##xwiki.cfg## file. See [[LDAP documentation>>platform:AdminGuide.Authentication\|\|anchor="HGenericLDAPconfiguration"]].
		79	* The "Empty is today" option on Date fields of classes created with Application Within Minutes is now working as expected. See [[XWIKI-10296>>http://jira.xwiki.org/browse/XWIKI-10296]]
		80	* Office macro can now take a URL as input. See [[extensions:Extension.Office Macro]] for more details
		81
		82	See the [[full list of JIRA issues>>http://jira.xwiki.org/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+in+%28XCOMMONS%2C+XRENDERING%2C+XWIKI%2C+XE%29+and+status+%3D+Closed+and+resolution+%3D+Fixed+and+fixVersion+%3D+%22<version>%22&tempMax=1000]] fixed in this release.
		83
		84	= For Developers =
		85
		86	== Velocity macros to display users and groups ==
		87
		88	We extracted the code that displays in view mode a property of type 'List of Users' and 'List of Groups' from the corresponding custom displayers (found in ##displayer_users.vm## and ##displayer_groups.vm##) into two Velocity macros that can be used to display arbitrary users and groups, even when you don't have an object. Here's how you can use them:
		89
		90	{{code language="none"}}
		91	{{velocity}}
		92	{{html wiki="true"}}
		93	= Users =
		94	== Just one ==
		95	#displayUser('XWiki.Admin')
		96
		97	== List of users ==
		98	#displayUser(['Admin', 'XWiki.mflorea'])
		99
		100	== A reference of a user ==
		101	#displayUser($xcontext.userReference)
		102
		103	== A list of references of users ==
		104	#displayUser([$xcontext.userReference, $otherUserReference])
		105
		106	= Groups =
		107	== Just one ==
		108	#displayGroup('XWiki.XWikiAdminGroup')
		109
		110	== List of groups ==
		111	#displayGroup(['XWikiAdminGroup','XWiki.HRGroup'])
		112
		113	== A reference of a group ==
		114	#set($adminGroupRef = $services.model.resolveDocument('XWiki.XWikiAdminGroup'))
		115	#set($allGroupRef = $services.model.resolveDocument('XWiki.XWikiAllGroup'))
		116	#displayGroup($adminGroupRef)
		117
		118	== A list of references of groups ==
		119	#displayGroup([$adminGroupRef, $allGroupRef])
		120
		121	{{/html}}
		122	{{/velocity}}
		123	{{/code}}
		124
		125	== New Velocity Tools ==
		126
		127	* New URL Tool ##$urltool##: A [[new tool>>extensions:Extension.Velocity Module\|\|anchor="HVelocityTools"]] has been added with one method to parse query string from the URL ##$urltool.parseQuery(String)##. The value returned by this is method is a ##Map<String, List<String>>## which maps parameter names to (possibly multiple) values, and can be passed e.g. directly into ##$escapetool.url(Map<String, ?>)## to convert it back to a string. This is useful e.g. in cases where one want to pass a complete query string around between requests, as it happend for the PDF export; the ##$urltool## allows for a sane deserialization of the value passed around.
		128	* New Exception Tool ##$exceptiontool##: A [[new tool>>extensions:Extension.Velocity Module\|\|anchor="HVelocityTools"]] to manipulate Java Exceptions (get root cause, convert into String, etc).
		129
		130	== Ability to catch Exceptions from Velocity ==
		131
		132	A new Velocity Directive has been added to catch Exceptions from Velocity. In addition a new ###displayUnexpectedException()## velocity macro has also been added to nicely display an exception to the user.
		133
		134	For example:
		135
		136	{{code language="velocity"}}
		137	#try()
		138	#set($outputSyntax = $xwiki.getAvailableRendererSyntax($request.outputSyntax, $request.outputSyntaxVersion))
		139	#if ($outputSyntax)
		140	## If the passed syntax is not an HTML-compatible syntax we need to HTML-escape it so that it can be
		141	## displayed fine in HTML (since at the point this vm file is called we're already inside an HTML page with
		142	## panels on the side, header, etc).
		143	#set($syntaxType = $outputSyntax.type.toIdString())
		144	#if (($syntaxType == "xhtml") \|\| ($syntaxType == "html"))
		145	#set ($renderedContent = $tdoc.getRenderedContent($outputSyntax))
		146	#else
		147	## Make sure to print correctly the result when it's not HTML
		148	#set ($renderedContent = "<pre>$escapetool.html($tdoc.getRenderedContent($outputSyntax))</pre>")
		149	#end
		150	#else
		151	#set ($renderedContent = $tdoc.getRenderedContent())
		152	#end
		153	#end
		154	...
		155	<div id="xwikicontent">
		156	#if ("$!exception" != '')
		157	#displayUnexpectedException($exception)
		158	#else
		159	$renderedContent
		160	#end
		161	</div>
		162	...
		163	{{/code}}
		164
		165	This generates the following in case of error rendering the page:
		166
		167	{{image reference="renderingerror.png"/}}
		168
		169	== New #displayException macro ==
		170
		171	Displays an error message with a title that can be clicked and expands to display an exception.
		172
		173	Example from a wiki page:
		174
		175	{{code language="none"}}
		176	{{velocity}}
		177	#set ($message = $services.mailsender.createMessage())
		178	$message.send()
		179
		180	{{html}}
		181	#displayException("hello world", $services.mailsender.lastError)
		182	{{/html}}
		183	{{/velocity}}
		184	{{/code}}
		185
		186	== Component Disposal ==
		187
		188	The order used by the ComponentManager to dispose its components is computed based on declared dependencies. However there might be cases when you wish a Component's ##dispose()## method to be called before or after all other components. In this case you can use the ##DisposePriority## annotation. The default priority is 1000. A higher value will mean disposing before all other components not having this annotation. For example:
		189
		190	{{code language="java"}}
		191	@Component
		192	@Singleton
		193	@DisposePriority(10000)
		194	public class DefaultHibernateSessionFactory implements HibernateSessionFactory, Disposable
		195	{
		196	...
		197	@Override
		198	public void dispose() throws ComponentLifecycleException
		199	{
		200	... called after other components in order to shut down the database late...
		201	}
		202	...
		203	}
		204	{{/code}}
		205
		206	See the [[Component Reference documentation>>extensions:Extension.Component Module]] for other details.
		207
		208	== New LiveTable Filtering Option ==
		209
		210	You can now specify how the filter value should be matched against the stored value. One use case when this is useful is when you have a live table for an XClass that has a Database List property and you want to use a text input filter instead of the default drop down list filter. Currently the user has to enter the full value in the text input in order to filter. Would be good if partial matching would work. This is possible starting with this version:
		211
		212	{{code language="none"}}
		213	#set ($columnsProperties = {
		214	'doc.name': {'type': 'text', 'size': 10, 'link': 'view'},
		215	...
		216	'myDatabaseList': {'type': 'text', 'size': 10, 'match': 'partial'},
		217	...
		218	})
		219	{{/code}}
		220
		221	Checkout the [[LiveTable Macro documentation>>extensions:Extension.Livetable Macro\|\|anchor="HParameter24columnsProperties"]] for more details about the match option.
		222
		223	== Miscellaneous ==
		224
		225	* The wiki provisioning job has now the current user set in the context.
		226	* 10 new icons have been mapped into [[Font Awesome Icon Theme>>extensions:Extension.Font Awesome Icon Theme]].
		227	* It's now possible to overwrite the id of a Java bean property using an annotation. See [[extensions:Extension.Properties Module\|\|anchor="HPopulateaJavaBean"]] for more.
		228	* [[It's possible to get DEBUG information only for shutdown operations>>dev:Community.Debugging\|\|anchor="HLoggingshutdownoperations"]] by editing ##logback.xml## and setting:(((
		229	{{code language="xml"}}
		230	<logger name="org.xwiki.shutdown" level="debug"/>
		231	{{/code}}
		232	)))
		233	* When importing an extension unknown but valid versions are not removed anymore
		234
		235	== Upgrades ==
		236
		237	The following dependencies have been upgraded:
		238
		239	* [[JGroups 3.5.1>>http://jira.xwiki.org/browse/XWIKI-10987]]
		240	* [[Tika 1.6>>http://jira.xwiki.org/browse/XWIKI-10956]]
		241	* [[reflections 0.9.9>>http://jira.xwiki.org/browse/XCOMMONS-654]]
		242	* [[Groovy 2.3.7>>http://jira.xwiki.org/browse/XCOMMONS-655]]
		243	* [[jQuery 1.11.1>>http://jira.xwiki.org/browse/XWIKI-11094]]
		244	* [[Doxia 1.6>>http://jira.xwiki.org/browse/XRENDERING-364]]
		245	* [[Joda-Time 2.5>>http://jira.xwiki.org/browse/XRENDERING-365]]
		246	* [[commons-compress 1.9>>http://jira.xwiki.org/browse/XCOMMONS-665]]
		247
		248	= Translations =
		249
		250	The following translations have been updated:
		251
		252	{{language codes="none, none"/}}
		253
		254	= Tested Browsers & Databases =
		255
		256	{{include reference="TestReports.ManualTestReportXWiki63M1Summary"/}}
		257
		258	= Known issues =
		259
		260	* [[Bugs we know about>>http://jira.xwiki.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=category+%3D+%22Top+Level+Projects%22+AND+issuetype+%3D+Bug+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC]]
		261
		262	= Backward Compatibility and Migration Notes =
		263
		264	== General Notes ==
		265
		266	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.
		267
		268	== API Breakages ==
		269
		270	The following APIs were modified since XWiki 6.2:
		271
		272	{{code language="none"}}
		273	<clirr output here>
		274	{{/code}}