cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Cohen <>
Subject Re: Grr. Maven.
Date Mon, 24 Nov 2008 19:46:54 GMT
To compile my client I only needed three of them.  To run my client, 
connect to the vendor's Web Service, I have to keep adding things to my 
runtime classpath. 

I am also trying to think a couple steps ahead, when I go from my simple 
client test application to deploying my client inside an existing Tomcat 
WebApp which has a completely different mechanism for managing runtime 
dependencies.  This is why I like to know what I need and why I need 
it.  But it seems the stars are aligning against my philosophy.

How is a Maven repository typically accessed in a runtime production 

Mick Knutson wrote:
> 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?

View raw message