Show last authors
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 <version>>>http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=<fill id here>]].
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
18 == Flamingo ==
19
20 {{info}}
21 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!
22 {{/info}}
23
24 * The 'Add' button has been moved back to the top bar and the search bar to the right:(((
25 {{image reference="ReleaseNotesXWiki622@flamingo-add.png" width="60%"/}}
26 )))
27 * 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:(((
28 {{image reference="ReleaseNotesXWiki622@flamingo-add-options.png"/}}
29 )))
30 * 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:(((
31 {{image reference="ReleaseNotesXWiki622@flamingo-menubar.png"/}}
32 )))
33 * To navigate to the current Wiki/Space/Page in the top bar, there is now a new "Go to..." item:(((
34 |=Wiki|=Space|=Page
35 |{{image reference="ReleaseNotesXWiki622@flamingo-goto-wiki.png"/}}|{{image reference="ReleaseNotesXWiki622@flamingo-goto-space.png"/}}|{{image reference="ReleaseNotesXWiki622@flamingo-goto-page.png"/}}
36 )))
37 * The languages selection is now located in the top bar. It is displayed only when the multilingual mode is enabled:(((
38 {{image reference="ReleaseNotesXWiki622@languages.png" width="60%"/}}
39 When there is no translation available:
40 {{image reference="ReleaseNotesXWiki622@languages-no-alternative.png"/}}
41 When there is some translations available:
42 {{image reference="ReleaseNotesXWiki622@languages-with-alternatives.png"/}}
43 )))
44 * The [[Livetable>>extensions:Extension.Livetable Macro]] is now responsive to the screen size, so you can use them with smartphones:(((
45 {{image reference="ReleaseNotesXWiki622@Livetable-Responsive.png"/}}
46 )))
47 * 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.(((
48 {{image reference="flamingo-add.png"/}}
49 )))
50 * The Flamingo Theme Application now uses a new Color Picker.(((
51 {{image reference="ReleaseNotesXWiki621@NewColorPicker.png"/}}
52 )))
53 * To sum up, this is the new look:(((
54 {{image reference="ReleaseNotesXWiki622@flamingo.png"/}}
55 )))
56
57 == Miscellaneous ==
58
59 * The default color themes (DefaultColorTheme and FlamingoDefaultTheme) have been renamed Azure and Charcoal.
60 * 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.
61 * Improved L&F when a template fails to render:(((
62 {{image reference="templateerror.png" width="650px"/}}
63 )))
64 * 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.(((
65 {{image reference="ColorThemeDisplayer.png"/}}
66 )))
67 * 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).
68 * [[It's possible to get DEBUG information only for shutdown operations>>dev:Community.Debugging||anchor="HLoggingshutdownoperations"]] by editing ##logback.xml## and setting:(((
69 {{code language="xml"}}
70 <logger name="org.xwiki.shutdown" level="debug"/>
71 {{/code}}
72 )))
73 * 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"]].
74 * 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]]
75 * Office macro can now take a URL as input. See [[extensions:Extension.Office Macro]] for more details
76
77 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.
78
79 = For Developers =
80
81 == Velocity macros to display users and groups ==
82
83 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:
84
85 {{code language="none"}}
86 {{velocity}}
87 {{html wiki="true"}}
88 = Users =
89 == Just one ==
90 #displayUser('XWiki.Admin')
91
92 == List of users ==
93 #displayUser(['Admin', 'XWiki.mflorea'])
94
95 == A reference of a user ==
96 #displayUser($xcontext.userReference)
97
98 == A list of references of users ==
99 #displayUser([$xcontext.userReference, $otherUserReference])
100
101 = Groups =
102 == Just one ==
103 #displayGroup('XWiki.XWikiAdminGroup')
104
105 == List of groups ==
106 #displayGroup(['XWikiAdminGroup','XWiki.HRGroup'])
107
108 == A reference of a group ==
109 #set($adminGroupRef = $services.model.resolveDocument('XWiki.XWikiAdminGroup'))
110 #set($allGroupRef = $services.model.resolveDocument('XWiki.XWikiAllGroup'))
111 #displayGroup($adminGroupRef)
112
113 == A list of references of groups ==
114 #displayGroup([$adminGroupRef, $allGroupRef])
115
116 {{/html}}
117 {{/velocity}}
118 {{/code}}
119
120 == New Velocity Tools ==
121
122 * 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.
123 * New Exception Tool ##$exceptiontool##: A [[new tool>>extensions:Extension.Velocity Module||anchor="HVelocityTools"]] to manipulate Java Exceptions (get root cause, convert into String, etc).
124
125 == Ability to catch Exceptions from Velocity ==
126
127 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.
128
129 For example:
130
131 {{code language="velocity"}}
132 #try()
133 #set($outputSyntax = $xwiki.getAvailableRendererSyntax($request.outputSyntax, $request.outputSyntaxVersion))
134 #if ($outputSyntax)
135 ## If the passed syntax is not an HTML-compatible syntax we need to HTML-escape it so that it can be
136 ## displayed fine in HTML (since at the point this vm file is called we're already inside an HTML page with
137 ## panels on the side, header, etc).
138 #set($syntaxType = $outputSyntax.type.toIdString())
139 #if (($syntaxType == "xhtml") || ($syntaxType == "html"))
140 #set ($renderedContent = $tdoc.getRenderedContent($outputSyntax))
141 #else
142 ## Make sure to print correctly the result when it's not HTML
143 #set ($renderedContent = "<pre>$escapetool.html($tdoc.getRenderedContent($outputSyntax))</pre>")
144 #end
145 #else
146 #set ($renderedContent = $tdoc.getRenderedContent())
147 #end
148 #end
149 ...
150 <div id="xwikicontent">
151 #if ("$!exception" != '')
152 #displayUnexpectedException($exception)
153 #else
154 $renderedContent
155 #end
156 </div>
157 ...
158 {{/code}}
159
160 This generates the following in case of error rendering the page:
161
162 {{image reference="renderingerror.png"/}}
163
164 == New #displayException macro ==
165
166 Displays an error message with a title that can be clicked and expands to display an exception.
167
168 Example from a wiki page:
169
170 {{code language="none"}}
171 {{velocity}}
172 #set ($message = $services.mailsender.createMessage())
173 $message.send()
174
175 {{html}}
176 #displayException("hello world", $services.mailsender.lastError)
177 {{/html}}
178 {{/velocity}}
179 {{/code}}
180
181 == Component Disposal ==
182
183 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:
184
185 {{code language="java"}}
186 @Component
187 @Singleton
188 @DisposePriority(10000)
189 public class DefaultHibernateSessionFactory implements HibernateSessionFactory, Disposable
190 {
191 ...
192 @Override
193 public void dispose() throws ComponentLifecycleException
194 {
195 ... called after other components in order to shut down the database late...
196 }
197 ...
198 }
199 {{/code}}
200
201 See the [[Component Reference documentation>>extensions:Extension.Component Module]] for other details.
202
203 == Deprecated and Retired projects ==
204
205 <description of deprecated and retired projects>
206
207 == Upgrades ==
208
209 The following dependencies have been upgraded:
210
211 * [[JGroups 3.5.1>>http://jira.xwiki.org/browse/XWIKI-10987]]
212 * [[Tika 1.6>>http://jira.xwiki.org/browse/XWIKI-10956]]
213 * [[reflections 0.9.9>>http://jira.xwiki.org/browse/XCOMMONS-654]]
214 * [[Groovy 2.3.7>>http://jira.xwiki.org/browse/XCOMMONS-655]]
215 * [[jQuery 1.11.1>>http://jira.xwiki.org/browse/XWIKI-11094]]
216 * [[Doxia 1.6>>http://jira.xwiki.org/browse/XRENDERING-364]]
217 * [[Joda-Time 2.5>>http://jira.xwiki.org/browse/XRENDERING-365]]
218 * [[commons-compress 1.9>>http://jira.xwiki.org/browse/XCOMMONS-665]]
219
220 == Miscellaneous ==
221
222 * The wiki provisioning job has now the current user set in the context.
223 * 10 new icons have been mapped into [[Font Awesome Icon Theme>>extensions:Extension.Font Awesome Icon Theme]].
224 * 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.
225 * When importing an extension unknown but valid versions are not removed anymore
226
227 = Translations =
228
229 The following translations have been updated:
230
231 {{language codes="none, none"/}}
232
233 = Tested Browsers & Databases =
234
235 {{include reference="TestReports.ManualTestReportXWiki63M1Summary"/}}
236
237 = Known issues =
238
239 * [[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]]
240
241 = Backward Compatibility and Migration Notes =
242
243 == General Notes ==
244
245 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.
246
247 == Issues specific to XWiki <version> ==
248
249 <issues specific to the project>
250
251 == API Breakages ==
252
253 The following APIs were modified since <project> <version - 1>:
254
255 {{code language="none"}}
256 <clirr output here>
257 {{/code}}

Get Connected