cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Mazza <>
Subject Re: Change to full spring jar?
Date Fri, 28 Mar 2008 22:26:32 GMT

I'm basically neutral on this, but I want to make sure the first advantage is
legitimate.  Are you sure you can't use "-DdownloadSources=true" on your mvn
eclipse:eclipse to grab the source files of the subsetted JARs of Spring? 
(I.e., you indeed see no source entries in the .classpath file if you do
that?)  It would seem unnatural for the Spring project to require you to
embed their full JAR just so you can get the source to the subset that you
need for Eclipse debugging.


dkulp wrote:
> What are peoples thoughts about changing from using the minimal spring 
> jars to using the full spring jar?
> The main advantages I see are:
> * Debugging is eclipse works as the full spring jar has the sources jar 
> in maven.   This is huge to me. :-)
> * Only one jar to deal with in lib (kind of, see disadvantages)
> * Would be a little bit easier to write some of the testcases and stuff 
> around some of the other features (like aop) as we wouldn't need to 
> track down so of those extra dependency jars and such.
> Main disadvantages:
> * The main spring jars sucks in a TON of dependencies.   We'll have to 
> look at it very carefully for things that can/should be excluded.  
> Otherwise, we get a ton of EXTRA jars in lib.
> * It's slightly larger.
> Thoughts?
> -- 
> J. Daniel Kulp
> Principal Engineer, IONA

View this message in context:
Sent from the cxf-dev mailing list archive at

View raw message