CN106155724B - Upgrading method and device - Google Patents

Abstract

The present application provides an upgrade method and device. The method includes: obtaining a first dependency link of a current project construction management Maven project, where the first dependency link includes a to-be-changed package; A mapping rule; modify the first dependent link according to the mapping rule to obtain a second dependent link. The present application modifies the to-be-changed package of the first dependency link to obtain the second dependency link through the preset mapping rules, realizes the automatic upgrade of the initial dependency link, and solves the problem that the dependency link cannot be automatically upgraded in the Maven project The problem.

Description

An upgrade method and device

technical field

The present application relates to the technical field of computer software, and in particular, to an upgrade method and device.

Background technique

Maven (Project Build Management) is a software project management tool based on POM (Project Object Model) that can manage project builds, reports and documentation through a small piece of descriptive information. Maven includes SNAPSHOT snapshot repository and release release repository. The SNAPSHOT snapshot repository is used to store unstable versions during development, and the official release repository is used to store stable releases. SNAPSHOT is a snapshot and can be overwritten by updates at any time, which leads to online failures. However, some Maven projects will directly or indirectly depend on the SNAPSHOT package, which requires the work of removing the SNAPSHOT package for the dependency link, which will soon depend on SNAPSHOT. The link of the package is upgraded to the link that depends on the release package.

At present, if you want to promote a Maven project to remove the SNAPSHOT package, the developer needs to make changes to the upper-layer business for each jar package layer by layer, such as the following link A->B->C-SNAPSHOT-> D->E-SNAPSHOT, for the current promoter A, he needs to push B and cannot rely on any SNAPSHOT version, which means that B needs to push business party C to release C' version. Similarly, C needs to push D, and D needs to To promote E, and to push the business side to upgrade the release package layer by layer, any link in the middle is indispensable, until the entire link changes the SNAPSHOT package, and an upgrade link is obtained.

However, since the entire Maven link will be very long and there may be 10 or more nodes, there is currently no automatic solution that can solve the process of removing the SNAPSHOT package, all of which are manual changes. When upgrading the dependent link, It is necessary to promote the business side to upgrade the release package layer by layer, the communication cost is high, and the problem solving is also very complicated.

SUMMARY OF THE INVENTION

The embodiments of the present application propose an upgrade method and device to solve the technical problem in the prior art that the dependency link cannot be automatically upgraded in the Maven project.

The embodiment of the present application provides an upgrade method, including:

Obtain the first dependency link of the current project construction management Maven project, where the first dependency link includes the package to be changed;

obtaining a mapping rule for converting the package to be changed into an upgrade package;

Modify the first dependent link according to the mapping rule to obtain a second dependent link.

The embodiment of the present application provides an upgrade device, including:

a dependency link obtaining module, used to obtain the first dependency link of the current project construction management Maven project, where the first dependency link includes the package to be changed;

A dependency link parsing module for obtaining the mapping rule for converting the to-be-changed package into an upgrade package;

The dependent link conversion module is configured to modify the first dependent link according to the mapping rule to obtain the second dependent link.

The beneficial effects are as follows:

Because the technical solution provided by the embodiments of the present application parses the dependency link of the current Maven project and the mapping rule of the package to be changed, and modifies the initial dependency link according to the mapping rule, thereby obtaining a stable dependency link and realizing the The upgrade of the initial dependency link solves the problem that the dependency link cannot be automatically upgraded in the Maven project.

Description of drawings

Specific embodiments of the present application will be described below with reference to the accompanying drawings, wherein:

FIG. 1 shows a schematic flowchart of implementing an upgrade method in an embodiment of the present application;

FIG. 2 shows a schematic flowchart of implementing another upgrade method in an embodiment of the present application;

FIG. 3 shows a schematic flowchart of implementing another upgrade method in an embodiment of the present application;

FIG. 4 shows a schematic structural diagram of an upgrading apparatus in an embodiment of the present application;

FIG. 5 shows a schematic structural diagram of another upgrading apparatus in an embodiment of the present application.

Detailed ways

In order to make the technical solutions and advantages of the present application clearer, the exemplary embodiments of the present application will be described in further detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of them. Exhaustive list of examples. Also, the embodiments in this specification and the features of the embodiments may be combined with each other without conflict.

