System and method for managing cross project dependencies at development time

1. A method for responding to a change in source code, said method comprising:

interconnecting, by an analysis stem, a plurality of nodes, each of the plurality of nodes representing a different software project to form a graph data structure wherein the graph data structure embodies at least one dependency between a plurality of software projects;

traversing, by the analysis system, the graph to identify dependent code affected by the change; and

evaluating, by the analysis system, the identified dependent code; wherein the changed source code is from a first software project and the identified dependent code is from a second software project; and wherein the plurality of nodes includes a binary-path, selected in order of dependency, that is an ordered list including references to a directory, locations of binary files, and other nodes wherein the order of the elements in the binary-path determines a search priority for resources that a corresponding project depend on.

2. The method of claim 1 , further comprising:

detecting the change to the source code.

3. The method of claim 1 , further comprising:

notifying the first software project of the evaluation.

4. The method of claim 1 wherein: a node of said plurality of nodes includes a list of one or more source files associated with a project.

5. The method of claim 1 wherein:

a software project is a logical container for the code associated with a software application.

6. The method of claim 1 wherein:

the graph data structure is directed and acyclic.

7. The method of claim 1 wherein:

a dependency is established by the use in one project of an application programming interface for a component defined in another project.

8. A system, comprising:

a processor; and

a memory;

wherein the processor is configured to

interconnect a plurality of nodes, each of the plurality of nodes representing a different software project to form a graph data structure wherein the graph data structure embodies at least one dependency between a plurality of software projects;

traverse the graph to identify dependent code affected by the change; and

evaluate the identified dependent code;

wherein the changed source code is from a first software project and the identified dependent code is from a second software project; and wherein the plurality of nodes includes a binary-path, selected in order of dependency, that is an ordered list including references to a directory, locations of binary files, and other nodes wherein the order of the elements in the binary-path determines a search priority for resources that a corresponding project depend on.

9. A non-transitory machine readable medium having instructions stored thereon to cause a system to:

interconnect a plurality of nodes to, each of the plurality of nodes representing a different software project form a graph data structure wherein the graph data structure embodies at least one dependency between a plurality of software projects;

traverse the graph to identify dependent code affected by a change;

evaluate the identified dependent code;

wherein the changed source code is from a first software project and the identified dependent code is from a second software project; and

wherein the plurality of nodes includes a binary-path, selected in order of dependency, that is an ordered list including references to a directory, locations of binary files, and other nodes wherein the order of the elements in the binary-path determines a search priority for resources that a corresponding project depend on.

10. The machine readable medium of claim 9 , further comprising instructions stored thereon to cause the system to:

detect the change to the source code.

11. The machine readable medium of claim 9 , further comprising instructions stored thereon to cause the system to:

notify the first project of the evaluation.

12. The machine readable medium of claim 9 wherein: a node of said plurality of nodes includes a list of one or more source files associated with a project.

13. The machine readable medium of claim 9 wherein:

a software project is a logical container for the code associated with a software application.

14. The machine readable medium of claim 9 wherein:

the graph data structure is directed and acyclic.

15. The machine readable medium of claim 9 wherein:

a dependency is established by the use in one project of an application programming interface for a component defined in another project.