Do not release OSGi HttpService

[lolodomo]

Related to openhab/openhab-core#4140

Signed-off-by: Laurent Garnier lg.hc@free.fr

[lolodomo]

Here are the DEBUG logs at startup:

15:04:14.402 [INFO ] [rg.jupnp.OSGiUpnpServiceConfiguration] - OSGiUpnpServiceConfiguration createConfiguration threadPoolSize = 15 true
15:04:14.409 [INFO ] [rg.jupnp.OSGiUpnpServiceConfiguration] - OSGiUpnpServiceConfiguration createConfiguration asyncThreadPoolSize = 30 true
15:04:14.416 [INFO ] [rg.jupnp.OSGiUpnpServiceConfiguration] - OSGiUpnpServiceConfiguration retryAfterSeconds = 600
15:04:14.424 [INFO ] [rg.jupnp.OSGiUpnpServiceConfiguration] - OSGiUpnpServiceConfiguration retryIterations = 5
15:04:14.430 [INFO ] [rg.jupnp.OSGiUpnpServiceConfiguration] - OSGiUpnpServiceConfiguration timeoutSeconds = 10
15:04:14.437 [DEBUG] [rg.jupnp.OSGiUpnpServiceConfiguration] - Creating mainThreadPool
15:04:14.449 [DEBUG] [rg.jupnp.OSGiUpnpServiceConfiguration] - Creating asyncThreadPool
15:04:14.456 [DEBUG] [rg.jupnp.OSGiUpnpServiceConfiguration] - Creating remoteThreadPool
15:04:14.579 [DEBUG] [rg.jupnp.OSGiUpnpServiceConfiguration] - org.openhab.core.config.jupnp.internal.OHUpnpServiceConfiguration@1878cb9 activated

15:04:14.733 [INFO ] [org.jupnp.UpnpServiceImpl            ] - Starting UPnP service...
15:04:14.739 [DEBUG] [org.jupnp.UpnpServiceImpl            ] - Using OSGi HttpService; using configuration: org.openhab.core.config.jupnp.internal.OHUpnpServiceConfiguration
15:04:14.823 [DEBUG] [rg.jupnp.OSGiUpnpServiceConfiguration] - createStreamServer using OSGi HttpService
15:04:14.876 [DEBUG] [rg.jupnp.OSGiUpnpServiceConfiguration] - createStreamServer using OSGi HttpService
15:04:14.904 [DEBUG] [org.jupnp.UpnpServiceImpl            ] - UPnP service started successfully

[wborn]

Thanks for investigating the issue @lolodomo!

[lolodomo]

@wborn : I am preparing a PR in openhab.core to switch to release 3.0.1.

[wborn]

Thanks for the fix!

[lolodomo]

@wborn: to you know the process to release a new version ? ;)

[wborn]

to you know the process to release a new version ? ;)

I know the process but only @kaikreuzer can do it. 😉
Would also be nice when the new release contains #229.

[kaikreuzer]

New version is published.

but only @kaikreuzer can do it. 😉

We should change that. Not sure how we get you the rights to push to Maven Central for the org, but according to https://central.sonatype.org/faq/what-happened-to-issues-sonatype-org/#i-used-to-registerudate-my-ossrh-account-at-issuessonatypeorg-what-do-i-do-now it sounds as if I have to send an email to Sonatype. Can you give me your OSSRH id for that?

[wborn]

Thanks for making the release. 👍

it sounds as if I have to send an email to Sonatype. Can you give me your OSSRH id for that?

I don't have a personal OSSRH account yet. It also seems that OSSRH is considered legacy nowadays because Maven Central has a new publishing mechanism. I do have a personal Maven Central account with a few verified namespaces. So I mailed them if it is required for me to also get a legacy OSSRH account or if the org.jupnp namespace can also be added to my existing Maven Central account.

[wborn]

I just got this reply from central-support@sonatype.com :

To grant you permissions to org.jupnp, I would need to get a request from someone with publishing access to that namespace.

Accounts on central.sonatype.com can be used to publish on OSSRH, provided they are username/password accounts. You cannot publish a namespace on both systems however, it's one or the other.

My central.sonatype.com account has wborn as username. It's username/password based and not using a social login. Do you also have a central.sonatype.com account?