Jump to: navigation, search

Difference between revisions of "Subversive New and Noteworthy"

 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''Also see the New & Noteworthy for:''' [[Subversive New and Noteworthy for Juno|Juno]], [[Subversive New and Noteworthy for Indigo|Indigo]], [[Subversive New and Noteworthy for Helios|Helios]], [[Subversive New and Noteworthy for Galileo|Galileo]]
+
'''Also see the New & Noteworthy for:''' [[Subversive New and Noteworthy for Mars|Mars]], [[Subversive New and Noteworthy for Luna|Luna]], [[Subversive New and Noteworthy for Kepler|Kepler]], [[Subversive New and Noteworthy for Juno|Juno]], [[Subversive New and Noteworthy for Indigo|Indigo]], [[Subversive New and Noteworthy for Helios|Helios]], [[Subversive New and Noteworthy for Galileo|Galileo]]
  
 
== Introduction  ==
 
== Introduction  ==
  
This release's main goal was plug-in stability improvement and we've fixed more than 60 different issues. On the other hand we've implemented a set of features that should benefit those who uses SVN in their everyday work and those who uses Subversive plug-in in their products.  
+
Main target of this release is performance optimization and introduction of SVN 1.9 support.
  
== Latest SVN client libraries included ==
+
== SVN 1.9 support ==
 +
   
 +
All the changes in SVN API that aren't regarded as experimental ones were reflected in SVN integration API. These changes are covered by the following tasks: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=488472 488472], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=485022 485022], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=488453 488453], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=487220 487220] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=487147 487147]. For the exact details please check the following section.
  
Bugs [https://bugs.eclipse.org/bugs/show_bug.cgi?id=406738 406738] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=406737 406737]. There were many issues fixed recently in the SVN support libraries and so, it's reasonable to update Subversive SVN Connectors with the most recent ones.
+
== Rework of SVN integration API  ==
  
== Win64 platform support  ==
+
The following API calls were added:
 +
* setConfigurationEventHandler() - set an event handler that will be called every time the configuration is loaded by this client object
 +
* getConfigurationEventHandler() - returns a reference to the installed configuration event handler
 +
* vacuum() - recursively vacuum a working copy, removing unnecessary data, including unversioned, externals, unused pristines, ignored and fixing time stamps
 +
The following API calls now accept additional behaviour switches:
 +
* status()
 +
* merge()
 +
* mergeTwo()
 +
* exportTo()
 +
* copyLocal()
 +
The following API calls signatures were changed:
 +
* revert()
 +
* cleanup()
 +
* getInfo()
 +
* streamFileContent()
 +
* copyLocal()
 +
* copyRemote()
 +
* annotate()
 +
The following previously deprecated API calls were removed:
 +
* mergeStatus()
 +
* merge() - the ones that were a counterpart to mergeStatus()
 +
Those modifications had no actual impact on the high-level command framework API.
  
Bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=376317 376317]. While installing JavaHL 64-binaries is easy enough task on unix-platform, that is not so for Win64 platform. Now there is a way to install them from the connectors update site or use those of the another distribution (SlikSVN, for example).
+
== Latest SVN client libraries included ==
  
== Plug-in integration API improvements ==
+
Bugs [https://bugs.eclipse.org/bugs/show_bug.cgi?id=485024 485024], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=485025 485025], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=480040 480040], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=480039 480039] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=487147 487147]. SVN Kit 1.8.12 supports SVN 1.9 working copy. While the native clients provide full-featured support for SVN 1.9.
  
Bugs [https://bugs.eclipse.org/bugs/show_bug.cgi?id=306806 306806],  [https://bugs.eclipse.org/bugs/show_bug.cgi?id=400575 400575] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=389933 389933]. There were important issues that needed our attention in order to simplify integrating our plug-in into other tools. That's why we've made improvements in the plug-in's integration API. Now there is a an extension point for declaring custom properties, post-commit hook's messages processing API, and the way to flexibly override SVN Core plug-in's configuration options provided by SVN UI or any other plug-in.
+
== Changes in extension points ==
  
== Usability improvements  ==
+
* The IOptionProvider interface was changed so that it allows to add configuration options in the future in a way which won't lead to new API changes. All the options now are provided in a uniform way, using the following methods:
 +
** get() - returns the option's value by its name
 +
** getString() - returns the option's value which is of the String type (basically it is a wrapper to the "get" call)
 +
** has() - returns true if the option is set at all
 +
** is() - returns true if the option is set to true (basically it is a wrapper to the "get" call)
 +
* The ICommitActionFactory interface now allows integrations to completely manage the comment editor control and so, now it contains few more methods:
 +
** initCommentManager() - called upon the CommentComposite initialization
 +
** confirmMessage() - called each time "Ok" button is pressed
 +
** cancelMessage() - called each time "Cancel" button is pressed
 +
* The IModifiableCommentDialogPanel interface is now marked as deprecated, since its functions were completely overtook by the more functional ICommentManager interface.
  
Bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=390467 390467]. We've implemented a human-readable numeric ordering of branches' and tags' names which allows to sort them naturally (1.1 -> 1.2 -> ... -> 1.10 instead of 1.1 -> 1.10 -> 1.2 -> ...) in difference to previously used string-based comparision (special thanks to Claudio Weiler and Jörg Thönnes).
+
== Usability improvements ==
  
Bugs [https://bugs.eclipse.org/bugs/show_bug.cgi?id=296239 296239] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=370254 370254]. There are some changes to clear misunderstandings on how the resource selection button works in Add/Commit/Replace dialogs, also there is an improvement with the default start and stop revisions of the SVN Annotate function.
+
There were request for new features by community which were solved in this version.
 +
Now there is a way to specify a default checkout location which may differ from the workspace location:
  
Bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=354843 354843]. SVN 1.7 API allows to handle post-commit hook's meassages nicely, so now Subversive will display a message, returned by post-commit hook (special thanks to Martin Kutter).
+
[[Image:Svn-project-structure.png]]
  
Bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=401612 401612]. Also now Subversive strictly follows guidelines on which resource type the property could be set: a file, a folder, both or a revision.
+
This allows you not to select the location manually each time you perform a checkout, in case you do not want to use the workspace location due to some reasons. Also the corresponding path selection control of the Checkout As wizard location page from now on will be enabled by default in order to lessen the amount of the actions required to change the location.
 +
 
 +
[[Image:Svn-checkout-as-location-page.png]]
 +
 
 +
Previously plug-in always ignored derived resources. But it seems sometimes it is useful to place them under source control. So, now we have the option to alter the behaviour:
 +
 
 +
[[Image:Svn-commit-options.png]]
 +
 
 +
Also, support form SVN 1.7-1.9 diff options was introduced into the "Create Patch" wizard:
 +
 
 +
[[Image:Svn-diff-options.png]]
 +
 
 +
== Performance ==
 +
 
 +
Thanks to the community people's help, there were some major performance improvements including both: CPU and memory usage reduction. For details please check the bugs [https://bugs.eclipse.org/bugs/show_bug.cgi?id=489143 489143] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=489649 489649].  
  
 
[[Category:Subversive]]
 
[[Category:Subversive]]

Latest revision as of 13:26, 5 April 2016

Also see the New & Noteworthy for: Mars, Luna, Kepler, Juno, Indigo, Helios, Galileo

Introduction

Main target of this release is performance optimization and introduction of SVN 1.9 support.

SVN 1.9 support

All the changes in SVN API that aren't regarded as experimental ones were reflected in SVN integration API. These changes are covered by the following tasks: 488472, 485022, 488453, 487220 and 487147. For the exact details please check the following section.

Rework of SVN integration API

The following API calls were added:

  • setConfigurationEventHandler() - set an event handler that will be called every time the configuration is loaded by this client object
  • getConfigurationEventHandler() - returns a reference to the installed configuration event handler
  • vacuum() - recursively vacuum a working copy, removing unnecessary data, including unversioned, externals, unused pristines, ignored and fixing time stamps

The following API calls now accept additional behaviour switches:

  • status()
  • merge()
  • mergeTwo()
  • exportTo()
  • copyLocal()

The following API calls signatures were changed:

  • revert()
  • cleanup()
  • getInfo()
  • streamFileContent()
  • copyLocal()
  • copyRemote()
  • annotate()

The following previously deprecated API calls were removed:

  • mergeStatus()
  • merge() - the ones that were a counterpart to mergeStatus()

Those modifications had no actual impact on the high-level command framework API.

Latest SVN client libraries included

Bugs 485024, 485025, 480040, 480039 and 487147. SVN Kit 1.8.12 supports SVN 1.9 working copy. While the native clients provide full-featured support for SVN 1.9.

Changes in extension points

  • The IOptionProvider interface was changed so that it allows to add configuration options in the future in a way which won't lead to new API changes. All the options now are provided in a uniform way, using the following methods:
    • get() - returns the option's value by its name
    • getString() - returns the option's value which is of the String type (basically it is a wrapper to the "get" call)
    • has() - returns true if the option is set at all
    • is() - returns true if the option is set to true (basically it is a wrapper to the "get" call)
  • The ICommitActionFactory interface now allows integrations to completely manage the comment editor control and so, now it contains few more methods:
    • initCommentManager() - called upon the CommentComposite initialization
    • confirmMessage() - called each time "Ok" button is pressed
    • cancelMessage() - called each time "Cancel" button is pressed
  • The IModifiableCommentDialogPanel interface is now marked as deprecated, since its functions were completely overtook by the more functional ICommentManager interface.

Usability improvements

There were request for new features by community which were solved in this version. Now there is a way to specify a default checkout location which may differ from the workspace location:

Svn-project-structure.png

This allows you not to select the location manually each time you perform a checkout, in case you do not want to use the workspace location due to some reasons. Also the corresponding path selection control of the Checkout As wizard location page from now on will be enabled by default in order to lessen the amount of the actions required to change the location.

Svn-checkout-as-location-page.png

Previously plug-in always ignored derived resources. But it seems sometimes it is useful to place them under source control. So, now we have the option to alter the behaviour:

Svn-commit-options.png

Also, support form SVN 1.7-1.9 diff options was introduced into the "Create Patch" wizard:

Svn-diff-options.png

Performance

Thanks to the community people's help, there were some major performance improvements including both: CPU and memory usage reduction. For details please check the bugs 489143 and 489649.