One way of updating the manifest is to unpack the original one (by using the dependency plugin for instance) and then re-pack it with the jar plugin specifying the updated manifest. It won't be fast though...
/Anders On Tue, Oct 20, 2009 at 19:19, _MS_ <[email protected]> wrote: > > I have following project: > > project > |-src > |-target > |-data > |README > |log4.properties > > These project has several library dependencies e.g. > log4j, junit, commons-vfs etc. > > My goal is to build module that I can install to my local repository and > also I want to make distribution with following layout: > > dist > |-lib(folder containing all dependency libraries) > |-project.jar(modified jar, manifest should contain Main-Class and > Class-Path sections, based on new layout) > |-data > |README > |log4j.properties > > The problem is that I want to be able to do two things: > 1. build pristine module(only contains compiled classes) > 2. build final distribution conforming to layout mentioned above. In order > to run application directly using > java -jar project.jar > > My question is really how would one go and change final module's MANIFEST. > Namely this module's MANIFEST would have to include those aforementioned > sections > Main-Class and Class-path. > > I can produce final distribution using assembly descriptor but I'm unable > to > change MANIFEST. > > If needed I can post my custom assembly descriptor. > > > -- > View this message in context: > http://www.nabble.com/How-to-change-jar-manifest-with-assembly-plugin-tp25979104p25979104.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
