WO2022199160A1

WO2022199160A1 - Method for resolving component version conflict, device, and storage medium

Info

Publication number: WO2022199160A1
Application number: PCT/CN2021/140190
Authority: WO
Inventors: 周智
Original assignee: 京东科技控股股份有限公司
Priority date: 2021-03-25
Filing date: 2021-12-21
Publication date: 2022-09-29
Also published as: CN115202714A

Abstract

The present application provides a method for resolving a component version conflict, a device, and a storage medium. The method comprises: after acquiring a component version setting request comprising application identifier information and first component version numbers set for information of first components of which component version numbers conflict, acquiring a plurality of first components corresponding to the information of the first components; acquiring a component dependency configuration file corresponding to the application identifier information; adjusting, to the first component version numbers, the component version numbers corresponding to the plurality of first components in the component dependency configuration file, so as to obtain an updated component dependency configuration file; and compiling, according to the updated component dependency configuration file, an application corresponding to the application identifier information.

Description

Method, device and storage medium for resolving component version conflicts

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the priority of the Chinese Patent Application No. 202110321895.9 filed with the China Patent Office on March 25, 2021, the entire contents of which are incorporated herein by reference.

technical field

The present application relates to the field of computer technology, and in particular, to a method, apparatus, electronic device and storage medium for resolving component version conflicts.

Background technique

At present, in the process of developing applications based on componentization, an application may depend on multiple components, and a component may exist in multiple versions. In the related art, in the process of developing an application, in order to improve the running stability of the developed application, it is necessary to check whether there are multiple versions of the same component in the developed application, and the developer needs to check whether the same component has multiple versions. Manually adjust the program code of the application to adjust the version of the same component to be consistent to solve the problem of version conflict. However, in the process of solving the problem of version conflict in the above method, the user has many operations, and the cost of solving the conflicting version is relatively high, thereby affecting the efficiency of developing the application program.

SUMMARY OF THE INVENTION

The present application provides a method, apparatus, electronic device and storage medium for resolving component version conflicts.

In one aspect of the present application, an embodiment of the present application proposes a method for resolving a component version conflict, receiving a component version setting request from a requesting end, wherein the component version setting request includes application identification information and information about a first component with conflicting component version numbers. The set version number of the first component; obtain a plurality of first components corresponding to the first component information; obtain a component dependency configuration file corresponding to the application identification information; The component version numbers corresponding to the plurality of first components are adjusted to the first component version number, so as to obtain the updated component dependency configuration file; according to the updated component dependency configuration file, compile the corresponding application identification information. s application.

In an embodiment of the present application, before the receiving the component version setting request of the requesting end, the method further includes: receiving a query request from the requesting end, wherein the query request includes the application identification information; In the designed database, obtain the component query result corresponding to the application program identification information, wherein the component query result includes the first component information; send the first component information to the requester, so that the The first component information is displayed on the requester.

In an embodiment of the present application, the obtaining the component query result corresponding to the application identification information from a preset database includes: obtaining the application identification information from the preset database The second component information that the identified application program directly depends on, wherein the second component information includes component information corresponding to each of multiple second components; for each second component, according to the component information of the second component , obtain the first component dependency data of the second component; determine the third component information with conflicting component version numbers according to the first component dependency data; according to the third component information of each of the components, The first component information is generated.

In an embodiment of the present application, acquiring the first component dependency data of the second component according to the component information of the second component includes: acquiring a target component directly dependent on the second component; Obtain the component directly dependent on the target component, and end when the component directly dependent on the corresponding component is empty; connect the second component and all the obtained components in turn to obtain the first component of the second component. Component dependency data.

In an embodiment of the present application, the determining, according to the first component dependency relationship data, third component information with conflicting component version numbers includes: for each component in the first component dependency relationship data, adding Components with the same component identification are grouped into one group to obtain multiple groups of components; determine whether the component version numbers of each component in each group of components are the same, and select target groups with different component version numbers from the multiple groups of components; For components in the target group with different component version numbers, the third component information is generated.

In an embodiment of the present application, the method further includes: receiving a component addition request from the requester, wherein the component addition request includes the application identification information and the information of the component to be added; component dependency relationship data corresponding to the identification information; adjust the component dependency relationship data according to the to-be-added component information; save the adjusted component dependency relationship data to the component dependency configuration file.

In an embodiment of the present application, the component addition request further includes a component version number corresponding to the component information to be added, and the method further includes: querying the component dependency data for whether the component to be added exists The target component corresponding to the information; if there is a target component corresponding to the component information to be added, then determine whether the component version number of the target component is the same as the component version number of the component identified by the component information to be added; if different, Then, the component information is adjusted according to the target component and the component information of the component identified by the to-be-added component information.

