I'll play devil's advocate here. What if the client jar has only a couple of classes, which are exactly the same as the ones included in the server jar. It doesn't make sense to me to have duplicate code in two locations.
I think the answer you will give will be to have a common project again which would hold those duplicate classes. How do you in include classes from project a in project c? Ruel Loehr JBoss QA -----Original Message----- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Monday, February 27, 2006 8:02 AM To: Maven Users List Subject: Re: [M2] Creating client jar On 2/27/06, Kees de Kooter <[EMAIL PROTECTED]> wrote: > I am building a client server project. A handful of interfaces need to > be distrubuted to the client. At the moment we use an ant script for > this. > > I would like to include this in the maven build process of the server > component. So I want to jar up a selection of .class files and publish > this to our repository so the client-side developers can pick it up in > their build process. The proper way to do this would be a "client" project, which emits a "client" jar file. The server project could then use the "client" project as a dependency. If the "client" is more than simply those interfaces, use a "common" project, on which both client and server depend. Jochen -- Whenever you find yourself on the side of the majority, it is time to pause and reflect. (Mark Twain) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
