Hi Peter, I am working about source code dependencies analyse algorithm design and implement job, i will finish the whole analyse algorithm in the coming month. This algorithm include two sections: package and class.
1. Package section a. It can analyse package cycles in project source code b. Analyse all the necessary packages for each package c. Tell us who use it about each package 2. Class section a. This algorithm will tell us all the class cycles in project source code (for example A -> B -> C -> A) b. Analyse all the necessary classes for each class (for example, it can tell us class A use class B, C and D) c. Tell us who use it about each class (for example, it can tell us class A was used by class B and C) After we get the source code analyse report, we should split the project into several OSGi bundles, so the problems is how should we split the project according to the report. In my initial option: A. classes in a cycle should be in the same bundle B. classes (or interfaces ) which were used much by other classes, but does not require any other class, can be in the same bundle. (Usually, these are basic interface or abstract class). These classes usually be API define classes. I am very clear about these two situations, but there should be many other situations. So, you advises ? -- Best Regards ---------------------------------------------------- Tiger Gui [[email protected]]
