I too would like to see a bundle jar so users don't have to manage all the cxf-* jars.
Currently we have a manifest jar which helps in setting up the classpath (you only have to reference cxf-incubator.jar), but managing the cxf-* jars is unwieldy and a PITA. I would like to see us have a bundle jar which includes the most commonly used modules. Then people could add the jbi, jca, etc jars if they wanted. - Dan On 3/26/07, Hani Suleiman <[EMAIL PROTECTED]> wrote:
I agree, the packaging is very awkward right now, and it's hard to find out why anyone would think that having 8+ jars to deploy what is essentially one framework is a good idea. Obviously this isn't about dependencies, but rather about the cxf-* jars. Modularising them makes sense, but for some things it's hard to understand what the thought process was when deciding that 'api' should be separate from 'core'. When would you deploy one without the other? On Mar 26, 2007, at 3:06 PM, tog wrote: > Hi folks > > Thanks a lot for all the work you have done so far. I am > enthousiastic user. > My goal is to link cxf with a dynamic languages namely Groovy. > Among the > difficulty I currently have is the selection of jar files would it be > possible to have different kind of packaging for example (this is > only a > proposal) a full jarfile (including dependencies) cxf-all.jar, a > minimum jar > file (not including the dependencies) for example based on aegis. > Of course > this does not prevent you to propose the single jars. Such jars > will ease > the integration and does not require much additional effort. > > Best Regards > Guillaume > > -- > > > <a target="_blank" > href="http://www.google.com/calendar/render?cid=guillaume.alleon% > 40gmail.com > "><img src="http://www.google.com/calendar/images/ext/ > gc_button1_en.gif" > border=0></a>
-- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
