Compensation mechanism system and method for analyzing component dependence based on Maven architecture

Abstract

The invention provides a compensation mechanism system and method based on Maven architecture analysis component dependency, the system comprises a service interface module, a system database and an analysis service module, the service interface module is a POM file transmission interface and provides POM file transmission interface calling for a user; the analysis service module comprises a POM file generation component dependency unit which is used for executing a maven command and generating a component dependency tree file; the component dependency compensation mechanism analysis unit is used for performing component package compensation when compiling errors occur in the process of compiling the component dependency tree file, and performing compiling again after compensation until compiling succeeds to generate a component dependency tree; and the component dependency information and hierarchical relationship analysis unit is used for analyzing the component dependency information, storing the component information and indirect dependency among the components, and transmitting hierarchical relationship information of the dependency. According to the method, the problem that the component dependency tree of the project cannot be generated due to the absence of the component package can be effectively solved.

Description

Technical Field

[0001] The present invention relates to the technical field of component dependency resolution, and in particular to a compensation mechanism system and method for resolving component dependencies based on a Maven architecture. Background Art

[0002] With the widespread application of open source software and the growth of the open source community, more and more open source software and components are created and shared. The open source software ecosystem provides developers with rich resources and choices, while the constantly updated versions and multi-level dependencies of open source software and components have caused some complex problems, such as: managing complex component dependencies requires considering compatibility, version conflicts, security vulnerabilities, etc. Therefore, the correctness and completeness of component dependency resolution can better provide effective support for the management and control of the use of open source components.

[0003] In the prior art, many open source components rely on the management tool Maven, and its components are mainly stored in Maven repositories, including central repositories, local repositories, and private repositories. The central repositories are Maven's default repositories, which contain a large number of open source components for download and use. The local repositories are repositories on each developer's local machine, which are used to cache downloaded components. The private repositories are repositories built within an organization, which are used to store self-developed components or third-party components.

[0004] In the POM file of the project, the dependencies element can be used to declare the components that the project depends on. Maven will automatically download and manage the components through the warehouse management system based on these dependencies. The dependencies of the components often involve multiple levels and multiple dependencies. In the Maven architecture project, the dependency:tree command provided by Maven can be used to generate the project component dependency tree. At the same time, by running this command, you can view the hierarchical relationship of all dependencies in the project, including direct dependencies, indirect dependencies, and transitive dependencies between them. When using this command, the project components involved will be searched in the local warehouse first. If they cannot be found, they will be searched in the remote warehouse. After being found in the remote warehouse, they will be downloaded to the local warehouse. When it cannot be found in the local warehouse and the remote warehouse and cannot be downloaded from the remote warehouse, the dependency:tree command will prompt an error message. At this time, the component package does not exist, which will eventually lead to the abnormal problem that the component dependency tree of the project cannot be generated. Traditional component dependency resolution depends on the success of the compilation process when Maven uses the POM file to resolve component dependencies. If the compilation fails, the component dependency resolution will be abandoned, which will cause a large error in the correctness and accuracy of component dependency resolution. Summary of the invention

[0005] The present invention aims at the technical problem in the prior art that when a Maven architecture project fails to parse component dependencies using a POM file, the component dependency tree of the project cannot be generated due to the non-existence of the component package. A compensation mechanism for parsing component dependencies based on the Maven architecture is proposed, which can effectively solve the problem that the compilation fails and the component dependency tree cannot be generated due to the non-existence of the component package. The specific invention contents are as follows:

[0006] A compensation mechanism system for parsing component dependencies based on Maven architecture, the system comprising: a service interface module, a system database and a parsing service module, wherein the service interface module and the parsing service module perform data exchange transmission through the system database;

[0007] The service interface module specifically refers to a POM file transmission interface, which is used to provide a POM file transmission interface call for service users;

[0008] The parsing service module includes a POM file generation component dependency unit, a component dependency compensation mechanism parsing unit, and a component dependency information and hierarchical relationship parsing unit, wherein:

[0009] The POM file generates component dependency units, which are used to execute Maven commands and generate component dependency tree files;

[0010] The component dependency parsing compensation mechanism unit is used to compensate for component packages when a parsing error occurs due to the non-existence of component packages during the compilation of component dependency tree files, and to compile again after compensation until the compilation successfully generates a component dependency tree;

[0011] The component dependency information and hierarchical relationship parsing unit is used to parse the component dependency tree, obtain the component information of the component dependency tree and the hierarchical relationship information of the indirect dependency and transitive dependency between components and store them.

[0012] Furthermore, the service interface module and the analysis service module perform data exchange and transmission through the system database, specifically including:

[0013] The service interface module encrypts and stores the POM file information, and transmits the POM file information to the system database by calling the POM file transmission interface;

[0014] After the POM file information is transmitted, the parsing service module operates the system database, including: storing and generating component dependency file information and status; querying component dependency files in a state to be compensated; querying various configurations of component packages that do not exist; and querying the configuration of the maximum number of compensation times defined for the compensation repair component package.

[0015] Furthermore, when calling the POM file transfer interface, a POM file transfer request needs to be sent, specifically: security authentication is performed through IP whitelist or token, and after the security authentication is passed, the POM file transfer interface is called to transfer the project POM file and store the POM file information in the library.

[0016] Furthermore, the Maven command is mvn dependency:tree, and a component dependency tree file is generated by executing the mvn dependency:tree command.

[0017] Furthermore, the parsing component dependency compensation mechanism unit is used to compensate for component packages when a parsing error occurs due to the non-existence of component packages during the process of compiling the component dependency tree file, and compile again after compensation until the compilation successfully generates the component dependency tree, and also includes:

[0018] The analysis component dependency compensation mechanism unit configures a maximum compensation number for the compensation component package operation. If the compensation number exceeds the maximum number, no compensation will be performed and the file will be marked as failed.

[0019] On the one hand, a compensation mechanism method for parsing component dependencies based on the Maven architecture is provided, which specifically includes the following steps:

[0020] Step S1: The user performs security authentication through IP whitelist or token. After passing the authentication, the POM file transfer interface is called to transfer the project POM file and store the POM file information in the library;

[0021] Step S2: Execute the mvn dependency:tree command based on the POM file information to generate a component dependency tree file;

[0022] Step S3: compile the generated component dependency tree file until a component dependency tree is generated when the compilation is successful;

[0023] Step S4: Parse the generated component dependency tree, obtain component information and component hierarchical relationships of the component dependency tree when the parsing is successful, and store the component information and component hierarchical relationships of the component dependency tree.

[0024] Further, in step S2, further, the system executes the mvn dependency:tree>tree.txt command and uses >tree.txt to store the output information in the tree.txt file.

[0025] Furthermore, in step S3, it also includes: compiling the tree.txt file, and if the compilation is successful, generating a component dependency tree; if the compilation fails, parsing the compilation failure information to obtain the component name in the error log, and in the system compensation mechanism, based on the component name in the error log, recreating a new simulation file with the same name in the local repository, and then executing the mvn dependency:tree command until the compilation is successful and the component dependency tree is generated.

[0026] Compared with the prior art, the present invention has the following advantages:

[0027] 1. The present invention provides a compensation mechanism for completing component dependency resolution based on a Maven architecture project when a component dependency resolution using a POM file fails due to the non-existence of a component package. The POM file is generated into a component dependency tree file by executing the mvn dependency:tree command, and the component dependency tree file is compiled. If the compilation is successful, the output information is a component dependency tree; if the compilation fails, the component package is used for compensation, and the compilation is performed again after compensation, and the repair is continued until the compilation is successful. The present invention effectively solves the problem that the compilation fails due to the non-existence of the component package, thereby failing to generate the component dependency tree, can 100% solve the abnormal problems caused by direct dependency, and can solve 80% of the abnormal problems caused by indirect dependency; after solving the abnormal problems, the accuracy rate of successful compilation is increased from 60% to more than 92%.

[0028] 2. During the implementation of the entire solution of the present invention, the system does not need to obtain all the codes of the project. By only transmitting the project POM file, subsequent compensation component operations can be performed, thereby ensuring the security of the code.

