CN112506560A - Microservice JAR packet management method and device and computer equipment - Google Patents
Microservice JAR packet management method and device and computer equipment Download PDFInfo
- Publication number
- CN112506560A CN112506560A CN202011473399.7A CN202011473399A CN112506560A CN 112506560 A CN112506560 A CN 112506560A CN 202011473399 A CN202011473399 A CN 202011473399A CN 112506560 A CN112506560 A CN 112506560A
- Authority
- CN
- China
- Prior art keywords
- jar package
- service module
- new
- jar
- basic framework
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims description 27
- 238000000034 method Methods 0.000 claims abstract description 26
- 238000012360 testing method Methods 0.000 claims description 17
- 230000002159 abnormal effect Effects 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 4
- 238000005096 rolling process Methods 0.000 claims description 3
- 238000000605 extraction Methods 0.000 claims description 2
- 230000010354 integration Effects 0.000 claims description 2
- 238000011161 development Methods 0.000 abstract description 3
- 238000001514 detection method Methods 0.000 description 12
- 230000008569 process Effects 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention relates to the technical field of JAVA application development and discloses a method and a device for managing a JAR packet of a micro-service and computer equipment. The method comprises the following steps: extracting a new JAR packet to be introduced into a service module; adding the new JAR package to the current basic framework of the project; the basic framework is a set of JAR packages quoted by all service modules in the project; respectively integrating the basic framework containing the new JAR package into each service module in the project; and respectively operating each service module integrating the basic framework containing the new JAR package, and if each service module is successfully operated, taking the basic framework containing the new JAR package as the new basic framework of the project. The embodiment of the invention can reduce the burden of developers in JAR package version management.
Description
Technical Field
The invention relates to the technical field of JAVA application development, in particular to a method and a device for managing a JAR packet of a micro-service and computer equipment.
Background
Micro-services are an architectural solution for building applications, which, unlike the more traditional monolithic solution, can split an application into multiple core functions, each of which is called a service, and can be built and deployed separately, which means that the services do not affect each other when working (and failing).
But it is this that causes a project (or application) to be split into multiple microservices, and some common projects may be split into tens or even hundreds of microservices. Each individual microservice needs to reference multiple three-party open source JAR (english acronym for Java Archive) packages. The JAR package is a combination of a series of JAVA files into a single compressed file. Before JAR files, the Web browser must repeatedly request the Web server many times in order to download all the files that make up a "program" (Applet). In addition, each file is uncompressed. After all these files are merged into one JAR file, only one request needs to be sent to the remote server. Meanwhile, due to the adoption of a compression technology, all files can be obtained in a shorter time. If one micro service references n three-party open source JAR packages, and one three-party open source JAR package has m versions, the three-party open source JAR package which one micro service may reference finally has n × m JAR package version combinations, and then the problem of version conflict of various JAR packages occurs. In the prior art, a developer needs to manually solve the problem of version conflict of the JAR package, and the operation is complex and time-consuming, so that the burden of the developer needs to be reduced urgently.
Disclosure of Invention
In view of this, an object of the embodiments of the present application is to provide a method and an apparatus for managing a microservice JAR package, and a computer device, which can reduce the burden of developers in managing the JAR package version.
In order to solve the above technical problem, an embodiment of the present invention provides a microservice JAR package management method, including:
extracting a new JAR packet to be introduced into a service module;
adding the new JAR package to a current basic frame of the project; the basic framework is a set of JAR packages quoted by all service modules in the project;
respectively integrating the basic framework containing the new JAR package into each service module in the project;
and respectively operating each service module integrating the basic framework containing the new JAR package, and if each service module is successfully operated, taking the basic framework containing the new JAR package as the new basic framework of the project.
The embodiment of the invention also provides a device for managing the JAR packet of the microservice, which comprises the following components:
the extraction module is used for extracting a new JAR packet to be introduced into the service module;
the adding module is used for adding the new JAR package into the current basic framework of the project; the basic framework is a set of JAR packages quoted by all service modules in the project;
the integration module is used for respectively integrating the basic framework containing the new JAR package into each service module in the project;
and the determining module is used for respectively operating each service module integrated with the basic framework containing the new JAR package, and if each service module is successfully operated, the basic framework containing the new JAR package is used as the new basic framework of the project.
An embodiment of the present invention also provides a computer device, including: a memory storing a computer program and a processor running the computer program to implement the micro-service JAR package management method as described above.
Compared with the prior art, the method and the device have the advantages that JAR packages needing to be quoted by all business modules (or called micro-services) under a project (or application) are uniformly added into the basic framework, when the business modules need to quote the new JAR packages, the new JAR packages needing to be introduced are extracted and added into the current basic framework, then the basic framework containing the new JAR packages is respectively integrated into the business modules in the project, whether the new JAR packages conflict with other JAR packages in the original basic framework is determined according to whether the business modules can run successfully or not, accordingly, the version conflict problem of the introduced new JAR packages can be automatically detected, compared with manual detection, the load of developers for detecting the version conflict of the JAR packages is reduced, and meanwhile, the new basic framework can be used for citing more business modules after one-time detection is successful.
In addition, the integrating the basic framework containing the new JAR package into each business module in the project respectively comprises:
and after trial compiling the basic framework containing the new JAR package, respectively integrating the compiled basic framework into the service codes of each service module.
In addition, the respectively operating each service module that integrates the basic framework including the new JAR package includes:
and respectively performing trial compilation on each service module integrating the basic framework containing the new JAR package, if the trial compilation is passed, performing containerization release trial operation on the service module passed by the trial compilation, and if the trial operation is successful, determining that no JAR package conflict exists in the service module passed by the trial operation.
In addition, still include:
if the trial compilation of the service module fails or if the trial operation of the service module fails, rolling back the basic framework and the state of each service module before the new JAR packet is added.
In addition, still include:
if the trial compilation of the service module fails or if the trial operation of the service module fails, backing up the service code of the service module to a code abnormal area in the containerized issuing trial operation environment, and backing up the basic frame containing the new JAR packet to a frame abnormal area.
In addition, still include:
if the trial operation of the service module fails, generating a trial operation error report of the service module;
the commissioning error report includes one or any combination of the following: and the service module is used for storing the service module in the test run, the processor in the test run, the test run time, the version information of the new JAR packet and the test run error information.
In addition, the JAR package is: a tripartite open source JAR package and/or a custom JAR package.
In addition, adding the new JAR package to the current basic framework of the project, including:
and if the version of the JAR package contained in the current basic framework is lower than that of the new JAR package, replacing the JAR package with the lower version by the new JAR package.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, it is understood that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a microservice JAR package management method according to a first embodiment of the present invention;
FIG. 2 is a flowchart of a method for managing a microservice JAR package according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a microservice JAR package management apparatus according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of a computer device according to four embodiments of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, it will be appreciated by those of ordinary skill in the art that numerous technical details are set forth in order to provide a better understanding of the present invention in its various embodiments. However, the technical solution claimed in the present invention can be implemented without these technical details and various changes and modifications based on the following embodiments.
The embodiment of the application provides a method for managing a micro-service JAR package. As shown in fig. 1, the microservice JAR package management method of the present embodiment includes steps 101 to 104.
Step 101: and extracting a new JAR packet to be introduced into the service module.
Step 102: and adding the new JAR package into the current basic framework of the project.
Wherein the base framework is a collection of JAR packages referenced by all business modules in the project.
In this embodiment, the project is a distributed project, one distributed project is split into a plurality of microservices, and each microservice is a business module. The project has a base framework that is a collection of JAR packages referenced by all business modules under the project, in other words, all business modules under the project inherit the base framework. Optionally, the JAR package in the basic framework may be a developer-defined JAR package or a three-party open source JAR package, and the three-party open source JAR package may be an open source JAR package provided by companies such as APPACHE and SUN. In addition, the basic framework may further include a package customized by a developer inside other enterprises and some personalized application implementation schemes, and the embodiment does not specifically limit the content in the basic framework.
Optionally, step 102 adds the new JAR package to the current base framework of the project, including: and if the version of the JAR package contained in the current basic framework is lower than that of the new JAR package, replacing the JAR package with the lower version with the new JAR package. For example, different business modules such as group chatting, bank cards and coupons exist under the WeChat item, and the JAR packages quoted by the business modules include three-party open source JAR packages such as a.jar, b.jar and c.jar. The new JAR package introduced at this time is a.jar, but the version of the new JAR package is 5, and the version of the JAR package a.jar in the current basic framework is 4, that is, the version of the a.jar contained in the current basic framework is lower than that of the new JAR package, before the new JAR package is added into the current basic framework, the JAR package of the a.jar of the version 4 is directly deleted, and then the new JAR package of the a.jar of the version 5 is copied into the current basic framework, so that all service modules under the project adopt the same JAR package of a higher version, thereby realizing the unified management of the JAR packages of all the service modules, and the unified management of the JAR packages can avoid the repetitive work which may occur when the conflict detection of the JAR packages is independently carried out on each service module. For example, the service module 1 and the service module 2 respectively refer to two JAR packages, and versions of each JAR package are different, for example, the service module 1 refers to a1.JAR and a b3.JAR, and the service module 2 refers to a2.JAR and a b2.JAR, version conflict detection needs to be performed on the two JAR packages, such as a1.JAR and a b3.JAR, referred to by the service module 1, and version conflict detection needs to be performed on the two JAR packages, such as a2.JAR and a b2.JAR, referred to by the service module 2, at the same time. Therefore, the process of carrying out conflict detection on JAR package versions with different high and low versions is avoided.
Step 103: and respectively integrating the basic frameworks containing the new JAR packages into all service modules in the project.
Optionally, step 103 comprises: and after trial compilation of the basic framework containing the new JAR package is passed, respectively integrating the compiled basic framework into the service codes of each service module. Specifically, after the new JAR package extracted in step 101 is added to the current base framework (denoted as base.jar), the base framework to which the new JAR package is added is compiled, the compiled base framework may be named as base.try.jar, and then the base.try.jar is integrated into the service codes of all service modules under the project.
Step 104: and respectively operating each service module integrating the basic framework containing the new JAR package, and if each service module is successfully operated, taking the basic framework containing the new JAR package as the new basic framework of the project.
Optionally, the respectively running the service modules that integrate the base framework including the new JAR package includes: and respectively performing trial compilation on each service module which integrates the basic framework containing the new JAR package, if the trial compilation is passed, performing containerization issuing trial operation on the service module which passes the trial compilation, and if the trial operation is successful, determining that no JAR package conflict exists in the service module which passes the trial operation. If all the service modules are successfully tried, the new JAR packet is considered to be not conflicted with other JAR packets in the basic framework, at this time, base. In this embodiment, in the process of performing trial compilation on each service module that integrates the basic framework including the new JAR package, most of the JAR package conflict problems can be detected through errors in the compilation process, while in the process of performing containerization release trial operation on each service module, some of the JAR package version conflict problems can be detected, and the containerization release trial operation is more comprehensive in function test on the service module than performing gray level test on sample module codes. The JAR packet collision detection in the service module compiling stage may be performed by using a detection method known to those skilled in the art, and is not described herein again. It should be noted that the commissioning method for the service module is not limited to the containerization publishing technology.
Optionally, in this embodiment, if the trial compilation of the service module fails or if the trial operation of the service module fails, the base frame and the service modules are rolled back to the state before the new JAR package is added. Thereby avoiding occupying system resources for a long time.
According to the microservice JAR package management method, after the new JAR package needing to be introduced is extracted, the new JAR package is added into the basic framework, the basic framework containing the new JAR package is integrated into the business codes of all business modules under the project, and then conflict detection of JAR package versions in the basic framework is achieved through respective trial operation of the business modules. Moreover, each service module inherits the basic framework, a new JAR package is not independently introduced, and only the higher version of each JAR package is reserved in the basic framework, so that the problem of dependency conflict among the JAR packages in the basic framework only needs to be detected, and the JAR package management burden of the whole project is favorably reduced.
A second embodiment of the present application provides a method for managing a microservice JAR package, which is improved based on the foregoing embodiments, and the main improvements are as follows: in this embodiment, a commissioning error report of a service module is generated when the commissioning of the service module fails.
As shown in fig. 2, the method for managing a microservice JAR package in this embodiment includes steps 201 to 205, where steps 201 to 204 are respectively the same as steps 101 to 104 of the first embodiment, and are not described herein again.
Step 205: and if the trial operation of the service module fails, generating a trial operation error report of the service module. The commissioning error report may include one or any combination of the following: the service module is used for storing the service module in the test run, the processor (CPU) in the test run, the test run time, the version information of the new JAR packet and the test run error information. Optionally, the trial-run error report may also be sent to a developer mailbox in step 205, so that the developer can analyze the cause of the JAR package version conflict according to the trial-run error report. After the service code of the service module which fails to be operated in the trial mode is upgraded, the service module can be recompiled and operated in the trial mode again, so that all the service modules can be operated successfully.
Optionally, in some examples, step 205 may further include: if the trial compilation of the service module fails or if the trial operation of the service module fails, the service code of the service module is backed up to the code abnormal area in a containerized issuing trial operation environment, and the basic framework containing the new JAR packet is backed up to the framework abnormal area, so that a developer can conveniently analyze the error reason in the follow-up process through the service code and the basic framework with errors.
According to the microservice JAR package management method, after the new JAR package needing to be introduced is extracted, the new JAR package is added into the basic framework, the basic framework containing the new JAR package is integrated into the business codes of all business modules under the project, and then conflict detection of JAR package versions in the basic framework is achieved through respective trial operation of the business modules. Moreover, each service module inherits the basic framework, a new JAR package is not independently introduced, and only the higher version of each JAR package is reserved in the basic framework, so that the problem of dependency conflict among the JAR packages in the basic framework only needs to be detected, and the JAR package management burden of the whole project is favorably reduced. In addition, the embodiment facilitates the developer to analyze the cause of the JAR package version conflict by generating a service module trial run error report and the like, and is beneficial to further reducing the burden of the developer.
The third embodiment of the present application further provides a microservice JAR package management apparatus 300, where the apparatus 300 includes:
the extracting module 301 is configured to extract a new JAR packet to be introduced into the service module.
An adding module 302, configured to add the new JAR package to the current basic framework of the project; wherein the base framework is a collection of JAR packages referenced by all business modules in the project.
And the integrating module 303 is used for integrating the basic framework containing the new JAR package into each service module in the project respectively.
The determining module 304 is configured to run each service module that integrates the basic framework including the new JAR package, respectively, and if each service module runs successfully, take the basic framework including the new JAR package as the new basic framework of the project.
Optionally, respectively integrating the basic framework containing the new JAR package into each service module in the project, including: and after trial compilation of the basic framework containing the new JAR package is passed, respectively integrating the compiled basic framework into the service codes of each service module.
Optionally, running each service module integrating the basic framework including the new JAR package respectively comprises: and respectively performing trial compilation on each service module which integrates the basic framework containing the new JAR package, if the trial compilation is passed, performing containerization issuing trial operation on the service module which passes the trial compilation, and if the trial operation is successful, determining that no JAR package conflict exists in the service module which passes the trial operation.
Optionally, the apparatus 300 of this embodiment may further include: and the rollback module is used for rolling back the basic framework and the states of the service modules before the new JAR package is added if the trial compilation of the service modules fails or if the trial operation of the service modules fails.
Optionally, the apparatus 300 of this embodiment may further include:
and the backup module is used for backing up the service codes of the service modules to the code abnormal area in a containerization release trial operation environment and backing up the basic frameworks containing the new JAR packages to the framework abnormal area if the trial compilation of the service modules fails or if the trial operation of the service modules fails.
Optionally, the apparatus 300 of the embodiment may further include:
the report generation module is used for generating a trial operation error report of the service module if the trial operation of the service module fails; the commissioning error report includes one or any combination of the following: the service module is used for storing the service module in the test run, the processor, the test run time, the version information of the new JAR packet and the test run error information.
Optionally, the JAR package is: a tripartite open source JAR package and/or a custom JAR package.
Optionally, the adding module 302 is configured to replace the JAR package with the lower version with the new JAR package if the version of the JAR package included in the current base framework is lower than the version of the new JAR package.
According to the microservice JAR package management device, after the new JAR package needing to be introduced is extracted, the new JAR package is added into the basic framework, the basic framework containing the new JAR package is integrated into the business codes of all business modules under the project, and then conflict detection of JAR package versions in the basic framework is achieved through respective trial operation of the business modules. Moreover, each service module inherits the basic framework, a new JAR package is not independently introduced, and only the higher version of each JAR package is reserved in the basic framework, so that the problem of dependency conflict among the JAR packages in the basic framework only needs to be detected, and the JAR package management burden of the whole project is favorably reduced. In addition, the embodiment facilitates the developer to analyze the cause of the JAR package version conflict by generating a service module trial run error report and the like, and is beneficial to further reducing the burden of the developer.
An embodiment of the present application further provides a computer device, as shown in fig. 4, the computer device includes: memory 402, processor 401;
wherein the memory 402 stores instructions executable by the at least one processor 401, and the instructions are executed by the at least one processor 401 to implement the microservice JAR package management method according to the foregoing embodiment.
The computer device includes one or more processors 401 and a memory 402, one processor 401 being exemplified in fig. 4. The processor 401 and the memory 402 may be connected by a bus or other means, and fig. 4 illustrates the connection by a bus as an example. Memory 402, which is a non-volatile computer-readable storage medium, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The processor 401 executes various functional applications and data processing of the device by running the nonvolatile software programs, instructions, and modules stored in the memory 402, that is, implements the above-described microservice JAR package management method.
The memory 402 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function, and the like. Further, the memory 402 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
One or more modules are stored in the memory 402 and, when executed by the one or more processors 401, perform the microservice JAR package management method of any of the method embodiments described above.
The above-mentioned device can execute the method provided by the embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method, and reference may be made to the method provided by the embodiment of the present invention for technical details that are not described in detail in the embodiment.
According to the microservice JAR package management method, after the new JAR package needing to be introduced is extracted, the new JAR package is added into the basic framework, the basic framework containing the new JAR package is integrated into the business codes of all business modules under the project, and then conflict detection of JAR package versions in the basic framework is achieved through respective trial operation of the business modules. Moreover, each service module inherits the basic framework, a new JAR package is not independently introduced, and only the higher version of each JAR package is reserved in the basic framework, so that the problem of dependency conflict among the JAR packages in the basic framework only needs to be detected, and the JAR package management burden of the whole project is favorably reduced. In addition, the embodiment facilitates the developer to analyze the cause of the JAR package version conflict by generating a service module trial run error report and the like, and is beneficial to further reducing the burden of the developer.
An embodiment of the present application further provides a non-volatile storage medium for storing a computer-readable program, where the computer-readable program is used for a computer to execute some or all of the above method embodiments.
That is, those skilled in the art can understand that all or part of the steps in the method according to the above embodiments may be implemented by a program instructing related hardware, where the program is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, etc.) or a processor (processor) to execute all or part of the steps in the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples for carrying out the invention, and that various changes in form and details may be made therein without departing from the spirit and scope of the invention in practice.
Claims (10)
1. A method for managing a micro-service JAR package is characterized by comprising the following steps:
extracting a new JAR packet to be introduced into a service module;
adding the new JAR package to a current basic frame of the project; the basic framework is a set of JAR packages quoted by all service modules in the project;
respectively integrating the basic framework containing the new JAR package into each service module in the project;
and respectively operating each service module integrating the basic framework containing the new JAR package, and if each service module is successfully operated, taking the basic framework containing the new JAR package as the new basic framework of the project.
2. The method according to claim 1, wherein the integrating the base framework including the new JAR package into the service modules in the project comprises:
and after trial compiling the basic framework containing the new JAR package, respectively integrating the compiled basic framework into the service codes of each service module.
3. The method according to claim 1, wherein the respectively running each of the service modules that incorporate a base framework including the new JAR package comprises:
and respectively performing trial compilation on each service module integrating the basic framework containing the new JAR package, if the trial compilation is passed, performing containerization release trial operation on the service module passed by the trial compilation, and if the trial operation is successful, determining that no JAR package conflict exists in the service module passed by the trial operation.
4. The microservice JAR package management method of claim 3, further comprising:
if the trial compilation of the service module fails or if the trial operation of the service module fails, rolling back the basic framework and the state of each service module before the new JAR packet is added.
5. The microservice JAR package management method of claim 3, further comprising:
if the trial compilation of the service module fails or if the trial operation of the service module fails, backing up the service code of the service module to a code abnormal area in the containerized issuing trial operation environment, and backing up the basic frame containing the new JAR packet to a frame abnormal area.
6. The microservice JAR package management method of claim 3, further comprising:
if the trial operation of the service module fails, generating a trial operation error report of the service module;
the commissioning error report includes one or any combination of the following: and the service module is used for storing the service module in the test run, the processor in the test run, the test run time, the version information of the new JAR packet and the test run error information.
7. The method of managing a microservice JAR package of claim 1, wherein the JAR package is: a tripartite open source JAR package and/or a custom JAR package.
8. The microservice JAR package management method of any of claims 1 to 7 wherein adding the new JAR package to a project's current base framework comprises:
and if the version of the JAR package contained in the current basic framework is lower than that of the new JAR package, replacing the JAR package with the lower version by the new JAR package.
9. A microservice JAR package management apparatus, comprising:
the extraction module is used for extracting a new JAR packet to be introduced into the service module;
the adding module is used for adding the new JAR package into the current basic framework of the project; the basic framework is a set of JAR packages quoted by all service modules in the project;
the integration module is used for respectively integrating the basic framework containing the new JAR package into each service module in the project;
and the determining module is used for respectively operating each service module integrated with the basic framework containing the new JAR package, and if each service module is successfully operated, the basic framework containing the new JAR package is used as the new basic framework of the project.
10. A computer device, comprising: a memory storing a computer program and a processor running the computer program to implement the microservice JAR package management method of any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011473399.7A CN112506560A (en) | 2020-12-15 | 2020-12-15 | Microservice JAR packet management method and device and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011473399.7A CN112506560A (en) | 2020-12-15 | 2020-12-15 | Microservice JAR packet management method and device and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112506560A true CN112506560A (en) | 2021-03-16 |
Family
ID=74973343
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011473399.7A Pending CN112506560A (en) | 2020-12-15 | 2020-12-15 | Microservice JAR packet management method and device and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112506560A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090327358A1 (en) * | 2008-06-26 | 2009-12-31 | Microsoft Corporation | Resolving conflicts in content management systems |
| CN108182068A (en) * | 2017-12-26 | 2018-06-19 | 杭州数梦工场科技有限公司 | The generation method of part and device, storage medium are delivered in deployment based on micro services |
| CN108595337A (en) * | 2018-05-07 | 2018-09-28 | 杭州有赞科技有限公司 | A kind of operation method and system of Jar packets |
| CN111198708A (en) * | 2018-11-16 | 2020-05-26 | 北京奇虎科技有限公司 | Method and device for solving conflict of jar packets |
| CN111414193A (en) * | 2020-02-26 | 2020-07-14 | 平安银行股份有限公司 | Method for implementing service system based on micro-service framework and related device |
| CN111666079A (en) * | 2019-03-05 | 2020-09-15 | 北京京东尚科信息技术有限公司 | Method, device, system, equipment and computer readable medium for software upgrading |
-
2020
- 2020-12-15 CN CN202011473399.7A patent/CN112506560A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090327358A1 (en) * | 2008-06-26 | 2009-12-31 | Microsoft Corporation | Resolving conflicts in content management systems |
| CN108182068A (en) * | 2017-12-26 | 2018-06-19 | 杭州数梦工场科技有限公司 | The generation method of part and device, storage medium are delivered in deployment based on micro services |
| CN108595337A (en) * | 2018-05-07 | 2018-09-28 | 杭州有赞科技有限公司 | A kind of operation method and system of Jar packets |
| CN111198708A (en) * | 2018-11-16 | 2020-05-26 | 北京奇虎科技有限公司 | Method and device for solving conflict of jar packets |
| CN111666079A (en) * | 2019-03-05 | 2020-09-15 | 北京京东尚科信息技术有限公司 | Method, device, system, equipment and computer readable medium for software upgrading |
| CN111414193A (en) * | 2020-02-26 | 2020-07-14 | 平安银行股份有限公司 | Method for implementing service system based on micro-service framework and related device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Wu et al. | UML-based integration testing for component-based software | |
| KR101687213B1 (en) | Dynamically loading graph-based computations | |
| US8924944B2 (en) | Implementation of distributed methods that support generic functions | |
| US7124060B1 (en) | Method for isolating a fault from error messages | |
| US8285662B2 (en) | Framework for delta analysis during automated builds | |
| CN101002174B (en) | Method for loading software with an intermediate object oriented language in a portable device | |
| CN111897548B (en) | Front-end resource issuing method and device, electronic equipment and computer storage medium | |
| US10083029B2 (en) | Detect application defects by correlating contracts in application dependencies | |
| CN112099880B (en) | Method and system for reducing application program driven by scene | |
| US10073686B1 (en) | Function serialization for inter-thread messaging | |
| WO2022038461A1 (en) | Method and system for identifying and extracting independent services from a computer program | |
| CN113050984A (en) | Resource calling method and device, electronic equipment and storage medium | |
| CN115220863A (en) | Operation and maintenance method and device for container application, computer equipment and storage medium | |
| CN111352631B (en) | Interface compatibility detection method and device | |
| Brada et al. | Practical verification of component substitutability using subtype relation | |
| CN108228266A (en) | Start the method and apparatus of Fragment components under a kind of Android card cages between different plug-in units | |
| US9396239B2 (en) | Compiling method, storage medium and compiling apparatus | |
| CN112506560A (en) | Microservice JAR packet management method and device and computer equipment | |
| CN116599881A (en) | Cloud platform tenant modeling test method, device, equipment and storage medium | |
| CN112328241B (en) | Method and device for creating Android library module dependency relationship in application program development | |
| CN115033489A (en) | Code resource detection method and device, electronic equipment and storage medium | |
| US20050034120A1 (en) | Systems and methods for cooperatively building public file packages | |
| CN111273940B (en) | Method and device for uploading program file to code warehouse | |
| CN113791824A (en) | Peripheral driver loading method, system and medium for terminal equipment | |
| CN103577170A (en) | Construction method and construction device for web application |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |