Hi, We have a project with about 50 subprojects, and, on average, each subproject has 20 dependencies. Every time we try to compile all subprojects, the reactor takes about 17 minutes to determine the order of the subprojects. I found that the reactor is trying to sort all the dependencies, even the third party software dependencies, and the ones that are not in the scope of the compile. Can't the dependency graph be pruned of all necessary dependencies before looking for cycles? I also found that there is an alternate Dependency Resolver. My tests showed that it was much faster that the default one ( about 5 minutes ) to order the dependencies using the option -Dmaven.core.dependencyresolver=org.apache.maven.jelly.tags.maven.GraphDepen dencyResolver Is there any reason why this is not the default resolver? Is there any reason that I should not be using it? Any help would be appreciated Thanks! Eric