[0029] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0031] Figure 1 This is a system architecture diagram of a compensation mechanism that parses component dependencies based on the Maven architecture;

[0032] Figure 2 A flow chart of the compensation mechanism for system component parsing based on Maven architecture to parse component dependencies;

[0033] Figure 3 It is a compensation mechanism system command execution code compilation diagram based on Maven architecture to parse component dependencies;

[0034] Figure 4 A simulation file code compilation diagram for a compensation mechanism system that parses component dependencies based on the Maven architecture;

[0035] Figure 5 Generates a code compilation diagram of component dependency files for a compensation mechanism system that parses component dependencies based on the Maven architecture DETAILED DESCRIPTION

[0036] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0037] In one embodiment, see Figure 1 and Figure 2 , provides a compensation mechanism system for parsing component dependencies based on the Maven architecture, the system includes: a service interface module, a system database and a parsing service module, the service interface module and the parsing service module perform data exchange transmission through the system database, specifically:

[0038] The service interface module encrypts and stores the POM file information, and transmits the POM file information to the system database by calling the POM file transmission interface;

[0039] Furthermore, when calling the POM file transfer interface, a POM file transfer request needs to be sent, including: security authentication through IP whitelist or token, calling the POM file transfer interface after the security authentication is passed, transferring the project POM file and storing the POM file information in the library.

[0040] The analysis service module operates the system database based on the POM file information in the system database, including: storing and generating component dependency file information and status; querying component dependency files in a state to be compensated; querying various configurations of non-existent component packages; and querying the configuration of the maximum number of compensation times defined for compensation repair component packages.

[0041] The parsing service module further includes a POM file generation component dependency unit, a component dependency compensation mechanism parsing unit, and a component dependency information and hierarchical relationship parsing unit;

[0042] Furthermore, the POM file generating component dependency unit is used to execute Maven commands to generate a component dependency tree file; the component dependency parsing compensation mechanism unit is used to compensate for component packages when a parsing error occurs due to the non-existence of component packages during the compilation of the component dependency tree file, and to compile again after compensation until the compilation is successful and the component dependency tree is generated; the component dependency information and hierarchical relationship parsing unit is used to parse the generated component dependency tree, and after parsing, the component information of the component dependency tree and the hierarchical relationship information of indirect dependencies and transitive dependencies between components are obtained and stored.

[0043] Furthermore, the Maven command is mvn dependency:tree, and a component dependency tree file is generated by executing the mvn dependency:tree command;

[0044] Furthermore, the parsing component dependency compensation mechanism unit is used to compensate for component packages when a parsing error occurs due to the non-existence of component packages during the process of compiling the component dependency tree file, and compile again after compensation until the compilation successfully generates the component dependency tree, and also includes:

[0045] The analysis component dependency compensation mechanism unit configures a maximum compensation number for the compensation component package operation. If the compensation number exceeds the maximum number, no compensation will be performed and the file will be marked as failed.

[0046] In one embodiment, see Figure 3 to Figure 5 The present invention is described in detail through specific operations, and provides a compensation mechanism method for parsing component dependencies based on the Maven architecture, which specifically includes the following steps:

[0047] Step S1: The user performs security authentication through IP whitelist or token. After passing the authentication, the POM file transfer interface is called to transfer the project POM file and store the POM file information in the library;

[0048] Step S2: Execute the mvn dependency:tree command based on the POM file information to generate a component dependency tree file;

[0049] For further information, see Figure 3 , the system executes the mvn dependency:tree>tree.txt command and uses >tree.txt to store the output information in the tree.txt file.

[0050] Step S3: compile the generated component dependency tree file until a component dependency tree is generated when the compilation is successful;

[0051] For further information, see Figure 4 , compile the tree.txt file. If the compilation is successful, a component dependency tree is generated; if the compilation fails, the compilation failure information is parsed to obtain the component name in the error log. In the system compensation mechanism, based on the component name in the error log, a new simulation file with the same name is recreated in the local warehouse, and then the mvn dependency:tree command is executed until the compilation is successful and the component dependency tree is generated.

