종속성

The dependencies attribute in the project manifest is a JSON object that maps a package name to a version. The version number indicates which version of the package to download from the package registry. For example:

{
  "dependencies": {
    "com.my-package": "2.3.1",
    "com.my-other-package": "1.0.1-preview.1",
       etc.
  }
}

In addition to using version numbers, the Package Manager also supports adding project dependencies with the following:

• 내장 종속성
• 로컬 경로
• Git URL

직접 및 간접 종속성

A direct dependency is a project-level dependency. When you install a package through the Package Manager window, or manually edit the project manifest.json file to explicitly add a dependency, you are creating a direct package dependency ():

Packages can declare their own dependencies to other packages. Such package dependencies become indirect (), or transitive, dependencies of your project when you install the package.

The Package Manager determines which version of each package to install, no matter how it becomes a dependency of your project. To do this, it prioritizes direct dependencies over indirect dependencies, as long as the higher priority version doesn’t violate any other requirements.

이러한 평가를 종속성 해결이라고 하며 다음의 논리를 따릅니다.

1. 직접 종속성의 버전을 선택합니다.
2. 직접 종속성이 없고 빌트인 패키지 버전인 경우 빌트인 버전을 선택합니다.
3. 직접 종속성이 없고 빌트인 버전이 아닌 경우 두 개 이상 패키지의 간접 종속성인지 확인합니다.
   • If this is an indirect dependency of only one package in the project, there is no conflict, so select the higher of these versions:
     • 이 간접 종속성의 버전
     • Unity에서 요구하는 최소 버전
   • 여러 개의 간접 종속성이 있는 경우 간접 종속성이 두 개 이상의 버전을 요청하면 충돌이 발생할 수 있습니다. 패키지 관리자는 자동 충돌 해결 전략을 통해 대부분의 충돌을 해결합니다.

In any case, you can manually override these resolution strategies. To do this, request a specific version in the project manifest (either by installing from the Package Manager window or by editing the manifest directly). This creates a direct dependency, which takes precedence over any resolution strategy.