Search Options

Results per page
Sort
Preferred Languages
Advance

Results 171 - 180 of 219 for sintaxe (0.34 sec)

  1. src/main/java/org/codelibs/core/convert/TimeConversionUtil.java

     * </tr>
     * <tr>
     * <td>{@link DateFormat#FULL} format without delimiters</td>
     * <td>{@literal HHmmss z}</td>
     * </tr>
     * <tr>
     * <td>Other</td>
     * <td>{@link Time#valueOf(String) JDBC escape syntax} format</td>
     * <td>{@literal HH:mm:ss}</td>
     * </tr>
     * </table>
     *
     * @author koichik
     * @see DateConversionUtil
     * @see TimestampConversionUtil
     */
    public abstract class TimeConversionUtil {
    
    Registered: Fri Sep 05 20:58:11 UTC 2025
    - Last Modified: Thu Jul 31 08:16:49 UTC 2025
    - 20.3K bytes
    - Viewed (0)
  2. LICENSE

          boilerplate notice, with the fields enclosed by brackets "{}"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Thu Sep 04 15:34:10 UTC 2025
    - Last Modified: Thu Jun 14 07:45:22 UTC 2018
    - 11.1K bytes
    - Viewed (0)
  3. LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Tue Nov 22 19:44:46 UTC 2016
    - 11.1K bytes
    - Viewed (0)
  4. LICENSES/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.3K bytes
    - Viewed (0)
  5. LICENSES/vendor/github.com/NYTimes/gziphandler/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Feb 03 21:57:36 UTC 2021
    - 11.2K bytes
    - Viewed (0)
  6. LICENSES/vendor/github.com/container-storage-interface/spec/LICENSE

          boilerplate notice, with the fields enclosed by brackets "{}"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.3K bytes
    - Viewed (0)
  7. LICENSES/vendor/github.com/coreos/go-semver/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  8. LICENSES/vendor/github.com/google/btree/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  9. LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Fri Sep 05 20:58:11 UTC 2025
    - Last Modified: Fri Apr 18 13:54:00 UTC 2025
    - 11.1K bytes
    - Viewed (0)
  10. apache-maven/src/main/appended-resources/licenses/Apache-2.0.txt

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Sun Sep 07 03:35:12 UTC 2025
    - Last Modified: Tue Jan 28 11:47:17 UTC 2020
    - 11.1K bytes
    - Viewed (0)
Back to top