[0052] Step S4: Parse the generated component dependency tree, obtain component information and component hierarchical relationships of the component dependency tree when the parsing is successful, and store the component information and component hierarchical relationships of the component dependency tree.

[0053] For further information, see Figure 5 , after continuous component compensation, the complete component dependency information of the project will be obtained after successful compilation.

[0054] Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent substitutions for some of the technical features therein; and these modifications or substitutions do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A compensation mechanism system for parsing component dependencies based on the Maven architecture, characterized by: It includes a service interface module, a system database and an analysis service module, wherein the service interface module and the analysis service module perform data exchange and transmission through the system database; The service interface module is a POM file transmission interface, which is used to provide users with a POM file transmission interface call; The parsing service module includes a POM file generation component dependency unit, a component dependency compensation mechanism parsing unit, and a component dependency information and hierarchical relationship parsing unit, wherein: The POM file generates component dependency units, which are used to execute Maven commands and generate component dependency tree files; The component dependency compensation mechanism unit is used to compensate for the component package when a compilation error occurs due to the non-existence of the component package during the compilation of the component dependency tree file, and to compile again after compensation until the compilation successfully generates the component dependency tree; The component dependency information and hierarchical relationship parsing unit is used to parse component dependency information, store component information and hierarchical relationship information of indirect dependencies and transitive dependencies between components.

2. A compensation mechanism system for parsing component dependencies based on Maven architecture as claimed in claim 1, characterized in that: The service interface module and the analysis service module perform data exchange and transmission through the system database, specifically including: The service interface module encrypts and stores the POM file information, and transmits the POM file information to the system database by calling the POM file transmission interface; After the POM file information is transmitted, the parsing service module operates the system database, including: storing and generating component dependency file information and status; querying component dependency files in the state to be compensated; querying various configurations of component packages that do not exist; querying the maximum number of compensation configurations defined for the compensation repair component package.

3. A compensation mechanism system for parsing component dependencies based on Maven architecture as claimed in claim 2, characterized in that: When calling the POM file transfer interface, you need to send a POM file transfer request, including: security authentication through IP whitelist or token, calling the POM file transfer interface after the security authentication is passed, transferring the project POM file and storing the POM file information in the library.

4. A compensation mechanism system for parsing component dependencies based on Maven architecture as claimed in claim 1, characterized in that: The Maven command is mvn dependency:tree.

5. A compensation mechanism system for parsing component dependencies based on Maven architecture as claimed in claim 1, characterized in that: The analysis component dependency compensation mechanism unit configures a maximum compensation number for the compensation component package operation. If the compensation number exceeds the maximum number, no compensation will be performed and the file will be marked as failed.

6. A compensation mechanism method for parsing component dependencies based on Maven architecture, used to implement a compensation mechanism system for parsing component dependencies based on Maven architecture as claimed in any one of claims 1 to 5, characterized in that: The user performs security authentication through IP whitelist or token. After passing the authentication, the POM file transfer interface is called to transfer the project POM file and store the POM file information in the library. Execute the mvn dependency:tree command based on the POM file information to generate a component dependency tree file; Compile the generated component dependency tree file until the component dependency tree is generated when the compilation succeeds; The generated component dependency tree is parsed, and when the parsing is successful, component information and component hierarchical relationships of the component dependency tree are obtained, and the component information and component hierarchical relationships of the component dependency tree are stored.

7. A compensation mechanism method for parsing component dependencies based on Maven architecture as claimed in claim 6, characterized in that: Generating a component dependency tree file by executing mvn dependency:tree includes: executing the mvn dependency:tree>tree.txt command and using>tree.txt to store output information in a tree.txt file.

8. A compensation mechanism method for parsing component dependencies based on Maven architecture as claimed in claim 7, characterized in that: Also includes: Compile the tree.txt file. If the compilation is successful, a component dependency tree file is generated. If the compilation fails, the compilation failure information is parsed to obtain the component name in the error log. In the system compensation mechanism, based on the component name in the error log, a new simulation file with the same name is recreated in the local repository, and then the mvn dependency:tree command is executed until the compilation is successful and the component dependency tree is generated.

Images