In the process of invention, the inventor noticed that in the existing Maven project, SNAPSHOT may be updated and covered at any time, which leads to online failures, and some Maven projects will directly or indirectly depend on the SNAPSHOT package, which requires Do SNAPSHOT package work on dependent links to upgrade existing dependent links. The current Maven project mentioned in this embodiment refers to the Maven project currently being executed by the system.

Based on this, the embodiments of the present application propose an upgrade method and device, which will be described below.

FIG. 1 shows an upgrade method provided by an embodiment of the present application, as shown in FIG. 1 , including:

Step 101: Obtain the first dependency link of the current project construction management Maven project, where the first dependency link includes the package to be changed;

Step 102, obtaining a mapping rule for converting the package to be changed into an upgrade package;

Step 103: Modify the first dependent link according to the mapping rule to obtain a second dependent link.

The package to be changed in this embodiment includes but is not limited to the SNAPSHOT package, which is not specifically limited in this embodiment.

In another possible implementation manner, the first dependency link relationship of the current Maven project is obtained, including:

Obtain the pom (project object model) file of the current Maven project through the Maven plugin;

Parse the pom file, sequentially acquire each link node of the current Maven project, and obtain the first dependency link of the current Maven project.

In another possible implementation manner, the acquiring a mapping rule for converting the to-be-changed package into an upgrade package includes:

Parse out the to-be-changed packet in the first dependency link;

Obtain the mapping rule of the package to be changed, where the mapping rule includes: if the package to be changed includes a preset suffix name, then correspondingly modify the suffix name of the version number of the package to be changed to the suffix of the upgrade package name, if the preset suffix name is not included in the to-be-changed package, then add the suffix name of the upgrade package after the to-be-changed package;

Confirm the suffix name of the upgrade package corresponding to the to-be-changed package according to the mapping rule of the to-be-changed package.

In another possible implementation manner, modifying the first dependent link according to the mapping rule to obtain a second dependent link, including:

Obtain the pom file corresponding to the jar (archive file) associated with the first dependency link;

Parse out the property list of the pom file corresponding to the jar, and add the built-in variables of the current Maven project to the property list, where the built-in variables of the current Maven project include: organization ID, project ID, and version number;

Modify the version number in the attribute list of the pom file corresponding to the jar according to the mapping rule to obtain a second dependency link.

In another possible implementation manner, before the second dependency link is obtained by modifying the version number in the attribute list of the pom file corresponding to the jar according to the mapping rule, the method further includes:

Obtain all parent pom lists of the pom file corresponding to the jar associated with the first dependency link;

Determine whether there is a parent pom list that needs to be modified, and if so, modify the version number in the attribute list of each pom file under the parent pom list that needs to be modified according to the mapping rule.

In another possible implementation, the method further includes:

Verify whether the MD5 (Message Digest Algorithm, Message Digest Algorithm Version 5) value of the second dependent link is the same as the MD5 value of the first link, and if so, store the second dependent link in the in the Maven repository.

In another possible implementation manner, verifying whether the MD5 value of the second dependent link is the same as the MD5 value of the first link includes:

Obtain the jar that needs to be modified in the first dependency link, and calculate the first MD5 value of the jar that needs to be modified in the first link;

Obtain the jar in the second dependency link corresponding to the modification in the first dependency link, and calculate the second MD5 value of the second link corresponding to the modified jar in the first dependency link;

Determine whether the first MD5 value is the same as the second MD5 value, and if so, confirm that the MD5 value of the second dependent link is the same as the MD5 value of the first link.

Beneficial effect: The technical solution provided by the embodiment of the present application analyzes the dependency link of the current Maven project and the mapping rule of the package to be changed, and modifies the initial dependency link according to the mapping rule, thereby obtaining a stable dependency link and realizing It upgrades the initial dependency link and solves the problem that the dependency link cannot be automatically upgraded in the Maven project.

Referring to FIG. 2, another embodiment of the present application provides an upgrade method. This embodiment provides a specific implementation based on the above-mentioned embodiment. When executing the current Maven project, the following steps can be automatically executed , without human involvement. As shown in Figure 2, the method includes:

