[Subclipse-Announce] Subclipse 1.10.2 Released
Mark Phippard <[email protected]> Tue, 3 Sep 2013 16:32:49 -0400
| Newsgroups | gmane.comp.version-control.subversion.subclipse.user |
|---|---|
| Message-ID | <CAHFaGCoTEnoDYagA6h6oTRbBDjLN-ujVjZp9gXOR3eT=X6g5zg@mail.gmail.com> |
Subclipse 1.10.2 has been released and is available via update site and as a zipped download. Note that this release includes a BETA release of the SVNKit library with support for the Subversion 1.8.0 working copy format. It also includes the latest Subversion 1.8.3 release of JavaHL. Just a note that only the update site includes the SVNKit library. It is not currently available in the zipped download. Here is the changelog for this release: Version 1.10.2 Sept 3, 2013 from: /trunk http://subclipse.tigris.org/svn/subclipse/tags/subclipse/1.10.2 - Update JavaHL to SVN 1.8.3 - SVNKit 1.8.0-Beta - Fix RevisionRange passed to merge API so that it will correctly determine type of merge to run. (1544<http://subclipse.tigris.org/issues/show_bug.cgi?id=1544> ) - Don't log an error when trying to get info for an unversioned folder. ( 1538 <http://subclipse.tigris.org/issues/show_bug.cgi?id=1538>) - Fix SVNMoveDeleteHook so that it does not interfere with moving a file or folder to a project that is not under version control. (1536<http://subclipse.tigris.org/issues/show_bug.cgi?id=1536> ) - Null proof CleanupResourcesCommand. (1535<http://subclipse.tigris.org/issues/show_bug.cgi?id=1535> ) - Fix potential NPE in history view when log entry containing a bug id is selected (with certain bugtraq:logregex patterns). (1539<http://subclipse.tigris.org/issues/show_bug.cgi?id=1539> ) - Don't show multiple prompts when files from multiple projects added to svn:ignore from sync view. (1543<http://subclipse.tigris.org/issues/show_bug.cgi?id=1543> ) -- Thanks Mark Phippard http://markphip.blogspot.com/ ------------------------------------------------------ http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=3063857 To unsubscribe from this discussion, e-mail: [[email protected]].