Project deployment method and system based on Maven dependency management and computer equipment

Abstract

The invention provides a project deployment method based on Maven dependency management. The project deployment method comprises the following steps: a dependency management structure construction step: creating a project private library directory, constructing a core parent module and a plurality of sub-modules under the project private library directory, constructing a hierarchical relationship between the core parent module and the sub-modules, and completing construction of a project dependency management structure; a configuration dependency management step: configuring project dependency management based on the project dependency management structure, and hierarchically introducing and only introducing the dependency of the previous level; and an encryption packaging and pom cleaning step: performing encryption packaging on the project and performing pom file cleaning.

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and in particular to a project deployment method, system and computer equipment based on Maven dependency management. Background Art

[0002] In the field of software development, project management and dependency management are key links to ensure the smooth progress of the project. Maven, as a widely used project management and build automation tool in the Java ecosystem, manages project builds, reports, and dependencies through its core file, the pom file, which is the project object model file. The pom file lists in detail the names and versions of all external libraries required for the project, making project builds and dependency management simple and efficient. However, with the increasing complexity of software projects and the improvement of security requirements, the existing Maven dependency management method exposes some problems that need to be solved:

[0003] In traditional Maven project management, all jar package dependency information is written directly in the pom file, and the project's dependencies are visible to all developers. This transparency is necessary in team collaboration, but it also brings security risks. If the project's pom file is obtained by an unauthorized third party, the third party can easily learn the specific libraries and versions that the project depends on, and may launch attacks against these dependencies. Existing encryption solutions for the above problems can often only encrypt the pom file itself, but cannot prevent experienced attackers from obtaining dependency information through decompilation. Once the pom file is cracked, the project's dependencies will be completely exposed, increasing the risk of the project being attacked.

[0004] Therefore, in large enterprises or organizations, dependency management of key projects often requires limiting access to and modification of pom files to only a few key personnel. The existing Maven management method lacks support for such fine-grained access control, which makes it easy for key dependency information to be improperly accessed or leaked.

[0005] Therefore, there is an urgent need to develop a project deployment method based on Maven dependency management that maintains the convenience of Maven dependency management while enhancing the security of the project, especially the protection of dependency information. Summary of the invention

[0006] The present invention provides a project deployment method, system and computer equipment based on Maven dependency management, so as to at least solve the dependency information leakage and security risk problems existing in traditional Maven project management.

[0007] The present invention provides a project deployment method based on Maven dependency management, comprising:

[0008] Steps for building a dependency management structure: creating a project private library directory, building a core parent module and multiple sub-modules under the project private library directory, building a hierarchical relationship between the core parent module and the sub-modules, and completing the construction of the project dependency management structure;

[0009] Configure dependency management step: configure project dependency management based on the project dependency management structure, and introduce dependencies in layers and only introduce dependencies of the previous layer;

[0010] Encryption packaging and pom cleaning steps: Encrypt the project and clean up the pom file.

[0011] Furthermore, the step of building a dependency management structure includes:

[0012] Create a project private library directory;

[0013] Constructing a third-party library dependency management submodule and a second-party library dependency management submodule under the private library directory;

[0014] Build the core parent module under the private library directory, and introduce the third-party library dependency management submodule and the second-party library dependency management submodule;

[0015] Under the directory of the core parent module, multiple public dependency management submodules are constructed.

[0016] Furthermore, the common dependency management submodule includes: a presentation layer dependency management submodule, a business layer dependency management submodule, a data layer dependency management submodule, and an external layer dependency management submodule.

[0017] Furthermore, the configuration dependency management and inheritance steps include:

[0018] Create a project working directory;

[0019] Create a project working root module in the project working directory and introduce the dependency configuration of the core parent module;

[0020] In the project working directory, create a presentation layer submodule, a business layer submodule, a data layer submodule and an external layer submodule, and introduce the dependency configuration of the presentation layer dependency management submodule, the dependency configuration of the business layer dependency management submodule, the dependency configuration of the data layer dependency management submodule and the dependency configuration of the external layer dependency management submodule respectively.

[0021] Furthermore, the encryption packaging and pom cleaning steps include: encrypting and packaging the project based on the AES algorithm, and configuring exclusion rules in the build script to exclude the pom file from the packaging file.

[0022] The present invention provides a project deployment system based on Maven dependency management, and the project deployment system based on Maven dependency management is applied, including:

[0023] Steps for building a dependency management structure: creating a project private library directory, building a core parent module and multiple sub-modules under the project private library directory, building a hierarchical relationship between the core parent module and the sub-modules, and completing the construction of the project dependency management structure;