Step 201: Obtain the first dependency link of the current Maven project.

In this embodiment, a Maven plug-in is set, and when the Maven project is executed, the plug-in is called, and the pom file (that is, the pom.xml file) of the current Maven project is parsed through the plug-in, and then each link node of the current Maven project is obtained in turn, Get the first dependency link of the current Maven project. Specific methods include:

Step 1) Obtain the pom file of the current Maven project through the Maven plugin;

Step 2) Parse the pom file to obtain the first node that the current Maven project depends on;

Step 3) parsing the first node through the Maven plug-in to obtain the parsing result of the first node;

Step 4) Determine whether there is a dependent node of the first node in the analysis result. If not, then the first node is used as the last dependent node of the current Maven project. If there is, then the first node is used as the dependent node. For the first node, repeat steps 3)-4) until the last dependency node of the current Maven project is found, and the first dependency link of the current Maven project is obtained.

where the pom file is the file in the Maven project. In a Maven project, not just a bunch of files containing code, but also pom files, which are used to manage: source code, configuration files, developer information and roles, issue tracking system, organization identification, project authorization, The dependencies of the project, etc., are consistent with the description of the pom file in the prior art, and are not repeated in this embodiment.

Since the dependencies of the project are stored in the pom file, the dependencies of the project can be obtained by parsing the pom file in the Maven project, one jar (archive file) and one data link. The data of each node is in the form of GroupId (organization ID): artifactId (project ID): Version (version number) combination, such as link:

com.tmall:sak-app:war:1.0-SNAPSHOT->com.tmall:sak-biz-common:jar:1.0-SNAPSHOT->com.taobao.carts:carts-client:jar:1.0.13->com .taobao.trade:tradebase:jar:1.0.37->com.taobao.trade.platform:tp-client:jar:1.4.32->com.taobao.misccenter:misccenter-client:jar:1.5.3.2_ladder- SNAPSHOT->com.taobao.tradesecurity:ts-client:jar:1.0.1-SNAPSHOT->com.taobao.sharereport:share-report-common:jar:1.5.1-SNAPSHOT.

Among them, com.tmall: sak-app: war: 1.0-SNAPSHOT, com.tmall: sak-biz-common: jar: 1.O-SNAPSHOT, com.taobao.trade: tradebase: jar: 1.0.37, etc. are dependencies The node in the link, the packet containing SNAPSHOT is the packet to be changed. In the specific parsing process, the pom file of the current project is obtained through the Maven plug-in, the first node com.tmall:sak-app:war:1.0-SNAPSHOT is parsed from the file, and then the node is parsed to parse the Analyze the result to confirm whether there is a dependent node of the node. If the dependent node of the node is com.tmall:sak-biz-common:jar:1.0-SNAPSHOT, continue to parse the node until it resolves to com .taobao.sharereport: share-report-common: jar: 1.5.1-SNAPSHOT node, if it is found that there is no subsequent dependent node, the analysis of the dependency link is completed, and the above dependent node is obtained.

In addition, it is worth noting that in this embodiment, one jar corresponds to one dependency link. If the current Maven project contains only one jar, the first dependency link includes one, but if the current Maven project includes multiple jars, the first dependency link is Dependent links refer to multiple links, and each link performs the following steps, which are not repeated in this embodiment.

Step 202: Obtain a mapping rule for converting the package to be changed into an upgrade package.

In a specific application, multiple mapping rules may be preset for different packages to be changed, including: if the package to be changed includes a preset suffix name, corresponding to the suffix name of the version number of the package to be changed The suffix name of the upgrade package is modified. If the preset suffix name is not included in the to-be-changed package, the suffix name of the upgrade package is added after the to-be-changed package. For example, each project's SNAPSHOT package has the following rules to be converted into a release package. If the version ends with -SNSPSHOT, change -SNAPSHOT to -mysuffix. If the version ends with .SNAPSHOT, then change .SNAPSHOT to -mysuffix. For other uniforms, add -mysuffix. For example, if the version is 2.0.0, then the changed version is 2.0.0-mysuffix. For other types of packages to be changed, other corresponding mapping rules may also be set, wherein the mapping rules may be stored in a Maven repository, or a file home storage may be created separately, which is not specifically limited in this embodiment.

