Jump to: navigation, search

Difference between revisions of "EGit/New and Noteworthy/2.3"

(New page: EGit 2.3 is planned to be released with Juno SR2 on Feb 22, 2013 = EGit Features = * "Fetch from Gerrit..." recognizes Gerrit fetch command copied to clipboard (https://git.eclipse.org/r...)
 
(Added new section on API changes)
(One intermediate revision by the same user not shown)
Line 1: Line 1:
EGit 2.3 is planned to be released with Juno SR2 on Feb 22, 2013
+
EGit 2.3 is planned to be released with Juno SR2 on Feb 22, 2013.
  
 
= EGit Features =
 
= EGit Features =
  
 
* "Fetch from Gerrit..." recognizes Gerrit fetch command copied to clipboard (https://git.eclipse.org/r/#/c/9391)
 
* "Fetch from Gerrit..." recognizes Gerrit fetch command copied to clipboard (https://git.eclipse.org/r/#/c/9391)
 +
* Linked resources are now handled correctly (https://git.eclipse.org/r/#/c/3680/). They are typically ignored unless they point to a resource within the same repository as the containing project. In that case they are decorated according to their git status, and one can operate on them along with regular resources.
 +
 +
= API changes =
 +
 +
* [https://git.eclipse.org/r/#/c/3680/25/org.eclipse.egit.core/src/org/eclipse/egit/core/project/RepositoryFinder.java RepositoryFinder] has now a more concise API for handling linked resources when searching candidate repositories for a project. '''The default search behavior has changed: linked resources are now ignored during the search instead of being traversed'''. Any code that depends on the old default behavior should now use the new find method that also takes a boolean in order to control the traversing of linked resources.
  
 
= Bug Fixes =
 
= Bug Fixes =

Revision as of 07:27, 1 February 2013

EGit 2.3 is planned to be released with Juno SR2 on Feb 22, 2013.

EGit Features

  • "Fetch from Gerrit..." recognizes Gerrit fetch command copied to clipboard (https://git.eclipse.org/r/#/c/9391)
  • Linked resources are now handled correctly (https://git.eclipse.org/r/#/c/3680/). They are typically ignored unless they point to a resource within the same repository as the containing project. In that case they are decorated according to their git status, and one can operate on them along with regular resources.

API changes

  • RepositoryFinder has now a more concise API for handling linked resources when searching candidate repositories for a project. The default search behavior has changed: linked resources are now ignored during the search instead of being traversed. Any code that depends on the old default behavior should now use the new find method that also takes a boolean in order to control the traversing of linked resources.

Bug Fixes

?? Bugs and ?? enhancement requests were closed

Contributors

TBD