In the method for resolving a component version conflict in the embodiment of the present application, after obtaining the component version setting request including the application identification information and the first component version number set for the first component information with the conflicting component version number, obtain the component version setting request with the first component version number. A plurality of first components corresponding to component information, obtain the component dependency configuration file corresponding to the application identification information, and adjust the component version numbers corresponding to the multiple first components in the component dependency configuration file to the first component version number , to obtain the updated component dependency configuration file, and compile the application corresponding to the application identification information according to the updated component dependency configuration file. Therefore, the developer can adjust the component version number of the component information with conflicting component version numbers by sending a component version setting request through the requester, so that the developer does not need to manually adjust the code of the application to resolve the component version number conflict. It reduces the developer's operation, reduces the development time, and improves the development efficiency.

Another embodiment of the present application provides an apparatus for resolving component version conflicts. The apparatus includes: a first receiving module, configured to receive a component version setting request from a requester, wherein the component version setting request includes an application identifier information, the first component version number set for the first component information with conflicting component version numbers; a first acquisition module, used to acquire a plurality of first components corresponding to the first component information; a second acquisition module, for obtaining the component-dependent configuration file corresponding to the application identification information; the configuration file update module is used to adjust the component version numbers corresponding to the multiple first components in the component-dependent configuration file to the A component version number to obtain an updated component dependency configuration file; a compilation module for compiling an application program corresponding to the application program identification information according to the updated component dependency configuration file.

In an embodiment of the present application, the apparatus further includes: a second receiving module, configured to receive a query request from the requester, wherein the query request includes the application identification information; a third obtaining module, configured with obtaining a component query result corresponding to the application identification information from a preset database, wherein the component query result includes the first component information; a sending module is configured to send the first component information to the requesting end, so that the first component information is displayed on the requesting end.

In an embodiment of the present application, the third obtaining module includes: a first obtaining unit, configured to obtain, from the preset database, a third obtaining unit directly dependent on the application identified by the application identification information. Two-component information, wherein the second component information includes component information corresponding to a plurality of second components; a second obtaining unit is configured to obtain, for each second component, according to the component information of the second component first component dependency data of the second component; a determining unit, configured to determine, according to the first component dependency data, third component information with conflicting component version numbers; a generating unit, configured to The third component information of the second component generates the first component information.

In an embodiment of the present application, the second obtaining unit is specifically configured to: obtain the target component directly dependent on the component; obtain the component directly dependent on the target component, until the component directly dependent on the corresponding component End when it is empty; connect the component and all the obtained components in sequence to obtain the first component dependency relationship data of the component.

In an embodiment of the present application, the determining unit is specifically configured to: for each component in the first component dependency relationship data, group components with the same component identification into one group to obtain multiple groups of components; determine Whether the component version numbers of each component in each group of components are the same, and select target groups with different component version numbers from the multiple groups of components; generate the fourth component according to the components with different component version numbers in the target group Component information.

In an embodiment of the present application, the apparatus further includes: a third receiving module, configured to receive a component addition request from the requester, wherein the component addition request includes the application identification information and the component to be added information The fourth acquisition module is used to acquire the component dependency data corresponding to the identification information of the application; the first adjustment module is used to adjust the component dependency data according to the component information to be added; for saving the adjusted component dependency data to the component dependency configuration file.

In an embodiment of the present application, the component addition request further includes a component version number corresponding to the component information to be added, and the apparatus further includes: a query module configured to query whether the component dependency relationship data exists the target component corresponding to the component information to be added; a determining module, configured to determine the component version number of the target component and the component identified by the component information to be added if there is a target component corresponding to the component information to be added Whether the version numbers of the components are the same; the second adjustment module is configured to adjust the component information according to the target component and the component information of the component identified by the component information to be added if they are different.

The device for resolving component version conflicts according to the embodiment of the present application, after obtaining the component version setting request including the application identification information and the first component version number set for the first component information with the conflicting component version numbers, obtains the component version setting request with the first component version number. A plurality of first components corresponding to component information, obtain the component dependency configuration file corresponding to the application identification information, and adjust the component version numbers corresponding to the multiple first components in the component dependency configuration file to the first component version number , to obtain the updated component dependency configuration file, and compile the application corresponding to the application identification information according to the updated component dependency configuration file. Therefore, the developer can adjust the component version number of the component information with conflicting component version numbers by sending a component version setting request through the requester, so that the developer does not need to manually adjust the code of the application to resolve the component version number conflict. It reduces the developer's operation, reduces the development time, and improves the development efficiency.

Another embodiment of the present application proposes an electronic device, comprising: a memory and a processor; the memory stores computer instructions, and when the computer instructions are executed by the processor, the solutions of the embodiments of the present application are realized. Component version conflict method.

Another embodiment of the present application provides a non-transitory computer-readable storage medium storing computer instructions, where the computer instructions are used to cause the computer to execute the method for resolving component version conflicts disclosed in the embodiments of the present application.

Another embodiment of the present application provides a computer program product, which implements the method for resolving component version conflicts in the embodiments of the present application when an instruction processor in the computer program product is executed.

Other effects of the above-mentioned optional manners will be described below with reference to specific embodiments.

Description of drawings

