To compile in Maven, you might need to reference all these jars. But you will not need to deploy all those jars. There are many things behind the scenes that you don't see that require many other jars than you are used to. The more you mes with Maven, the more you will totally fall in love with everything it is providing. Even if you don't understand it right now.
Once you download those jars, they are local and you do NOT have to re-download everything each time. On Mon, Nov 24, 2008 at 2:02 PM, Steve Cohen <[EMAIL PROTECTED]> wrote: > I am trying to build a client to a web-service using their vendor-supplied > WSDL. The vendor-recommended approach is to use Maven with their pom.xml. > > building the source code brings in something like 50 jars. Only three > appear to be needed for compilation, but at runtime, I am adding jar after > jar to get my code over each succeeding hurdle. > > Is this really the way software is developed now? Call me old fashioned, > but I like to know what I'm depending on. It shouldn't require 50 jars to > run a simple SOAP client. What is the thinking behind this? Must I bite > the bullet, load all this crap, and stop thinking about it? > -- Thank You… Mick Knutson BASE Logic, inc. (415) 685-4233 Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Vacation Rental: http://tahoe.baselogic.com coming soon: 866-BLiNC-411: (254-6241-1) ---
