From 7e68bb74701692cf131e61606eab31bf9146df72 Mon Sep 17 00:00:00 2001 From: Florian Schmaus Date: Mon, 23 Feb 2015 22:17:31 +0100 Subject: [PATCH] Javadoc fixes in Roster --- .../main/java/org/jivesoftware/smack/roster/Roster.java | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/smack-im/src/main/java/org/jivesoftware/smack/roster/Roster.java b/smack-im/src/main/java/org/jivesoftware/smack/roster/Roster.java index fe22360da..06a63392f 100644 --- a/smack-im/src/main/java/org/jivesoftware/smack/roster/Roster.java +++ b/smack-im/src/main/java/org/jivesoftware/smack/roster/Roster.java @@ -655,8 +655,8 @@ public class Roster extends Manager { /** * Returns the presence info for a particular user. If the user is offline, or * if no presence data is available (such as when you are not subscribed to the - * user's presence updates), unavailable presence will be returned.

- *

+ * user's presence updates), unavailable presence will be returned. + *

* If the user has several presences (one for each resource), then the presence with * highest priority will be returned. If multiple presences have the same priority, * the one with the "most available" presence mode will be returned. In order, @@ -665,7 +665,8 @@ public class Roster extends Manager { * {@link org.jivesoftware.smack.packet.Presence.Mode#away away}, * {@link org.jivesoftware.smack.packet.Presence.Mode#xa extended away}, and * {@link org.jivesoftware.smack.packet.Presence.Mode#dnd do not disturb}.

- *

+ *

+ *

* Note that presence information is received asynchronously. So, just after logging * in to the server, presence values for users in the roster may be unavailable * even if they are actually online. In other words, the value returned by this @@ -673,6 +674,7 @@ public class Roster extends Manager { * other user's presence instant by instant. If you need to track presence over time, * such as when showing a visual representation of the roster, consider using a * {@link RosterListener}. + *

* * @param user an XMPP ID. The address could be in any valid format (e.g. * "domain/resource", "user@domain" or "user@domain/resource"). Any resource