[0024] Configure dependency management step: configure project dependency management based on the project dependency management structure, and introduce dependencies in layers and only introduce dependencies of the previous layer;

[0025] Encryption packaging and pom cleaning steps: Encrypt the project and clean up the pom file.

[0026] Furthermore, the building dependency management structure module includes:

[0027] Create a project private library directory;

[0028] Constructing a third-party library dependency management submodule and a second-party library dependency management submodule under the private library directory;

[0029] Build the core parent module under the private library directory, and introduce the third-party library dependency management submodule and the second-party library dependency management submodule;

[0030] Under the directory of the core parent module, multiple public dependency management submodules are constructed.

[0031] Furthermore, the common dependency management submodule includes: a presentation layer dependency management submodule, a business layer dependency management submodule, a data layer dependency management submodule, and an external layer dependency management submodule.

[0032] The present invention provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned project deployment method based on Maven dependency management when executing the computer program.

[0033] The present invention provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the project deployment method based on Maven dependency management as described above is implemented.

[0034] Compared with the prior art, the advantages and positive effects of the present invention are:

[0035] The present invention effectively reduces the security risk caused by the leakage of dependency information by limiting the management of dependency information to the core team of the project. Only a few key personnel can access and modify the dependency information, thereby reducing the possibility of the project being subjected to targeted attacks.

[0036] The present invention realizes fine-grained access control to dependency information by constructing a dependency management hierarchy. This control mechanism ensures that only authorized developers can access specific dependency information, thereby enhancing the confidentiality of the project. At the same time, by configuring exclusion rules in the build script, the present invention can remove pom files during the packaging process, thereby avoiding the exposure of dependency information in the deployment package, and further protecting the security of the project.

[0037] In addition, the present invention combines the encryption packaging technology of the AES algorithm to encrypt the JAR file generated by the project. Even if an attacker obtains the deployment package, he cannot easily obtain the source code and dependency information of the project through decompilation. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 This is a schematic diagram of the project deployment method based on Maven dependency management of the present invention;

[0039] Figure 2 A schematic diagram of a dependency management structure of an embodiment of a project deployment method based on Maven dependency management according to the present invention;

[0040] Figure 3 A schematic diagram of dependency management configuration of an embodiment of a project deployment method based on Maven dependency management of the present invention;

[0041] Figure 4 This is a schematic diagram of the project deployment system structure based on Maven dependency management of the present invention;

[0042] Figure 5 A framework diagram of an electronic device according to an embodiment of the present invention.

[0043] In the above picture:

[0044] 100. Build dependency management structure module; 200. Configure dependency management module; 300. Encryption packaging and pom cleaning module; 80. Bus; 81. Processor; 82. Memory; 83. Communication interface. DETAILED DESCRIPTION

[0045] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0046] In the description of the present application, it should be understood that the terms "center", "up", "down", "front", "back", "left", "right", "vertical", "liquid level", "top", "bottom", "inside", "outside" and the like indicate positions or positional relationships based on the positions or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present application and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present application. The terms "first" and "second" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the present application, unless otherwise specified, "multiple" means two or more.

[0047] In the description of this application, it should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0048] Embodiment 1:

[0049] Please refer to Figure 1 , Figure 1 The following is a flow chart of the project deployment method based on Maven dependency management in the present invention. Figure 1 As shown, the present invention provides a project deployment method based on Maven dependency management, comprising:

[0050] Step S100 of building a dependency management structure: creating a project private library directory, building a core parent module and multiple sub-modules under the project private library directory, building a hierarchical relationship between the core parent module and the sub-modules, and completing the construction of the project dependency management structure;

[0051] Configure dependency management step S200: configure project dependency management based on the project dependency management structure, and introduce dependencies in layers and only introduce dependencies of the previous layer;

[0052] Encryption packaging and pom cleaning step S300: encrypt and package the project and clean up the pom file.

[0053] Preferably, the step S100 of building a dependency management structure includes:

[0054] Create a project private library directory;

[0055] Build the third-party library dependency management submodule and the second-party library dependency management submodule in the private library directory;

[0056] Build the core parent module in the private library directory, and introduce the third-party library dependency management submodule and the second-party library dependency management submodule;

[0057] Under the directory of the core parent module, build multiple public dependency management submodules.

[0058] Preferably, the public dependency management submodule includes: a presentation layer dependency management submodule, a business layer dependency management submodule, a data layer dependency management submodule, and an external layer dependency management submodule.

[0059] Please refer to Figure 2 , Figure 2 Schematic diagram of dependency management structure of the project deployment method embodiment based on Maven dependency management of the present invention. Figure 2 As shown, in some embodiments, the steps of building a dependency management structure are specifically as follows:

