We have a separate project that wants to use a module with jar packaging, the core, from another project. That core module's dependencies take their artifact versions from dependencyManagement in its parent pom (which we understand is a good practice). When the core is installed to the local maven repository the core pom is packaged with it, but not the parent pom. So now it seems the versions of the core dependencies can't be determined. We would like to know how this should be done. Would it be to create the same dependencies (runtime) in the new project pom? Or would it be to add dependencyManagement to that pom? Either way seems un-maven-like, as that project seems to have to define the transitive dependency verisions of one of its artifacts. Maybe there is another way? During install, could the effective core pom be packaged instead of the literal pom?
Put another way: What is the right way to depend on only one module of a multiple module project that uses dependencyManagement? Thanks, Richard Brewster Senior Associate Perrin Quarles Associates [EMAIL PROTECTED] (434) 817-2640
