Hi Nathan,

I was going to use MUSE-38 (the JIRA for checking in OSGi support) to
put all my OSGi java and maven stuff in. It's due at the end of the
week. Let me know how you'd like to proceed - if you want to send me an
example, point me to the correct reference info, or attach a sample
POM.xml to the JIRA - up to you. 

Thanks again for the help,
Joel

Perhaps it makes more sense to  
-----Original Message-----
From: Nathan Sowatskey [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, July 18, 2006 11:10 AM
To: [email protected]
Subject: Re: Stupid Maven Questions

Got it, is there a Jira entry for this? Also, what is the priority and 
when do you need it by?

Many thanks

Nathan

Hawkins, Joel wrote:
> Sure! I'll give you one from each end, and then I should be able to
copy
> your solution:
> 
> muse-wsa-soap-2.0.0-M2-SNAPSHOT.jar -> org.apache.muse.wsa.soap.jar
with
> the following manifest - 
> 
> Manifest-Version: 1.0
> Bundle-ManifestVersion: 2
> Bundle-Name: Soap Plug-in
> Bundle-SymbolicName: org.apache.muse.wsa.soap
> Bundle-Version: 1.0.0
> Bundle-Localization: plugin
> Export-Package:
> org.apache.muse.ws.addressing,org.apache.muse.ws.addressing.soap
> Require-Bundle: org.apache.muse.util
> Import-Package: javax.xml.soap
> 
> 
> And 
> muse-util-2.0.0-M2-SNAPSHOT.jar,
muse-util-qname-2.0.0-M2-SNAPSHOT.jar, 
> muse-util-xml-2.0.0-M2-SNAPSHOT.jar, and
> muse-util-xstream-2.0.0-M2-SNAPSHOT.jar combine into
> org.apache.muse.util.jar with the following manifest - 
> 
> Manifest-Version: 1.0
> Bundle-ManifestVersion: 2
> Bundle-Name: Util Plug-in
> Bundle-SymbolicName: org.apache.muse.util
> Bundle-Version: 1.0.0
> Bundle-Localization: plugin
> Export-Package: javax.xml.namespace,
>  org.apache.muse.core.serializer.xstream,
>  org.apache.muse.util,
>  org.apache.muse.util.messages,
>  org.apache.muse.util.uuid,
>  org.apache.muse.util.xml
> Import-Package: org.apache.xml.serialize,
>  org.apache.xpath,
>  org.apache.xpath.axes,
>  org.apache.xpath.compiler,
>  org.apache.xpath.domapi,
>  org.apache.xpath.functions,
>  org.apache.xpath.jaxp,
>  org.apache.xpath.objects,
>  org.apache.xpath.operations,
>  org.apache.xpath.patterns,
>  org.apache.xpath.res
> 
> -----Original Message-----
> From: Nathan Sowatskey [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, July 18, 2006 10:28 AM
> To: [email protected]
> Subject: Re: Stupid Maven Questions
> 
> OK, got it.
> 
> What you want to do here is probably the same as an Eclipse plugin, 
> which are also OSGI bundles. I am not an expert in this aspect of
Maven,
> 
> but at least I have a better idea of where to look now :-)
> 
> Do you have a list of which bundles you want from which jars?
> 
> Many thanks
> 
> Nathan
> 
> Hawkins, Joel wrote:
>> 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 - 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]

Reply via email to