This is simply an incorrect assumption on your part. If you use <modules> and set up <dependencies> between them etc, the code will be packaged up in its own module-specific jar. So you would expect to only see commons-specific code in the commons.jar, and client-specific code in the client.jar. This is how Maven works without additional configuration.
There are ways to put all the code in one big jar, but this is not the default and not the normal way to use Maven. Google (or search the Maven website) for "jar-with-dependencies" and the assembly plugin for more details. Or search the Maven Users archive, this comes up every couple of weeks. Wayne On Mon, May 5, 2008 at 6:37 PM, Nicola Benaglia <[EMAIL PROTECTED]> wrote: > Hi, > I started up a project consisting of 3 modules (to learn maven): > > commons > client > server > > client and server depends on commons and I want to open the client.jar and > see all packages of commons + all packages of client. > > So far I open client.jar and see only its packages and not its father's one > (commons) as I was expected. > > Could you please help me? > > Thank you, > Nicola > > --------------------------------------------------------------------- > 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]
