On 7/20/05, J. Matthew Pryor <[EMAIL PROTECTED]> wrote: > Obviously the assembly plugin suits my needs very well here, as it does all > the work, but it also adds its own Manifest. > > I guess I saw an assembly simply as a 'superjar' but basically the same > artifact as the project is meant to produce, just one that includes > (transitively) all the dependent classes.
This sounds right. Assembly should let you specify your own manifest fields though - if it is not, its a bug. But what I'm thinking is that it should have an OSGi JAR format that will add these fields automatically using POM data. We could use the Maven1 OSGi plugin as a starting point: http://mavenosgiplugin.berlios.de/osgidevandbuild.html - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
