> -----Original Message----- > From: Ben Walding [mailto:[EMAIL PROTECTED]
Hi Ben, Thanks for the response. > "Maven's not going to figure out the package dependency graph of > my projects." > > Why not? I ask, why would it? It's not analyzing Java source to build a dependency graph of the Java packages (a la JDepend or Pasta). It's sorting a set of jar file names. In Maven a dependency is just a jar file name and nothing more, right? Unfortunately, there's no distinction between a static jar file/resource dependency and an inter-project dependency where a project dependency indicates a need to execute one project (and spit out the named jar) before executing the dependent project. > Have you placed the inter project dependencies properly? I believe so, but how would I know? For example, all my projects have a dependency on the jar produced by the kernel-system project, except kernel-system itself. Shouldn't kernel be sorted first? It's not. It comes out second to last in one sort, and fourth in another. Doesn't anyone use Maven in a waterfall/cascading build, where one project builds, outputs a jar, next project picks up that jar, builds, outputs a jar, next project uses the jars produced by the previous two projects, etc. That sort of thing? Scott Stirling Framingham, MA --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
