Nathan, Yup, that's pretty much it. For a most of muse, there's a 1 to 1 mapping of jars to bundles, so in effect I just need to make alternative versions of the jars with a different manifest. For one particular set (the util-* jars), I need to actually combine them into a single jar with a different manifest.
I've started looking into creating a jar-re-packager plug-in, but I'd be more than happy to abandon that approach if you've got a better one! Thanks, Joel -----Original Message----- From: Nathan Sowatskey [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 18, 2006 8:52 AM To: [email protected] Subject: Re: Stupid Maven Questions Hi I always check the requirements before commenting on the implementation ;-) So, what is it you want to achieve here? It reads like you want to create OSGi deployment bundles (just so you know I actually read the email ;-) ), but I don't want to project my assumptions :-) Regards Nathan Hawkins, Joel wrote: > Hey Nathan - I guess these are for you! > > For the OSGi support, a large part of what I'm doing is repackaging > existing code. I've got two cases, really. The first is a pretty > straight-forward repackaging, where I need to replace the > Maven-generated manifest with an OSGI-specific manifest. I'm assuming > some clever use of resource filters and properties may accomplish this? > (Did a bit of reading from 'Better Builds with Maven). The second has me > stumped - and that is the need to combine multiple jars (in this case, > all of the muse-util* targets) into a single jar. In Maven 2.0, I can > apparently broom up resources from multiple directories, but I can't > specify multiple source trees to the compiler. Should I try to compile > from multiple source trees? Should I (somehow) get the jars I'm trying > to repackage, unjar and then rejar them? I know I can do all this in > ant, but using the ant integration features seems like cheating. Can you > point me to an example of the Maven-approved way of doing these? > > Thanks 10^6, > Joel > The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Nathan Sowatskey - Technical Leader, NMTG CTO Engineering - Desk +34-91-201-2139 - Mobile +34-638-083-675 - AIM id NathanCisco - [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
