Multi-module project source code separation method and device

Abstract

The embodiment of the invention provides a multi-module project source code separation method and equipment. The method comprises the steps of obtaining a source code file set related to a target project, wherein the source code file set is developed based on a multi-module framework; based on the source code file set, identifying a source code file actually used by the target project and judging a redundant file; and deleting the redundant file from the source code file set so as to separate the source code of the target project. By means of the method, convenience brought by module development can be enjoyed, the target source code with the complete function can be conveniently separated from a large-size multi-module project, and the input and maintenance cost is low when the source code is separated.

Description

technical field [0001] Embodiments of the present invention relate to the field of computer technology, and in particular, to a method and device for separating source code of a multi-module project. Background technique [0002] At present, both companies and individual developers basically use a modular approach to develop projects. This development method has many advantages: clear division of labor, which can be developed collaboratively; single responsibility, which can reduce code coupling; code reuse, which can reduce duplication of code. [0003] The public modules in modular development are a collection of a large number of public methods. These public methods have a single responsibility and a clear division of labor, just like the basic building blocks in building blocks, which are used frequently and in large numbers. The difference between public methods and public building blocks is that as many building blocks need to be produced as the public building blocks...

AI Technical Summary

Problems solved by technology

Public modules contain a large amount of public code, and only a part of it is used by a single system. If the unused code is also included in the source code of a single system, the unused code and the comments in the code will expose some unnecessary information , which will also cause the volume of the delivered source code to be bloated

[0005] At this time, it often takes a lot of manpower to do manual deletion and code adaptation

If there is a change in requirements, the manpower investment will increase exponentially; if the separated code is developed separately, it is not conducive to synchronizing the latest public module code with other projects, and if the branch is developed separately, it will consume Excessive time cost in synchronizing code changes to branches with little difference

Images