Fix Javadoc errors so the sdk can build.

I unhid some API in a previous install, triggering javadoc processing on
their buggy comments.

Fixing build.
This commit is contained in:
Robert Greenwalt
2010-01-13 11:29:03 -08:00
parent c0ee47ffc5
commit 993d19f923

View File

@@ -129,14 +129,14 @@ public class ConnectivityManager
public static final int TYPE_WIFI = 1; public static final int TYPE_WIFI = 1;
/** /**
* An MMS-specific Mobile data connection. This connection may be the * An MMS-specific Mobile data connection. This connection may be the
* same as {@link #TYPEMOBILE} but it may be different. This is used * same as {@link #TYPE_MOBILE} but it may be different. This is used
* by applications needing to talk to the carrier's Multimedia Messaging * by applications needing to talk to the carrier's Multimedia Messaging
* Service servers. It may coexist with default data connections. * Service servers. It may coexist with default data connections.
*/ */
public static final int TYPE_MOBILE_MMS = 2; public static final int TYPE_MOBILE_MMS = 2;
/** /**
* A SUPL-specific Mobile data connection. This connection may be the * A SUPL-specific Mobile data connection. This connection may be the
* same as {@link #TYPEMOBILE} but it may be different. This is used * same as {@link #TYPE_MOBILE} but it may be different. This is used
* by applications needing to talk to the carrier's Secure User Plane * by applications needing to talk to the carrier's Secure User Plane
* Location servers for help locating the device. It may coexist with * Location servers for help locating the device. It may coexist with
* default data connections. * default data connections.
@@ -144,7 +144,7 @@ public class ConnectivityManager
public static final int TYPE_MOBILE_SUPL = 3; public static final int TYPE_MOBILE_SUPL = 3;
/** /**
* A DUN-specific Mobile data connection. This connection may be the * A DUN-specific Mobile data connection. This connection may be the
* same as {@link #TYPEMOBILE} but it may be different. This is used * same as {@link #TYPE_MOBILE} but it may be different. This is used
* by applicaitons performing a Dial Up Networking bridge so that * by applicaitons performing a Dial Up Networking bridge so that
* the carrier is aware of DUN traffic. It may coexist with default data * the carrier is aware of DUN traffic. It may coexist with default data
* connections. * connections.
@@ -152,7 +152,7 @@ public class ConnectivityManager
public static final int TYPE_MOBILE_DUN = 4; public static final int TYPE_MOBILE_DUN = 4;
/** /**
* A High Priority Mobile data connection. This connection is typically * A High Priority Mobile data connection. This connection is typically
* the same as {@link #TYPEMOBILE} but the routing setup is different. * the same as {@link #TYPE_MOBILE} but the routing setup is different.
* Only requesting processes will have access to the Mobile DNS servers * Only requesting processes will have access to the Mobile DNS servers
* and only IP's explicitly requested via {@link #requestRouteToHost} * and only IP's explicitly requested via {@link #requestRouteToHost}
* will route over this interface if a default route exists. * will route over this interface if a default route exists.