<
From version < 10.2 >
edited by Sorin Burjan
on 2012/03/14
To version < 10.3 >
edited by Sergiu Dumitriu
on 2012/03/15
>
Change comment: Typos

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Sorin
1 +XWiki.Sergiu
Content
... ... @@ -25,7 +25,7 @@
25 25  
26 26  == Extension Manager moved to commons ==
27 27  
28 -Everything not not specifically related to wiki is now part of xwiki-commons. That means that anyone can get all Extension Manager features (easy live JAR installation/uninstallation from remote repositories, dependency management, etc.) in any Java application.
28 +Everything not specifically related to XWiki is now part of xwiki-commons. That means that anyone can get all Extension Manager features (easy live JAR installation/uninstallation from remote repositories, dependency management, etc.) in any Java application.
29 29  
30 30  == Classloader module moved to commons ==
31 31  
... ... @@ -33,17 +33,17 @@
33 33  
34 34  == New Job module ==
35 35  
36 -The code to execute a task in backgroup and provide related progress and isolated log has been extracted from Extension Manager and is now in its own module.
36 +The code to execute a task in background and provide related progress and isolated log has been extracted from Extension Manager and is now in its own module.
37 37  
38 38  == Component related improvements ==
39 39  
40 40  === Role moved from Class to Type ===
41 41  
42 -In order to support parameterized role like DocumentReferenceResolver<String>, all the APIs of ComponentManager and Component descriptors has been changed to take Type instead of Class. All the old API are still here and working but deprecated.
42 +In order to support parameterized role like DocumentReferenceResolver<String>, all the APIs of ComponentManager and Component descriptors have been changed to take Type instead of Class. All the old APIs are still available and working, but have been deprecated.
43 43  
44 44  === ComponentRole is deprecated ===
45 45  
46 -You should now use @Role instead of @ComponentRole. The difference is that when using @Role the generic parameters will be taken into account as part of the role while with @ComponentRole the role stay the Class of the component role so be careful when you do this change, it might break everything if you don't want to take into account parameters (that's why a new annotation has been introduced instead of changing the behavior of ComponentRole).
46 +You should now use @Role instead of @ComponentRole. The difference is that when using @Role the generic parameters will be taken into account as part of the role while with @ComponentRole the role stays the Class of the component role so be careful when you do this change, it might break everything if you don't want to take into account parameters (that's why a new annotation has been introduced instead of changing the behavior of ComponentRole).
47 47  
48 48  === References resolver/serializer and Provider now support parameter type as part of the role ===
49 49  
... ... @@ -123,7 +123,6 @@
123 123  
124 124  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>>dev:Community.BrowserSupportStrategy]]):
125 125  
126 -
127 127  {{browser name='firefox' version= '10.0.1'/}}
128 128  
129 129  {{browser name='chrome' version= '17'/}}
... ... @@ -145,17 +145,17 @@
145 145  You need to enable database migration (//xwiki.store.migration=1//) to upgrade existing databases to the new identifier format.
146 146  
147 147  {{info}}
148 -This is a major migration affecting almost all rows and relations in the database. I may takes a while before the wiki respond to your initial request when you are migrating a large database. The initial request may even timeout but the database migration continue in the background.
147 +This is a major migration affecting almost all rows and relations in the database. I may takes a while before the wiki respond to your initial request when you are migrating a large database. The initial request may even timeout but the database migration continues in the background.
149 149  {{/info}}
150 150  
151 151  {{warning}}
152 -Avoid to interrupt the database migration process and check the current progress of the database migration in the console output or the log file. The progress may be slow, so be patient during document id and object id conversion.
151 +Avoid interrupting the database migration process, you can check the current progress of the database migration in the console output or the log file. The progress may be slow, so be patient during document id and object id conversion.
153 153  {{/warning}}
154 154  
155 -In case of interruption, the migration procedure could be restarted by restarting XWiki, and it will start over where it have been interrupted.
154 +In case of interruption, the migration procedure could be restarted by restarting XWiki, and it will continue from where it has been interrupted.
156 156  
157 157  {{warning}}
158 -We have taken many precaution to provide a reliable migration procedure, but due to the large changes it made, and this release being an unstable one, you should be really careful and ensure that you keep an appropriate backup until you are sure that your data has been properly migrated.
157 +We have taken many precautions to provide a reliable migration procedure, but due to the large changes it made, and this release being an unstable one, you should be really careful and ensure that you keep an appropriate backup until you are sure that your data has been properly migrated.
159 159  {{/warning}}
160 160  
161 161  If you have custom mapped classes used externally, be aware that all internal identifier are now full 64bits longs.

Get Connected