Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v753)
In-Reply-To: <47945445.5030400@bestsolution.at>
References: <47692CCB.7020608@apache.org>
	 <55afdc850712191242k32107b51pa1d4f83291bedb0a@mail.gmail.com>
	 <8ED8F00A-73D1-4BB9-BA79-7D805060E11F@apache.org>
	 <476A73F1.4000801@apache.org>
	 <4c39e3030712200601m6ee67bd4jd8233f04bf841668@mail.gmail.com>
	 <476A7830.8010500@apache.org>
 <4774EDAB.1060208@apache.org>	 <1a5b6c410712280639h139c7e20p1ac40a3a9c58c148@mail.gmail.com>
 <55afdc850801170850l2d614e9ep9efd3df9c403e046@mail.gmail.com>
 <47945445.5030400@bestsolution.at>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2A976906-8326-4DE8-B262-9D6C940BD774@apache.org>
Content-Transfer-Encoding: 7bit
From: Torsten Curdt <tcurdt@apache.org>
Subject: Re: Support for OSGi
Date: Mon, 21 Jan 2008 09:32:47 +0100
To: "Jakarta Commons Developers List" <dev@commons.apache.org>

Not everyone is using OSGi ...so I doubt this is really an option to  
prevent a package shift.

My 2 cents
--
Torsten

On 21.01.2008, at 09:13, Tom Schindl wrote:

> Hi,
>
> Couldn't this OSGi-adoption made by some commons packages make the  
> package shift for java5 unneeded?
> With OSGi one can run different versions in the same JVM so its not  
> needed any more.
>
> Tom
>
> Niall Pemberton schrieb:
>> On Dec 28, 2007 2:39 PM, Carlos Sanchez <carlos@apache.org> wrote:
>>
>>> Two things:
>>>
>>> - if the bundle plugin could be released, it'd be great, if not
>>> projects won't be able to make a release
>>>
>>> - my approach to add an osgified manifest to the current project is
>>> different in order not to change the packaging to bundle. bundle
>>> packaging only needs to be used to osgify 3rd party libraries. The
>>> manifest goal of the bundle plugin will generate the OSGi  
>>> manifest for
>>> any maven project.
>>>
>>
>> I missed this originally - is there any reason to not use  
>> packaging of
>> "bundle" and let the bundle plugin create the jar?
>>
>> Seems like that would be an easy way to turn it on/off for components
>> (the recommendation for logging was to not do it).
>>
>> Niall
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org