On Wed, Nov 26, 2008 at 7:10 PM, CheapLisa <[EMAIL PROTECTED]> wrote: > > setting the Class-Path in MANIFEST.MF can be done (and should be done) with > the assembly plugin. There is an option for that.
It may do that. What I have posted will work and is perfectly acceptable. By using the jar plugin you are saying that the jar containing your Main class also has known dependencies which must be on the classpath. And that this artifact will be in your maven repository. By using the assembly plugin (and I am guessing) then the assembly plugin must change your artifact containing the Main jar to include a classpath definition. Which doesn't feel right. > Also copying jars to a lib/ directory (and checking them in) is the reason > we moved away from ant to maven and I do not believe this is necessary. Where did I say that you check in a lib directory? The assembly is built in target/<artifact>-bin.zip and the ZIP file contains a lib/ directory. When you unzip the -bin.zip file your executable bundle will have all your dependencies located in the lib/ directoy. Perhaps you should try the example first and see what it does prior to commenting? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
