Ivy Chinese Reference Document (2)-terminology

Many of the terms used in Ivy were defined as follows:

* Organisation/organization

* Module/Modules

* Module Descriptor/Modular Descriptor

* Artifact/Products

* Type of an artifact/product types

* Artifact file name extension/product name extension

* Module Revision/Modular Revision

* Branch/Branch

* Status of a revision/revised state

* Configurations of a module/module configuration

* Ivy Settings/ivy Set

* Repository/Warehouse

I. Overview

The following illustration shows all the key terms:

Http://ant.apache.org/ivy/history/2.1.0-rc1/images/ivy-terminology.png

Two. Organisation/organization

An organization can be a company, an individual, or just a group of people who develop software. In principle, ivy deals with only a single level of organization, which means they have a flat namespace in the Ivy module descriptor. Therefore, if you use a hierarchical naming convention, the Ivy descriptor can only describe the tree organization structure. The organization name is used to align the software produced by the same team, just to help locate their release.

Works.

The inverted domain name is usually used in ivy as the name of the organization, because the domain name is unique. Companies with domain name www.example.com can use Com.example, or if they have multiple teams, their organization name can begin with Com.example (for example, Com.example.rd, Com.example.infra, com.example.services). The organization name is not mandatory if the domain name is reversed or globally unique, but the only name is highly recommended. The owner of a widely recognized trademark or business name may choose to use their trademark name. such as Org.apache, IBM, Jayasoft

Notice that Ivy's "organization" is very similar to the "GroupId" in the Maven POM.