CN101145101A - Method, device and system for customizing and executing strategy in edition control - Google Patents
Method, device and system for customizing and executing strategy in edition control Download PDFInfo
- Publication number
- CN101145101A CN101145101A CN 200610153879 CN200610153879A CN101145101A CN 101145101 A CN101145101 A CN 101145101A CN 200610153879 CN200610153879 CN 200610153879 CN 200610153879 A CN200610153879 A CN 200610153879A CN 101145101 A CN101145101 A CN 101145101A
- Authority
- CN
- China
- Prior art keywords
- version control
- strategy
- custom strategies
- mentioned
- project
- 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 OR CALCULATING; 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 invention provides a method to custom strategies for the setting of version control, a method of version control, a device to custom strategies for the setting of version control, an actuator to custom strategies for version control as well as a version control system. According to one aspect of the invention, the method to custom strategies for the setting of version control is provided, and the steps of the method are that at least one customized strategy of version control can be produced by selecting or setting version control options; the produced customized strategy of version control can be associated with a program or a user; the information about the produced customized strategy of version control, as well as the associated program and user can be saved.
Description
Technical field
The present invention relates to the Version Control technology, more particularly, be related to the technology that Version Control is provided with custom strategies.
Background technology
Usually, (Integrated Development Environment IDE) revises the content of source file, and (Version Control System VCS) carries out the Version Control of source file to use version control system to use Integrated Development Environment.In most of the cases, VCS can not insert additional information in the content of source file, but adds the change of some metadata (Metadata) of this document with the trace sources FileVersion in VCS.This means that the developer can not directly see Version Control information.In case source file takes out from VCS, the user can't directly check the Version Control of source file and help the additional information of identification modification state.
Most of existing VCS products, (the Concurrent VersionsSystem of for example parallel version system, CVS), ClearCase and configuration management and Version Control (ConfigurationManagement Version Control, CMVC) etc., be the user powerful version control function is provided, the for example operation that source file is carried out that the interpolation source is controlled, logged on, checks out etc. is shown in the synoptic diagram of Fig. 1.
CVS is used for the modification history of all source codes is carried out record.The groundwork thinking of CVS is the file store of creating a file on a station server, can deposit the source program of many disparity items in the archive files storehouse, by the storage and the configuration in keeper's unified management archive files storehouse.Each user can add new file in the archive files storehouse or the existing item file in the archive files storehouse to downloading to this locality when using version control tool.Any modification that the user makes at first all is to carry out in this locality, submits to the CVS order then, and the CVS system follows the tracks of the variation of file, and detects and revise conflict etc.
ClearCase is that (Software Configuration Management, SCM) instrument provide the necessary robotization means and the flow process support that are used to realize the SCM best practices to software configuration management.ClearCase provides an opening framework, is used to realize various dissimilar SCM solutions.
CMVC is based on project database, and it separates itself all storages and source file to the description of development project and source file metamessage (being metadata, as file new record etc. more), is kept in the independent database.
Yet there is following problem in the version control system shown in Fig. 1 (CVS, ClearCase, CMVC etc.):
(1) carrying out file operation action, for example adding source file control, when logging on/checking out etc., these actions are fixed, and the user can not customize during these actions.
(2) do not allow file content to change (for example inserting label information).That is to say, do not allow to change the content of source file, for example insert Version Control mark, time tag information etc.
(3) Project Manager can not be the specific Version Control custom strategies of each project definition.
(4) the project developer need add note and illustrates and be modified source code position and relevant information (for example " //modified by Sam atMay 5,2006 ") in the source file content.
In a word, these version control systems can only provide unified method and action to handle all situations, and the user can not customize during different source files and project are developed.
Summary of the invention
In order to solve above-mentioned problems of the prior art, the invention provides to Version Control and the method, edition control method of custom strategies is set, device, Version Control custom strategies actuating unit and the version control system of custom strategies are set for Version Control.
According to an aspect of the present invention, provide a kind of, may further comprise the steps:, generate at least one Version Control custom strategies by selecting or the Version Control option being set for Version Control is provided with the method for custom strategies; The Version Control custom strategies that has generated is associated with a project or user; And the information of preserving above-mentioned Version Control custom strategies and project that is associated or user.
According to another aspect of the present invention, provide a kind of edition control method, may further comprise the steps: received the order of Version Control; At least one Version Control custom strategies that acquisition is associated with the order of above-mentioned Version Control, wherein each above-mentioned Version Control custom strategies comprises the Version Control option of selecting or being provided with in advance; Project that acquisition is associated or user's information; And, make the order that above-mentioned Version Control is carried out in the free burial ground for the destitute by oneself according at least one Version Control custom strategies of above-mentioned acquisition and project that is associated or user's information.
According to another aspect of the present invention, a kind of device that custom strategies is set for Version Control is provided, comprise: tactful generation unit (policy generating unit) is used for generating at least one Version Control custom strategies by selecting or the Version Control option being set; Strategy customization units (policycustomizing unit) is used for the Version Control custom strategies that above-mentioned tactful generation unit generates is associated with a project or user; And preserve unit (saving unit), be used to preserve above-mentioned Version Control custom strategies and project that is associated or user's information.
According to another aspect of the present invention, provide a kind of device that is used to carry out the Version Control custom strategies, having comprised: order receiving element (command receiving unit) is used to receive the order of Version Control; Strategy obtains unit (policy obtaining unit), be used at least one Version Control custom strategies of obtaining to be associated with the order of above-mentioned Version Control, wherein each above-mentioned Version Control custom strategies comprises the Version Control option of selecting or being provided with in advance; Related information obtains unit (associated information obtaining unit), is used to the project that obtains to be associated or user's information; And command executing unit (command performing unit), obtain at least one Version Control custom strategies and the project that is associated of above-mentioned related information acquisition unit acquisition or user's the information that the unit obtains according to above-mentioned strategy, make the order that above-mentioned Version Control is carried out in the free burial ground for the destitute by oneself.
According to another aspect of the present invention, provide a kind of version control system, having comprised: above-mentioned for Version Control is provided with the device of custom strategies, be used to be provided with the Version Control custom strategies; The Version Control file store; And above-mentioned being used to carry out the device of Version Control custom strategies, is used for carrying out above-mentioned Version Control custom strategies with described Version Control file store.
Description of drawings
Believe by below in conjunction with the explanation of accompanying drawing, can make people understand the above-mentioned characteristics of the present invention, advantage and purpose better the specific embodiment of the invention.
Fig. 1 is the synoptic diagram according to the version control system of prior art;
Fig. 2 is the process flow diagram that the method for custom strategies is set for Version Control according to an embodiment of the invention;
Fig. 3 is the synoptic diagram of customizable according to an embodiment of the invention strategic layer and Version Control file store;
Fig. 4 is the process flow diagram of edition control method according to another embodiment of the invention;
Fig. 5 is that user command and custom strategies and project force policy are carried out the synoptic diagram of relevant action according to an embodiment of the invention;
Fig. 6 selects and the synoptic diagram of definition project force policy according to embodiments of the invention Project Manager when the customizable strategic layer of initialization;
Fig. 7 be according to another embodiment of the invention the block scheme of the device of custom strategies is set for Version Control;
Fig. 8 is the block scheme of device that is used to carry out the Version Control custom strategies according to another embodiment of the invention; And
Fig. 9 is the block scheme of version control system according to another embodiment of the invention.
Embodiment
Below just in conjunction with the accompanying drawings each embodiment of the present invention is described in detail.
The method of custom strategies is set for Version Control
Fig. 2 is the process flow diagram that the method for custom strategies is set for Version Control according to an embodiment of the invention.
As shown in Figure 2, at first,,, generate one or more Version Control custom strategies by selecting or the Version Control option being set in step 201.
Specifically, Version Control file store (version control repository) is a center storage position in the version control system, is used to store the controlled file on the share service device.The Version Control file store is storage file itself not only, and stores the version information and the file change of each controlled file.The user can take out the file that (checking out) has particular version from the Version Control file store, and file can be write back (logging on) Version Control file store, is write the version of file simultaneously by the version control system automatic setting.Physically, the Version Control file store uses the file system of operating system to carry out document control and version management.Concrete Version Control file store will be elaborated with reference to figure 3 below.
In the present embodiment, the Version Control option is used for controlled file is carried out various custom operation, in fact can think a kind of tactful atom, and these tactful atoms include but not limited to:
(1) code formatization (Code Formatting) option
When logging on source file, the code format option will be according to default type template style type of code, so that easier reading of source file and understanding.
(2) documentation summary generates (Document Summary Generating) option
In order to check documentation summary information, the user will check out whole file usually.Documentation summary generates option and will scan and produce a short summary according to file structure and content document, so that the user checks documentation summary information.Can save transmission volume like this and can only summary info be sent to the user.
(3) copyright information scanning (Copyright information validation) option
When adding new source file, the copyright information Scanning Options will come the scan source code confirming whether it comprises third party's code by checking file title and comment section, thereby the code of guaranteeing copyright not to be conflicted logs on the Version Control file store.
(4) metadata is replaced (Metadata Replacement) option
When Edit Document, need usually to replace source document attribute, for example information such as Word document author, tissue, business unit with active user's information.Metadata is replaced option and will be is automatically utilized new metadata to replace old metadata logging on or check out the stage.
(5) open API protection (Public API Protection) option
For open API (application programming interface), do not allow the interface definition of the open API that rename, change or deletion issued.Open API protection option will stop any change request to open api interface code, the compatible a plurality of versions of the API that exposes.
(6) title is added to source file (the Adding Header to New AddedSource File) option of new interpolation
When adding to new source file in the version control system, the source file option that title (as company information, project information etc.) is added to new interpolation will add default heading message to source file automatically.
(7) intelligence merges (Smart Merging) option
When several developers revise a source file simultaneously, intelligence merges option will judge whether to exist possible conflict after simple content scanning.If there is no possible conflict, union operation will be carried out automatically and need not the people and get involved.
(8) content update mark (Information Update Tagging) option
Content update mark option will more add the annotation information row in the front of new portion at source file.
(9) derive (Exporting for Different Platform) option for different platform
When taking out source file, the format conversion of source file is become the form of particular platform for different platform the Export Option based on different platform.
(10) set version (Setting Version for Specific User) option for the specific user
If log on the user name of file is " Jack ", for the specific user sets the version option version of this document is set at for example 1.5 versions so.
(11) conflict notification (Confliction Notifying) option
If clash when file logs on, and time of origin is weekend, and the conflict notification option will send mail to the keeper so.
Should be appreciated that these Version Control options that list above are just in order to illustrate, the present invention is not limited to this, and therefore, the known any Version Control option existing and exploitation in the future of any those skilled in the art can be realized in framework of the present invention.
Strategy has been formed in the set of these tactful atoms provides bag, and usually, the user provides from strategy and selects one or more tactful atoms to form strategy the bag, or the input customized information comes filling Strategy.Each tactful atom all needs a software code module to carry out this strategy atom, and the code of all support policy atoms all can be placed in the strategic layer and carry out.
In above-mentioned steps 201,, generate one or more Version Control custom strategies by selecting, being provided with or making up above-mentioned Version Control option.
Specifically, the Version Control custom strategies is a kind of entity of carrying out, and its preference for the user provides input template, receives several files as input source, and produces output file according to user's inputting preferences.This strategy can add annotation information to each new source file for example " title to be added to the source file of new interpolation ".Then, strategic layer receives one or more files as input source.This means that strategic layer can be operated single file input and a plurality of file is imported.Then, strategic layer produces output file according to user's inputting preferences, and this is a process one by one.The quantity of output file equals the quantity of input file.Each tactful atom has type attribute (for example " control of interpolation source ", " logging on ", " checking out " and " derivation "), to show the user and to belong to which kind of type based on the customizable version control system of strategy.
The example of the Version Control custom strategies that generates in step 201 includes but not limited to: code format strategy, documentation summary generation strategy, copyright information scanning, metadata replacement policy, open API protection strategy, with title add to the source file strategy of new interpolation, intelligent consolidation strategy, content update labelling strategies, tactful for the different platform derivation, set version policy, conflict notification strategy and combination thereof for the specific user.Should be appreciated that the example of the Version Control custom strategies of generation is not limited to this, it can be the combination of above-mentioned Version Control option, also can comprise the known any Version Control custom strategies existing and that develop in the future of those skilled in the art.
Then, in step 202, the Version Control custom strategies that generates is associated with a project or user.
Particularly, the Project Manager generates new Version Control custom strategies according to the preference of this project in step 201, as the project force policy of this project; Perhaps the Project Manager selects one in the Version Control custom strategies that has generated, as the project force policy of this project.Term " project force policy " is meant that this strategy is associated with the user relevant with this project, promptly when the user relevant with this project moves to source file, can carry out this project force policy simultaneously.In addition, different Project Manager can select separately project force policy according to the preference of project separately.The project force policy can comprise one or more above-mentioned Version Control custom strategies, and these strategies constitute the strategy group of this project.
Strategy group is to be used for one or more strategies that specific project uses, and as shown in Figure 6, wherein shows according to embodiments of the invention Project Manager when the customizable strategic layer of initialization and selects and the synoptic diagram of definition project force policy.
In Fig. 6, the keeper of project A has customized project A strategy group for project A, and this strategy group comprises tactful X, tactful Y etc.The keeper of item B has customized item B strategy group for item B, and this strategy group comprises tactful P, tactful Q etc.
In addition, the Version Control custom strategies that selection or customization are associated with it in the Version Control custom strategies that the user can generate from step 201 according to the preference of oneself is as this user's customization strategy.Term " customization strategy " is meant when this user moves to source file, can carry out this customization strategy simultaneously.The customization strategy can comprise one or more above-mentioned Version Control custom strategies, and the present invention is to this not restriction.
At last, in step 203, preserve above-mentioned Version Control custom strategies and project that is associated or user's information.
Particularly, Version Control custom strategies that will generate in step 201 and the project that is associated with the Version Control custom strategies that obtains in step 202 or user's information are kept in the customizable strategic layer (customizable policy layer) of version control system, as shown in Figure 3, it is the synoptic diagram of customizable according to an embodiment of the invention strategic layer and Version Control file store.
In Fig. 3, customizable strategic layer is between user and Version Control file store.Customizable strategic layer comprises all strategies (for example customizable interpolation source control strategy, customizable logging on/check out strategy, customizable derivation strategy etc.) and strategy group, and project that is associated with this strategy or strategy group or user's information.Each strategy group all is associated with a project at least.The Policy List that each user selectes enters customizable strategic layer, as the input source of selected strategy, carries out selected strategy then in customizable strategic layer execution module.In addition, also can generate the customized version control strategy earlier, then with the customized version control strategy storage that generates, the Project Manager selects one or more in the Version Control custom strategies that has generated in project is used, again with the incidence relation storage, also be step 201,203, a kind of particular embodiment of 203 after being associated with user and project.
By above explanation as can be known, the method that custom strategies is set for Version Control of present embodiment can be in version control system be different project or the different strategies of customization, and during different source files and project are developed, customizing accordingly, thereby the dirigibility that has greatly improved version control system.
Edition control method
Under same inventive concept, Fig. 4 is the process flow diagram of edition control method according to another embodiment of the invention.Below just in conjunction with this figure, present embodiment is described.For those parts identical, suitably omit its explanation with front embodiment.
In Fig. 4, at first,, receive the order of Version Control in step 401.
Generally speaking, the Version Control order is included in the interpolation file that the user sends in the version control system, upgrades the file in the version control system, or takes out from version control system in other related command that file or system send.Specifically, this order can be included in that the interpolation source is controlled, logs on, checked out, in derivation and known any other order of those skilled in the art, and the present invention does not limit this.
Then, in step 402, one or more Version Control custom strategies that acquisition is associated with the order of described Version Control, wherein each above-mentioned Version Control custom strategies comprises the Version Control option of selecting or being provided with in advance, and project that is associated with this Version Control custom strategies or user's information.Also may Version Control the custom strategies project or the user profile that are not associated, but in the Version Control order that receives, include the project that is associated or user's information, this situation associates them at this.These Version Control custom strategies and the project that is associated with each Version Control custom strategies or user's information can be kept in the customizable strategic layer of version control system.Here, the Version Control custom strategies that obtains to be associated with the order of described Version Control can customized version be controlled custom strategies when carrying out the Version Control order, also can be in advance the order of Version Control be associated with one or more Version Control custom strategies of having stored, when the order of operation Version Control, take out this Version Control custom strategies again, also can first customized version control custom strategies, but it is not associated with the order of Version Control, and related again when the order of operation Version Control, or the like numerous embodiments.
The example of optional Version Control custom strategies includes but not limited to: code format strategy, documentation summary generation strategy, copyright information scanning, metadata replacement policy, open API protection strategy, with title add to the source file strategy of new interpolation, intelligent consolidation strategy, content update labelling strategies, for different platform derive tactful, set version policy, conflict notification strategy etc. for the specific user.Should be appreciated that optionally the example of Version Control custom strategies is not limited to this, it can be the combination of above-mentioned Version Control custom strategies, also can comprise the known any Version Control custom strategies existing and that develop in the future of those skilled in the art.
At last, in step 403,, make the order that above-mentioned Version Control is carried out in the free burial ground for the destitute by oneself according to the Version Control custom strategies of selecting.
Particularly, as shown in Figure 5, show the synoptic diagram that user command and custom strategies and project force policy are according to an embodiment of the invention carried out relevant action.The order shown in the left side is for example interpolation/updating file order among Fig. 5.This order has custom strategies A and the tactful E that the user selects, and the project custom strategies of the project relevant with this order, and this project force policy comprises tactful X and tactful Y.Making the free burial ground for the destitute by oneself carries out the step of the order of this Version Control and comprises: at first the file relevant with this order sent to customizable strategic layer, then in customizable strategic layer to the action of this associated documents implementation strategy A, tactful E, tactful X and tactful Y, the file that produces is sent to be used in the Version Control file store preserving afterwards.
Order among Fig. 5 shown in the right side is for for example taking out file command.This order has custom strategies B, tactful D and the tactful F that the user selects, and the project custom strategies of the project relevant with this order, and this project force policy comprises tactful X and tactful Y.Making the free burial ground for the destitute by oneself carries out the step of the order of this Version Control and comprise: at first file that will be relevant with this order takes out and sends to customizable strategic layer from the Version Control file store, then in customizable strategic layer to the action of this associated documents implementation strategy B, tactful D, tactful F, tactful X and tactful Y, afterwards the file that produces is sent to the user.
Below by a preferred embodiment the present invention's process that strategy is provided with and strategy is realized in Version Control is described.
Phase one: customization project force policy
When a project proceeded to coding stage, (Versioned Object Base VOB), and had selected the strategy group of several custom strategies as this project, i.e. project force policy to the Project Manager for this project has been set up a versioned library of object.Following table 1 shows an example of user interface (UI).
Table 1
The keeper of project " P " the following project force policy that has been this project definition for example:
(a) title is added to the source file strategy of new interpolation
The source file policy enforcement module of adding title to new interpolation is added the heading message of customization to the front of the content of source file automatically.Its type shows that it is controlled in the interpolation source when mutual and carries out.The Project Manager has defined following content information:
/*
*Name:<file?name>
*Author:<user?name>
*Creation?date:<time?stamp>
*Copyright(c)2006，International?Business?Machines?Corporation
*All?right?reserved.
*/
(b) intelligent consolidation strategy
When a plurality of developers revised a source file simultaneously, intelligent consolidation strategy execution module carried out intelligence source file content merging automatically in the concurrent development process.Its type shows that it carries out logging on when mutual.In case when merging, clash, judge by content being carried out analysis scan, if find the modification of source code is not influenced the logic of program itself, such as having increased blank line, blank character or annotation information, the teat branch that can liquidate so directly superposes; If the modification of source code has been influenced the logic of program itself, can notify the user and finally whether cover according to default mode so by user's decision.
(c) code format strategy
The code format policy enforcement module will be according to default type template style type of code, so that easier reading of source file and understanding in the strategic layer.Its type shows that it is in interpolation source control with log on and carry out when mutual.
(d) copyright information scanning strategy
Copyright information scanning strategy execution module will come scan source code (for example " GPL ", " CPL " permission flag symbol) whether to comprise third party's code to confirm it by checking file title and comment section in the strategic layer, thereby the code of guaranteeing copyright not to be conflicted logs on the Version Control file store.If find to violate, will stop this operation.Its type shows that it is in interpolation source control with log on and carry out when mutual.
(e) open API protection strategy
Open API protection policy enforcement module will not allow these open API are carried out interface change, for example rename, change or deletion in the strategic layer.If find to violate, will stop this operation.Its type shows that it carries out logging on when mutual.
Subordinate phase: add new source file
The developer begins new source file is added in the source control of customizable version control system.Developer " Sam " does not select any strategy simultaneously in " 2006-04-28 " added project " P " in the control of source source file " Hello.java ".Source file is through customizable strategic layer, and customizable strategic layer is found the strategy group of project " P ".Then, according to correct type, to the above-mentioned strategy in the source file implementation strategy group.In the case, source file is revised by " title being added to the source file strategy of new interpolation " and " code format strategy ".
Source file is:
package?com.ibm.abc；
public?class?Hello{int?x＝0；public?void?printHello(){
System.our.println(
“Hello?world”)；}public?void
printBye()
{System.out
.println(“Bye”)；}}
Amended source file is:
/*
*Name:Hello.java
*Author:Sam
*Creation?date：2006-04-28
*Copyright(c)2006，International?Business?Machines?Corporation
*All?right?reserved.
*/
package?com.ibm.abc；
public?class?Hello{
int?x＝0；
public?void?printHello(){
System.out.println?(“Hello?world”)；
}
public?void?printBye(){
System.out.println(“Bye”)；
}
}
At this moment, developer " Ling " thinks and will add to from third-party source file in the control of source.For example he wants following source file is added in the control of source, does not select any strategy simultaneously:
...
//GPL?License?agreement，2006
...
At this moment, the policy enforcement module in the strategic layer will be moved.In the case, " copyright information scanning strategy " execution module determines that " GPL " signature means existence some contents by third party's exploitation.Therefore, this adds the operation failure of source file, and " Ling " will obtain an error message thus.
Phase III: concurrent development
The parallel source file that upgrades of developer.Usually, allow a plurality of developers that identical source file is carried out parallel processing.For example, two developers " Sam " and " Ling " the same source file " Hello.java " of new projects " p " more simultaneously.They check out this document simultaneously, and " Ling " at first log on this document, and have selected " content update labelling strategies ".The content that this means source file will be estimated, and will be in the content of the source file that upgrades the code section front following insertion information row:
...
public?class?Hello{
int?x＝0；
//print?hello?message
public?void?printHello(){
System.out.println(“Hello?world”)；
}
public?void?printBye(){
System.out.println(“Bye”)；
}
}
...
Then, according to correct type, utilize the above-mentioned strategy modification source file in the strategy group of this project.In the case,, do not carry out " intelligent consolidation strategy " for the action that logs on of " Ling " because do not exist with he log on conflicting of action.In addition, the execution module of " code format strategy ", " copyright information scanning strategy " and " open API protection strategy " also will move.In the case, source file will not change.
Subsequently, " Sam " finishes his renewal and file logged on, and also selected " content update labelling strategies " simultaneously, and the result is as follows:
....
public?class?Hello{
int?x＝0；
//Update?atMay?1，2006-By?Sam
int?a＝1；
public?void?printHello(){
System.out.println(“Hello?world”)；
}
public?void?printBye(){
System.out.println(“Bye”)；
}
}
...
Then, according to correct type, utilize the above-mentioned strategy modification source file in the strategy group of this project.In the case,, will carry out " intelligent consolidation strategy " for the action that logs on of " Sam ", because there be " Sam " and " Ling " " action between potentially conflicting.Simple judge after, not conflict between the action of " Sam " and " Ling " is thought by system, thereby followingly automatically performs the intelligence merging:
...
public?class?Hello{
int?x＝0；
//Update?at?May?1，2006-By?Sam
int?a＝1；
//print?hello?message
public?void?printHello(){
System.out.println(“Hello?world”)；
}
public?void?printBye(){
System.out.println(“Bye”)；
}
}
...
In addition, " code format strategy ", " copyright information scanning strategy " and " open API protection strategy " execution module also will move in the strategic layer.In the case, source file will not change.
Afterwards, developer " Ling " checks out source file once more, and he logs on source file, does not select any strategy.He is following to have changed an open API Name:
...
public?void?printHelloWorld(){
...
Policy enforcement module in the strategic layer will be carried out action.In the case, " open API protection strategy " execution module will be determined that open api interface changes, thereby log on operation failure this moment." Ling " will obtain an error message, and source file will not change.
Afterwards, another developer " Tom " wants the main contents of viewing files " Hello.java ".He opens file and selects " documentation summary produces strategy ", and at this moment, only the major part with file sends to him.Theing contents are as follows of major part:
public?class?Hello{
public?void?printHello()；
public?voidprintBye()；
}
Quadravalence section: for different platform makes up
Integrated personnel take out relevant file and are used for different structure (build).In most of the cases, need different structures to be used for different platforms.Therefore, integrated personnel selection " for different platform derives strategy " also selects " DOS " and " UNIX " as user preference.This means that these source files will derive two parts in this locality: portion is " DOS " formatted file, and another part is " UNIX " formatted file.
By above explanation as can be known, the edition control method of present embodiment can be different project or the different strategies of customization in version control system, and during different source files and project are developed, customizing accordingly, thereby the dirigibility that has greatly improved version control system.
In addition, it may be noted that and of the present inventionly not only be applicable to programming development environment described above and can be applied to other and need carry out in the environment of Version Control for Version Control is provided with the method for custom strategies and edition control method, for example, document file management system, office automation system or the like, its principle is identical with previously described program development, does not do repeat specification at this.
The device of custom strategies is set for Version Control
Under same inventive concept, Fig. 7 be according to another embodiment of the invention the block scheme of the device of custom strategies is set for Version Control.Below just in conjunction with this figure, present embodiment is described.For those parts identical, suitably omit its explanation with front embodiment.
As described in Figure 7, the device 700 that custom strategies is set for Version Control of present embodiment comprises: tactful generation unit 701 is used for generating one or more Version Control custom strategies by selecting or the Version Control option being set; Strategy customization units 702 is used for the Version Control custom strategies that tactful generation unit 701 generates is associated with a project or user; And preserve unit 703, be used to preserve above-mentioned Version Control custom strategies and project that is associated or user's information.
Particularly, that describes among Version Control file store and the above-mentioned embodiment with reference to figure 2 is identical, is not giving unnecessary details at this.The Version Control option includes but not limited to: code format strategy, documentation summary generation strategy, copyright information scanning, metadata replacement policy, open API protection strategy, with title add to the source file strategy of new interpolation, intelligent consolidation strategy, content update labelling strategies, for different platform derive tactful, set version policy, conflict notification strategy and combination thereof for the specific user.Should be appreciated that the present invention is not limited to this, therefore, Version Control file store of the present invention can comprise the known any Version Control option existing and that develop in the future of those skilled in the art.
By above explanation as can be known, the device 700 that custom strategies is set for Version Control of present embodiment can be different projects or the different strategy of customization, and during different source files and project are developed, customizing accordingly, thereby the dirigibility that has greatly improved version control system.
Version Control custom strategies actuating unit
Under same inventive concept, Fig. 8 is the block scheme of device that is used to carry out the Version Control custom strategies according to another embodiment of the invention.Below just in conjunction with this figure, present embodiment is described.For those parts identical, suitably omit its explanation with front embodiment.
As described in Figure 8, the Version Control custom strategies actuating unit 800 of present embodiment comprises: order receiving element 801, the order that is used to receive Version Control; Strategy obtains unit 802, one or more Version Control custom strategies that acquisition is associated with the order of the Version Control of ordering receiving element 801 to receive, and wherein each above-mentioned Version Control custom strategies comprises the Version Control option of selecting or being provided with in advance; Related information obtains unit 803, project that acquisition is associated or user's information; And command executing unit 804, obtain one or more Version Control custom strategies and the project that is associated of related information acquisition unit 803 acquisitions or user's the information that unit 802 obtains according to strategy, make the order that above-mentioned Version Control is carried out in the free burial ground for the destitute by oneself.
Particularly, the order that order receiving element 801 receives is included in adds file in the version control system, upgrade the file in the version control system, or take out file from version control system.Specifically, this order can comprise that the interpolation source is controlled, logs on, checked out, derivation and known any other order of those skilled in the art, and the present invention does not limit this.
The example that strategy obtains selection in advance that comprises in each above-mentioned Version Control custom strategies of unit 802 acquisitions or the Version Control option that is provided with includes but not limited to: the code format strategy; the documentation summary generation strategy; copyright information scanning; the metadata replacement policy; open API protection strategy; title is added to the source file strategy of new interpolation; the intelligence consolidation strategy; the content update labelling strategies; for different platform derives strategy; for the specific user sets version policy; conflict notification strategy etc.Should be appreciated that optionally the example of Version Control custom strategies is not limited to this, it can be the combination of above-mentioned Version Control custom strategies, also can comprise the known any Version Control custom strategies existing and that develop in the future of those skilled in the art.
Related information obtains the project that is associated of unit 803 acquisitions or user's information can be included in the Version Control custom strategies, project or user profile that perhaps also possible Version Control custom strategies is not associated, but in the Version Control order that receives, include the project that is associated or user's information, this situation associates them at this.These Version Control custom strategies and the project that is associated with each Version Control custom strategies or user's information can be kept in the customizable strategic layer of version control system.Here, the Version Control custom strategies that obtains to be associated with the order of described Version Control can customized version be controlled custom strategies when carrying out the Version Control order, also can be in advance the order of Version Control be associated with one or more Version Control custom strategies of having stored, when the order of operation Version Control, take out this Version Control custom strategies again, also can first customized version control custom strategies, but it is not associated with the order of Version Control, and related again when the order of operation Version Control, or the like numerous embodiments
By above explanation as can be known, the Version Control custom strategies actuating unit 800 of present embodiment can be different projects or the different strategy of customization, and during different source files and project are developed, customizing accordingly, thereby the dirigibility that has greatly improved version control system.
Version control system
Under same inventive concept, Fig. 9 is the block scheme of version control system according to another embodiment of the invention.Below just in conjunction with this figure, present embodiment is described.For those parts identical, suitably omit its explanation with front embodiment.
As described in Figure 9, the version control system 900 of present embodiment comprises: above-mentioned Version Control custom strategies setting device 700; Version Control file store 903; And above-mentioned Version Control custom strategies actuating unit 800.
By above explanation as can be known, the version control system 900 of present embodiment can be different projects or the different strategy of customization, and during different source files and project are developed, customizing accordingly, thereby the dirigibility that has greatly improved version control system.
Though more than described in detail by some exemplary embodiments and of the present inventionly the method, edition control method of custom strategies to be set, device, Version Control custom strategies actuating unit and the version control system of custom strategies are set for Version Control for Version Control, but above these embodiment are not exhaustive, and those skilled in the art can realize variations and modifications within the spirit and scope of the present invention.Therefore, the present invention is not limited to these embodiment, and scope of the present invention only is as the criterion by claims.
Claims (25)
1. one kind for Version Control is provided with the method for custom strategies, may further comprise the steps:
By selecting or the Version Control option being set, generate at least one Version Control custom strategies;
The Version Control custom strategies that has generated is associated with a project or user; And
Preserve above-mentioned Version Control custom strategies and project that is associated or user's information.
2. the method that custom strategies is set for Version Control according to claim 1; wherein, above-mentioned Version Control option comprise be selected from following at least a: code format strategy, documentation summary generation strategy, copyright information scanning, metadata replacement policy, open API protection strategy, with title add to the source file strategy of new interpolation, intelligent consolidation strategy, content update labelling strategies, for different platform derive tactful, set version policy, conflict notification strategy and combination thereof for the specific user.
3. according to claim 1 and 2 for Version Control is provided with the method for custom strategies, also comprise and repeat above-mentioned generation to the step of preserving.
4. according to claim 3 for Version Control is provided with the method for custom strategies, wherein, a project is associated with a plurality of Version Control custom strategies.
5. according to claim 3 or 4 described for Version Control is provided with the method for custom strategies, wherein, a user is associated with a plurality of Version Control custom strategies.
6. according to claim 1 or 3 described for Version Control is provided with the method for custom strategies, wherein, user relevant with project and the Version Control custom strategies that is associated with this project are associated.
7. according to claim 1 for Version Control is provided with the method for custom strategies, wherein, above-mentioned preservation step is kept at above-mentioned Version Control custom strategies and project that is associated or user's information in the customizable strategic layer.
8. edition control method may further comprise the steps:
Receive the order of Version Control;
At least one Version Control custom strategies that acquisition is associated with the order of above-mentioned Version Control, wherein each above-mentioned Version Control custom strategies comprises the Version Control option of selecting or being provided with in advance;
Project that acquisition is associated or user's information; And
According at least one Version Control custom strategies of above-mentioned acquisition and project that is associated or user's information, make the order that above-mentioned Version Control is carried out in the free burial ground for the destitute by oneself.
9. edition control method according to claim 8; wherein, above-mentioned Version Control option comprise be selected from following at least a: code format strategy, documentation summary generation strategy, copyright information scanning, metadata replacement policy, open API protection strategy, with title add to the source file strategy of new interpolation, intelligent consolidation strategy, content update labelling strategies, for different platform derive tactful, set version policy, conflict notification strategy and combination thereof for the specific user.
10. according to Claim 8 or 9 described edition control methods, wherein, the step of at least one Version Control custom strategies that above-mentioned acquisition is associated with the order of above-mentioned Version Control comprises:
Obtain with the order of above-mentioned Version Control at least one Version Control custom strategies of being associated of project.
11. any one described edition control method according to Claim 8-10, wherein, the step of at least one Version Control custom strategies that above-mentioned acquisition is associated with the order of above-mentioned Version Control comprises:
At least one Version Control custom strategies that acquisition is associated with above-mentioned user.
12. according to Claim 8 or 10 described edition control methods, wherein, user relevant with project and the Version Control custom strategies that is associated with this project are associated.
13. one kind for Version Control is provided with the device of custom strategies, comprising:
The strategy generation unit is used for generating at least one Version Control custom strategies by selecting or the Version Control option being set;
The strategy customization units is used for the Version Control custom strategies that above-mentioned tactful generation unit generates is associated with a project or user; And
Preserve the unit, be used to preserve above-mentioned Version Control custom strategies and project that is associated or user's information.
14. the device that custom strategies is set for Version Control according to claim 13; wherein, above-mentioned Version Control option comprise be selected from following at least a: code format strategy, documentation summary generation strategy, copyright information scanning, metadata replacement policy, open API protection strategy, with title add to the source file strategy of new interpolation, intelligent consolidation strategy, content update labelling strategies, for different platform derive tactful, set version policy, conflict notification strategy and combination thereof for the specific user.
15. according to claim 13 or 14 described for Version Control is provided with the device of custom strategies, wherein above-mentioned tactful generation unit generates a plurality of Version Control custom strategies.
16. according to claim 15 for Version Control is provided with the device of custom strategies, wherein, above-mentioned tactful customization units makes a project be associated with a plurality of Version Control custom strategies.
17. according to claim 15 or 16 described for Version Control is provided with the device of custom strategies, wherein, above-mentioned tactful customization units makes a user be associated with a plurality of Version Control custom strategies.
18. according to claim 13 or 15 described for Version Control is provided with the device of custom strategies, wherein, above-mentioned tactful customization units makes the user relevant with project and the Version Control custom strategies that is associated with this project is associated.
19. according to claim 13 for Version Control is provided with the device of custom strategies, wherein, above-mentioned preservation unit is kept at above-mentioned Version Control custom strategies and project that is associated or user's information in the customizable strategic layer.
20. a device that is used to carry out the Version Control custom strategies comprises:
The order receiving element is used to receive the order of Version Control;
Strategy obtains the unit, is used at least one Version Control custom strategies of obtaining to be associated with the order of above-mentioned Version Control, and wherein each above-mentioned Version Control custom strategies comprises the Version Control option of selecting or being provided with in advance;
Related information obtains the unit, is used to the project that obtains to be associated or user's information; And
Command executing unit obtains at least one Version Control custom strategies and the project that is associated of above-mentioned related information acquisition unit acquisition or user's the information that the unit obtains according to above-mentioned strategy, makes the order that above-mentioned Version Control is carried out in the free burial ground for the destitute by oneself.
21. the device that is used to carry out the Version Control custom strategies according to claim 20; wherein, above-mentioned Version Control option comprise be selected from following at least a: code format strategy, documentation summary generation strategy, copyright information scanning, metadata replacement policy, open API protection strategy, with title add to the source file strategy of new interpolation, intelligent consolidation strategy, content update labelling strategies, for different platform derive tactful, set version policy, conflict notification strategy and combination thereof for the specific user.
22. according to claim 20 or the 21 described devices that are used to carry out the Version Control custom strategies, wherein, above-mentioned strategy obtain the unit obtain with the order of above-mentioned Version Control at least one Version Control custom strategies of being associated of project.
23. according to any one described device that is used to carry out the Version Control custom strategies among the claim 20-22, wherein, above-mentioned strategy obtains at least one Version Control custom strategies that the unit acquisition is associated with above-mentioned user.
24. according to claim 20 or the 22 described devices that are used to carry out the Version Control custom strategies, wherein, user relevant with project and the Version Control custom strategies that is associated with this project are associated.
25. a version control system comprises:
According to any one described device that custom strategies is set for Version Control among the claim 13-19;
The Version Control file store; And
According to any one described device that is used to carry out the Version Control custom strategies among the claim 20-24.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200610153879 CN101145101A (en) | 2006-09-14 | 2006-09-14 | Method, device and system for customizing and executing strategy in edition control |
| US11/854,812 US8910117B2 (en) | 2006-09-14 | 2007-09-13 | Customizing and performing policy in version control |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200610153879 CN101145101A (en) | 2006-09-14 | 2006-09-14 | Method, device and system for customizing and executing strategy in edition control |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101145101A true CN101145101A (en) | 2008-03-19 |
Family
ID=39190158
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200610153879 Pending CN101145101A (en) | 2006-09-14 | 2006-09-14 | Method, device and system for customizing and executing strategy in edition control |
Country Status (2)
| Country | Link |
|---|---|
| US (1) | US8910117B2 (en) |
| CN (1) | CN101145101A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101526957B (en) * | 2009-04-09 | 2010-09-22 | 北京四方继保自动化股份有限公司 | A Version Management Method of Graph and Model Integration Applied in Electric Power Automation System |
| CN101873352A (en) * | 2010-06-12 | 2010-10-27 | 田小平 | Device and method for remotely managing health files |
| CN104156278A (en) * | 2014-08-01 | 2014-11-19 | 江苏大学 | File version control system and file version control method |
| CN105183789A (en) * | 2015-08-21 | 2015-12-23 | 福建天晴数码有限公司 | File merging method and system based on git source code confliction |
| CN106528071A (en) * | 2015-09-15 | 2017-03-22 | 阿里巴巴集团控股有限公司 | Selection method and device for target code |
| CN106991176A (en) * | 2017-04-06 | 2017-07-28 | 广州视源电子科技股份有限公司 | File management method, device, equipment and storage medium |
| CN108322540A (en) * | 2018-02-08 | 2018-07-24 | 深圳创维－Rgb电子有限公司 | Customized data lead-in method, terminal and computer readable storage medium |
| CN108369498A (en) * | 2015-12-23 | 2018-08-03 | Git软件中心公司 | Distributed code repository with limited synchronization locks |
Families Citing this family (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8266122B1 (en) * | 2007-12-19 | 2012-09-11 | Amazon Technologies, Inc. | System and method for versioning data in a distributed data store |
| US20100153919A1 (en) * | 2008-12-11 | 2010-06-17 | Wolfram Kramer | Systems and methods for tracking software stands in a software production landscape |
| US8200860B2 (en) * | 2009-02-13 | 2012-06-12 | International Business Machines Corporation | Apparatus and method to perform a version pre-check of a storage controller command |
| US9128805B2 (en) | 2011-05-04 | 2015-09-08 | Microsoft Technology Licensing, Llc | Automated modification integration and conflict resolution for software development |
| US9626379B1 (en) * | 2011-09-22 | 2017-04-18 | Amazon Technologies, Inc. | Optimistic commit processing for an offline document repository |
| WO2013184133A1 (en) * | 2012-06-08 | 2013-12-12 | Hewlett-Packard Development Company, L.P. | Cloud application deployment portability |
| EP2859439A4 (en) * | 2012-06-08 | 2016-03-30 | Hewlett Packard Development Co | DEPLOYMENT OF CLOUD APPLICATION |
| CN104246697A (en) * | 2012-06-08 | 2014-12-24 | 惠普发展公司，有限责任合伙企业 | Version management for applications |
| US8990168B1 (en) | 2012-06-21 | 2015-03-24 | Emc Corporation | Efficient conflict resolution among stateless processes |
| CN104572145B (en) * | 2013-10-16 | 2019-08-30 | 北大方正集团有限公司 | File edition management method and system |
| US10089213B1 (en) * | 2013-11-06 | 2018-10-02 | Amazon Technologies, Inc. | Identifying and resolving software issues |
| US9430359B1 (en) | 2013-11-06 | 2016-08-30 | Amazon Technologies, Inc. | Identifying and resolving software issues |
| US10176193B2 (en) * | 2014-06-23 | 2019-01-08 | International Business Machines Corporation | Holding specific versions of a document |
| CN106293662A (en) * | 2015-05-22 | 2017-01-04 | 中兴通讯股份有限公司 | A kind of code change statistics of variables method and device thereof |
| CN106572128A (en) * | 2015-10-09 | 2017-04-19 | 阿里巴巴集团控股有限公司 | Method and device used for deploying applications in integrated development environment (IDE) |
| US9996342B2 (en) * | 2016-01-22 | 2018-06-12 | International Business Machines Corporation | Automatic detection of potential merge errors |
| CA3016693A1 (en) * | 2016-03-09 | 2017-09-14 | Bitspray Corporation | Secure file sharing over multiple security domains and dispersed communication networks |
| CN105867978B (en) * | 2016-04-11 | 2018-12-11 | 平安科技（深圳）有限公司 | OGG version dispositions method and system |
| US10827036B2 (en) * | 2016-09-19 | 2020-11-03 | Palantir Technologies Inc. | Version control machine |
| US10534856B2 (en) | 2016-10-17 | 2020-01-14 | International Business Machines Corporation | Atom-based sensible synchronization for information indexing |
| US10831635B2 (en) * | 2016-10-27 | 2020-11-10 | International Business Machines Corporation | Preemption of false positives in code scanning |
| US10127019B2 (en) * | 2017-03-08 | 2018-11-13 | Hartford Fire Insurance Company | System to coordinate source code module changes |
| US11294661B2 (en) * | 2017-04-25 | 2022-04-05 | Microsoft Technology Licensing, Llc | Updating a code file |
| US11275624B2 (en) | 2018-06-14 | 2022-03-15 | Qliktech International Ab | Methods and systems for application program interface management |
| US10489144B1 (en) * | 2019-07-22 | 2019-11-26 | Capital One Services, Llc | Automated bucket policy management arrangements |
| CN110765145B (en) * | 2019-10-15 | 2022-08-09 | 益萃网络科技（中国）有限公司 | Content item transmission method, device, equipment and storage medium |
| US12039473B2 (en) * | 2021-11-01 | 2024-07-16 | T-Mobile Innovations Llc | Software development project infrastructure builder tool |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6993759B2 (en) * | 1999-10-05 | 2006-01-31 | Borland Software Corporation | Diagrammatic control of software in a version control system |
| US7035850B2 (en) * | 2000-03-22 | 2006-04-25 | Hitachi, Ltd. | Access control system |
| US6631386B1 (en) * | 2000-04-22 | 2003-10-07 | Oracle Corp. | Database version control subsystem and method for use with database management system |
| US20020162077A1 (en) * | 2001-04-30 | 2002-10-31 | Chau-Iou Jeng | In-sync hierarchy browser which provides version and access control on design collaboration for chip designs |
| US6928637B2 (en) * | 2001-08-10 | 2005-08-09 | Wind River Systems, Inc. | Version control adapter interface to support integration of multiple vendors integrated development environments (IDEs) |
| US7099899B2 (en) * | 2002-04-23 | 2006-08-29 | International Business Machines Corporation | System and method for item versioning in a content mangement system |
| US20030233621A1 (en) * | 2002-06-13 | 2003-12-18 | International Business Machines Corporation | Editor for smart version control |
| US20040073581A1 (en) * | 2002-06-27 | 2004-04-15 | Mcvoy Lawrence W. | Version controlled associative array |
| US20050044531A1 (en) * | 2003-06-09 | 2005-02-24 | Erc-Ip, Llc | Methods and systems for deploying computer source code |
| US20050114692A1 (en) * | 2003-11-26 | 2005-05-26 | Brett Watson-Luke | Systems, methods and software to configure and support a telecommunications system |
| US7437722B2 (en) * | 2004-07-19 | 2008-10-14 | Accurev, Inc. | Determining which software component versions of an issue resolution are included in a version of a software development project at a particular time |
| US20060026567A1 (en) * | 2004-07-27 | 2006-02-02 | Mcvoy Lawrence W | Distribution of data/metadata in a version control system |
-
2006
- 2006-09-14 CN CN 200610153879 patent/CN101145101A/en active Pending
-
2007
- 2007-09-13 US US11/854,812 patent/US8910117B2/en not_active Expired - Fee Related
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101526957B (en) * | 2009-04-09 | 2010-09-22 | 北京四方继保自动化股份有限公司 | A Version Management Method of Graph and Model Integration Applied in Electric Power Automation System |
| CN101873352A (en) * | 2010-06-12 | 2010-10-27 | 田小平 | Device and method for remotely managing health files |
| CN104156278A (en) * | 2014-08-01 | 2014-11-19 | 江苏大学 | File version control system and file version control method |
| CN104156278B (en) * | 2014-08-01 | 2017-06-27 | 江苏大学 | A file version control system and method thereof |
| CN105183789A (en) * | 2015-08-21 | 2015-12-23 | 福建天晴数码有限公司 | File merging method and system based on git source code confliction |
| CN106528071A (en) * | 2015-09-15 | 2017-03-22 | 阿里巴巴集团控股有限公司 | Selection method and device for target code |
| CN106528071B (en) * | 2015-09-15 | 2019-08-13 | 阿里巴巴集团控股有限公司 | The choosing method and device of object code |
| CN108369498A (en) * | 2015-12-23 | 2018-08-03 | Git软件中心公司 | Distributed code repository with limited synchronization locks |
| CN106991176A (en) * | 2017-04-06 | 2017-07-28 | 广州视源电子科技股份有限公司 | File management method, device, equipment and storage medium |
| CN108322540A (en) * | 2018-02-08 | 2018-07-24 | 深圳创维－Rgb电子有限公司 | Customized data lead-in method, terminal and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| US20080072217A1 (en) | 2008-03-20 |
| US8910117B2 (en) | 2014-12-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101145101A (en) | Method, device and system for customizing and executing strategy in edition control | |
| US10755234B2 (en) | System and method for offline synchronization of exception items of shared services for client applications | |
| US8918447B2 (en) | Methods, apparatus, systems and computer readable mediums for use in sharing information between entities | |
| US7496890B2 (en) | Generation of configuration instructions using an abstraction technique | |
| CN100576205C (en) | Data storage for software application documentation | |
| US7194730B2 (en) | System and method for the configuration of software products | |
| US7735062B2 (en) | Software development system and method | |
| CN101263477B (en) | Systems and methods for managing data associated with computer-generated documents | |
| US20060101443A1 (en) | Source code management system and method | |
| US7617234B2 (en) | XML schema for binding data | |
| US20060080329A1 (en) | Systems and methods for creating a template from an existing file | |
| CN103019718A (en) | Use of distributed source control in centralized source control environment | |
| US9229920B1 (en) | Compound undo/redo manager for mixed model edits | |
| CN101685394A (en) | Method and device for providing inter-version document compatibility | |
| US11625228B2 (en) | System and method for facilitating efficient round-trip engineering using intermediate representations | |
| JPWO2011118003A1 (en) | Web application construction system, web application construction method, web application construction program, and recording medium recording web application construction program | |
| Tröls et al. | Instant and global consistency checking during collaborative engineering | |
| US20080209572A1 (en) | Data Processing System, Data Processing Method, and Management Server | |
| EP1684170A2 (en) | Software development system and method | |
| Predoaia et al. | Streamlining the development of hybrid graphical-textual model editors for domain-specific languages | |
| CN110544092B (en) | Dynamic newly-added multi-type database data operation chaining method for block chain | |
| US7827195B2 (en) | Document management device and document management method | |
| JP2010061200A (en) | Document management system and operation history display method | |
| JP6011790B2 (en) | File management apparatus and computer program | |
| Radjenovic et al. | The role of dependency links in ensuring architectural view consistency |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20080319 |