The accompanying drawings are used for better understanding of the present solution, and do not constitute a limitation to the present application. in:

FIG. 1 is a schematic flowchart of a method for resolving a component version conflict according to an embodiment of the present application.

FIG. 2 is a schematic flowchart of a method for resolving a component version conflict according to another embodiment of the present application.

FIG. 3 is a schematic flowchart of a method for resolving a component version conflict according to another embodiment of the present application.

FIG. 4 is a schematic flowchart of a method for resolving a component version conflict according to another embodiment of the present application.

FIG. 5 is a schematic flowchart of a method for resolving a component version conflict according to another embodiment of the present application.

FIG. 6 is a schematic flowchart of a method for resolving a component version conflict according to another embodiment of the present application.

FIG. 7 is a schematic structural diagram of an apparatus for resolving component version conflicts according to an embodiment of the present application.

FIG. 8 is a block diagram of an electronic device according to an embodiment of the present application.

Detailed ways

The following describes in detail the embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals refer to the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary, and are intended to be used to explain the present application, but should not be construed as a limitation to the present application.

The following describes the method, apparatus, electronic device, and storage medium for resolving component version conflicts according to the embodiments of the present application with reference to the accompanying drawings.

FIG. 1 is a schematic flowchart of a method for resolving a component version conflict according to an embodiment of the present application. It should be noted that the execution body of the method for resolving component version conflicts provided by this embodiment is a device for resolving component version conflicts, and the device for resolving component version conflicts may be implemented in software and/or hardware. This embodiment The device for resolving component version conflicts in the system can be configured in an application management server, and the application management server can provide an application development environment and development tools, so as to improve the development efficiency of the application. The application management server may be configured in an electronic device, and the electronic device in this embodiment may include, but is not limited to, a terminal device and a server and other devices, and the electronic device is not specifically limited in this embodiment.

As shown in FIG. 1 , the method for resolving component version conflicts may include steps 101 to 105 .

Step 101: Receive a component version setting request from a requesting end, wherein the component version setting request includes application identification information and a first component version number set for the first component information with conflicting component version numbers.

In some embodiments, the above-mentioned requesting end may be any type of electronic device, for example, a personal computer, and the requesting end is not specifically limited in this embodiment.

The application identification information is used to uniquely identify the application, and the application identification information corresponding to different applications is different.

In some embodiments, the first component information with conflicting component version numbers of the corresponding application may be displayed on the requesting end.

In other embodiments, in order to facilitate developers to visually check the dependencies of components in the application, the component dependencies may be displayed on the requesting side in a graphical manner, and the component information of the conflicting component version numbers may be displayed in the component dependencies. mark.

Correspondingly, after the requesting end visually displays the component information with conflicting component version numbers, the developer can set the component version number of the component information through an editing operation on the requesting end.

Specifically, multiple candidate component version numbers corresponding to the component information may also be displayed on the requesting end, and the developer may select the first component version number from the multiple candidate component version numbers through a selection operation.

The above marking method is preset, for example, the component information with conflicting component version numbers can be highlighted, marked in yellow, marked in red, etc., and the method of marking the component by the requester is not specified in this embodiment. limited.

Step 102: Acquire multiple first components corresponding to the first component information.

As a possible implementation manner, a plurality of first components corresponding to the first component information may be acquired according to the pre-stored correspondence between each component and component information.

The component information may include, but is not limited to, component identification information, component name information, and the like.

Step 103: Obtain a component dependency configuration file corresponding to the application identification information.

As a possible implementation manner, the component dependency configuration file corresponding to the application identification information may be acquired according to the pre-saved correspondence between the application identification information and the component dependency configuration file.

Step 104: Adjust the component version numbers corresponding to the multiple first components in the component dependency configuration file to the first component version numbers, so as to obtain an updated component dependency configuration file.

In some embodiments, for each first component, it may be determined whether the current component version number of the first component is the same as the first component version number, and if the two are the same, adjust the current component version number of the first component is the version number of the first component.

It can be understood that, when the current component version number of the first component is the same as the first component version number, the current component version number of the first component is kept unchanged, that is, the current component version number of the first component is not adjusted.

The first component version number may be one of conflicting component version numbers, or a new component version number.

For example, the application is applied to the component 1 twice, and in the two processes of using the component 1, the component version numbers corresponding to the component 1 are the component version number A and the component version number B, respectively. In order to avoid instability of the subsequently developed application program, the component version number of the component 1 applied to both times can be set to the component version number A or B.

For another example, the component version numbers corresponding to component 1 include component version number A, component version number B, and component version number C. Assuming that the application is applied to component 1 twice, in the two processes of using component 1, the component version numbers corresponding to component 1 are component version number A and component version number B, respectively. In order to avoid instability of the subsequently developed application program, the component version number of the component 1 applied to both times can be set to the component version number C.

Step 105: Compile an application program corresponding to the application program identification information according to the updated component dependency configuration file.

