From bfc43c13bcf65d9ed29a9b1c70a829bcec9c5693 Mon Sep 17 00:00:00 2001 From: "Shawn O. Pearce" Date: Tue, 22 Jun 2010 16:48:37 -0700 Subject: [PATCH] Expose RefUpdate constructor to any subclass When we finally move RefDirectory to the new storage.file package, its associated RefDirectoryUpdate will need visiblity to this constructor in order to initialize itself. This is true of any other repository implementation, so make it protected rather than package level visible. Change-Id: If838aec9baeb80ee2f12dcbca717657c725a9242 Signed-off-by: Shawn O. Pearce --- .../src/org/eclipse/jgit/lib/RefUpdate.java | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/org.eclipse.jgit/src/org/eclipse/jgit/lib/RefUpdate.java b/org.eclipse.jgit/src/org/eclipse/jgit/lib/RefUpdate.java index 89f59150a..e04a587ac 100644 --- a/org.eclipse.jgit/src/org/eclipse/jgit/lib/RefUpdate.java +++ b/org.eclipse.jgit/src/org/eclipse/jgit/lib/RefUpdate.java @@ -167,7 +167,16 @@ public static enum Result { private final Ref ref; - RefUpdate(final Ref ref) { + /** + * Construct a new update operation for the reference. + *

+ * {@code ref.getObjectId()} will be used to seed {@link #getOldObjectId()}, + * which callers can use as part of their own update logic. + * + * @param ref + * the reference that will be updated by this operation. + */ + protected RefUpdate(final Ref ref) { this.ref = ref; oldValue = ref.getObjectId(); refLogMessage = "";