If you are on trunk then running the following will generate you a client build in client/release:
ant release-bin Though this mechanism is likely to change as Rajith says we do plan on doing granular release. Something like this should do the trick if you just have a release artifact: backport-util-concurrent-2.2.jar geronimo-jms_1.1_spec-1.0.jar qpid-client-X.jar commons-codec-1.3.jar log4j-1.2.12.jar qpid-common-X.jar commons-collections-3.2.jar mina-core-1.0.1.jar slf4j-api-1.4.0.jar commons-configuration-1.2.jar mina-filter-ssl-1.0.1.jar slf4j-log4j12-1.4.0.jar commons-lang-2.2.jar That said not sure why commons-configuration is in there, will have to check my local packaging. Regards Martin 2009/1/21 Rajith Attapattu <rajit...@gmail.com>: > Totally agree with you. > We are planning to make more granular releases from the next cycle onwards. > As a temp meassure, I can compile a list of jars needed by the client only. > You could then get rid of the rest of the jars. > > Regards, > > Rajith > > On Wed, Jan 21, 2009 at 12:56 AM, falconair <shahb...@gmail.com> wrote: > >> >> I just downloaded qpid M3 java and the number of jars is astounding. I >> suspect that most of them are of no interest to qpid client only (no qpid >> broker)...correct? If so, can we separate the client only jars? >> >> Thanks >> -- >> View this message in context: >> http://n2.nabble.com/java-qpid-client-only-libraries--tp2190674p2190674.html >> Sent from the Apache Qpid users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:users-subscr...@qpid.apache.org >> >> > > > -- > Regards, > > Rajith Attapattu > Red Hat > http://rajith.2rlabs.com/ > -- Martin Ritchie --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