In some embodiments, when the application corresponding to the application identification information is developed based on the Android system development tool, and when the application is triggered, the Gradle plug-in pre-installed in the requester can be controlled, and after the update is read, the Gradle plugin can be controlled. The component dependency configuration file is updated, and the application corresponding to the application identification information is compiled according to the updated component dependency configuration file. Therefore, it is unnecessary for the developer to manually adjust the code of the application to solve the problem of the conflict of the component version numbers, which reduces the operation of the developer, reduces the development time, and improves the development efficiency.

In some embodiments, the application can be triggered by establishing a build, synchronizing sync, or being tasked by a task.

In some embodiments, the general process for the developer to obtain the component dependency data of the corresponding application is as follows: the developer enters the corresponding instruction in the requesting terminal by means of code, and correspondingly, according to the corresponding instruction, from the project management warehouse corresponding to the application Obtain all the dependent components in the , and analyze based on the dependent components, and determine the dependencies of the components and the conflict information of the component versions according to the analysis results. However, in the above method, since an application usually depends on a lot of components, the efficiency of obtaining the component dependency relationship and the component version conflict information is relatively low. In order to quickly obtain the component version dependency data of the corresponding application, in some embodiments, a component relationship query request sent by the requesting end may also be received, where the component relationship query request includes application identification information. Correspondingly, the component dependency relationship data corresponding to the identification information of the application may be obtained from a preset database, and the component dependency relationship data may be sent to the requester. Correspondingly, the requester visually displays component dependency data.

In an embodiment of the present application, in order to facilitate developers to quickly obtain the first component information with conflicting component version numbers, before receiving the component version setting request from the requesting end, as shown in FIG. 2 , steps 201 to 201 may be included. 203.

Step 201: Receive a query request from a requester, where the query request includes application identification information.

Step 202: Obtain a component query result corresponding to the application identification information from a preset database, wherein the component query result includes first component information.

In some embodiments, the above-mentioned preset database may store component information in which each application identification information conflicts with its corresponding component version number.

After the query request is obtained, the application identification information can be obtained from the query request, and then the first component information with conflicting component version numbers corresponding to the application identification information can be obtained from the database.

Step 203: Send the first component information to the requester, so that the requester displays the first component information.

In other embodiments, a possible implementation manner of obtaining the component query result corresponding to the application identification information from the preset database, as shown in FIG. 3 , may include steps 301 to 304 .

Step 301: Acquire from a preset database second component information that an application identified by the application identification information directly depends on, wherein the second component information includes component information corresponding to each of a plurality of second components.

Step 302 , for each second component, obtain first component dependency relationship data of the second component according to the component information of the second component.

In some embodiments, for each second component, according to the component information of the second component, a preset database can be queried to see whether there is component dependency data corresponding to the component information, and if so, the preset database can be queried. Get the component dependency data corresponding to this component.

It can be understood that there are usually fixed dependencies between some components. Therefore, in the process of obtaining the component dependency data corresponding to the application identification information, the data of the application corresponding to the application identification can be traversed from the database. Directly dependent first-level components, then obtain the component dependency data corresponding to each component in the first-level component, and determine the component dependency corresponding to the application identifier according to the component dependency data corresponding to each component in the first-level component. data. Therefore, the component dependency data of the corresponding application can be quickly determined by analyzing the component dependency data of the components, thereby improving the efficiency of acquiring the component dependency data of the corresponding application.

In other embodiments, another possible implementation manner of obtaining the first component dependency relationship data of the second component according to the component information of the second component is as follows: obtaining the target component directly dependent on the second component; obtaining the target component The directly dependent component ends when the component directly dependent on the corresponding component is empty; the second component and all the acquired components are connected in sequence to obtain the first component dependency relationship data of the second component.

Among them, it should be noted that in different application scenarios, the target component directly dependent on the second component can be obtained in different ways. Examples are as follows:

In some embodiments, an object model file corresponding to the second component is obtained; the object model file is parsed to obtain a parsing result, wherein the parsing result includes a component identifier of a target component directly dependent on the second component; according to the target component identifier , to get the target component.

Specifically, after the object model file is acquired, analysis can be performed according to the component coordinate information in the object model file to obtain the component identifier of the target component directly dependent on the second component.

The component coordinate information is composed of component identification and component version number and other information. For example, the application is an application based on the Android system, and when the application is developed, all the dependent data of the application (including aar/jar packages, pom files, etc.) are stored in the Maven repository. Correspondingly, the object model file is a pom.xml file, and the pom.xml file stores Maven coordinates, wherein the Maven coordinates corresponding to different components are different, and the Maven coordinates are expressed in the form of groupId:atifactId:version. Among them, groupId: defines the project to which the current Maven project belongs, organization artifactId: defines a module in the actual project, version: defines the current version of the current project. Among them, it should be noted that the direct dependencies of a component are stored in the dependencies node of the pom.xml file.

For example, the application APP directly depends on the component libraryA-1.0->libraryB-1.0, then the storage form of the pom that depends on libraryA-1.0 is as follows:

