Re: [equinox-dev] Equinox HTTP component move to jakarta namespace

[Christoph Läubrich <laeubi@xxxxxxxxxxxxxx>]

Hi Mark,

in general contributions are always welcome and I don't see a reason why 
the servlet bridge should not be supporting both (javax+jakarta) like 
Felix Http, or only use jakarta if no further dependencies exit to the 
old HttpService.

The process would be roughly to open a PR with the proposed changed, 
then they get reviewd, merged and if all this happens in a timley manner 
it could be part of the next 2024-09 eclipse release.

HTH

Am 16.07.24 um 17:47 schrieb Mark Hoffmann:
> Hi Christoph,
>
> I wanted to say all I would migrate equinox.http.* including the http 
> whiteboard implementation. I do not intend to migrate the http service.
>
> We need this old stuff because the customer uses the servletbridge and 
> some other components the reuse the servlet container implementation 
> from a JakartaEE server. If you are interested they still use Riena, 
> also an Eclipse project that is not active anymore (maybe someone 
> remembers it).
>
> In general I dont asked, if the community does it or plans it. I would 
> do this and contribute the work, if someone is interested.
>
> Means, I will do it anyways, at least by forking.
>
> I open a github discussion.
>
> Thanks,
>
> Mark Hoffmann
> M.A. Dipl.-Betriebswirt (FH)
> CEO/CTO
>
> Phone: +49 3641 384 9100 <tel:+49 3641 384 910>
> Mobile: +49 175 701 2201 <tel:+49 175 701 2201>
> E-Mail: m.hoffmann@xxxxxxxxxxxxxxxx
>
> Web: www.datainmotion.com
>
> Data In Motion Consulting GmbH
> Kahlaische Strasse 4
> 07745 Jena
> Germany
>
> Geschäftsführer/CEO
> Mark Hoffmann
> Jürgen Albert
>
> Jena HRB 513025
> Steuernummer 162/107/05779
> USt-Id DE310002614
>
>
> -------- Ursprüngliche Nachricht --------
> Von: Christoph Läubrich via equinox-dev <equinox-dev@xxxxxxxxxxx>
> Datum: 16.07.24 16:23 (GMT+01:00)
> An: equinox-dev@xxxxxxxxxxx
> Cc: Christoph Läubrich <laeubi@xxxxxxxxxxxxxx>
> Betreff: Re: [equinox-dev] Equinox HTTP component move to jakarta namespace
>
> Hi Mark,
>
> Equinox uses Github Discussions now [1] so it would be best to start a
> new thread there.
>
> Beside that, its is quite unlikely that this will happen for the
> following reasons:
>
> 1) it would be a breaking change for consumers
> 2) all of this is based on the HttpService that was dropped from the
> current OSGi Spec and there are no plans to revive it [2]
> 3) today one would use Http Whiteboard Specification [3]
>
> So if you want to have "old" equinox-http upgraded I fear there is
> little hope (beside simply fork that part) but I see some potential to
> move Eclipse (mainly the helpcenter) to Http Whiteboard Specification
> would be the path forward.
>
> [1] https://github.com/eclipse-equinox/equinox/discussions
> [2] https://github.com/osgi/osgi/issues/551
> [3]
> https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.http.whiteboard.html
>
> Am 16.07.24 um 15:16 schrieb Mark Hoffmann via equinox-dev:
>  > Hello together,
>  >
>  > for a customer project it seems we need to move the Equinox HTTP bundles
>  > (except the jetty) from javax into jakarta namespace. This also belongs
>  > to the servlet and servletbridge bundles.
>  >
>  > Are there interests in such an contribution? If yes, how can this be
>  > handled regarding the release management.
>  >
>  > Regards,
>  >
>  > Mark
>  >
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/equinox-dev