On 2/16/07, Matt Raible <[EMAIL PROTECTED]> wrote: > I'm willing to bet this problem is caused by using the full Spring > dependency rather than fine-grained Spring dependencies. I use the > full Spring dependency and have experienced this issue as well. It's > too bad there's not a way in Maven to say "this JAR overrides all > others".
not yet, but it'll be in this case that's not the problem as i said in my previous answer. > This isn't the "Maven way" as they recommend using Spring's > fine-grained dependencies. However, I've found that the fine-grained > dependencies refer to artifacts that aren't in the Maven repos - so > the this way seems more pragmatic to me. ;-) i don't know what artifacts are missing, if you point it out you know that that things get fixed. if people keep using the coarse grained dependencies we'll keep getting this user questions all the time. > > Hope this helps, > > Matt ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Home: http://acegisecurity.org Acegisecurity-developer mailing list Acegisecurity-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
