So, Dependency Resolution has problems - and isn't that the whole REASON to use Maven? No wonder I keep wondering what the point of Maven is...
-----Original Message----- From: Barrie Treloar [mailto:[email protected]] Sent: Tuesday, March 15, 2011 5:45 PM To: Maven Users List Cc: Dirk Olmes Subject: Re: Extra dependency added to eclipse projects On Tue, Mar 15, 2011 at 7:33 PM, Dirk Olmes <[email protected]> wrote: > On 03/15/2011 05:45 AM, Jason Nerothin wrote: > > I mean the following suggestion in all seriousness (because I think > > it might work to help find your problem). > > > > 1. Download IntelliJ Idea 10, ultimate edition. You'll get a free 30 > > day trial. > > Great tip. But I'd really like to understand what it does different from > e.g. dependency:tree. I encountered this kind of situation before, > albeit with Maven 2.0.x and always wondered why dependency:tree and > project-info-reports:dependencies come to different results. > > Dependency resolution is a known short coming that is not easily isolated in the code base and therefore not easily re-usable in a consistent manner. I think that's being worked on in 3.0. This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
