Re: Retiring http/cometd and http/bundle
Thanks everyone, I removed both modules (and the corresponding sample) Regards Carsten Am 13.10.2022 um 09:37 schrieb Carsten Ziegeler: Hi, both modules http/cometd and http/bundle haven't been updated or released for years. I think its time to retire them and remove from the main branch. If interest picks up again we can easily restore it from history Regards Carsten -- Carsten Ziegeler Adobe cziege...@apache.org
Re: Retiring http/cometd and http/bundle
+1 Regards JB On Thu, Oct 13, 2022 at 9:37 AM Carsten Ziegeler wrote: > > Hi, > > both modules http/cometd and http/bundle haven't been updated or > released for years. > > I think its time to retire them and remove from the main branch. > If interest picks up again we can easily restore it from history > > Regards > Carsten > -- > Carsten Ziegeler > Adobe > cziege...@apache.org
Re: Retiring http/cometd and http/bundle
+1 On Thu, Oct 13, 2022 at 4:44 AM Rob Walker wrote: > +1 > > We've long since moved on to the newer/current bundle > > --- > Rob Walker > > -Original Message- > From: Karl Pauls > Sent: 13 October 2022 09:20 > To: dev@felix.apache.org > Subject: Re: Retiring http/cometd and http/bundle > > +1 > > regards, > > Karl > > On Thu, Oct 13, 2022 at 9:38 AM Carsten Ziegeler > wrote: > > > Hi, > > > > both modules http/cometd and http/bundle haven't been updated or > > released for years. > > > > I think its time to retire them and remove from the main branch. > > If interest picks up again we can easily restore it from history > > > > Regards > > Carsten > > -- > > Carsten Ziegeler > > Adobe > > cziege...@apache.org > > > > > -- > Karl Pauls > karlpa...@gmail.com > -- *Raymond Augé* (@rotty3000) Senior Software Architect *Liferay, Inc.* (@Liferay) OSGi Fellow, Java Champion
RE: Retiring http/cometd and http/bundle
+1 We've long since moved on to the newer/current bundle --- Rob Walker -Original Message- From: Karl Pauls Sent: 13 October 2022 09:20 To: dev@felix.apache.org Subject: Re: Retiring http/cometd and http/bundle +1 regards, Karl On Thu, Oct 13, 2022 at 9:38 AM Carsten Ziegeler wrote: > Hi, > > both modules http/cometd and http/bundle haven't been updated or > released for years. > > I think its time to retire them and remove from the main branch. > If interest picks up again we can easily restore it from history > > Regards > Carsten > -- > Carsten Ziegeler > Adobe > cziege...@apache.org > -- Karl Pauls karlpa...@gmail.com
Re: Retiring http/cometd and http/bundle
+1 regards, Karl On Thu, Oct 13, 2022 at 9:38 AM Carsten Ziegeler wrote: > Hi, > > both modules http/cometd and http/bundle haven't been updated or > released for years. > > I think its time to retire them and remove from the main branch. > If interest picks up again we can easily restore it from history > > Regards > Carsten > -- > Carsten Ziegeler > Adobe > cziege...@apache.org > -- Karl Pauls karlpa...@gmail.com
Retiring http/cometd and http/bundle
Hi, both modules http/cometd and http/bundle haven't been updated or released for years. I think its time to retire them and remove from the main branch. If interest picks up again we can easily restore it from history Regards Carsten -- Carsten Ziegeler Adobe cziege...@apache.org
Re: Cometd and http bundle
Am 01.10.15 um 18:52 schrieb Sten Roger Sandvik: > I am looking at the http bundle which contains jetty, bridge, cometd and > whiteboard. Have some questions regarding that. > > 1) It includes the whiteboard bundle, but I see that the new whiteboard > stuff is implemented in http.base. Should we still include the old > whiteboard jar or should we just remove it? If we do a http bundle, I guess we should include it for some time for compatibility. > > 2) I think that cometd is a little troublesome in the http.bundle. First, > it's bringing in SLF4J dependency. And second, it seems to me that this > cometd support is really optional and should just be provided on-top of the > bundle. > The idea of the http bundle is to have a single bundle that contains everything. > Or, maybe the http.bundle shoud not be there at all? Maybe we should just > have api, base, bridge, jetty and cometd bundles? > I think removing the http bundle but including the http api in the http jetty bundle is the better option. Users can then install the jetty bundle and if they want cometd they add that one, same with the felix whiteboard support etc. Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Cometd and http bundle
I am looking at the http bundle which contains jetty, bridge, cometd and whiteboard. Have some questions regarding that. 1) It includes the whiteboard bundle, but I see that the new whiteboard stuff is implemented in http.base. Should we still include the old whiteboard jar or should we just remove it? 2) I think that cometd is a little troublesome in the http.bundle. First, it's bringing in SLF4J dependency. And second, it seems to me that this cometd support is really optional and should just be provided on-top of the bundle. Or, maybe the http.bundle shoud not be there at all? Maybe we should just have api, base, bridge, jetty and cometd bundles?
