Iterative development with prioritized build

• US 20050278318A1
• Filed: 05/31/2005
• Published: 12/15/2005
• Est. Priority Date: 02/22/2002
• Status: Abandoned Application

• Current Assignee: David Bau III, Kenneth Eric Vasilik, Roderick A. Chavez
• Original Assignee: David Bau III, Kenneth Eric Vasilik, Roderick A. Chavez
• Inventors: Vasilik, Kenneth Eric, Chavez, Roderick A., Bau, David III
• Application Number:
  US11/142,897
• Publication Number:
  US 20050278318A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

An iterative software development environment is provided to perform modified dependency analyses for use in building a target file and all the files on which it depends from one or more source files using a set of prioritized build rules. In one embodiment, the build rules indicate how different types of target files can be generated from different source file types. A given target file type may be associated with several rules, each having a different priority, for building the target from different source file types. In one embodiment, if more than one source file exists that can be used to generate a given target file, the rule with the highest priority is used. In one embodiment, the build environment identifies how to generate a particular target file by identifying the highest priority rule for which an associated source file type exists. Moreover, the development environment identifies the presence of a new source file having a corresponding build rule with a higher priority than that of the source file type(s) previously used in the generation of the target file. In one embodiment of the invention, the target file is rebuilt if such a new source file is identified, or if one or more source files previously used to build the target file are determined to have been modified more recently than that indicated by the build date/time of the target file itself.

Claims

1-36. -36. (canceled)

37. A computing device implemented method comprising:

determining by a computing device whether an application corresponding to a received request is present within a designated search path; and

generating by a computing device the application by compiling one or more source files, if it is determined that the application is not present within the designated search path.

38. The method as recited in claim 37, further comprising determining by a computing device whether regeneration of the application is needed, if it is determined that the application is present within the designated search path.

39. The method as recited in claim 38, further comprising regenerating by a computing device the application by compiling the one or more source files, if it is determined that the application is present and regeneration is needed.

40. A computing device implemented method comprising:

identifying by a computing device a target file corresponding to an application identified by a request;

accessing by a computing device a compilation rule associated with the identified target file, the compilation rule identifying at least a source file type for use in generating the associated target file; and

generating by a computing device the identified target file.

41. The method of claim 40, wherein said accessing comprises

selecting by a computing device the compilation rule from an ordered set of compilation rules.

42. The method of claim 40, wherein the generating comprises

determining by a computing device whether a source file corresponding to the source file type of the compilation rule exists within a designated search path.

43. The method as recited in claim 40, further comprising storing by a computing device a representation of the source file in a persistent data structure, if a source file corresponding to the source file type of the selected compilation rule exists within a designated search path.

44. The method as recited in claim 40, further comprising storing by a computing device a derived source file representation in a persistent data structure, if a source file corresponding to the source file type of the selected compilation rule does not exist within the designated search path.

45. An apparatus comprising:

a processor; and

a module operated by the processor and adapted to enable the apparatus to

determine whether an application corresponding to a received request is present within a designated search path; and

generate the application by compiling one or more source files, if it is determined that the application is not present within the designated search path.

46. The apparatus of claim 45, wherein the module is further adapted to enable the apparatus to determine whether regeneration of the application is needed, if it is determined that the application is present within the designated search path.

47. The apparatus of claim 46, wherein the module is further adapted to enable the apparatus to regenerate the application by compiling the one or more source files, if it is determined that the application is present and regeneration is needed.

48. An apparatus comprising:

a processor; and

a module operated by the processor and adapted to enable the apparatus to

identify a target file corresponding to an application identified by a request;

access a compilation rule associated with the identified target file, the compilation rule identifying at least a source file type for use in generating the associated target file; and

generate the identified target file.

49. The apparatus of claim 48, wherein the module is further adapted to enable the apparatus to select the compilation rule from an ordered set of compilation rules.

50. The apparatus of claim 48, wherein the module is further adapted to enable the apparatus to determine whether a source file corresponding to the source file type of the compilation rule exists within a designated search path.

51. The apparatus of claim 48, wherein the module is further adapted to enable the apparatus to store a representation of the source file in a persistent data structure, if a source file corresponding to the source file type of the selected compilation rule exists within a designated search path.

52. The apparatus of claim 48, wherein the module is further adapted to enable the apparatus to store a derived source file representation in a persistent data structure, if a source file corresponding to the source file type of the selected compilation rule does not exist within the designated search path.