mvn -X install will give you the debug info including things like [DEBUG] Retrieving parent-POM from the repository for project: plexus:plexus-components:pom:1.1.2 [DEBUG] plexus:plexus-compiler-api:jar:1.5 (selected for compile) [DEBUG] junit:junit:jar:3.8.1 (selected for compile) [DEBUG] plexus:plexus-container-default:jar:1.0-alpha-6 (selected for compile) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for compile) [DEBUG] plexus:plexus-utils:jar:1.0.2 (removed - nearer found: 1.0.3) [DEBUG] plexus:plexus-utils:jar:1.0.2 (selected for compile)
which should get you going.. jesse On 10/19/05, Brill Pappin <[EMAIL PROTECTED]> wrote: > > I'm trying to set up my first m2 project and am having a lot of dependency > issues. Most seem to be broken dependencies in dynamically included POMs. > > It's pretty annoying the lib developers don't check this, but the only > thing > to do in the short tem is install them myself and send in a bug report to > the developers of the lib. > > Now, finding the broken dep is the hard part... is there a switch I can > add > when running m2 that will tell me what POM had the dynamic dependency that > was not listed correctly? > Without that information, it's kind of hard to find it. > -- jesse mcconnell