[0060] Create a gosci-nexus directory, which is a private library directory. It will be used as the basic configuration of the private server and used to deploy the project to the Nexus private server later. Nexus private server is a powerful warehouse manager that can store and manage binary files and dependencies of the project;

[0061] In the gosci-nexus directory, build a submodule named gosci-dependencies to manage the dependencies of all third-party libraries. This submodule is the third-party library dependency management submodule, which contains common and unique third-party library dependencies, as well as the versions and names of the dependencies;

[0062] In the gosci-nexus directory, build a submodule named gosci-bom. This submodule is the second-party library dependency management submodule, which is used to manage second-party library dependencies, that is, the dependency version management of internal enterprise services. This submodule also includes jar packaging encryption dependencies to ensure the security of dependencies;

[0063] In the gosci-nexus directory, build a parent module named gosci-parent, which serves as the core parent module of the project. Introduce the gosci-dependencies submodule and the gosci-bom submodule under the gosci-parent parent module, including the versions and names of the two submodules;

[0064] Under the gosci-parent parent module, build multiple public dependency management submodules, including:

[0065] Add submodule gosci-parent-controller: Under gosci-parent, build a submodule named gosci-parent-controller, which is dedicated to managing the public dependencies of the presentation layer and only contains the names of the dependencies;

[0066] Add submodule gosci-parent-service: Under gosci-parent, build the gosci-parent-service submodule to manage the public dependencies of the business layer. It also only contains the name of the dependency.

[0067] Add submodule gosci-parent-mapper: Under gosci-parent, build the gosci-parent-mapper submodule to manage the public dependencies of the data layer, which only contains the name of the dependency;

[0068] Add submodule gosci-parent-api: Under gosci-parent, build the gosci-parent-api submodule to manage public dependencies on the external layer, which only contains the name of the dependency;

[0069] Finally, deploy gosci-nexus as a whole to the Nexus private server to complete the project deployment, so that all dependencies and modules can be managed and accessed in the private server, while maintaining the security of the project and the consistency of dependencies.

[0070] Preferably, the configuration dependency management and inheritance step S200 includes:

[0071] Create a project working directory;

[0072] Create a project working root module in the project working directory and introduce the dependency configuration of the core parent module;

[0073] In the project working directory, create the presentation layer submodule, business layer submodule, data layer submodule and external layer submodule, and introduce the dependency configuration of the presentation layer dependency management submodule, the business layer dependency management submodule, the data layer dependency management submodule and the external layer dependency management submodule respectively.

[0074] Please refer to Figure 3 , Figure 3 FIG. 1 is a schematic diagram of dependency management configuration for an embodiment of a project deployment method based on Maven dependency management according to the present invention. Figure 3 As shown, in some embodiments, the configuration dependency management and inheritance steps are specifically as follows:

[0075] Create a project working directory;

[0076] Create a project working root module in the project working directory, introduce the dependencies of the gosci-parent module, including the version and name, to ensure that the pom file in the project root directory does not contain specific dependency details and only inherits the dependency management of the parent module;

[0077] Create a presentation layer submodule in the project working directory and only import the version and name of gosci-parent-controller, which helps limit the dependency management of the presentation layer to the minimum necessary scope;

[0078] Create a business layer submodule in the project working directory and only import the version and name of gosci-parent-service;

[0079] Create a data layer submodule in the project working directory and only import the version and name of gosci-parent-mapper. This helps with dependency management of the data access layer and ensures that only necessary dependencies are imported.

[0080] Create a foreign submodule in your project working directory and import only the version and name of gosci-parent-api. This helps manage dependencies for interacting with external systems.

[0081] By building and configuring the above dependency management hierarchy structure, the pom files referenced in the project are only in the hands of a few people in the enterprise. General developers can only use them for reference and cannot know the specific jar package dependency names and versions referenced in the pom file, thereby reducing the risk of exposing the jar package dependency names and versions referenced in the project.

[0082] Preferably, the encryption packaging and pom cleaning step S300 includes: encrypting and packaging the project based on the AES algorithm, and configuring exclusion rules in the build script to exclude the pom file from the packaging file.

[0083] In some embodiments, after the project is developed, the project is encrypted and packaged using the Advanced Encryption Standard (AES) algorithm. AES is a widely used symmetric key encryption algorithm that is considered to be very secure. Through AES encryption, the JAR or WAR file of the project is encrypted, making it difficult for unauthorized third parties to obtain the source code and sensitive information of the project through decompilation.

