cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mick Knutson" <>
Subject Re: Grr. Maven.
Date Mon, 24 Nov 2008 19:21:41 GMT
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 <> 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

BLiNC Magazine:
Linked IN:
DJ Mick:
Vacation Rental:

coming soon: 866-BLiNC-411: (254-6241-1)

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message