In this step, after the first link is acquired, the packet to be changed in the first link is parsed, the mapping rule corresponding to the to-be-changed packet is found in a plurality of mapping rules, and the confirmation is confirmed according to the corresponding mapping rule. The suffix name of the corresponding upgrade package. For example, the upgrade package corresponding to the SNAPSHOT package is a release package. The suffix name of the upgrade package is parsed, and the mapping rule for storing the to-be-changed package and its corresponding upgrade package is stored.

In this embodiment, the unstable packet to be changed is converted into a stable packet by modifying the suffix name, so that even if there is a new unstable packet, the packet whose suffix name has been modified will not be overwritten, thus ensuring the stability of the link .

It is worth noting that in this step, only the mapping rule corresponding to the modification is obtained, and the modification of the package is not specifically performed. And in this embodiment, the SNAPSHOT package is removed and converted into a release package as an example, but in different application scenarios, it is not limited to this implementation, and the corresponding mapping rules in other implementations may also be different, This embodiment does not specifically limit this.

Step 203: Obtain all parent pom lists of the poms corresponding to the jars associated with the first dependency link, and determine whether there is a parent pom list that needs to be modified. If yes, go to step 204, otherwise go to step 205.

In this embodiment, if there are multiple dependency links, the pom file of each jar in the dependency link is traversed to obtain all parent pom lists of the pom corresponding to the current jar, where the parent pom list is in the form of GroupId:artifactId: version. Check whether there are packages to be changed in the parent pom list, such as the SNAPSHOT package. If so, confirm that the parent pom list needs to be modified. If there are no packages to be changed, no modification is required.

Step 204: Modify the version number in the attribute list of each pom file under the parent pom list to be modified according to the mapping rule.

In this step, obtain all pom files under the parent pom list to be modified, parse out the property list of each pom file, and add the built-in variables of the current Maven project to the property list. Specifically, for the list of parent poms that need to be modified, traverse down from the top-level pom to obtain the properties (property list) of each pom, the element is //project/properties, and append the built-in variables that come with the Maven project to the In the property list, such as ${project.groupId}, ${project.artifactid}, ${project.version}, etc.

It is worth noting that after adding a variable value, the variable needs to be parsed into constant values in sequence, and the specific parsing process is the same as that in the prior art, which is not repeated in this embodiment.

According to the parsed attribute list, change the version in the current pom file, where the version change is replaced according to the mapping rule obtained in step 202, that is, if the version ends with -SNSPSHOT, change -SNAPSHOT to -mysuffix, if the version ends with .SNAPSHOT At the end, change .SNAPSHOT to -mysuffix, and add -mysuffix to others.

In a possible embodiment, GroupId can be inherited from parent pom, that is, if a current pom has a parent pom, then this current pom does not need to define GroupId, because GroupId will be inherited from parent pom come over. Then when modifying the current pom, if the GroupId is found to be empty, in order to make the process clearer, optionally, add the GroupId of the corresponding parent pom to the current pom. Therefore, when changing the current pom file, if the above situation is encountered, the following three elements <groupId>, <artifacfId>, <version> in the pom file can be changed in sequence. Among them, <artifactId> does not need to be modified, and is directly reserved. The one that may be modified is <groupId>, and the one that must be modified is <version>.

It is worth noting that steps 203-204 in this embodiment are optional, and the parent pom list may not be modified in the actual execution process, but step 205 is directly executed, which is not specifically limited in this embodiment.

Step 205: Obtain the pom file corresponding to the jar associated with the first dependency link, obtain the attribute list of the pom file, and modify the version number in the attribute list of the pom file according to the mapping rule to obtain the second dependency link.

Specifically, the method of obtaining the attribute list of the pom file corresponding to the jar associated with the first dependency link is similar to the method of obtaining the pom file under the parent pom list, including: parsing out the attribute list of the pom file, and retrieving the attribute list of the current Maven project Built-in variables are added to the property list, and the built-in variables of the current Maven project include: organization ID, project ID, and version number.

In this step, according to the parsed attribute list, change <groupId>, <artifactId>, <version> in sequence, wherein the change of version is replaced according to the mapping rule obtained in step 202. This is similar to the modification of the pom file under the parent pom list. , which will not be repeated in this embodiment.

