Remove volatile keyword from RepositoryEvent

We don't need this field to be volatile.  Events are delivered by
the same thread that created the RepositoryEvent object, and thus
any cross-thread operations would need to be handled by some other
type of synchronization in the listener, and that would protect
both the repository field and any other per-event data.

Change-Id: Iefe345959e1a2d4669709dbf82962bcc1b8913e3
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
This commit is contained in:
Shawn O. Pearce 2010-06-28 12:46:18 -07:00
parent aa4b06e087
commit 242b4026d9
1 changed files with 1 additions and 1 deletions

View File

@ -53,7 +53,7 @@
* type of listener this event dispatches to.
*/
public abstract class RepositoryEvent<T extends RepositoryListener> {
private volatile Repository repository;
private Repository repository;
/**
* Set the repository this event occurred on.