// do not convert to UTC, because we assume the user intends to encode
		// the date using the specified timezone. A user may want this control
		// because many legacy ZIP readers interpret the timestamp according
		// to the local timezone.
		//
		// The timezone is only non-UTC if a user directly sets the Modified
		// field directly themselves. All other approaches sets UTC.

    String USER_CODE_REQUEST_PARAMETER = "user.code.request.parameter";

    /** The key of the configuration. e.g. 20 */
    String USER_CODE_MIN_LENGTH = "user.code.min.length";

    /** The key of the configuration. e.g. 100 */
    String USER_CODE_MAX_LENGTH = "user.code.max.length";

    /** The key of the configuration. e.g. [a-zA-Z0-9_]+ */
    String USER_CODE_PATTERN = "user.code.pattern";

 * This is not correct as it should do this with the built distribution instead.
 *
 * Doing it correctly would require running a Gradle build with the full
 * distribution and extracting the generated api jar from its Gradle user home,
 * slowing down building documentation.
 *
 * All this would be so much simpler if the Kotlin extensions to the Gradle API
 * were generated at build time instead.
 *

 * {@code long} values. When possible, it is recommended that the {@link UnsignedLong} wrapper class
 * be used, at a small efficiency penalty, to enforce the distinction in the type system.
 *
 * <p>See the Guava User Guide article on <a
 * href="https://github.com/google/guava/wiki/PrimitivesExplained#unsigned-support">unsigned
 * primitive utilities</a>.
 *
 * @author Louis Wasserman
 * @author Brian Milch
 * @author Colin Evans

/**
 * Determines profile activation based on the existence/absence of some file.
 * File name interpolation support is limited to <code>${project.basedir}</code>
 * system properties and user properties.
 *
 * @see ActivationFile
 * @see org.apache.maven.model.validation.DefaultModelValidator#validateRawModel
 * @deprecated use {@link org.apache.maven.api.services.ModelBuilder} instead
 */
@Named("file")

`Form` sınıfıyla tanımlama yaparken `Body`, `Query`, `Path` ve `Cookie` sınıflarında kullandığınız aynı validasyon, örnekler, isimlendirme (örneğin `username` yerine `user-name` kullanımı) ve daha fazla konfigurasyonu kullanabilirsiniz.

/// info | "Bilgi"

`Form` doğrudan `Body` sınıfını miras alan bir sınıftır.

///

/// tip | "İpucu"

 * <li>Settings: the {@code settings.xml} can be used to provide additional repositories in the three level of settings (user, project, installation).</li>
 * </ol>

 * <li>Settings: the {@code settings.xml} can be used to provide additional repositories in the three level of settings (user, project, installation).</li>
 * </ol>

<div class="wrapper">
    <jsp:include page="/WEB-INF/view/common/admin/header.jsp"></jsp:include>
    <jsp:include page="/WEB-INF/view/common/admin/sidebar.jsp">
        <jsp:param name="menuCategoryType" value="user"/>
        <jsp:param name="menuType" value="role"/>
    </jsp:include>
    <div class="content-wrapper">
        <div class="content-header">
            <div class="container-fluid">

labels.general_menu_ldap = LDAP
labels.general_menu_notification = 알림
labels.ldapProviderUrl = LDAP URL
labels.ldapSecurityPrincipal = User DN
labels.ldapAdminSecurityPrincipal = Bind DN
labels.ldapAdminSecurityCredentials = 비밀번호
labels.ldapBaseDn = Base DN
labels.ldap_provider_url = LDAP URL
labels.ldap_security_principal = User DN
labels.ldap_admin_security_principal = Bind DN
labels.ldap_admin_security_credentials = 비밀번호