As the link demonstrated in step 201, it is converted to com.tmall:sak-app:war:1.0-mysuffix->com.tmall:sak-biz-common:jar:1.0-mysuffix->com.taobao.carts after the upgrade :carts-client:jar:1.0.13-mysuffix->com.taobao.trade:tradebase:jar:1.0.37-mysuffix->com.taobao.trade.platform:tp-client:jar:1.4.32-mysuffix ->com.taobao.misccenter:misccenter-client:jar:1.5.3.2_ladder-mysuffix->com.taobao.tradesecurity:ts-client:jar:1.0.1-mysuffix->com.taobao.sharereport:share-report -common:jar:1.5.1-mysuffix.

In this embodiment, if a node in the dependent link does not include the to-be-changed packet, no conversion is required. For example, if the dependent link is A->B->C-SNAPHOST->D->E-SNAPSHOT->F->G, then the final result will have the following packages: A-mysuffix->B-mysuffix ->C-mysuffix->D-mysuffix->E-mysuffix->F->G. Among them, A, B, C, D, and E generate 5 new packages, and F and G do not need to generate new packages because they do not depend on any SNAPSHOT version later.

Beneficial effect: In this embodiment, by analyzing the dependency link of the current Maven project and the mapping rule of the package to be changed, and modifying the initial dependency link according to the mapping rule, a stable dependency link is obtained, and the initial dependency link is realized. Upgrade, which solves the problem that dependency links cannot be automatically upgraded in Maven projects.

Referring to FIG. 3 , another embodiment of the present application provides an upgrade method, which is a specific optimization of the implementation details of the embodiment shown in FIG. 2 . As shown in FIG. 3 , the method includes:

Step 301: Obtain the first dependency link of the current Maven project, and store the relevant information of the dependency link in a first folder.

In practical applications, in order to facilitate the subsequent processing of the dependency link, create a corresponding folder, and output the parsed link to the first folder, such as outputting to the dependency.1ist file, the specific naming of the folder. There is no specific limitation in the embodiment. The specific parsing process of the dependent link is similar to step 201 in the foregoing embodiment, which is not repeated in this embodiment.

Step 302: Analyze the first dependency link to obtain a mapping rule for converting the package to be changed into an upgrade package, and store the mapping rule in the second folder.

The step of acquiring the mapping rule in this step is similar to step 202 in the foregoing embodiment, which is not repeated in this embodiment. After the mapping rule is acquired, the rule is separately stored in the second folder, such as the jarRulesMap file.

Step 303: Obtain all parent pom lists of the pom corresponding to the jar associated with the first dependency link, and store all parent pom lists in a third folder.

In this embodiment, if there are multiple dependency links, the pom file of each jar in the dependency link is traversed to obtain all parent pom lists of the pom corresponding to the current jar, where the parent pom list is in the form of Groupid:artifactId: version, and store the parent pom list in the data form of Groupid:artifactId:version in the third folder, such as parentPomList.

Step 304 , traverse the parent list in the third folder to determine whether there is a parent pom list that needs to be modified, if yes, go to step 305 , otherwise go to step 306 .

Check whether there are packages to be changed in the parent pom list, such as the SNAPSHOT package. If so, confirm that the parent pom list needs to be modified. If there are no packages to be changed, no modification is required.

Step 305: Modify the version number in the attribute list of each pom file under the parent pom list to be modified according to the mapping rule.

Step 306: Obtain the pom file corresponding to the jar associated with the first dependency link, obtain the attribute list of the pom file, and modify the version number in the attribute list of the pom file according to the mapping rule to obtain the second dependency link.

The foregoing steps 305 to 306 are similar to the steps 204 to 205 in the embodiment shown in FIG. 2 , which will not be repeated in this embodiment.

Step 307 , verify whether the MD5 value of the second dependent link is the same as the MD5 value of the first link, if so, go to Step 308 , otherwise, return to Step 301 .

