<modelVersion>4.0.0</modelVersion>
  <groupId>com.example.group</groupId>
  <artifactId>testvalidpom</artifactId>
  <version>0.0.1-SNAPSHOT</version>

  <description>
    This will test if the module validator recognized that this dependency with classifier
    is not the same as the module itself.
  </description>
  <dependencies>
    <dependency>
      <groupId>com.example.group</groupId>
      <artifactId>testvalidpom</artifactId>

  <modelVersion>4.0.0</modelVersion>
  <groupId>com.example.group</groupId>
  <artifactId>testinvalidpom</artifactId>
  <version>0.0.1-SNAPSHOT</version>

  <description>
    This will test if the module validator recognized that this
    dependency is the same as the module itself.
  </description>
  <dependencies>
    <dependency>
      <groupId>com.example.group</groupId>
      <artifactId>testinvalidpom</artifactId>

pkg os/user, func LookupGroup(string) (*Group, error)
pkg os/user, func LookupGroupId(string) (*Group, error)
pkg os/user, method (*User) GroupIds() ([]string, error)
pkg os/user, method (UnknownGroupError) Error() string
pkg os/user, method (UnknownGroupIdError) Error() string
pkg os/user, type Group struct
pkg os/user, type Group struct, Gid string
pkg os/user, type Group struct, Name string

    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see
    https://groups.google.com/g/google-web-toolkit-contributors/c/CqYH59Dt_rQ/m/uVGW1QdUsXUJ
    for details.

    The summary is that it ignores one file in favor of the other.

그리고 [*경로 처리 데코레이터*에 `dependencies` 추가하기](dependencies-in-path-operation-decorators.md) 섹션의 모든 아이디어는 여전히 적용되지만, 이 경우에는 애플리케이션의 모든 *경로 처리*에 적용됩니다.

## *경로 처리* 그룹에 대한 의존성 { #dependencies-for-groups-of-path-operations }

                            if (rGroup == null) {
                                // relocated dependency artifact is declared excluded, no need to add and recurse
                                // further
                                continue;
                            }

                            child.addDependencies(rGroup.getArtifacts(), rGroup.getResolutionRepositories(), filter);

      <description>Describes a build extension to utilise.</description>
      <version>1.0.0+</version>
      <fields>
        <field>
          <name>groupId</name>
          <description>The group ID of the extension's artifact.</description>
          <version>1.0.0+</version>
          <required>true</required>
          <type>String</type>
        </field>
        <field>
          <name>artifactId</name>

    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see
    https://groups.google.com/g/google-web-toolkit-contributors/c/CqYH59Dt_rQ/m/uVGW1QdUsXUJ
    for details.

    The summary is that it ignores one file in favor of the other.

 */

package jcifs.dcerpc.msrpc;

/**
 * MSRPC implementation for enumerating aliases within a domain.
 * This class provides functionality to enumerate security aliases (local groups)
 * within a SAM domain using the SAMR RPC interface.
 */
public class MsrpcEnumerateAliasesInDomain extends samr.SamrEnumerateAliasesInDomain {

    /**
     * Creates a new request to enumerate aliases in a domain.

 */

package jcifs.smb1.dcerpc.msrpc;

/**
 * MSRPC implementation for enumerating aliases within a domain.
 * This class provides functionality to enumerate security aliases (local groups)
 * within a SAM domain using the SAMR RPC interface.
 */
public class MsrpcEnumerateAliasesInDomain extends samr.SamrEnumerateAliasesInDomain {

    /**
     * Creates a new request to enumerate aliases in a domain.