It can be understood that, in some embodiments, if the component dependency data of component libraryA needs to be analyzed, libraryA can be obtained by adding /com/test/libraryB/1.0/libraryA-1.0.pom to the specified maven repository access address All dependencies, so that you can recursively traverse all dependencies in any project (including direct dependencies, subordinate dependencies of direct dependencies, and so on), and can also analyze the scope of the dependency mode, and analyze the dependency hierarchy relationship, which is stored in the database. middle.

In some embodiments, in the case that the above application is developed based on an Android system development tool, the above dependency may include implementation, interface api, and compileOnly.

Among them, implementation: The library that this dependency method depends on will not be passed, and will only take effect in the current module.

api: This dependency method will pass the dependent library. When other modules depend on this module, you can use the api-dependent library under this module.

compileOnly: Only valid at compile time and will not participate in packaging.

In other embodiments, the target component directly dependent on the second component may be acquired according to the pre-saved dependencies between the components.

Step 303: Determine, according to the first component dependency relationship data, third component information with conflicting component version numbers.

In an embodiment of the present application, in order to accurately determine the third component information with conflicting component version numbers, a possible implementation of the above-mentioned determining the third component information with conflicting component version numbers according to the first component dependency data The method is as follows: for each component in the first component dependency data, the components with the same component ID are grouped into one group to obtain multiple groups of components; it is judged whether the component version numbers of each component in each group of components are the same, and from the multiple groups of components. A target group with different component version numbers is selected from the components; the third component information is generated according to the components with different component version numbers in the target group.

Step 304: Generate first component information according to the third component information of each second component.

Based on any of the foregoing embodiments, in order to meet the requirements of the corresponding developers to dynamically add components, in some embodiments, as shown in FIG. 4 , the method may further include steps 401 to 404 .

Step 401: Receive a component addition request from a requesting end, where the component addition request includes application identification information and information of a component to be added.

Step 402: Obtain component dependency relationship data corresponding to the application identification information.

In some embodiments, the component dependency relationship data corresponding to the application identification information may be acquired from a preset database.

The component dependency relationship data in the above-mentioned preset database is obtained by pre-analyzing the component dependency configuration file corresponding to the application program representation information.

Step 403: Adjust the component dependency relationship data according to the component information to be added.

Step 404: Save the adjusted component dependency relationship data to a component dependency configuration file.

In some embodiments, the application server may include a PaaS platform for managing the database, and a code server corresponding to the PaaS platform. Correspondingly, after obtaining the adjusted component dependency data, the adjusted component dependency data can be saved in the database in the PaaS platform, and the adjusted component dependency data can be sent to the code server in a preset manner. , correspondingly, the code server obtains the adjusted component dependency data, and writes the component dependency data into the component dependency configuration file corresponding to the application identification information.

As an exemplary implementation, the component dependency data can be transmitted between the application server and the code server in json format, so that the code server can obtain the component dependency data in json format, and the component dependency data in json format can be transmitted. The dependency relationship data is parsed to obtain the component dependency relationship data, and then the component dependency relationship data is written into the component dependency configuration file corresponding to the application identification information.

Correspondingly, after the application is triggered, the Gradle plug-in pre-installed in the requester can be controlled, the updated component dependency configuration file can be read, and according to the updated component dependency configuration file, the application corresponding to the application identification information can be identified. program to compile. As a result, the user can add components in a visual manner, which reduces the trouble of adding components through code, facilitates development, and improves development efficiency.

In some embodiments, the application can be triggered by establishing a build, synchronizing sync, or executing a certain task task.

In some embodiments, the above-mentioned component addition request further includes the component identifier of the component to be added. Based on the embodiment shown in FIG. 4 , as shown in FIG. 5 , the method may further include steps 501 to 503 .

Step 501: Query whether there is a target component corresponding to the component information to be added in the component dependency relationship data.

Step 502: If there is a target component corresponding to the component information to be added, determine whether the component version number of the target component is the same as the component version number of the component identified by the component information to be added.

Step 503, if different, adjust the component information according to the target component and the component information of the component identified by the component information to be added.

In the embodiment of the present application, in the process of adding a component at the requesting end, a target component with the same component identifier as the component to be added is obtained from the component dependency relationship, and it is compared whether the component version numbers of the target component and the component to be added are consistent, And in the case of inconsistency between the two, according to the target component and the component information of the component to be added, adjust the component information with conflicting component version numbers.

In order for those skilled in the art to clearly understand the present application, a process of adding components is exemplarily described below with reference to FIG. 6 . Among them, in this embodiment, the application management end is the paas platform server end as an example for illustration, wherein, the Paas platform, namely (Platform-as-a-Service: Platform-as-a-Service: Platform-as-a-Service), takes the operation and development environment of the application service as a A platform for providing services.

As shown in FIG. 6 , steps 601 to 608 may be included.

Step 601, pre-enter the components on the front-end interface to the Paas platform server.

Step 602, build different component versions and store the dependency analysis data in the database (Data Base) DB.