In this step, preferably, verifying whether the MD5 value of the second dependent link is the same as the MD5 value of the first link includes: acquiring the jar that needs to be modified in the first dependent link, calculating the first link The first MD5 value of the jar that needs to be modified in the The second MD5 value of the modified jar; determine whether the first MD5 value is the same as the second MD5 value, and if so, confirm that the MD5 value of the second dependent link is the same as the first link's MD5 value. MD5 values are the same.

In this embodiment, the node that does not contain the package to be changed does not need to be modified, so when verifying, only the modified jar in the first dependency link needs to be verified, for example, the dependency link is A->B-> C-SNAPHOST->D->E-SNAPSHOT->F->G, the modified second dependency link is A-mysuffix->B-mysuffix->C-mysuffix->D-mysuffix->E- mysuffix->F->G. Among them, A, B, C, D, E generate new 5 packages, F, G do not need to verify F, G because they do not depend on any SNAPSHOT version later, just verify A, B, C, D , whether the MD5 value of E is the same in the first link and the second link.

In other possible implementations, the regression verification method in the prior art may also be used to verify the first dependent link and the second dependent link, which is not specifically limited in this embodiment.

When the verification result is wrong, an error indication may be popped up, prompting the developer to perform steps 301-307 again, of course, the error indication may not be popped up, and the execution of step 301 may be directly returned, which will not be repeated in this embodiment.

Step 308: Store the second dependency link in the Maven repository.

In this embodiment, in order to improve efficiency and reduce the complexity of code execution, after the upgraded second dependency link is obtained, the dependency link is stored in the Maven repository, so that when other Maven projects include this link , you don't need to re-upgrade, you can call it directly.

Beneficial effect: In this embodiment, by analyzing the dependency link of the current Maven project and the mapping rule of the package to be changed, and modifying the initial dependency link according to the mapping rule, a stable dependency link is obtained, and the initial dependency link is realized. Upgrade, which solves the problem that dependency links cannot be automatically upgraded in Maven projects. In addition, in this embodiment, the intermediate data converted by the link is managed through a folder, the identification path of the intermediate data is clarified, and the execution efficiency of the link upgrade is improved. On the other hand, by upgrading the MD5 value of the link jar, the upgrade link can be verified, which improves the controllability of online risks.

Based on the same inventive concept, the embodiments of the present application also provide an upgrade apparatus. Since the principle of the apparatus for solving problems is similar to that of an upgrade method, the implementation of these apparatuses can be referred to the implementation of the method, and repeated descriptions will not be repeated.

As shown in FIG. 4 , the apparatus may include: a dependent link acquiring module 401 , a dependent link parsing module 402 , and a dependent link converting module 403 .

The dependency link obtaining module 401 is used to obtain the first dependency link of the current project construction management Maven project, and the first dependency link includes the package to be changed;

A dependency link parsing module 402, configured to obtain a mapping rule for converting the to-be-changed package into an upgrade package;

The dependent link conversion module 403 is configured to modify the first dependent link according to the mapping rule to obtain a second dependent link.

Referring to FIG. 5, in another possible implementation manner, the dependent link obtaining module 401 includes:

The first obtaining unit 401a is used to obtain the project object model pom file of the current Maven project through the Maven plug-in;

The first parsing unit 401b is configured to parse the pom file, obtain each link node of the current Maven project in sequence, and obtain the first dependency link of the current Maven project.

Referring to FIG. 5, in another possible implementation manner, the dependency link parsing module 402 includes:

A second parsing unit 402a, configured to parse out the to-be-changed packet in the first dependency link;

The second obtaining unit 402b is configured to obtain the mapping rule of the package to be changed, where the mapping rule includes: if the package to be changed includes a preset suffix name, then the suffix of the version number of the package to be changed is The name is correspondingly modified to the suffix name of the upgrade package. If the preset suffix name is not included in the to-be-changed package, the suffix name of the upgrade package is added after the to-be-changed package;

The confirming unit 402c is configured to confirm the suffix name of the upgrade package corresponding to the to-be-changed package according to the mapping rule of the to-be-changed package.

Referring to FIG. 5, in another possible implementation manner, the dependent link conversion module 403 includes:

A third obtaining unit 403a, configured to obtain the pom file corresponding to the archive file jar associated with the first dependency link;

