Application component version management method and device

Abstract

The invention discloses an application component version management method and device. The device comprises the steps that a component information verification request sent by a client is received, wherein the component information verification request contains first version information of a first application component and second version information of a second application component, the first version information depends on the second version information and contains a first version dependence relation; whether multiple second version dependence relations stored in a product management platform contain the first version dependence relation or not is judged; if yes, a verification passing message is fed back to the client to prompt the client to save the first version information and the second version information; if not, first prompt information is pushed to the client to prompt the user to modify the first version information and / or the second version information. Accordingly, the client can be prompted to use the application component compatible with versions, then the problem that the versions are not compatible when the client calls the component to achieve corresponding functions is avoided, and the user experience is improved.

Description

technical field [0001] The invention relates to the technical field of computer applications, in particular to a method and device for managing application component versions. Background technique [0002] When the third-party build tool builds the dependency relationship between application components, it does not know whether there is really a dependency relationship between the application components it builds, but builds the dependency relationship between application components according to the pre-existing build mechanism. For example, the build.gradle file stores two sets of application components with dependencies written by users. For example, application component A with version number 1.0 depends on application component B with version number 2.0, and application component with version number 1.0 Component C depends on application component B with a version number of 2.1. The gradle build plugin detects that there are two application component B with inconsistent ...

AI Technical Summary

Problems solved by technology

[0003] The main purpose of the present invention is to provide a method and device for managing application component versions, which aims to solve the problem that the current third-party construction tools cannot manage the dependencies between application components, resulting in incompatible versions between various groups of application components after construction. question

Images