diff options
author | Robin Stocker <robin@nibor.org> | 2013-01-12 15:20:32 +0100 |
---|---|---|
committer | Matthias Sohn <matthias.sohn@sap.com> | 2013-02-06 08:48:54 +0100 |
commit | 60d538fe5142dc1ce547a77391e4142c4fb8a251 (patch) | |
tree | 1e53171fe47cf4f018acf920c4049870993aecdd /org.eclipse.jgit.packaging/pom.xml | |
parent | 767be14f34b07e5acb8f332032fd97dd3e19a059 (diff) | |
download | jgit-60d538fe5142dc1ce547a77391e4142c4fb8a251.tar.gz jgit-60d538fe5142dc1ce547a77391e4142c4fb8a251.zip |
Add getConflictingNames to RefDatabase
This has the same logic as isNameConflicting, but instead of only
returning a boolean, it returns a collection of names that conflict.
It will be used in EGit to provide a better message to the user when
validating a ref name, see Ibea9984121ae88c488858b8a8e73b593195b15e0.
Existing implementations of isNameConflicting could be rewritten like
this:
return !getConflictingNames(name).isEmpty();
But I'm not sure about that, as isNameConflicting can be implemented in
a faster way than getConflictingNames.
Change-Id: I11e0ba2f300adb8b3612943c304ba68bbe73db8a
Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
Diffstat (limited to 'org.eclipse.jgit.packaging/pom.xml')
0 files changed, 0 insertions, 0 deletions