- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for scenarios (0.22 sec)
-
maven-core/src/test/resources/apiv4-repo/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3-sources.jar
Matcher<String> aNonEmptyString = new CustomMatcher<String>("a non empty string") { * public boolean matches(Object object) { * return ((object instanceof String) && !((String) object).isEmpty(); * } * }; * </pre> * <p> * This class is designed for scenarios where an anonymous inner class * matcher makes sense. It should not be used by API designers implementing * matchers. * * @author Neil Dunn * @see CustomTypeSafeMatche for a type safe variant of this class that you probably * want to use. * @param...
Archive - Registered: Sun Apr 14 03:35:08 GMT 2024 - Last Modified: Sun Oct 02 08:41:25 GMT 2022 - 31.9K bytes - Viewed (0) -
maven-core/src/test/resources/apiv4-repo/commons-logging/commons-logging/1.0.3/commons-logging-1.0.3.jar
steps: Acquire a reference to an instance of org.apache.commons.logging.Log, by calling the factory method LogFactory.getInstance(String name). Your application can contain references to multiple loggers that are used for different purposes. A typical scenario for a server application is to have each major component of the server use its own Log instance. Cause messages to be logged (if the corresponding detail level is enabled) by calling appropriate methods (debug(), info(), warn(), error, and fatal())....
Archive - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Dec 19 19:08:55 GMT 2023 - 30.9K bytes - Viewed (0) -
maven-core/src/test/resources/apiv4-repo/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
steps: Acquire a reference to an instance of org.apache.commons.logging.Log, by calling the factory method LogFactory.getInstance(String name). Your application can contain references to multiple loggers that are used for different purposes. A typical scenario for a server application is to have each major component of the server use its own Log instance. Cause messages to be logged (if the corresponding detail level is enabled) by calling appropriate methods (trace(), debug(), info(), warn(), error, and...
Archive - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Dec 19 19:08:55 GMT 2023 - 37.1K bytes - Viewed (0) -
maven-core/src/test/resources/apiv4-repo/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3-javadoc.jar
matchers. For example: Matcher<String> aNonEmptyString = new CustomMatcher<String>("a non empty string") { public boolean matches(Object object) { return ((object instanceof String) && !((String) object).isEmpty(); } }; This class is designed for scenarios where an anonymous inner class matcher makes sense. It should not be used by API designers implementing matchers. Author: Neil Dunn See Also: for a type safe variant of this class that you probably want to use. Constructor Summary CustomMatcher(java.lang.String...
Archive - Registered: Sun Apr 14 03:35:08 GMT 2024 - Last Modified: Sun Oct 02 08:41:25 GMT 2022 - 236.8K bytes - Viewed (0)