1. Yes, if you want to have your classes in a jar, this involves a multi-module approach - have a separate project for your classes with jar packaging and another project with ear packaging, having a dependency to the jar project.
2. If you want to exclude some dependencies from the ear but you need them for compilation, change their scope to provided - this does exactly what you need. Regards, Richard Gerard Garrigan wrote: > > Hello, > > I have some issues that are slightly different to my last email on the > topic. > > I'm generating an ear file for a project. The requirement is that the > java classes for that project are put into a jar prior to being included > in the ear. Does this still fall under the multiple module approach or > is there some other way of achieving this? Also when I generate the ear > all the projects dependant jars are included. Is there some way of > generating the ear without including all the jars as they are being set > in the classpath already and they make the ear file very large? > > > > Thanks again, > > Ger Garrigan > Software Engineer > -- View this message in context: http://www.nabble.com/The-generated-ear-file-t1374035.html#a3687946 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
