Jump to: navigation, search

Difference between revisions of "Subversive New and Noteworthy"

(5 intermediate revisions by 4 users not shown)
Line 1: Line 1:
'''Also see the New & Noteworthy for:''' [[Subversive New and Noteworthy for Galileo|Galileo]], [[Subversive New and Noteworthy for Helios|Helios]]
+
'''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]]
  
Subversive for Indigo does not have many new features, instead we concentrated on plug-in stability and fixed a lot of different issues piled up in the project development time. Still there are some interesting moments that could benefit your work with SVN.  
+
== 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.  
  
 
== Latest SVN client libraries included  ==
 
== Latest SVN client libraries included  ==
  
Bugs [https://bugs.eclipse.org/bugs/show_bug.cgi?id=326829 326829] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=334452 334452]. 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. Although latest SVN client libraries does not only contain a lots of bug fixes, but also in case of SVN Kit client library there is a way to improve Subversive functionality too: recent SVN Kit version allows creation of an FSFS repositories.  
+
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.  
  
== Repository creation with SVN Kit ==
+
== Win64 platform support ==
  
Bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=333202 333202]. SVN Kit 1.3.5 allows creation of FSFS repositories and so, now this feature could be used not with the native connectors only, but with the pure Java connector too. When you use recent SVN Kit version you have access to the repository creation feature with the FSFS option available:<br>
+
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).
  
[[Image:Svnrepositorycreation.png]]
+
== Plug-in integration API improvements ==
  
== Ignoring incoming changes in the Synchronize View ==
+
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.
  
Bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=297821 297821]. There are times when you just want to reject incoming changes for whatever the reason is. For example when there was quick fix commited for some issue and you have a better solution which does not need any changes in the code which was modified by quick fix. So, what should you do in that case? Is there any other way except making a fake conflict? Well, now there is! Just use 'Mark as merged' action over the unneeded incoming change and you will get your wish granted:
+
== Usability improvements  ==
  
[[Image:Svnrejectchanges.png]]  
+
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).
  
== Use Mylyn-based facilities to report issues and feature requests  ==
+
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.
  
Bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=229495 229495]. There were times when we used our own proprietary bug and feature request reporting facilities and that required placing our menu item in a non-desired place - Help menu. And now we have this feature we integrated with, provided by the Mylyn project:
+
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:Svnreporting.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.
  
 
[[Category:Subversive]]
 
[[Category:Subversive]]

Revision as of 03:46, 19 May 2013

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

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.

Latest SVN client libraries included

Bugs 406738 and 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.

Win64 platform support

Bug 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).

Plug-in integration API improvements

Bugs 306806, 400575 and 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.

Usability improvements

Bug 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).

Bugs 296239 and 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.

Bug 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).

Bug 401612. Also now Subversive strictly follows guidelines on which resource type the property could be set: a file, a folder, both or a revision.