Hi Dan, Editting the META-INF/MANIFEST.MF to include a "Class-Path: " entry seems to do the trick.
As for creating the jars, I am currently manually creating the 3 jars by making copies of the output "war" from the (in this case, html-viewer module), as produced by "mvn -o clean package". In each of the copies, I am deleting the parts that don't belong - i.e. in my "application domain" jar, I delete everything but the domain directories, etc. The application domain jar also is the only jar to contain a Main Class statement in the manifest. So, not fully automatic, but close enough. Now I can upload just 1 or 2 portions to the client's server.. I may look into how to get the package plugin to automate this later. Regards, Kevin On 25 May 2011 at 22:19, Dan Haywood wrote: > Hi Kevin, > It is possible to have the master jar reference other JARs, using the > Class-Path: entry in its META-INF/MANIFEST.MF file. For details, see [1] > > A separate problem is how to create the different JARs in the first > place. Maven works best when you arrange it such that each module > creates a single artifact. So I think you could create new plugins to > represent aech the different bits of the JAR that you want, and use the > shade plugin just in these dependent modules but *not* for the module > that will have the customised manifest. > > HTH > Dan > > [1] http://download.oracle.com/javase/tutorial/deployment/jar/downman.html
