Thanks for the responses. I thought there was greater usage of maven as a build system and as such that people on the list might have examples or war stories to share. Looks like i'll get the pioneering enjoyment.
Thanks, Cam On 7/10/07, Glen Mazza <[EMAIL PROTECTED]> wrote:
Am Montag, den 09.07.2007, 16:00 +0100 schrieb Cameron Jones: > After a bit more playing round today i'm slightly concerned by the > number of dependencies which cxf has... before adding > cxf-rt-frontend-jaxws, cxf-rt-transports-http and > cxf-rt-transports-http-jetty to my pom i had 9 libraries and > afterwards i have 51. > > Does CXF really need 42 libraries to do a simple web service? > > Cam > I doubt it. But I don't believe many people use Maven to generate their web services, so CXF's Maven implementation may not have incurred the simplifications/optimizations over the months that would come from heavy usage, users supplying patches, etc. It might just download all libraries by default. In the past, I have found using Ant to be very useful in streamlining libraries needed[1]. Although such a downsizing needs to be done by the user, by explicitly listing the libraries in a <classpath/> it becomes nicely self-documenting which jars you need, and have the added benefit of knowing that the system is not compiling/running on CLASSPATH classes that you might be unaware of. I think the fundamental problem is that (AFAIK) Maven by itself does *not* have the ability to go through Java source code, and from that, determine which JARs are needed. If that was your reason in wanting to use Maven, you may end up being disappointed. At any rate, if you can offer any improvements with CXF Maven's implementation, please send them via JIRA. Regards, Glen [1] http://marc.info/?l=axis-user&m=117932579025508&w=2
