You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Gary Gregory <ga...@gmail.com> on 2016/12/22 20:51:54 UTC
OSGi vs. not
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
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
JUnit in Action, Second Edition
<https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
Spring Batch in Action
<https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: OSGi vs. not
Posted by Gary Gregory <ga...@gmail.com>.
But yeah, I see you point about not dragging in extra deps.
Gary
On Dec 23, 2016 8:51 AM, "Gary Gregory" <ga...@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" <ol...@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
>>
>>
Re: OSGi vs. not
Posted by Gary Gregory <ga...@gmail.com>.
Over at Log4j and Commons, we add the OSGi stuff to the normal jars.
Gary
On Dec 23, 2016 2:04 AM, "Oleg Kalnichevski" <ol...@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
>
>
Re: OSGi vs. not
Posted by Oleg Kalnichevski <ol...@apache.org>.
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