The third parsing unit 403b is configured to parse out the property list of the pom file corresponding to the jar, and add the built-in variables of the current Maven project to the property list, where the built-in variables of the current Maven project include: organization logo, project logo and version number;

The modifying unit 403c is configured to modify the version number in the attribute list of the pom file corresponding to the jar according to the mapping rule to obtain a second dependency link.

Referring to FIG. 5, in another possible implementation manner, the dependent link conversion module 403 further includes:

a fourth obtaining unit 403d, configured to obtain all parent pom lists of the pom files corresponding to the jars associated with the first dependency link before the modification unit 403c obtains the second dependency link;

The modifying unit 403c is further configured to determine whether there is a parent pom list that needs to be modified, and if so, modify the version number in the attribute list of each pom file under the parent pom list that needs to be modified according to the mapping rule.

Referring to FIG. 5, in another possible implementation manner, the apparatus further includes:

Verification module 404, configured to verify whether the MD5 value of the message digest algorithm version 5 of the second dependent link is the same as the MD5 value of the first link, and if so, store the second dependent link in the in the Maven repository.

Referring to FIG. 5, in another possible implementation manner, the verification module 404 includes:

a fifth obtaining unit 404a, configured to obtain the jar that needs to be modified in the first dependency link, and calculate the first MD5 value of the jar that needs to be modified in the first link;

The sixth obtaining unit 404b is configured to obtain the modified jar in the second dependent link corresponding to the first dependent link, and calculate the modified jar corresponding to the first dependent link in the second link. The second MD5 value of the jar;

A verification unit 404c, configured to judge whether the first MD5 value obtained by the fifth obtaining unit is the same as the second MD5 value obtained by the sixth obtaining unit, and if they are the same, then confirm the MD5 value of the second dependent link The same as the MD5 value of the first link.

Beneficial effect: In this embodiment, by analyzing the dependency link of the current Maven project and the mapping rule of the package to be changed, and modifying the initial dependency link according to the mapping rule, a stable dependency link is obtained, and the initial dependency link is realized. Upgrade, which solves the problem that dependency links cannot be automatically upgraded in Maven projects.

For the convenience of description, each part of the device described above is divided into various modules or units by function and described respectively. Of course, when implementing the present application, the functions of each module or unit may be implemented in one or more software or hardware.

As will be appreciated by those skilled in the art, the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

While the preferred embodiments of the present application have been described, additional changes and modifications to these embodiments may occur to those skilled in the art once the basic inventive concepts are known. Therefore, the appended claims are intended to be construed to include the preferred embodiment and all changes and modifications that fall within the scope of this application.

Claims (10)

1. An upgrade method, comprising the steps of:

acquiring a first dependent link of a current project construction management Maven project, wherein the first dependent link comprises a packet to be changed;

the obtaining of the mapping rule for converting the package to be changed into the upgrade package includes: analyzing the packet to be changed in the first dependent link; obtaining a mapping rule corresponding to the packet to be changed, wherein the mapping rule comprises: if the packet to be changed comprises a preset suffix name, correspondingly modifying the suffix name of the version number of the packet to be changed into the suffix name of an upgrade packet, and if the packet to be changed does not comprise the preset suffix name, adding the suffix name of the upgrade packet after the packet to be changed; confirming the suffix name of the upgrading packet corresponding to the packet to be changed according to the mapping rule of the packet to be changed;

modifying the first dependent link according to the mapping rule to obtain a second dependent link, wherein the method comprises the steps of obtaining a pom file corresponding to an archive file jar associated with the first dependent link; analyzing an attribute list of a pom file corresponding to the jar, and adding the built-in variables of the current Maven project into the attribute list, wherein the built-in variables of the current Maven project comprise: organization identity, item identity, and version number.

2. The method of claim 1, wherein the obtaining the first dependency link relationship for the current Maven project comprises:

acquiring a project object model (pom) file of a current Maven project through a Maven plug-in; and analyzing the pom file, and sequentially acquiring each link node of the current Maven project to obtain a first dependent link of the current Maven project.

3. The method of claim 1, wherein before modifying the version number in the pom file attribute list corresponding to jar according to the mapping rule to obtain the second dependent link, the method further comprises:

acquiring all father pom lists of pom files corresponding to jar associated with the first dependent link;