Step 603, enter the APP management page, and select an APP.

Step 604, displaying a list of dependent components that can be added by the APP.

Step 605: Select the added component on the page and send it to the Pass platform server in the form of a json string.

Step 606, the Paas platform server stores the data in the DB, and then sends the list of uniform components to the code server.

Step 607: On the code server, write the dependency list of the json string into the component dependency configuration file of the APP.

For example, a json string has the form:

{{"scope":"implementation","component_id":"com.test:libraryA","maven_coordinate":"co m.test:libraryA:1.0"},{"scope":"implementation","component_id" :"com.test:libraryB","maven_coordinate":"com.test:libraryB:1.0"}}.

Step 608, the APP adds the dependency to the APP.

In some embodiments, the APP triggers a custom Gradle plugin when executing build, sync, or executing a certain task, and dynamically adds dependencies to the APP through the method Configuration.getDependencies().addAll(List).

Corresponding to the methods for resolving component version conflicts provided by the above-mentioned embodiments, an embodiment of the present application further provides an apparatus for resolving component version conflicts. The methods for resolving component version conflicts provided in several embodiments correspond to each other, so the implementation of the method for resolving component version conflicts is also applicable to the device for resolving component version conflicts provided in this embodiment, which will not be described in detail in this embodiment. .

FIG. 7 is a schematic structural diagram of an apparatus for resolving component version conflicts according to an embodiment of the present application. It should be noted that the device in this embodiment is applied to the application management server.

As shown in FIG. 7 , the apparatus 700 for resolving component version conflicts includes:

A first receiving module 701, configured to receive a component version setting request from a requesting end, wherein the component version setting request includes application identification information and a first component version number set for the first component information with conflicting component version numbers;

a first obtaining module 702, configured to obtain a plurality of first components corresponding to the first component information;

A second obtaining module 703, configured to obtain a component-dependent configuration file corresponding to the application identification information;

The configuration file update module 704 is used to adjust the component version numbers corresponding to the multiple first components in the component dependency configuration file to the first component version numbers, so as to obtain the updated component dependency configuration file;

The compiling module 705 is configured to compile an application program corresponding to the application program identification information according to the updated component dependency configuration file.

In an embodiment of the present application, the device may further include:

a second receiving module, configured to receive a query request from a requesting end, wherein the query request includes application identification information;

The third acquisition module is used to acquire the component query result corresponding to the application identification information from the preset database, wherein the component query result includes the first component information;

The sending module is configured to send the first component information to the requester, so that the requester displays the first component information.

In an embodiment of the present application, the third acquisition module may include:

The first obtaining unit is configured to obtain, from a preset database, second component information that an application identified by the application identification information directly depends on, wherein the second component information includes component information corresponding to each of a plurality of second components ;

a second obtaining unit, configured to obtain, for each second component, the first component dependency relationship data of the second component according to the component information of the second component;

a determining unit, configured to determine third component information with conflicting component version numbers according to the first component dependency data;

The generating unit is configured to generate the first component information according to the third component information of each second component.

In an embodiment of the present application, the second acquisition unit is specifically used for:

Get the target component that the component directly depends on;

Get the components directly dependent on the target component, until the component directly dependent on the corresponding component is empty;

The components and all the acquired components are connected in sequence to obtain the first component dependency relationship data of the components.

In an embodiment of the present application, the determining unit is specifically used for:

For each component in the first component dependency data, the components with the same component identification are grouped into one group to obtain multiple groups of components;

Determine whether the component version numbers of each component in each group of components are the same, and select target groups with different component version numbers from multiple groups of components;

Fourth component information is generated according to components in the target group with different component version numbers.

In an embodiment of the present application, the device further includes:

a third receiving module, configured to receive a component addition request from the requesting end, wherein the component addition request includes application identification information and information about the component to be added;

a fourth acquisition module, configured to acquire component dependency data corresponding to the application identification information;

a first adjustment module, configured to adjust the component dependency data according to the component information to be added;

The save module is used to save the adjusted component dependency data to the component dependency configuration file.

In an embodiment of the present application, the component addition request further includes a component version number corresponding to the component information to be added, and the device further includes:

A query module, used to query whether there is a target component corresponding to the component information to be added in the component dependency data;

a determining module, configured to determine whether the component version number of the target component is the same as the component version number of the component identified by the component information to be added if there is a target component corresponding to the component information to be added;

The second adjustment module is configured to adjust the component information according to the target component and the component information of the component identified by the component information to be added if they are different.

According to the embodiments of the present application, the present application further provides an electronic device and a readable storage medium.

As shown in Figure 8, the electronic device includes:

Memory 801 , processor 802 , and computer instructions stored on memory 801 and executable on processor 802 .

When the processor 802 executes the instructions, the method for resolving a component version conflict provided in the foregoing embodiment is implemented.

Further, the electronic device also includes:

The communication interface 803 is used for communication between the memory 801 and the processor 802 .