[0084] In some embodiments, exclude rules are configured in the Maven build script (usually the pom.xml file) to ensure that the pom.xml file is not included in the final deployment package during the packaging process. This can be done by setting the pom.xml <build>Partial use <excludes>Tags to achieve, for example:

[0085] xml

[0086] <build>

[0087] <plugins>

[0088] <plugin>

[0089] <artifactid> maven-jar-plugin< / artifactid>

[0090] <configuration>

[0091] <excludes>

[0092] <exclude> ** / pom.xml< / exclude>

[0093] < / excludes>

[0094] < / configuration>

[0095] < / plugin>

[0096] < / plugins>

[0097] < / build>

[0098] This configuration ensures that the pom file will not be packaged into the final JAR or WAR file, thereby reducing the risk of leaking build configuration information.

[0099] After completing the above steps, you can deploy the project. Before the project is deployed, you must complete the deployment and testing in the test environment to ensure the stability and reliability of the project in the production environment.

[0100] Embodiment 2:

[0101] Please refer to Figure 4 , Figure 4 This is a schematic diagram of the project deployment system structure based on Maven dependency management in the present invention. Figure 4 As shown, the present invention provides a project deployment system based on Maven dependency management, comprising:

[0102] Build dependency management structure module 100: create a project private library directory, build a core parent module and multiple sub-modules under the project private library directory, build a hierarchical relationship between the core parent module and the sub-modules, and complete the construction of the project dependency management structure;

[0103] Configuration dependency management module 200: configure project dependency management based on the project dependency management structure, hierarchically introduce and only introduce dependencies of the previous level;

[0104] Encryption packaging and pom cleaning module 300: encrypts and packages the project and cleans up the pom file.

[0105] In some embodiments, building the dependency management structure module 100 includes:

[0106] Create a project private library directory;

[0107] Build the third-party library dependency management submodule and the second-party library dependency management submodule in the private library directory;

[0108] Build the core parent module in the private library directory, and introduce the third-party library dependency management submodule and the second-party library dependency management submodule;

[0109] Under the directory of the core parent module, build multiple public dependency management submodules.

[0110] In some embodiments, the public dependency management submodule includes: a presentation layer dependency management submodule, a business layer dependency management submodule, a data layer dependency management submodule, and an external layer dependency management submodule.

[0111] Embodiment three:

[0112] Combination Figure 5 As shown, this embodiment discloses a specific implementation of an electronic device. The electronic device may include a processor 81 and a memory 82 storing computer program instructions.

[0113] Specifically, the processor 81 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0114] Among them, the memory 82 may include a large-capacity memory for data or instructions. By way of example and not limitation, the memory 82 may include a hard disk drive (HDD), a floppy disk drive, a solid-state drive (SSD), a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these. Where appropriate, the memory 82 may include a removable or non-removable (or fixed) medium. Where appropriate, the memory 82 may be inside or outside the data processing device. In a specific embodiment, the memory 82 is a non-volatile memory. In a specific embodiment, the memory 82 includes a read-only memory (ROM) and a random access memory (RAM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (Programmable Read-Only Memory, PROM for short), an erasable PROM (Erasable ProgrammableRead-Only Memory, EPROM for short), an electrically erasable PROM (Electrically Erasable ProgrammableRead-Only Memory, EEPROM for short), an electrically alterable ROM (Electrically Alterable Read-Only Memory, EAROM for short) or a flash memory (FLASH) or a combination of two or more of these. Under appropriate circumstances, the RAM can be a static random access memory (SRAM) or a dynamic random access memory (DRAM), wherein the DRAM can be a fast page mode dynamic random access memory (FPMDRAM), an extended data output dynamic random access memory (EDODRAM), a synchronous dynamic random access memory (SDRAM), etc.

[0115] The memory 82 may be used to store or cache various data files required for processing and / or communication, as well as possible computer program instructions executed by the processor 81 .

[0116] The processor 81 reads and executes computer program instructions stored in the memory 82 to implement any one of the navigation route acquisition methods for the sidebar in the above embodiments.

[0117] In some of the embodiments, the electronic device may further include a communication interface 83 and a bus 80. Figure 5 As shown, the processor 81, the memory 82, and the communication interface 83 are connected via a bus 80 and communicate with each other.

[0118] The communication interface 83 is used to realize the communication between each module, device, unit and / or device in the embodiment of the present application. The communication interface 83 can also realize data communication with other components such as: external devices, image / data acquisition equipment, databases, external storage, and image / data processing workstations. The bus 80 includes hardware, software, or both, and couples the components of the electronic device to each other. The bus 80 includes, but is not limited to, at least one of the following: data bus (Data Bus), address bus (Address Bus), control bus (Control Bus), expansion bus (Expansion Bus), local bus (Local Bus). By way of example and not limitation, bus 80 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses or a combination of two or more of the above. Where appropriate, bus 80 may include one or more buses. Although embodiments of the present application describe and illustrate a particular bus, the present application contemplates any suitable bus or interconnect.

[0119] The electronic device can obtain the navigation route based on the sidebar, thereby realizing the combination Figure 1 Describe the method.

[0120] In addition, in combination with the navigation route acquisition method for the sidebar in the above embodiment, the embodiment of the present application can provide a computer-readable storage medium for implementation. The computer-readable storage medium stores computer program instructions; when the computer program instructions are executed by the processor, any one of the navigation route acquisition methods for the sidebar in the above embodiment is implemented.

[0121] The technical features of the above-described embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0122] The above description is only a preferred embodiment of the present invention and does not limit the present invention in other forms. Any technician familiar with the profession may use the technical content disclosed above to change or modify it into an equivalent embodiment with equivalent changes and apply it to other fields. However, any simple modification, equivalent change and modification made to the above embodiment based on the technical essence of the present invention without departing from the content of the technical solution of the present invention still falls within the protection scope of the technical solution of the present invention.< / excludes> < / build>

