[jira] [Resolved] (FELIX-6636) Migrate to Jakarta Servlet Whiteboard
[ https://issues.apache.org/jira/browse/FELIX-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6636. - Resolution: Fixed https://github.com/apache/felix-dev/commit/f7798e18205dd6d0c6d012a1b95c5b5de65c8a97 > Migrate to Jakarta Servlet Whiteboard > - > > Key: FELIX-6636 > URL: https://issues.apache.org/jira/browse/FELIX-6636 > Project: Felix > Issue Type: Improvement > Components: Health Checks >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: healthcheck.core 2.2.0 > > > The hc core is currently based on javax.servlet and the corresponding > whiteboard. We should update to jakarta.servlet and the jakarta servlet > whiteboard. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6636) Migrate to Jakarta Servlet Whiteboard
Carsten Ziegeler created FELIX-6636: --- Summary: Migrate to Jakarta Servlet Whiteboard Key: FELIX-6636 URL: https://issues.apache.org/jira/browse/FELIX-6636 Project: Felix Issue Type: Improvement Components: Health Checks Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: healthcheck.core 2.2.0 The hc core is currently based on javax.servlet and the corresponding whiteboard. We should update to jakarta.servlet and the jakarta servlet whiteboard. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Release Healthcheck Core 2.1.0 and Generalchecks 3.0.8
+1 regards, Karl On Thu, Aug 24, 2023 at 5:43 PM Raymond Augé wrote: > > +1 > > On Thu, Aug 24, 2023 at 11:20 AM Carsten Ziegeler > wrote: > > > Hi, > > > > We solved one issue for healthcheck core: > > https://issues.apache.org/jira/browse/FELIX-6565 > > > > and two issues for healthcheck generalchecks: > > https://issues.apache.org/jira/projects/FELIX/versions/12353414 > > > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachefelix-1469 > > > > You can use this UNIX script to download the release and verify the > > signatures: > > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh > > > > Usage: > > sh check_staged_release.sh 1469 /tmp/felix-staging > > > > Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] -1 Veto the release (please provide specific comments) > > > > This vote will be open for 72 hours. > > > > Regards > > Carsten > > -- > > Carsten Ziegeler > > Adobe > > cziege...@apache.org > > > > > -- > *Raymond Augé* (@rotty3000) > Senior Software Architect *Liferay, Inc.* (@Liferay) > OSGi Fellow, Java Champion -- Karl Pauls karlpa...@gmail.com
Re: [VOTE] Release Apache Felix Http Jetty 5.1.0, Http Bridge 5.1.0, Http Base 5.1.0 and Http Wrappers 1.0.0
+1 regards, Karl On Thu, Aug 24, 2023 at 3:15 PM Raymond Augé wrote: > > +1 > > On Thu, Aug 24, 2023 at 9:09 AM Thomas Watson wrote: > > > +1 > > Tom > > > > On Thu, Aug 24, 2023 at 12:32 AM Carsten Ziegeler > > wrote: > > > > > Hi, > > > > > > We solved one issue in these releases: > > > https://issues.apache.org/jira/browse/FELIX-6632 > > > > > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachefelix-1468 > > > > > > You can use this UNIX script to download the release and verify the > > > signatures: > > > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh > > > > > > Usage: > > > sh check_staged_release.sh 1468 /tmp/felix-staging > > > > > > Please vote to approve this release: > > > > > > [ ] +1 Approve the release > > > [ ] -1 Veto the release (please provide specific comments) > > > > > > This vote will be open for 72 hours. > > > > > > Regards > > > Carsten > > > -- > > > Carsten Ziegeler > > > Adobe > > > cziege...@apache.org > > > > > > > > -- > *Raymond Augé* (@rotty3000) > Senior Software Architect *Liferay, Inc.* (@Liferay) > OSGi Fellow, Java Champion -- Karl Pauls karlpa...@gmail.com
Re: [VOTE] Release Healthcheck Core 2.1.0 and Generalchecks 3.0.8
+1 On Thu, Aug 24, 2023 at 11:20 AM Carsten Ziegeler wrote: > Hi, > > We solved one issue for healthcheck core: > https://issues.apache.org/jira/browse/FELIX-6565 > > and two issues for healthcheck generalchecks: > https://issues.apache.org/jira/projects/FELIX/versions/12353414 > > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-1469 > > You can use this UNIX script to download the release and verify the > signatures: > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 1469 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > This vote will be open for 72 hours. > > Regards > Carsten > -- > Carsten Ziegeler > Adobe > cziege...@apache.org > -- *Raymond Augé* (@rotty3000) Senior Software Architect *Liferay, Inc.* (@Liferay) OSGi Fellow, Java Champion
[VOTE] Release Healthcheck Core 2.1.0 and Generalchecks 3.0.8
Hi, We solved one issue for healthcheck core: https://issues.apache.org/jira/browse/FELIX-6565 and two issues for healthcheck generalchecks: https://issues.apache.org/jira/projects/FELIX/versions/12353414 Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-1469 You can use this UNIX script to download the release and verify the signatures: https://github.com/apache/felix-dev/blob/master/check_staged_release.sh Usage: sh check_staged_release.sh 1469 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours. Regards Carsten -- Carsten Ziegeler Adobe cziege...@apache.org
[jira] [Updated] (FELIX-6631) Migrate webconsole plugins to jakarta.servlet api
[ https://issues.apache.org/jira/browse/FELIX-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-6631: Fix Version/s: healthcheck.webconsole 2.2.0 > Migrate webconsole plugins to jakarta.servlet api > - > > Key: FELIX-6631 > URL: https://issues.apache.org/jira/browse/FELIX-6631 > Project: Felix > Issue Type: New Feature > Components: Web Console >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: webconsole-packageadmin-plugin 1.0.6, > webconsole-gogo-plugin-1.0.0, webconsole-event-plugin-1.2.0, > webconsole-memoryusage-plugin-1.0.12, webconsole-ds-plugin-2.3.0, > webconsole-obr-plugin-1.0.6, healthcheck.webconsole 2.2.0 > > > With FELIX-6626, the web console supports plugins leveraging the > jakarta.servlet api (in addition to the javax.servlet.api). > With this in place we can now migrate the web console plugins -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Release Apache Felix Http Jetty 5.1.0, Http Bridge 5.1.0, Http Base 5.1.0 and Http Wrappers 1.0.0
+1 On Thu, Aug 24, 2023 at 9:09 AM Thomas Watson wrote: > +1 > Tom > > On Thu, Aug 24, 2023 at 12:32 AM Carsten Ziegeler > wrote: > > > Hi, > > > > We solved one issue in these releases: > > https://issues.apache.org/jira/browse/FELIX-6632 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachefelix-1468 > > > > You can use this UNIX script to download the release and verify the > > signatures: > > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh > > > > Usage: > > sh check_staged_release.sh 1468 /tmp/felix-staging > > > > Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] -1 Veto the release (please provide specific comments) > > > > This vote will be open for 72 hours. > > > > Regards > > Carsten > > -- > > Carsten Ziegeler > > Adobe > > cziege...@apache.org > > > -- *Raymond Augé* (@rotty3000) Senior Software Architect *Liferay, Inc.* (@Liferay) OSGi Fellow, Java Champion
Re: [VOTE] Release Apache Felix Http Jetty 5.1.0, Http Bridge 5.1.0, Http Base 5.1.0 and Http Wrappers 1.0.0
+1 Tom On Thu, Aug 24, 2023 at 12:32 AM Carsten Ziegeler wrote: > Hi, > > We solved one issue in these releases: > https://issues.apache.org/jira/browse/FELIX-6632 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-1468 > > You can use this UNIX script to download the release and verify the > signatures: > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 1468 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > This vote will be open for 72 hours. > > Regards > Carsten > -- > Carsten Ziegeler > Adobe > cziege...@apache.org >
[jira] [Resolved] (FELIX-6635) Remove dependency to HttpService
[ https://issues.apache.org/jira/browse/FELIX-6635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6635. - Resolution: Fixed https://github.com/apache/felix-dev/commit/866c7e7bb0f50719916b6c42a3c0be65ac96a1b5 > Remove dependency to HttpService > > > Key: FELIX-6635 > URL: https://issues.apache.org/jira/browse/FELIX-6635 > Project: Felix > Issue Type: Improvement > Components: Health Checks >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: healthcheck.generalchecks 3.0.8 > > > The generalchecks have an unnecessary dependency to the outdated HttpService. > We should remove this -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6635) Remove dependency to HttpService
Carsten Ziegeler created FELIX-6635: --- Summary: Remove dependency to HttpService Key: FELIX-6635 URL: https://issues.apache.org/jira/browse/FELIX-6635 Project: Felix Issue Type: Improvement Components: Health Checks Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: healthcheck.generalchecks 3.0.8 The generalchecks have an unnecessary dependency to the outdated HttpService. We should remove this -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FELIX-6612) Upgrade Apache Felix to Jakarta Servlet API 6.x
[
https://issues.apache.org/jira/browse/FELIX-6612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17758389#comment-17758389
]
Carsten Ziegeler commented on FELIX-6612:
-
[~mattrpav] The best place for questions is our dev mailing list
(dev@felix.apache.org).
There is already a Jakarta based release of Felix Jetty, latest one is 5.0.6
> Upgrade Apache Felix to Jakarta Servlet API 6.x
> ---
>
> Key: FELIX-6612
> URL: https://issues.apache.org/jira/browse/FELIX-6612
> Project: Felix
> Issue Type: New Feature
> Components: Health Checks, HTTP Service, Inventory, iPOJO, JAAS,
> System Ready, Web Console
>Reporter: Michael H. Siemaszko
>Assignee: Michael H. Siemaszko
>Priority: Major
> Attachments: Upgrade Apache Felix to Jakarta Servlet API
> 6.x.20230713.pdf, Upgrade Apache Felix to Jakarta Servlet API
> 6.x.20230731.pdf, Upgrade Apache Felix to Jakarta Servlet API 6.x.pdf
>
>
> Goal is to upgrade all relevant Apache Felix modules, which currently are
> using either +Jakarta Servlet API 5.x+ or J{+}ava Servlet{+}, to {+}Jakarta
> Servlet API 6.x{+}.
> Attached Mikado graph ({color:#80}+[https://mikadomethod.info/]+{color})
> has all so far identified prerequisites listed, as well as progress on path
> to main goal – i.e. items already completed are checked off
> ({*}{color:#57d9a3}green icon{color}{*}). Code is shared via
> [https://github.com/DataInMotion/felix-dev/tree/jakarta-servlet-6-x] (no pull
> request for now – please see sections ‘Questions’ and ‘Next steps’ below).
> Before starting, I asked on Apache Felix Users list
> ({color:#80}+[https://www.mail-archive.com/users@felix.apache.org/msg18693.html]+{color}),
> as well as researched if there is any ongoing effort to upgrade Apache Felix
> to Jakarta Servlet 6.x (issues / pull requests, etc.). Besides
> {color:#80}+https://issues.apache.org/jira/browse/FELIX-6389+{color},
> which resembles this effort, I did not find anything. However, that issue is
> open since 22/02/2021 and there has been no updates since 09/01/2022, as well
> as no code shared as part of it. If any progress was made as part of
> {color:#80}+https://issues.apache.org/jira/browse/FELIX-6389+{color},
> kindly please provide status update and perhaps these efforts can be merged.
> h1. Modules affected
> Modules with dependency on Java Servlet or Jakarta Servlet.
> h2. org.apache.felix.http
> * org.apache.felix.http.parent
> * org.apache.felix.http.base
> * org.apache.felix.http.bridge
> * org.apache.felix.http.inventoryprinter
> * org.apache.felix.http.itest
> * org.apache.felix.http.jetty
> * org.apache.felix.http.proxy
> * org.apache.felix.http.samples.whiteboard
> * org.apache.felix.http.servlet-api
> * org.apache.felix.http.sslfilter
> * org.apache.felix.http.webconsoleplugin
> h2. org.apache.felix.webconsole
> * org.apache.felix.webconsole
> * org.apache.felix.webconsole.plugins.deppack
> * org.apache.felix.webconsole.plugins.ds
> * org.apache.felix.webconsole.plugins.event
> * org.apache.felix.webconsole.plugins.gogo
> * org.apache.felix.webconsole.plugins.memoryusage
> * org.apache.felix.webconsole.plugins.metatype
> * org.apache.felix.webconsole.plugins.obr
> * org.apache.felix.webconsole.plugins.packageadmin
> * org.apache.felix.webconsole.plugins.scriptconsole
> * org.apache.felix.webconsole.plugins.shell
> * org.apache.felix.webconsole.plugins.subsystems
> * org.apache.felix.webconsole.plugins.upnp
> * org.apache.felix.webconsole.plugins.useradmin
> h2. org.apache.felix.healthcheck
> * org.apache.felix.healthcheck.core
> * org.apache.felix.healthcheck.webconsoleplugin
> h2. Other
> * org.apache.felix.jaas
> * org.apache.felix.example.jaas.app
> * org.apache.felix.example.jaas.jdbc-h2
> * org.apache.felix.ipojo.webconsole
> * org.apache.felix.systemready
> * org.apache.felix.servicediagnostics.plugin
> * org.apache.felix.inventory
> h1. Questions
> 1. Regarding modules affected, are there any additional modules which should
> be taken into account?
> 2. Regarding modules affected, should any of the modules listed be dropped
> from that list ? (e.g. some may be out of date / replaced by other already)
> 3. Do you know of any ongoing effort to migrate `org.osgi.service.http`
> specification to Jakarta ? How otherwise should modules currently using
> `org.osgi.service.http` specification API classes and methods be refactored ?
> I am aware of
> {color:#80}+[https://github.com/eclipse-equinox/equinox/issues/183]+{color}
> but it is not clear to me from that discussion if any such effort will be
> actually made.
> 4. Do you know of any ongoing effort to upgrade `org.osgi.service.servlet` to
> support Jakarta Servlet API 6.x ?
> 5. If `javax.servlet` dependency is removed
The road from Servlet API 3 to Servlet API 6
Hi some of our released modules are still based on Servlet API 3. Starting with version 5 of the Servlet API, the packages have been renamed from javax.servlet to jakarta.servlet and with version 6 of the API, deprecated methods have been removed. This means that a module compiled for Servlet API 3 does not run ootb with Servlet API 5. And a module compiled for Servlet API 5 might not run ootb with Servlet API 6. For users of our modules we have to provide a way forward to allow them to leverage newer Servlet API versions - but without loosing our user base or making it unnecessarily hard for them. We have a large user base out there which is still on Servlet API 3. This is how I think a path forward can look like: For our http server implementation (http jetty and http bridge), we have the 4.x branch - it supports Servlet API 3, OSGi HTTP Service and OSGi HTTP Whiteboard 1.x. We'll continue to provide fixes for this branch. However this branch is based on Eclipse Jetty 9.4 and the Jetty project recommends to update to newer Jetty versions. For users who want to leverage Servlet API, we have http jetty and http bridge 5.x on our main branch. This is based on Jetty 11. Our implementation on the main branch supports Servlet API 3, Servlet API 5, OSGi HTTP Service and OSGi HTTP Whiteboard 1.x and 2.x. This allows our users to run modules using older servlet APIs with modules using newer Servlet APIs in parallel - without a need to migrate their code. We should encourage our users to move to this version - which should be a drop-in replacement for most users. Only users who also leverage Jetty API of 9.x might need to update their code to Jetty API 11.x. Most of the other modules in Apache Felix around servlets are the webconsole and various webconsole plugins. Currently the webconsole uses Servlet API 3 and the OSGi HTTP Service. With the next release of the webconsole, we will move to the OSGi HTTP Whiteboard 1.x away from the outdated OSGi HTTP Service. In addition the webconsole will optionally support *plugins* using the Servlet API 5. This gives a migration path for all plugins while still allowing all of this to run in a Servlet API 3 container. With that in place, we can migrate our webconsole plugins to Servlet API 5. And we already started with this in our code base. Once we have all plugins migrated, we can switch the webconsole to be based on Servlet API 5, OSGi HTTP Whiteboard 2.x and then optionally support plugins using Servlet API 3. With that all our code should be on Servlet API 5 - but all existing plugins regardless if they use Servlet API 3 or 5 should still work in the webconsole. The final piece is Servlet API 6 - I think for the webconsole and the plugins, we can make them work with Servlet API 5 and Servlet API 6 by basing them on Servlet API 5 and avoiding the removed methods. This way we don't need to maintain any branches for all of that code. But for the http server implementations (http base and http jetty) this is not possible. We already have a branch for those leveraging Jetty 12 which supports Servlet API 6. However, this version does not support any earlier Servlet API. While it is good to get this work started, I think the first hill we have to climb is to get all our code to use Servlet API 5 and take our users with us. Once we are there we can look down on the road ahead to Servlet API 6 as we will have a much clearer view by then. Regards Carsten -- Carsten Ziegeler Adobe cziege...@apache.org
