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]

Reply via email to