on the second thought, if you can whip you installer easily thru a small ant script, you can use maven-antrun-plugin to create the installer, then use build-helper-maven-plugin to attach your output to be installed/deploy
-D On 4/25/06, Martin Cooper <[EMAIL PROTECTED]> wrote: > > On 4/25/06, dan tran <[EMAIL PROTECTED]> wrote: > > > > take a look at > http://mojo.codehause.org/maven-native/native-maven-plugin > > > That would be: > > http://mojo.codehaus.org/maven-native/native-maven-plugin/ > > (No 'e' on the end of codehaus ;) > > -- > Martin Cooper > > > it uses build lifecyle extension to provide its own packaging type. > > > > -Dan > > > > > > On 4/25/06, Marteijn Nouwens <[EMAIL PROTECTED]> wrote: > > > > > > Hello everybody maybe are repost but my subscribing went wrong, > > > > > > I am new to maven 2.0. but experienced 1.0 user. > > > > > > Do i understand correctly that packaging defines the type of product > > that > > > is > > > being build. If so, can you define more than one and define your own > > > custom > > > types. like installer and application. With matching plugins. > > > > > > Thanks > > > > > > > > > > > >