and judging whether a parent pom list needing to be modified exists, and if so, modifying the version number in each pom file attribute list under the parent pom list needing to be modified according to the mapping rule.

4. The method of claim 1, wherein the method further comprises:

verifying whether the MD5 value of the fifth version of the message digest algorithm of the second dependent link is the same as the MD5 value of the first dependent link, and if so, storing the second dependent link into a Maven warehouse.

5. The method of claim 4, wherein verifying whether the MD5 value of the second dependent link is the same as the MD5 value of the first dependent link comprises:

acquiring jar needing to be modified in the first dependent link, and calculating a first MD5 value of the jar needing to be modified in the first dependent link;

acquiring jar corresponding to the modification in the first dependent link in the second dependent link, and calculating a second MD5 value corresponding to the modified jar in the first dependent link in the second dependent link;

and judging whether the first MD5 value is the same as the second MD5 value, and if so, confirming that the MD5 value of the second dependent link is the same as the MD5 value of the first dependent link.

6. An upgrade apparatus, comprising:

the system comprises a dependent link acquisition module, a mapping module and a mapping module, wherein the dependent link acquisition module is used for acquiring a first dependent link of a current project construction management Maven project, and the first dependent link comprises a packet to be changed;

the dependent link analysis module is used for acquiring a mapping rule for converting the packet to be changed into an upgrading packet; wherein the dependent link parsing module comprises: the second analysis unit is used for analyzing the packet to be changed in the first dependent link; a second obtaining unit, configured to obtain a mapping rule of the packet to be changed, where the mapping rule includes: if the packet to be changed comprises a preset suffix name, correspondingly modifying the suffix name of the version number of the packet to be changed into the suffix name of an upgrade packet, and if the packet to be changed does not comprise the preset suffix name, adding the suffix name of the upgrade packet after the packet to be changed; the confirming unit is used for confirming the suffix name of the upgrading packet corresponding to the packet to be changed according to the mapping rule of the packet to be changed;

the dependent link conversion module is used for modifying the first dependent link according to the mapping rule to obtain a second dependent link;

wherein the dependent link conversion module comprises: a third obtaining unit, configured to obtain a pom file corresponding to the archived file jar associated with the first dependency chain; a third parsing unit, configured to parse an attribute list of a pom file corresponding to the jar, and add a built-in variable of the current Maven project to the attribute list, where the built-in variable of the current Maven project includes: organization identity, item identity, and version number.

7. The apparatus of claim 6, wherein the dependent link acquisition module comprises:

the system comprises a first obtaining unit, a second obtaining unit and a third obtaining unit, wherein the first obtaining unit is used for obtaining a project object model pom file of the current Maven project through a Maven plug-in;

and the first analysis unit is used for analyzing the pom file, sequentially acquiring each link node of the current Maven project and acquiring a first dependent link of the current Maven project.

8. The apparatus of claim 7, wherein the dependent link translation module further comprises:

a fourth obtaining unit, configured to obtain all parent pom lists of pom files corresponding to jar associated with the first dependent link before the modifying unit obtains the second dependent link;

and the modifying unit is also used for judging whether a parent pom list needing to be modified exists, and if so, modifying the version number in each pom file attribute list under the parent pom list needing to be modified according to the mapping rule.

9. The apparatus of claim 6, wherein the apparatus further comprises:

and the verification module is used for verifying whether the MD5 value of the fifth version of the message digest algorithm of the second dependent link is the same as the MD5 value of the first dependent link, and if so, storing the second dependent link into a Maven warehouse.

10. The apparatus of claim 9, wherein the authentication module comprises:

a fifth obtaining unit, configured to obtain jar needing to be modified in the first dependent link, and calculate a first MD5 value of jar needing to be modified in the first dependent link;

a sixth obtaining unit, configured to obtain jar corresponding to the modification in the first dependent link in the second dependent link, and calculate a second MD5 value corresponding to the modified jar in the first dependent link in the second dependent link;

and the verification unit is used for judging whether the first MD5 value acquired by the fifth acquisition unit is the same as the second MD5 value acquired by the sixth acquisition unit, and if so, confirming that the MD5 value of the second dependent link is the same as the MD5 value of the first dependent link.

Images