Claims

1. A project deployment method based on Maven dependency management, characterized in that: include: Steps for building a dependency management structure: creating a project private library directory, building a core parent module and multiple sub-modules under the project private library directory, building a hierarchical relationship between the core parent module and the sub-modules, and completing the construction of the project dependency management structure; Configure dependency management step: configure project dependency management based on the project dependency management structure, and introduce dependencies in layers and only introduce dependencies of the previous layer; Encryption packaging and pom cleaning steps: Encrypt the project and clean up the pom file.

2. The project deployment method based on Maven dependency management according to claim 1, characterized in that: The steps of building a dependency management structure include: Create a project private library directory; Constructing a third-party library dependency management submodule and a second-party library dependency management submodule under the private library directory; Build the core parent module under the private library directory, and introduce the third-party library dependency management submodule and the second-party library dependency management submodule; Under the directory of the core parent module, multiple public dependency management submodules are constructed.

3. The project deployment method based on Maven dependency management according to claim 2, characterized in that: The public dependency management submodule includes: a presentation layer dependency management submodule, a business layer dependency management submodule, a data layer dependency management submodule, and an external layer dependency management submodule.

4. The project deployment method based on Maven dependency management according to claim 3 is characterized in that: The configuration dependency management and inheritance steps include: Create a project working directory; Create a project working root module in the project working directory and introduce the dependency configuration of the core parent module; In the project working directory, create a presentation layer submodule, a business layer submodule, a data layer submodule and an external layer submodule, and introduce the dependency configuration of the presentation layer dependency management submodule, the dependency configuration of the business layer dependency management submodule, the dependency configuration of the data layer dependency management submodule and the dependency configuration of the external layer dependency management submodule respectively.

5. The project deployment method based on Maven dependency management according to claim 1, characterized in that: The encryption packaging and pom cleaning steps include: encrypting and packaging the project based on the AES algorithm, and configuring exclusion rules in the build script to exclude the pom file from the packaging file.

6. A project deployment system based on Maven dependency management, applying the project deployment system based on Maven dependency management as described in any one of claims 1 to 5, comprising: Build dependency management structure module: create a project private library directory, build a core parent module and multiple sub-modules under the project private library directory, build a hierarchical relationship between the core parent module and the sub-modules, and complete the construction of the project dependency management structure; Configuration dependency management module: configure project dependency management based on the project dependency management structure, and introduce dependencies in layers and only introduce dependencies of the previous layer; Encrypted packaging and pom cleaning module: encrypt and package the project and clean up the pom file.

7. The project deployment system based on Maven dependency management according to claim 6, characterized in that: The building dependency management structure module includes: Create a project private library directory; Constructing a third-party library dependency management submodule and a second-party library dependency management submodule under the private library directory; Build the core parent module under the private library directory, and introduce the third-party library dependency management submodule and the second-party library dependency management submodule; Under the directory of the core parent module, multiple public dependency management submodules are constructed.

8. The project deployment system based on Maven dependency management according to claim 6, characterized in that: The public dependency management submodule includes: a presentation layer dependency management submodule, a business layer dependency management submodule, a data layer dependency management submodule, and an external layer dependency management submodule.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the project deployment method based on Maven dependency management is implemented as described in any one of claims 1 to 6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the project deployment method based on Maven dependency management as described in any one of claims 1 to 6 is implemented.

Images