It unfortunately happens when there is a conflict as well... so if you have two ranges that cannot be resolved you get an OverConstrainedException which gets hidden with -X
do mvn -X and you will see the exception... and can traceback to the conflict On Wed, 20 Aug 2008 03:18:38 Alex. wrote: > This happen when Maven don't know whitch artifact version to use. > > > [INFO] Failed to resolve artifact. > > >> Couldn't find a version in [1.6] to match range [1.7,) > >> commons-digester:commons-digester:jar:null > -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
