hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: OSGi vs. not
Date Fri, 23 Dec 2016 16:52:29 GMT
But yeah, I see you point about not dragging in extra deps.

Gary

On Dec 23, 2016 8:51 AM, "Gary Gregory" <garydgregory@gmail.com> wrote:

> Over at Log4j and Commons, we add the OSGi stuff to the normal jars.
>
> Gary
>
> On Dec 23, 2016 2:04 AM, "Oleg Kalnichevski" <olegk@apache.org> wrote:
>
>> On Thu, 2016-12-22 at 12:51 -0800, Gary Gregory wrote:
>> > Hi,
>> >
>> > WRT to the VOTE and
>> >
>> >  224816183f20c871d453b648d465a813 httpcomponents-core-5.0-
>> > alpha2-osgi-bin.zip
>> >  b8947275fe21cde3e99ee554b9464a95 httpcomponents-core-5.0-alpha2
>> -src.zip
>> >
>> > Why do we have an OSGi download? What's the diff?
>> >
>> > Gary
>> >
>>
>> There are two main distinctions
>> (1) OSGi bundles usually pull in several Maven artifacts
>> (2) They also include OSGi specific functionality such as OSGi container
>> integration. This is presently not the case with HttpCore but is
>> certainly the case with HttpClient.
>>
>> I am aware that many projects simply add OSGi metadata to their Maven
>> artifacts and do not bother with OSGi specific bundles. I am perfectly
>> fine with revising our approach to OSGi support as long as someone is
>> willing to make it consistent across all our projects.
>>
>> I often cannot help feeling that if we are not able to maintain our OSGi
>> stuff properly we would be better off dropping it entirely.
>>
>> Oleg
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
>> For additional commands, e-mail: dev-help@hc.apache.org
>>
>>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message