I've been experimenting with the assembly plugin and it looks like it unpacks the dependent jars and creates a large jar with dependencies built-in into one plugin. Is this the preferred deployment mechanism?
I can see benefits to this--namely tying it to the build and source more easily. Are there any benefits to releasing the individual JARs and the dependent JARs packaged in a lib directory referenced from the manifest of the main modules JAR file? Is there a way to accomplish this with an existing plugin? Would I want to? I'm working on a command line app for someone. Most of my prior work had been either Web based (either Webstart or Web apps) so I'm not sure of what the best practice is for this. Brian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
