CN114816498A - Resource file management method, device, equipment, storage medium and program product - Google Patents
Resource file management method, device, equipment, storage medium and program product Download PDFInfo
- Publication number
- CN114816498A CN114816498A CN202210408692.8A CN202210408692A CN114816498A CN 114816498 A CN114816498 A CN 114816498A CN 202210408692 A CN202210408692 A CN 202210408692A CN 114816498 A CN114816498 A CN 114816498A
- Authority
- CN
- China
- Prior art keywords
- file
- resource
- feature code
- resource file
- target
- 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
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/116—Details of conversion of file system types or formats
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Software Systems (AREA)
- Human Computer Interaction (AREA)
- Library & Information Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a resource file management method, a resource file management device, a computer device, a storage medium and a computer program product. The method comprises the following steps: acquiring a first file feature code of a resource file to be converted; the resource file to be converted is a file compiled by adopting a first compiling type and is stored in a local server; searching a target resource file corresponding to the resource file to be converted from the cloud server according to the first file feature code; the target resource file is a file compiled by adopting a second compiling type; acquiring attribute information of a target resource file, and managing the target resource file according to the attribute information; the attribute information includes coordinate information of the target resource file. By adopting the method, the efficiency and the accuracy of the conversion of the management mode of the dependent resource file can be improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for managing resource files, a computer device, a storage medium, and a computer program product.
Background
In the process of developing, operating and maintaining the software project, different software project building tools are usually used, for example, ant and Maven are common project building tools. The dependent resource files corresponding to the ant software project constructed by ant are usually managed locally, and the dependent resource files corresponding to the Maven software project constructed by Maven are usually managed in a central warehouse. However, the dependent resource files are usually difficult to modify and maintain when locally managed, so the ant software project needs to be converted into a Maven software project to realize management of the dependent resource files corresponding to the ant software project in the central repository.
In the process of converting an ant software project into a Maven software project, in the prior art, a manual method is usually adopted to search a dependent resource file of the Maven software project corresponding to the dependent resource file of the ant software project from a central repository, so that the ant software project is converted into the Maven software project.
However, the efficiency and accuracy of manual conversion of the resource-dependent file management is low.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a resource file management method, device, computer-readable storage medium, and computer program product that can improve the efficiency and accuracy of performing conversion depending on the resource file management manner.
In a first aspect, the present application provides a resource file management method. The method comprises the following steps:
acquiring a first file feature code of a resource file to be converted; the resource file to be converted is a file compiled by adopting a first compiling type and is stored in a local server; searching a target resource file corresponding to the resource file to be converted from the cloud server according to the first file feature code; the target resource file is a file compiled by adopting a second compiling type; acquiring attribute information of a target resource file, and managing the target resource file according to the attribute information; the attribute information includes coordinate information of the target resource file.
In one embodiment, the cloud server stores a plurality of resource files and second file feature codes of the resource files, wherein the resource files are files compiled by adopting a second compiling type; searching a target resource file corresponding to the resource file to be converted from the cloud server according to the first file feature code, wherein the searching comprises the following steps:
matching the first file feature code with second file feature codes of a plurality of resource files stored in a cloud server, and determining a target second file feature code matched with the first file feature code; and according to the target second file feature code, acquiring a resource file corresponding to the target second file feature code from the cloud server, and taking the resource file as a target resource file.
In one embodiment, the cloud server comprises at least one of a first server and a second server; the first server stores the resource file corresponding to the private warehouse and the second file feature code of the resource file, and the second server stores the resource file corresponding to the public warehouse and the second file feature code of the resource file.
In one embodiment, if the cloud server includes a first server, matching the first file feature code with a second file feature code of a plurality of resource files stored in the cloud server, and determining a target second file feature code matched with the first file feature code includes:
matching the first file feature code with second file feature codes of a plurality of resource files stored in a first server to generate a first matching result; and if the first matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code.
In one embodiment, if the cloud server includes a first server and a second server, matching the first file feature code with second file feature codes of a plurality of resource files stored in the cloud server, and determining a target second file feature code matched with the first file feature code includes:
matching the first file feature code with second file feature codes of a plurality of resource files stored in a first server to generate a first matching result; if the first matching result is matching failure, matching the first file feature code with a second file feature code of a plurality of resource files stored in a second server to generate a second matching result; and if the second matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code.
In one embodiment, the method further includes:
if the second matching result is matching failure, new attribute information corresponding to the resource file to be converted is obtained; and compiling the new attribute information according to the second compiling type to generate a target resource file corresponding to the resource file to be converted.
In one embodiment, acquiring attribute information of a target resource file, and managing the target resource file according to the attribute information includes:
acquiring initial attribute information of the target resource file, wherein the initial attribute information is stored in a table file; carrying out format conversion on the table file to generate a project object model file corresponding to the second compiling type; and managing the target resource file based on the attribute information in the project object model file.
In one embodiment, the first compilation type is an ant compilation type, and the second compilation type is a maven compilation type.
In a second aspect, the present application further provides a resource file management apparatus. The device comprises:
the first acquisition module is used for acquiring a first file feature code of the resource file to be converted; the resource file to be converted is a file compiled by adopting a first compiling type and is stored in a local server;
the searching module is used for searching a target resource file corresponding to the resource file to be converted from the cloud server according to the first file feature code; the target resource file is a file compiled by adopting a second compiling type;
the management module is used for acquiring the attribute information of the target resource file and managing the target resource file according to the attribute information; the attribute information includes coordinate information of the target resource file.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the method steps in any of the embodiments of the first aspect described above when executing the computer program.
In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the method steps of any of the embodiments of the first aspect described above.
In a fifth aspect, the present application further provides a computer program product. The computer program product comprising a computer program that when executed by a processor performs the method steps of any of the embodiments of the first aspect described above.
According to the resource file management method, the resource file management device, the computer equipment, the storage medium and the computer program product, the first file feature code of the resource file to be converted is obtained; the resource file to be converted is a file compiled by adopting a first compiling type and is stored in a local server; searching a target resource file corresponding to the resource file to be converted from the cloud server according to the first file feature code; the target resource file is a file compiled by adopting a second compiling type; acquiring attribute information of a target resource file, and managing the target resource file according to the attribute information; the attribute information includes coordinate information of the target resource file. In the technical scheme provided by the embodiment of the application, compared with the prior art, the target resource file corresponding to the resource file to be converted is searched from the cloud server without depending on a manual mode, and the corresponding target resource file can be automatically searched according to the first file feature code of the resource file to be converted, so that the efficiency of searching the corresponding target resource file is improved, and the efficiency of managing the resource file is improved; and moreover, the corresponding target resource file is searched by adopting the first file feature code of the resource file to be converted, and the feature code of each resource file is unique, so that the corresponding target resource file can be searched more accurately, and the accuracy of resource file management is improved.
Drawings
FIG. 1 is a diagram of an application environment of a method for resource file management in one embodiment;
FIG. 2 is a flowchart illustrating a resource file management method according to an embodiment;
FIG. 3 is a diagram of a presentation interface for a target resource file in one embodiment;
FIG. 4 is a diagram illustrating an interface for displaying attribute information of a target resource file, according to an embodiment;
FIG. 5 is a flowchart illustrating a process for searching for a target resource file in one embodiment;
FIG. 6 is a flowchart illustrating an embodiment of determining a target second file feature code;
FIG. 7 is a flowchart illustrating the process of determining the feature code of the target second file according to another embodiment;
FIG. 8 is a schematic diagram of a process for generating a target resource file in one embodiment;
FIG. 9 is a flow diagram that illustrates the management of a target resource file, under an embodiment;
FIG. 10 is a diagram of a table file in one embodiment;
FIG. 11 is a diagram illustrating conversion of a table file in one embodiment;
FIG. 12 is a flowchart illustrating a resource file management method according to another embodiment;
FIG. 13 is a block diagram showing the construction of a resource file management apparatus according to an embodiment;
FIG. 14 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The resource file management method provided by the embodiment of the application can be applied to the application environment shown in fig. 1. The user terminal 102, the first server 104 and the second server 106 may communicate with each other and invoke each other, the user terminal 102 is used for a user to input query parameters corresponding to resource files to be converted, the first server 104 is used for executing a resource file management method, and the second server 106 is used for managing related data of the resource files to be converted. The server may be one server or a server cluster composed of a plurality of servers, which is not specifically limited in this embodiment of the present application.
It should be noted that the execution subject of the embodiment of the present application may be a computer device, or may be a resource file management apparatus, and the following method embodiment describes a method in which a computer device is used as an execution subject.
In one embodiment, as shown in fig. 2, which illustrates a flowchart of resource file management provided by an embodiment of the present application, the method may include the following steps:
In the process of developing, operating and maintaining the software project, different software project building tools are generally used, the software project building tools are tools for automating processes related to the software project building, and the different software project building tools have different compiling types, so that resource files on which the software project depends are compiled and stored. Building a software project typically involves one or more of the following processes: generating a source code; generating a project document from the source code; compiling the source code; packaging the compiled codes into JAR files or ZIP files; the packaged code is installed on a server or elsewhere.
Depending on the nature of the software project building tool, the resource files compiled by the partial software project building tool may be stored on a local server, e.g., an ant software project building tool. Specifically, the ant software project building tool uses an imperative way, i.e., the operations that an ant should perform need to be specified in an ant build file. Low-level operations, such as copying files, compiling code, etc., may be specified, and the order in which the operations are performed may need to be specified after specifying the corresponding operations.
The first compilation type is a compilation type adopted by the software project building tool itself, and may include contents such as a compilation language, a compilation flow and the like, and if the software project building tool is ant, the first compilation type is an ant compilation type. The first file feature code of the resource file to be converted is a feature code uniquely corresponding to the resource file to be converted, and may be generated by calculating the resource file to be converted by using a preset algorithm, for example, a hash value of the resource file to be converted may be calculated by using a hash algorithm, so that the hash value is used as the first file feature code; of course, the first file feature code of the resource file to be converted may also be calculated in other manners, which is not limited in this embodiment.
Among other things, resource files need to be converted because they are often difficult to modify and maintain when managed at a local server. After the first file feature code of the resource file to be converted is obtained, a target resource file corresponding to the resource file to be converted can be searched from the cloud server based on the first file feature code, wherein the target resource file is a resource file compiled based on a second compiling type adopted by another software project building tool and is stored in the cloud server. For example, if the software project building tool is a maven, then the second compilation type is a maven compilation type. The maven software project building tool mainly does two things: and uniformly developing specifications and tools and uniformly managing jar packages.
Specifically, when searching, the feature codes corresponding to the multiple target resource files may be obtained first, and after the first file feature code is matched with the feature codes corresponding to the multiple target resource files, the corresponding target resource files are obtained. The feature code corresponding to the target resource file may be obtained by real-time calculation, or may be pre-calculated and stored.
The attribute information of the target resource file is a specific attribute of the target resource file, and may specifically include coordinate information of the target resource file. The coordinate information represents the position of a target resource file in the cloud server and can be represented by groupId, artifactId and version. As shown in fig. 3 and 4, the interface of fig. 3 shows the storage form of the target resource file as a jdom document object model, and the interface of fig. 4 shows the specific content of the attribute information of the target resource file.
Specifically, the groupId is an identifier unique to project organization, namely, a package name of a jar package depending on a resource file in the current software project; the artifactId is the only identifier of the project, and actually corresponds to the name of the project, namely the name of the jar package of the dependent resource file; version is the version number of the item. For example, the groupId is set to cn, which indicates that the domain is china, and zr can be an abbreviation of the personal name of the user; the artifactId is set to testProj, which indicates that the name of the item is testProj; version is set to 1.0, indicating that the version number of the item is 1.0.
In the embodiment, a first file feature code of a resource file to be converted is obtained; the resource file to be converted is a file compiled by adopting a first compiling type and is stored in a local server; searching a target resource file corresponding to the resource file to be converted from the cloud server according to the first file feature code; the target resource file is a file compiled by adopting a second compiling type; acquiring attribute information of a target resource file, and managing the target resource file according to the attribute information; the attribute information includes coordinate information of the target resource file. Compared with the prior art, the target resource file corresponding to the resource file to be converted is searched from the cloud server without depending on a manual mode, and the corresponding target resource file can be automatically searched according to the first file feature code of the resource file to be converted, so that the efficiency of searching the corresponding target resource file is improved, and the efficiency of managing the resource file is improved; and moreover, the corresponding target resource file is searched by adopting the first file feature code of the resource file to be converted, and the feature code of each resource file is unique, so that the corresponding target resource file can be searched more accurately, and the accuracy of resource file management is improved.
In an embodiment, as shown in fig. 5, which illustrates a flowchart of resource file management provided in an embodiment of the present application, and particularly relates to a possible process for finding a target resource file, the method may include the following steps:
The cloud server stores a plurality of resource files and second file feature codes of the resource files, and the resource files are files compiled by adopting a second compiling type. Optionally, a hash algorithm may be applied to each resource file stored in the cloud server in advance to calculate a corresponding MD5 hash value, so as to obtain the second file feature code of each resource file. Specifically, the hash algorithm is to calculate resource files with different lengths by using a hash function and output a value with the same length.
The second file feature codes of the resource files stored in the cloud server also can comprise a plurality of feature codes, so that the first file feature codes can be sequentially matched with the second file feature codes in sequence, and a target second file feature code matched with the first file feature code is further determined, namely the target second file feature code is consistent with the first file feature code; other matching methods may also be used to match the first file feature code with the plurality of second file feature codes, which is not specifically limited in this embodiment.
And 540, acquiring a resource file corresponding to the target second file feature code from the cloud server according to the target second file feature code, and taking the resource file as a target resource file.
And acquiring a resource file corresponding to the target second file feature code from the cloud server based on the determined target second file feature code, and taking the resource file as a target resource file. Optionally, the location information of the resource file may be directly determined according to the target second file feature code, so that the resource file corresponding to the target second file feature code is read based on the location information, and the resource file is used as the target resource file.
In this embodiment, a target second file feature code matched with a first file feature code is determined by matching the first file feature code with a second file feature code of a plurality of resource files stored in a cloud server; and according to the target second file feature code, acquiring a resource file corresponding to the target second file feature code from the cloud server, and taking the resource file as a target resource file. The accuracy and reliability of the target resource file are higher by matching the first file feature code with the second file feature code, and the second file feature code is generated and stored in advance, so that the efficiency of determining the target resource file is improved.
In one embodiment, the cloud server comprises at least one of a first server and a second server; the first server stores the resource file corresponding to the private warehouse and the second file feature code of the resource file, and the second server stores the resource file corresponding to the public warehouse and the second file feature code of the resource file. The number of the resource files stored in the first server is smaller than that of the resource files stored in the second server.
If the cloud server includes a first server, as shown in fig. 6, which shows a flowchart of resource file management provided in an embodiment of the present application, specifically, a possible process of determining a target second file feature code is provided, where the method may include the following steps:
The first server may be a server corresponding to a private warehouse, and the second file feature codes of the resource files stored in the first server may also include a plurality of feature codes, so that the first file feature codes may be sequentially matched with the plurality of second file feature codes, and a target second file feature code matched with the first file feature code is determined, that is, the target second file feature code is consistent with the first file feature code; other matching methods may also be used to match the first file feature code with the plurality of second file feature codes, which is not specifically limited in this embodiment.
And step 640, if the first matching result is that the matching is successful, determining that the successfully matched second file feature code is the target second file feature code.
If the first matching result is successful, the second file feature code consistent with the first file feature code is matched in the first server, and the successfully matched second file feature code is directly used as the target second file feature code.
In this embodiment, a first matching result is generated by matching the first file feature code with second file feature codes of a plurality of resource files stored in the first server; and if the first matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code. Because the number of the resource files stored in the first server is small, the searching is directly carried out from the first server, and the efficiency of searching the target second file feature code is higher.
In an embodiment, if the cloud server includes a first server and a second server, as shown in fig. 7, which shows a flowchart of resource file management provided in an embodiment of the present application, specifically, another possible process for determining a target second file feature code is provided, where the method includes the following steps:
and 720, matching the first file feature code with second file feature codes of a plurality of resource files stored in the first server to generate a first matching result.
The process of searching in the first server through the first file feature code is the same as the above embodiment, and is not described herein again.
If the first matching result is a matching failure, that is, a second file feature code consistent with the first file feature code is not matched in the first server, matching the first file feature code with second file feature codes of a plurality of resource files stored in the second server to generate a second matching result. The second server may be a server corresponding to a common warehouse or a central warehouse, and the second file feature codes of the plurality of resource files stored in the second server may also include a plurality of feature codes, so that the first file feature codes may be sequentially matched with the plurality of second file feature codes, and a target second file feature code matched with the first file feature code is determined, that is, the target second file feature code is consistent with the first file feature code; other matching methods may also be used to match the first file feature code with the plurality of second file feature codes, which is not specifically limited in this embodiment.
And 760, if the second matching result is that the matching is successful, determining that the successfully matched second file feature code is the target second file feature code.
If the second matching result is successful, the second file feature code consistent with the first file feature code is matched in the second server, and the successfully matched second file feature code is directly used as the target second file feature code.
In this embodiment, a first matching result is generated by matching the first file feature code with second file feature codes of a plurality of resource files stored in the first server; if the first matching result is matching failure, matching the first file feature code with a second file feature code of a plurality of resource files stored in a second server to generate a second matching result; and if the second matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code. And under the condition that the matching in the first server fails, the matching can be actively carried out in the second server, so that the reliability of obtaining the target second file feature code is ensured.
In one embodiment, as shown in fig. 8, which illustrates a flowchart of resource file management provided in an embodiment of the present application, and particularly relates to a possible process for generating a target resource file, the method may include the following steps:
and 820, if the second matching result is matching failure, acquiring new attribute information corresponding to the resource file to be converted.
If the second matching result is a matching failure, that is, the second file feature code consistent with the first file feature code is not matched in the second server, new attribute information corresponding to the resource file to be converted needs to be acquired. The new attribute information corresponding to the resource file to be converted may also include coordinate information of the resource file to be converted, and may be manually customized.
And 840, compiling the new attribute information according to the second compiling type to generate a target resource file corresponding to the resource file to be converted.
When the new attribute information is compiled according to the second compiling type, the following compiling mode can be adopted, and the specific content of the resource file to be converted is combined, so that the target resource file corresponding to the resource file to be converted is generated.
Wherein: the groupId is a package name of a jar package depending on resource files in the current software project, namely the package name is com.icbc.cism; the artifactId is the file name of the jar package of the dependent resource file, namely the file name is 'cocoa-dsf-ctp'; version is an item version number, i.e. the item version number is "1.0"; if systemmpath is that the device cannot find the corresponding GAV, i.e., coordinate information, in the enterprise private repository and the maven central repository, the actual path of the current resource file in the software project is described in pom.
In this embodiment, if the second matching result is a matching failure, new attribute information corresponding to the resource file to be converted is acquired; and compiling the new attribute information according to the second compiling type to generate a target resource file corresponding to the resource file to be converted. When the corresponding target resource file is not found, the target resource file corresponding to the resource file to be converted can be actively added, so that the reliability of resource file management is further improved.
In one embodiment, as shown in fig. 9, which illustrates a flowchart of resource file management provided in an embodiment of the present application, and particularly relates to a possible process for managing a target resource file, the method may include the following steps:
and 920, acquiring initial attribute information of the target resource file, wherein the initial attribute information is stored in the table file.
The initial attribute information of the target resource file is coordinate information of the target resource file directly extracted from the cloud server, and the initial attribute information of the target resource file can be directly stored in the table file when the coordinate information is output. Xls, the specific form of the table file is shown in fig. 10, wherein the first column "Filename" represents the file name of the resource file to be converted in the first server; the second column "Filepath" represents the path of the resource file to be converted in the first server; the third column "Mavenflag" indicates whether the cloud server corresponding to Maven is found; the fourth column to the sixth column respectively represent coordinate information groupId, artifactId, version; the seventh column "gavInfo" represents the conversion of coordinate information into a character string.
And 940, converting the format of the table file to generate a project object model file corresponding to the second compiling type.
And converting the format of the table file to generate a project object model file corresponding to the second compiling type, wherein the project object model file is in an XML format and is written as pom. This file is used to manage: the specific conversion mode is as shown in fig. 11, that is, the coordinate information in the form file can be extracted and filled in the fixed position of the pom.
After the form file is subjected to format conversion, the target resource file can be managed based on the attribute information in the project object model file.
In the embodiment, the initial attribute information of the target resource file is acquired and stored in the table file; carrying out format conversion on the table file to generate a project object model file corresponding to the second compiling type; and managing the target resource file based on the attribute information in the project object model file. The method is simple to operate and easy to realize, and the efficiency of managing the target resource file is improved.
In one embodiment, as shown in fig. 12, which shows a flowchart of resource file management provided by an embodiment of the present application, the method may include the following steps:
For example, the code base address: git @ gitlab. abc. com. usrid/project _ name. git; the downloading user is a user with the right to download the code, namely inputting userid.
And downloading project source codes and project dependent resource jar files to a preset specified conversion directory of the device, such as WEB-INF \ lib in a lib directory, by a specified user under a configured code base address.
After downloading, actively scanning the conversion directory, sequentially traversing the resource file directory to be converted, and calculating a first file feature code of the current resource file to be converted, namely a unique feature code MD5 value.
And step 1204, matching in the private warehouse according to the first file feature code. Specifically, the first file feature code is matched with a second file feature code of a plurality of resource files stored in the private warehouse, and a first matching result is generated.
And step 1205, judging whether the first matching result is a successful matching result.
And step 1206, if the first matching result is that the matching is successful, determining that the successfully matched second file feature code is the target second file feature code and recording the target second file feature code in the table file.
And step 1208, calling the maven compiling command to compile the converted resource file for verification.
And 1212, if the second matching result is a matching failure, regenerating the target resource file corresponding to the resource file to be converted. Specifically, new attribute information corresponding to a resource file to be converted is acquired; and compiling the new attribute information according to the second compiling type to generate a target resource file corresponding to the resource file to be converted.
Compared with the prior art, the method and the device have the advantages that the target resource file corresponding to the resource file to be converted is searched from the cloud server without depending on a manual mode, the corresponding target resource file can be automatically searched according to the first file feature code of the resource file to be converted, efficiency of searching the corresponding target resource file is improved, and accordingly efficiency of resource file management is improved; and moreover, the corresponding target resource file is searched by adopting the first file feature code of the resource file to be converted, and the feature code of each resource file is unique, so that the corresponding target resource file can be searched more accurately, and the accuracy of resource file management is improved.
In one embodiment, in practical applications, the conventional method is to comb jar resource files relied on under the original conventional project by a user, and then search resource files meeting conditions from products managed by an internal private warehouse of an enterprise. The method comprises the following specific steps: inputting a resource file name in a private warehouse for searching; obtaining coordinate values according to the query result; combining the inquired coordinate values into a cave.xml file of the maven project dependent resource management; software which cannot be found in the enterprise private library is searched in the central warehouse, the steps are repeated on the inquired result, and a pom.xml file is finally formed; the dependent resource files which cannot be found by the central warehouse are manually added directly in the dependent resource management file pom.
Specifically, the searched coordinate values are combined into a cave.xml file of the maven project dependent resource management in the following way:
in the dependent resource management file pom.xml, the following method is adopted for manual addition:
wherein: the groupId is the package name of a jar package depending on the resource file in the current software project, namely the package name is com.icbc.cism; the artifactId is the file name of the jar package of the dependent resource file, namely the file name is 'cocoa-dsf-ctp'; version is an item version number, i.e. the item version number is "1.0"; if systemmpath is that the device cannot find the corresponding GAV, i.e., coordinate information, in the enterprise private repository and the maven central repository, the actual path of the current resource file in the software project is described in pom.
However, the existing technical solution has a high degree of dependence on manual work, and the accuracy of combing the dependent resource files is low, specifically as follows:
the efficiency is low: in the prior art, products matched with original project dependent resources are searched in an enterprise private warehouse and a central warehouse manually, and pom.xml files are combined in a manual mode; the accuracy is low: the accuracy rate is low in a mode of manually checking the file name, the name of the resource file which is depended on in the original project is not standard, and the risk of manually modifying the name of the resource file exists and cannot be traced; the cost is high: the existing technical means is to search and compile a pom.xml file in a warehouse by manpower, although a certain tool is used for supporting, the manpower efficiency is low and the technical requirement on the manpower is high; the risk is high: in the prior art, because the conversion is only carried out by depending on the name of the resource file, the risk of false alarm exists, and the potential risk is caused to be produced; not easy to popularize: the conversion of individual projects is supported by the technical ability of developers, and the replication and inheritance of the ability are lacked.
The device mavenConvert that the method that this application provided corresponds can be with the project conversion of traditional ant compile type Maven project into, the core function is the resource dependence that the resource dependence of passing through manual management with ant project converts Maven management into, need not artifical intervention and can realize that traditional project relies on the high-efficient automatic Maven project of converting into of resource dependence management mode, it has non-invasive characteristics to support all enterprise's applications, only need the enterprise provide treat the resource place route of conversion project, provide brief information can, there is the safety guarantee to the enterprise. Moreover, the method supports the non-invasive characteristic for all enterprise applications, only needs the enterprise to provide the path of the resource file of the project to be converted, and provides brief information, thereby ensuring the safety of the enterprise.
It should be understood that, although the steps in the flowcharts related to the embodiments as described above are sequentially displayed as indicated by arrows, the steps are not necessarily performed sequentially as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts related to the embodiments described above may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the execution order of the steps or stages is not necessarily sequential, but may be rotated or alternated with other steps or at least a part of the steps or stages in other steps.
Based on the same inventive concept, the embodiment of the present application further provides a resource file management apparatus for implementing the above-mentioned resource file management method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so the specific limitations in one or more embodiments of the resource file management device provided below can refer to the limitations in the above resource file management method, and are not described herein again.
In one embodiment, as shown in fig. 13, there is provided a resource file management apparatus 1300, including: a first obtaining module 1302, a lookup module 1304, and a management module 1306, wherein:
a first obtaining module 1302, configured to obtain a first file feature code of a resource file to be converted; the resource file to be converted is a file compiled by adopting a first compiling type and is stored in a local server;
the searching module 1304 is configured to search a target resource file corresponding to the resource file to be converted from the cloud server according to the first file feature code; the target resource file is a file compiled by adopting a second compiling type;
the management module 1306 is configured to obtain attribute information of the target resource file, and manage the target resource file according to the attribute information; the attribute information includes coordinate information of the target resource file.
In one embodiment, the cloud server stores a plurality of resource files and second file feature codes of the resource files, wherein the resource files are files compiled by adopting a second compiling type; the searching module 1304 is specifically configured to match the first file feature code with second file feature codes of multiple resource files stored in the cloud server, and determine a target second file feature code matched with the first file feature code; and according to the target second file feature code, acquiring a resource file corresponding to the target second file feature code from the cloud server, and taking the resource file as a target resource file.
In one embodiment, the cloud server comprises at least one of a first server and a second server; the first server stores the resource file corresponding to the private warehouse and the second file feature code of the resource file, and the second server stores the resource file corresponding to the public warehouse and the second file feature code of the resource file.
In an embodiment, if the cloud server includes a first server, the searching module 1304 is further configured to match the first file feature code with a second file feature code of a plurality of resource files stored in the first server, so as to generate a first matching result; and if the first matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code.
In an embodiment, if the cloud server includes a first server and a second server, the searching module 1304 is further configured to match the first file feature code with a second file feature code of a plurality of resource files stored in the first server, so as to generate a first matching result; if the first matching result is matching failure, matching the first file feature code with a second file feature code of a plurality of resource files stored in a second server to generate a second matching result; and if the second matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code.
In one embodiment, the resource file management apparatus further includes a second obtaining module and a generating module, where:
and the second obtaining module is used for obtaining new attribute information corresponding to the resource file to be converted if the second matching result is matching failure.
And the generating module is used for compiling the new attribute information according to the second compiling type to generate a target resource file corresponding to the resource file to be converted.
In an embodiment, the management module 1306 is specifically configured to obtain initial attribute information of the target resource file, where the initial attribute information is stored in a table file; carrying out format conversion on the table file to generate a project object model file corresponding to the second compiling type; and managing the target resource file based on the attribute information in the project object model file.
In one embodiment, the first compilation type is an ant compilation type and the second compilation type is a maven compilation type.
The modules in the resource file management device can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
The resource file management method provided by the application can be applied to computer equipment, the computer equipment can be a server or a terminal, wherein the server can be one server or a server cluster consisting of a plurality of servers.
Taking the example of a computer device being a server, fig. 14 shows a block diagram of a server, which, as shown in fig. 14, includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is for storing resource file management data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a resource file management method.
Those skilled in the art will appreciate that the architecture shown in fig. 14 is a block diagram of only a portion of the architecture associated with the subject application, and does not constitute a limitation on the servers to which the subject application applies, and that servers may alternatively include more or fewer components than those shown, or combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
acquiring a first file feature code of a resource file to be converted; the resource file to be converted is a file compiled by adopting a first compiling type and is stored in a local server; searching a target resource file corresponding to the resource file to be converted from the cloud server according to the first file feature code; the target resource file is a file compiled by adopting a second compiling type; acquiring attribute information of a target resource file, and managing the target resource file according to the attribute information; the attribute information includes coordinate information of the target resource file.
In one embodiment, the cloud server stores a plurality of resource files and second file feature codes of the resource files, wherein the resource files are files compiled by adopting a second compiling type;
the processor, when executing the computer program, further performs the steps of:
matching the first file feature code with second file feature codes of a plurality of resource files stored in a cloud server, and determining a target second file feature code matched with the first file feature code; and according to the target second file feature code, acquiring a resource file corresponding to the target second file feature code from the cloud server, and taking the resource file as a target resource file.
In one embodiment, the cloud server comprises at least one of a first server and a second server; the first server stores the resource file corresponding to the private warehouse and the second file feature code of the resource file, and the second server stores the resource file corresponding to the public warehouse and the second file feature code of the resource file.
In one embodiment, if the cloud server comprises a first server;
the processor, when executing the computer program, further performs the steps of:
matching the first file feature code with second file feature codes of a plurality of resource files stored in a first server to generate a first matching result; and if the first matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code.
In one embodiment, if the cloud server comprises a first server and a second server;
the processor, when executing the computer program, further performs the steps of:
matching the first file feature code with second file feature codes of a plurality of resource files stored in a first server to generate a first matching result; if the first matching result is matching failure, matching the first file feature code with a second file feature code of a plurality of resource files stored in a second server to generate a second matching result; and if the second matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
if the second matching result is matching failure, acquiring new attribute information corresponding to the resource file to be converted; and compiling the new attribute information according to the second compiling type to generate a target resource file corresponding to the resource file to be converted.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
acquiring initial attribute information of the target resource file, wherein the initial attribute information is stored in a table file; carrying out format conversion on the table file to generate a project object model file corresponding to the second compiling type; and managing the target resource file based on the attribute information in the project object model file.
In one embodiment, the first compilation type is an ant compilation type and the second compilation type is a maven compilation type.
The implementation principle and technical effect of the computer device provided by the embodiment of the present application are similar to those of the method embodiment described above, and are not described herein again.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
acquiring a first file feature code of a resource file to be converted; the resource file to be converted is a file compiled by adopting a first compiling type and is stored in a local server; searching a target resource file corresponding to the resource file to be converted from the cloud server according to the first file feature code; the target resource file is a file compiled by adopting a second compiling type; acquiring attribute information of a target resource file, and managing the target resource file according to the attribute information; the attribute information includes coordinate information of the target resource file.
In one embodiment, the cloud server stores a plurality of resource files and second file feature codes of the resource files, wherein the resource files are files compiled by adopting a second compiling type;
the computer program when executed by the processor further realizes the steps of:
matching the first file feature code with second file feature codes of a plurality of resource files stored in a cloud server, and determining a target second file feature code matched with the first file feature code; and according to the target second file feature code, acquiring a resource file corresponding to the target second file feature code from the cloud server, and taking the resource file as a target resource file.
In one embodiment, the cloud server comprises at least one of a first server and a second server; the first server stores the resource file corresponding to the private warehouse and the second file feature code of the resource file, and the second server stores the resource file corresponding to the public warehouse and the second file feature code of the resource file.
In one embodiment, if the cloud server comprises a first server;
the computer program when executed by the processor further realizes the steps of:
matching the first file feature code with second file feature codes of a plurality of resource files stored in a first server to generate a first matching result; and if the first matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code.
In one embodiment, if the cloud server comprises a first server and a second server;
the computer program when executed by the processor further realizes the steps of:
matching the first file feature code with second file feature codes of a plurality of resource files stored in a first server to generate a first matching result; if the first matching result is matching failure, matching the first file feature code with a second file feature code of a plurality of resource files stored in a second server to generate a second matching result; and if the second matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code.
In one embodiment, the computer program when executed by the processor further performs the steps of:
if the second matching result is matching failure, acquiring new attribute information corresponding to the resource file to be converted; and compiling the new attribute information according to the second compiling type to generate a target resource file corresponding to the resource file to be converted.
In one embodiment, the computer program when executed by the processor further performs the steps of:
acquiring initial attribute information of the target resource file, wherein the initial attribute information is stored in a table file; carrying out format conversion on the table file to generate a project object model file corresponding to the second compiling type; and managing the target resource file based on the attribute information in the project object model file.
In one embodiment, the first compilation type is an ant compilation type and the second compilation type is a maven compilation type.
The implementation principle and technical effect of the computer-readable storage medium provided by this embodiment are similar to those of the above-described method embodiment, and are not described herein again.
In one embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, performs the steps of:
acquiring a first file feature code of a resource file to be converted; the resource file to be converted is a file compiled by adopting a first compiling type and is stored in a local server; searching a target resource file corresponding to the resource file to be converted from the cloud server according to the first file feature code; the target resource file is a file compiled by adopting a second compiling type; acquiring attribute information of a target resource file, and managing the target resource file according to the attribute information; the attribute information includes coordinate information of the target resource file.
In one embodiment, the cloud server stores a plurality of resource files and second file feature codes of the resource files, wherein the resource files are files compiled by adopting a second compiling type;
the computer program when executed by the processor further realizes the steps of:
matching the first file feature code with second file feature codes of a plurality of resource files stored in a cloud server, and determining a target second file feature code matched with the first file feature code; and according to the target second file feature code, acquiring a resource file corresponding to the target second file feature code from the cloud server, and taking the resource file as a target resource file.
In one embodiment, the cloud server comprises at least one of a first server and a second server; the first server stores the resource file corresponding to the private warehouse and the second file feature code of the resource file, and the second server stores the resource file corresponding to the public warehouse and the second file feature code of the resource file.
In one embodiment, if the cloud server comprises a first server;
the computer program when executed by the processor further realizes the steps of:
matching the first file feature code with second file feature codes of a plurality of resource files stored in a first server to generate a first matching result; and if the first matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code.
In one embodiment, if the cloud server comprises a first server and a second server;
the computer program when executed by the processor further realizes the steps of:
matching the first file feature code with second file feature codes of a plurality of resource files stored in a first server to generate a first matching result; if the first matching result is matching failure, matching the first file feature code with a second file feature code of a plurality of resource files stored in a second server to generate a second matching result; and if the second matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code.
In one embodiment, the computer program when executed by the processor further performs the steps of:
if the second matching result is matching failure, acquiring new attribute information corresponding to the resource file to be converted; and compiling the new attribute information according to the second compiling type to generate a target resource file corresponding to the resource file to be converted.
In one embodiment, the computer program when executed by the processor further performs the steps of:
acquiring initial attribute information of the target resource file, wherein the initial attribute information is stored in a table file; carrying out format conversion on the table file to generate a project object model file corresponding to the second compiling type; and managing the target resource file based on the attribute information in the project object model file.
In one embodiment, the first compilation type is an ant compilation type and the second compilation type is a maven compilation type.
The computer program product provided in this embodiment has similar implementation principles and technical effects to those of the method embodiments described above, and is not described herein again.
It should be noted that, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high-density embedded nonvolatile Memory, resistive Random Access Memory (ReRAM), Magnetic Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (PCM), graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others. The databases referred to in various embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing based data processing logic devices, etc., without limitation.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.
Claims (12)
1. A method for resource file management, the method comprising:
acquiring a first file feature code of a resource file to be converted; the resource file to be converted is a file compiled by adopting a first compiling type and is stored in a local server;
searching a target resource file corresponding to the resource file to be converted from a cloud server according to the first file feature code; the target resource file is a file compiled by adopting a second compiling type;
acquiring attribute information of the target resource file, and managing the target resource file according to the attribute information; the attribute information includes coordinate information of the target resource file.
2. The method of claim 1, wherein a plurality of resource files and second file feature codes of the resource files are stored in the cloud server, and the resource files are files compiled by adopting a second compiling type; the searching for the target resource file corresponding to the resource file to be converted from the cloud server according to the first file feature code includes:
matching the first file feature codes with second file feature codes of a plurality of resource files stored in a cloud server, and determining target second file feature codes matched with the first file feature codes;
and according to the target second file feature code, acquiring a resource file corresponding to the target second file feature code from the cloud server, and taking the resource file as the target resource file.
3. The method of claim 2, wherein the cloud server comprises at least one of a first server and a second server; the first server stores resource files corresponding to a private warehouse and second file feature codes of the resource files, and the second server stores resource files corresponding to a public warehouse and second file feature codes of the resource files.
4. The method of claim 3, wherein if the cloud server comprises a first server, the matching the first file feature code with a second file feature code of a plurality of resource files stored in the cloud server to determine a target second file feature code that matches the first file feature code comprises:
matching the first file feature code with second file feature codes of a plurality of resource files stored in the first server to generate a first matching result;
and if the first matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code.
5. The method of claim 3, wherein if the cloud server comprises a first server and a second server, the matching the first file feature code with a second file feature code of a plurality of resource files stored in the cloud server to determine a target second file feature code matching the first file feature code comprises:
matching the first file feature code with second file feature codes of a plurality of resource files stored in the first server to generate a first matching result;
if the first matching result is matching failure, matching the first file feature code with second file feature codes of a plurality of resource files stored in the second server to generate a second matching result;
and if the second matching result is successful matching, determining that the successfully matched second file feature code is the target second file feature code.
6. The method of claim 5, further comprising:
if the second matching result is matching failure, acquiring new attribute information corresponding to the resource file to be converted;
and compiling the new attribute information according to the second compiling type to generate a target resource file corresponding to the resource file to be converted.
7. The method according to claim 1, wherein the obtaining attribute information of the target resource file and managing the target resource file according to the attribute information comprises:
acquiring initial attribute information of the target resource file, wherein the initial attribute information is stored in a table file;
carrying out format conversion on the table file to generate a project object model file corresponding to the second compiling type;
and managing the target resource file based on the attribute information in the project object model file.
8. The method of any of claims 1-7, wherein the first coding type is an ant coding type, and wherein the second coding type is a maven coding type.
9. An apparatus for resource file management, the apparatus comprising:
the first acquisition module is used for acquiring a first file feature code of the resource file to be converted; the resource file to be converted is a file compiled by adopting a first compiling type and is stored in a local server;
the searching module is used for searching a target resource file corresponding to the resource file to be converted from a cloud server according to the first file feature code; the target resource file is a file compiled by adopting a second compiling type;
the management module is used for acquiring the attribute information of the target resource file and managing the target resource file according to the attribute information; the attribute information includes coordinate information of the target resource file.
10. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 8.
11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 8.
12. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method of any one of claims 1 to 8 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210408692.8A CN114816498A (en) | 2022-04-19 | 2022-04-19 | Resource file management method, device, equipment, storage medium and program product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210408692.8A CN114816498A (en) | 2022-04-19 | 2022-04-19 | Resource file management method, device, equipment, storage medium and program product |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114816498A true CN114816498A (en) | 2022-07-29 |
Family
ID=82506606
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210408692.8A Pending CN114816498A (en) | 2022-04-19 | 2022-04-19 | Resource file management method, device, equipment, storage medium and program product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114816498A (en) |
-
2022
- 2022-04-19 CN CN202210408692.8A patent/CN114816498A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210248487A1 (en) | Framework management method and apparatus | |
| CN109032631B (en) | Application program patch package obtaining method and device, computer equipment and storage medium | |
| US8793706B2 (en) | Metadata-based eventing supporting operations on data | |
| US20220198003A1 (en) | Detecting added functionality in open source package | |
| CN111008034B (en) | Patch generation method and device | |
| JP6367444B2 (en) | How to transport relationship data | |
| CN106776720A (en) | A kind of document handling method and device | |
| WO2019037414A1 (en) | Page configuration update method and device, and server and storage medium | |
| CN114780641A (en) | Multi-library multi-table synchronization method and device, computer equipment and storage medium | |
| CN113515303B (en) | Project transformation method, device and equipment | |
| CN113535141A (en) | Database operation code generation method and device | |
| CN113918437A (en) | User behavior data analysis method and device, computer equipment and storage medium | |
| US11347533B2 (en) | Enhanced virtual machine image management system | |
| CN114816498A (en) | Resource file management method, device, equipment, storage medium and program product | |
| CN116069725A (en) | File migration method, device, apparatus, medium and program product | |
| CN111400243B (en) | Development management system based on pipeline service and file storage method and device | |
| US20200175202A1 (en) | Synchronizing masking jobs between different masking engines in a data processing system | |
| CN115061726A (en) | Script file batch processing method, device, equipment, medium and program product | |
| CN114691653A (en) | Account set migration method and device, computer equipment and storage medium | |
| CN114416689A (en) | Data migration method and device, computer equipment and storage medium | |
| CN115454476A (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN116483532A (en) | Scheduling processing method, device, computer equipment and storage medium | |
| CN116089387A (en) | Resource allocation method, apparatus, electronic device, readable medium and program product | |
| CN114153457A (en) | Application program installation file generation method and device and storage medium | |
| CN114840217A (en) | Compiling method, device, equipment and readable storage medium |
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 |