Memory 801 is used to store computer instructions executable on processor 802 .

The memory 801 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk memory.

The processor 802 is configured to implement the method for resolving a component version conflict in the foregoing embodiment when executing the program.

If the memory 801, the processor 802 and the communication interface 803 are independently implemented, the communication interface 803, the memory 801 and the processor 802 can be connected to each other through a bus and complete communication with each other. The bus may be an Industry Standard Architecture (referred to as ISA) bus, a Peripheral Component (referred to as PCI) bus, or an Extended Industry Standard Architecture (referred to as EISA) bus or the like. The bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.

Optionally, in terms of specific implementation, if the memory 801, the processor 802 and the communication interface 803 are integrated on one chip, the memory 801, the processor 802 and the communication interface 803 can communicate with each other through an internal interface.

The processor 802 may be a central processing unit (Central Processing Unit, referred to as CPU), or a specific integrated circuit (Application Specific Integrated Circuit, referred to as ASIC), or is configured to implement one or more of the embodiments of the present application integrated circuit.

The present application also provides a computer program product, which implements the method for resolving component version conflicts according to the embodiments of the present application when an instruction processor in the computer program product is executed.

In the description of this specification, description with reference to the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples", etc., mean specific features described in connection with the embodiment or example , structure, material or feature is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, those skilled in the art may combine and combine the different embodiments or examples described in this specification, as well as the features of the different embodiments or examples, without conflicting each other.

In addition, the terms "first" and "second" are only used for descriptive purposes, and should not be construed as indicating or implying relative importance or implying the number of indicated technical features. Thus, a feature delimited with "first", "second" may expressly or implicitly include at least one of that feature. In the description of the present application, "plurality" means at least two, such as two, three, etc., unless expressly and specifically defined otherwise.

Any process or method description in the flowcharts or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing custom logical functions or steps of the process , and the scope of the embodiments of the present application includes alternative implementations in which the functions may be performed out of the order shown or discussed, including performing the functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be Those skilled in the art to which the embodiments of the present application pertain will be understood.

The logic and/or steps represented in flowcharts or otherwise described herein, for example, may be considered an ordered listing of executable instructions for implementing the logical functions, may be embodied in any computer-readable medium, For use with, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other system that can fetch instructions from and execute instructions from an instruction execution system, apparatus, or apparatus) or equipment. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport the program for use by or in connection with an instruction execution system, apparatus, or apparatus. More specific examples (non-exhaustive list) of computer readable media include the following: electrical connections with one or more wiring (electronic devices), portable computer disk cartridges (magnetic devices), random access memory (RAM), Read Only Memory (ROM), Erasable Editable Read Only Memory (EPROM or Flash Memory), Fiber Optic Devices, and Portable Compact Disc Read Only Memory (CDROM). In addition, the computer readable medium may even be paper or other suitable medium on which the program may be printed, as may be done, for example, by optically scanning the paper or other medium, followed by editing, interpretation, or other suitable means as necessary process to obtain the program electronically and then store it in computer memory.

It should be understood that various parts of this application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented by any one of the following techniques known in the art, or a combination thereof: discrete with logic gates for implementing logic functions on data signals Logic circuits, application specific integrated circuits with suitable combinational logic gates, Programmable Gate Arrays (PGA), Field Programmable Gate Arrays (FPGA), etc.

Those of ordinary skill in the art can understand that all or part of the steps carried by the methods of the above embodiments can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, and when the program is executed, Include one or a combination of the steps of a method embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing module, or each unit may exist physically alone, or two or more units may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.

The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, and the like. Although the embodiments of the present application have been shown and described above, it should be understood that the above embodiments are exemplary and should not be construed as limitations to the present application. Embodiments are subject to variations, modifications, substitutions and variations.

Claims

A method for resolving component version conflicts, including:

Receive a component version setting request from the requesting end, wherein the component version setting request includes application identification information and a first component version number set for the first component information whose component version numbers are in conflict;

acquiring a plurality of first components corresponding to the first component information;

obtaining a component-dependent configuration file corresponding to the application identification information;

Adjusting the component version numbers corresponding to the multiple first components in the component dependency configuration file to the first component version numbers to obtain an updated component dependency configuration file;

The application corresponding to the application identification information is compiled according to the updated component dependency configuration file.
The method according to claim 1, wherein before the receiving the request for setting the component version of the requester, the method further comprises:

receiving a query request from the requester, wherein the query request includes the application identification information;

Obtain, from a preset database, a component query result corresponding to the application identification information, wherein the component query result includes the first component information;

Sending the first component information to the requester, so that the requester displays the first component information.
The method according to claim 2, wherein the obtaining the component query result corresponding to the application identification information from a preset database comprises:

Acquiring, from the preset database, second component information on which the application identified by the application identification information directly depends, wherein the second component information includes component information corresponding to each of a plurality of second components;

For each second component, obtain the first component dependency relationship data of the second component according to the component information of the second component;

According to the first component dependency relationship data, determine third component information with conflicting component version numbers;

The first component information is generated according to the third component information of each of the components.
The method according to claim 3, wherein the obtaining the first component dependency relationship data of the second component according to the component information of the second component comprises:

Obtain the target component that the second component directly depends on;

Obtain the component directly dependent on the target component, and end when the component directly dependent on the corresponding component is empty;

Connect the second component and all the obtained components in sequence to obtain the first component dependency relationship data of the second component.
The method according to claim 3, wherein the determining, according to the first component dependency relationship data, the third component information with conflicting component version numbers, comprising:

For each component in the first component dependency data, the components with the same component identification are grouped into one group to obtain multiple groups of components;

Determine whether the component version numbers of each component in each group of components are the same, and select target groups with different component version numbers from the multiple groups of components;

The third component information is generated according to components in the target group with different component version numbers.
The method of claim 1, further comprising:

receiving a component addition request from the requester, wherein the component addition request includes the application identification information and the component to be added information;

obtaining component dependency data corresponding to the application identification information;

adjusting the component dependency data according to the component information to be added;

Save the adjusted component dependency data to the component dependency configuration file.
The method of claim 6, wherein the component addition request further includes a component version number corresponding to the component information to be added, and the method further includes:

query whether the target component corresponding to the to-be-added component information exists in the component dependency relationship data;

If there is a target component corresponding to the component information to be added, determine whether the component version number of the target component is the same as the component version number of the component identified by the component information to be added;

If different, the component information is adjusted according to the target component and the component information of the component identified by the to-be-added component information.
A means of resolving component version conflicts, including:

a first receiving module, configured to receive a component version setting request from a requesting end, wherein the component version setting request includes application identification information and a first component version number set for the first component information with conflicting component version numbers;

a first obtaining module, configured to obtain a plurality of first components corresponding to the first component information;

a second obtaining module, configured to obtain a component-dependent configuration file corresponding to the application identification information;

A configuration file update module, configured to adjust the component version numbers corresponding to the multiple first components in the component dependency configuration file to the first component version numbers, so as to obtain an updated component dependency configuration file;

A compiling module, configured to compile an application program corresponding to the application program identification information according to the updated component dependency configuration file.
The apparatus of claim 8, further comprising:

a second receiving module, configured to receive a query request from the requester, wherein the query request includes the application identification information;

a third obtaining module, configured to obtain a component query result corresponding to the application identification information from a preset database, wherein the component query result includes the first component information;

A sending module, configured to send the first component information to the requester, so that the requester displays the first component information.
The apparatus of claim 9, wherein the third acquisition module comprises:

The first obtaining unit is configured to obtain, from the preset database, second component information that the application identified by the application identification information directly depends on, wherein the second component information includes a plurality of second components. Component information corresponding to each component;

a second obtaining unit, configured to obtain, for each second component, the first component dependency data of the second component according to the component information of the second component;

a determining unit, configured to determine third component information with conflicting component version numbers according to the first component dependency data;

A generating unit, configured to generate the first component information according to the third component information of each of the second components.
The apparatus of claim 10, wherein the second obtaining unit is further configured to:

Obtain the target component that the component directly depends on;

Obtain the component directly dependent on the target component, and end when the component directly dependent on the corresponding component is empty;

Connect the components and all the obtained components in sequence to obtain the first component dependency relationship data of the components.
The apparatus of claim 10, wherein the determining unit is further configured to:

For each component in the first component dependency data, the components with the same component identification are grouped into one group to obtain multiple groups of components;

Determine whether the component version numbers of each component in each group of components are the same, and select target groups with different component version numbers from the multiple groups of components;

The fourth component information is generated according to components in the target group with different component version numbers.
The apparatus of claim 8, further comprising:

A third receiving module, configured to receive a component addition request from the requester, wherein the component addition request includes the application identification information and the component information to be added;

a fourth acquisition module, configured to acquire component dependency data corresponding to the application identification information;

a first adjustment module, configured to adjust the component dependency relationship data according to the to-be-added component information;

The saving module is used for saving the adjusted component dependency relationship data to the component dependency configuration file.
The apparatus according to claim 13, wherein the component addition request further includes a component version number corresponding to the component information to be added, and the apparatus further includes:

a query module, configured to query whether there is a target component corresponding to the to-be-added component information in the component dependency relationship data;

a determining module, configured to determine whether the component version number of the target component is the same as the component version number of the component identified by the component information to be added if there is a target component corresponding to the component information to be added;

A second adjustment module, configured to adjust the component information according to the target component and the component information of the component identified by the to-be-added component information if they are different.
An electronic device comprising:

memory,

processor;

The memory stores computer instructions, and when the computer instructions are executed by the processor, implements the method for resolving a component version conflict according to any one of claims 1-7.
A non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the method for resolving component version conflicts of any of claims 1-7.
A computer program product wherein, when executed by an instruction processor in the computer program product, the method for resolving a component version conflict as claimed in any one of claims 1-7 is implemented.